Your message dated Tue, 27 Oct 2026 10:20:27 +0000
with message-id <[email protected]>
and subject line Re: Bug#1151767: nc-py-api: FTBFS: ImportError: cannot import 
name 'ArgsKwargs' from 'pydantic_core._pydantic_core' (unknown location)
has caused the Debian Bug report #1151767,
regarding nc-py-api: FTBFS: ImportError: cannot import name 'ArgsKwargs' from 
'pydantic_core._pydantic_core' (unknown location)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1151767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151767
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:nc-py-api
Version: 0.19.2-1
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202610/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:nc-py-api, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
    from pydantic_core import __version__ as __pydantic_core_version__
  File "/usr/lib/python3/dist-packages/pydantic_core/__init__.py", line 8, in 
<module>
    from ._pydantic_core import (
    ...<21 lines>...
    )
ImportError: cannot import name 'ArgsKwargs' from 
'pydantic_core._pydantic_core' (unknown location)


----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.15_nextcloud-api/build; python3.15 -m 
unittest discover -v 
W: pybuild base:326: No test runner selected, defaulting to unittest, ignoring 
test discovery problems.
Use --test-unittest to explicitly select the unittest runner.
I: pybuild base:383: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_nextcloud-api/build; python3.14 -m 
unittest discover -v 

----------------------------------------------------------------------
Ran 0 tests in 0.000s

NO TESTS RAN
        rm -fr -- /tmp/dh-xdg-rundir-ZJNgQdJL
dh_auto_test: error: pybuild --test -i python{version} -p "3.15 3.14" 
--parallel=2 returned exit code 13
make: *** [debian/rules:11: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
On Fri, Oct 23, 2026 at 04:27:00PM +0000, Santiago Vila wrote:
   from pydantic_core import __version__ as __pydantic_core_version__
 File "/usr/lib/python3/dist-packages/pydantic_core/__init__.py", line 8, in 
<module>
   from ._pydantic_core import (
   ...<21 lines>...
   )
ImportError: cannot import name 'ArgsKwargs' from 
'pydantic_core._pydantic_core' (unknown location)

This was a temporary problem, fixed by rebuilding pydantic-core against Python 3.15. I've confirmed that nc-py-api builds again now.

--
Colin Watson (he/him)                              [[email protected]]

--- End Message ---

Reply via email to