Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco
Hi Chris, * Chris Knadle [2024-01-02 03:06]: Can the poco library be updated? Can I help in some way? poco is basically orphaned, as I dropped myself from Uploaders in git and did not hear from the other maintainers for some time. The best way to help is to step up as a maintainer and update it ;). Unless the Poco library can be updated the only way to save Mumble will be to introduce an epoch in the package version to upload the now well outdated mumble 1.3.4 again which upstream cannot support anymore. Nit: please don't use epochs for that, also see Policy 5.6.12.1. Cheers Jochen signature.asc Description: PGP signature
Bug#1058083: Before I try to tackle this bug - can we move the package to DPT
Ping? If I do not hear from you in the next couple of days I'll move the package to DPT at beginning of next week. Kind regards Andreas. Am Mon, Dec 25, 2023 at 08:34:58AM +0100 schrieb Andreas Tille: > Hi Agustin and Ulises, > > I noticed there were several NMUs not commited to the Git repository of > this package. I'd volunteer to bring the repository in sync with latest > uploads and move it to Debian Python Team before I try to tacke bug > #1058083. > > Kind regards > Andreas. > > -- > http://fam-tille.de -- http://fam-tille.de
Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Hello Julian,
Am 03.01.24 um 22:22 schrieb Julian Gilbey:
Just to throw in: these werkzeug failures are also causing a similar
FTBFS in debugpy; I've temporarily addressed it by skipping these unit
tests, but that's not a great solution.
I just took a quick look at upgrading the unstable/testing version of
werkzeug to 2.3.8 in the meantime. It was pretty quick, and the
package tests all pass. Shall I upload it to unstable?
in the end it's up to you. I personally still see no real gain in doing
such a version bump if we could spend the same time on fixing issues we
currently see for Flask/Werkzeug >= 3.x given that we need to migrate
any way in a not to far future. Why spend now time on things that could
happen already within the past 6 months? What do we really gain?
And, in case you decide to upload Werkzeug 2.3.8, my guess is you will
see almost the same fallout as that is still visible for the both
packages with the version bump to 3.x in experimental. With one
exception, it will produce pressure to fix out the issues we seen until
now even more.
I worked on a lot of packages that had FTBFS or test suite issues in the
past 2-3 weeks, the current queue of outstanding packages for
Flask/Werkzeug 3.x is down to 5 packages.
I've seen other Python team members who did also some upload to fix
packages, thank you all for working on that.
https://qa.debian.org/excuses.php?experimental=1=python-werkzeug
https://qa.debian.org/excuses.php?experimental=1=flask
flask-dance (python-werkzeug)
I've done several attempts to get it build with the newer versions, it's
tricky and in my opinion the upstream package isn't really ready for the
newer versions.
Would need open a upstream issue about the problems to get that addressed.
onionshare (python-werkzueg)
Did not look that much yet into the culprit, might be easy to fix.
https://github.com/onionshare/onionshare/pull/1677
It's tiring to work on a active upstream project that did the last
version update now more than one year ago.
beets (flask)
Fixed locally, waiting on response from Stefano due missing commits in
the Salsa tree.
flask-dance (flask)
Same as above.
flask-socketio (flask)
Might be fixed by a newer upstream version, I opened a wishlist bug
about updating (http://bugs.debian.org/1059538). Maybe someone can cross
check?
ironic-inspector (flask)
Did not look deep into that yet. Might be fixed by a newer available
upstream version. The package currently is marked for auto removal on
25th January, I guess Thomas Goirand is happily taking any help on this
package.
(Incidentally, while doing this, I spotted one bug with the current
experimental version: it is missing a Build-Depends on
python3-markupsafe.)
The only requirement for Markupsafe in Flask 3.0.0 is listed in
requirements/tests-pallets-min{.*}.
The build of src:flask is depending on python3-werkzeug >= 3.x, which
has itself a dependency on python3-markupsafe, so if you spot a missing
direct dependency I'm interested how this comes to play as Markupsafe
should be around at build time.
--
Regards
Carsten
Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Hello Gregor, Am 22.12.23 um 00:04 schrieb Gregor Riepl: My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for release, it should be enough to upgrade to 2.3.5 to address these unit test failures. I did come to the conclusion that Werkzeug 2.3.x has some bigger changes that will break most of the existing packages in some way. The main differences to Werkzeug 3.x than isn't that big. flask-login got recent updates which so far I've seen will fix these issues in the test suite. So if you want to push things further try to update/patch flask-login to a recent version targeting experimental. Just rebuilding flask-login against the version of python3-werkzeug in experimental will not fix the problems, so also not an intermediate update to 2.3.5, Python 3.12 is now very strict about deprecation warnings. That doesn't make any sense to me. These deprecations are obviously in werkzeug and not flask-login. Why would changes in flask-login fix them? Because a updated flask-login and other (updated) packages have also underlying changes that require than a updated package of Werkzeug. And some upstream projects did change their source in a way so they can deal different versions of Werkzeug. So a usual update is magical fixing build issues we did have in older versions against recent Flask/Werkzeug versions. I was able to fix not all of the current fallout, but quite a few of them. -- Regards Carsten
Bug#1054943: marked as done (haskell-yesod-bin: FTBFS: unsatisfiable build-dependency: libghc-fsnotify-dev (< 0.4) but 0.4.1.0-1+b1 is to be installed)
Your message dated Thu, 04 Jan 2024 05:19:07 + with message-id and subject line Bug#1054943: fixed in haskell-yesod-bin 1.6.2.2-2 has caused the Debian Bug report #1054943, regarding haskell-yesod-bin: FTBFS: unsatisfiable build-dependency: libghc-fsnotify-dev (< 0.4) but 0.4.1.0-1+b1 is to be installed 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 ow...@bugs.debian.org immediately.) -- 1054943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-yesod-bin Version: 1.6.2.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: haskell-devscripts (>= 0.13), cdbs, debhelper (>= 10), > ghc, libghc-aeson-dev, libghc-conduit-dev (>= 1.3), libghc-conduit-extra-dev > (>= 1.3), libghc-data-default-class-dev, libghc-file-embed-dev, > libghc-fsnotify-dev (>= 0.0), libghc-fsnotify-dev (<< 0.4), > libghc-http-client-dev (>= 0.4.7), libghc-http-client-tls-dev, > libghc-http-reverse-proxy-dev (>= 0.4), libghc-http-types-dev (>= 0.7), > libghc-network-dev (>= 2.5), libghc-optparse-applicative-dev (>= 0.11), > libghc-project-template-dev (>= 0.1.1), libghc-say-dev, libghc-split-dev (>= > 0.2), libghc-split-dev (<< 0.3), libghc-streaming-commons-dev, libghc-tar-dev > (<< 0.6), libghc-tar-dev (>= 0.4), libghc-transformers-compat-dev, > libghc-unliftio-dev, libghc-unordered-containers-dev, libghc-wai-dev (>= > 2.0), libghc-wai-extra-dev, libghc-warp-dev (>= 1.3.7.5), libghc-warp-tls-dev > (>= 3.0.1), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), > libghc-zlib-dev (>= 0.5), build-essential, fakeroot > Filtered Build-Depends: haskell-devscripts (>= 0.13), cdbs, debhelper (>= > 10), ghc, libghc-aeson-dev, libghc-conduit-dev (>= 1.3), > libghc-conduit-extra-dev (>= 1.3), libghc-data-default-class-dev, > libghc-file-embed-dev, libghc-fsnotify-dev (>= 0.0), libghc-fsnotify-dev (<< > 0.4), libghc-http-client-dev (>= 0.4.7), libghc-http-client-tls-dev, > libghc-http-reverse-proxy-dev (>= 0.4), libghc-http-types-dev (>= 0.7), > libghc-network-dev (>= 2.5), libghc-optparse-applicative-dev (>= 0.11), > libghc-project-template-dev (>= 0.1.1), libghc-say-dev, libghc-split-dev (>= > 0.2), libghc-split-dev (<< 0.3), libghc-streaming-commons-dev, libghc-tar-dev > (<< 0.6), libghc-tar-dev (>= 0.4), libghc-transformers-compat-dev, > libghc-unliftio-dev, libghc-unordered-containers-dev, libghc-wai-dev (>= > 2.0), libghc-wai-extra-dev, libghc-warp-dev (>= 1.3.7.5), libghc-warp-tls-dev > (>= 3.0.1), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), > libghc-zlib-dev (>= 0.5), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1522 B] > Get:5 copy:/<>/apt_archive ./ Packages [1552 B] > Fetched 3689 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libghc-fsnotify-dev (< 0.4) but > 0.4.1.0-1+b1 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/28/haskell-yesod-bin_1.6.2.2-1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1056471: python-fabio: debdiff with patch from upstream recommendation
Source: python-fabio
Version: 2023.6.0-3
Followup-For: Bug #1056471
X-Debbugs-Cc: kd8...@gmail.com
Hi,
I went ahead and created a patch following the upstream author's advice.
I've attached the debdiff for you to check out.
Cheers!
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.1.0-17-arm64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
fabio-debdiff content:
diff -Nru python-fabio-2023.6.0/debian/changelog
python-fabio-2023.6.0/debian/changelog
--- python-fabio-2023.6.0/debian/changelog 2023-07-22 11:07:18.0
+
+++ python-fabio-2023.6.0/debian/changelog 2024-01-04 02:28:15.0
+
@@ -1,3 +1,10 @@
+python-fabio (2023.6.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Bug fix for autopkg tests fail with Python 3.12 (Closes: #1056471).
+
+ -- Yogeswaran Umasankar Thu, 04 Jan 2024 02:28:15 +
+
python-fabio (2023.6.0-3) unstable; urgency=medium
* Bug fix: "undeclared file conflict between fabio-viewer and
diff -Nru python-fabio-2023.6.0/debian/patches/0004-autopkgtest-py312.patch
python-fabio-2023.6.0/debian/patch>
--- python-fabio-2023.6.0/debian/patches/0004-autopkgtest-py312.patch
1970-01-01 00:00:00.0 +
+++ python-fabio-2023.6.0/debian/patches/0004-autopkgtest-py312.patch
2024-01-04 02:28:15.0 +
@@ -0,0 +1,24 @@
+From fb4a48b77c6130f4f9f9e626d84cbb5f3abac20b Mon Sep 17 00:00:00 2001
+From: Jerome Kieffer
+Date: Mon, 11 Dec 2023 09:57:06 +0100
+Subject: [PATCH] Update ExternalResources.py
+
+close #549
+---
+ src/fabio/utils/ExternalResources.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/src/fabio/utils/ExternalResources.py
b/src/fabio/utils/ExternalResources.py
+index 58a7bfe51..4d9d9e3bb 100644
+--- a/src/fabio/utils/ExternalResources.py
b/src/fabio/utils/ExternalResources.py
+@@ -289,7 +289,8 @@ def get_file_and_repack(self, filename):
+
+ if not gz_file_exists:
+ try:
+-gzip.open(fullimagename_gz, "wb").write(decompressed)
++with gzip.open(fullimagename_gz, "wb") as g:
++g.write(decompressed)
+ except IOError:
+ raise IOError("unable to write gzipped \
+ data to disk at %s" % self.data_home)
diff -Nru python-fabio-2023.6.0/debian/patches/series
python-fabio-2023.6.0/debian/patches/series
--- python-fabio-2023.6.0/debian/patches/series 2023-07-22 11:07:18.0
+
+++ python-fabio-2023.6.0/debian/patches/series 2024-01-04 02:28:15.0
+
@@ -1,2 +1,3 @@
0002-reproducible-build.patch
0003-use-the-system-mathjax.patch
+0004-autopkgtest-py312.patch
Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco
All recent versions of Mumble now require Poco to build and will not build without it. Unless the Poco library can be updated the only way to save Mumble will be to introduce an epoch in the package version to upload the now well outdated mumble 1.3.4 again which upstream cannot support anymore. Can the poco library be updated? Can I help in some way? -- Chris Knadle chris.kna...@coredump.us
Bug#1054973: marked as done (libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 04 Jan 2024 00:19:50 + with message-id and subject line Bug#1054973: fixed in libcgi-application-plugin-authentication-perl 0.23+~cs0.5-3 has caused the Debian Bug report #1054973, regarding libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 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 ow...@bugs.debian.org immediately.) -- 1054973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcgi-application-plugin-authentication-perl Version: 0.23+~cs0.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/driver-dbic' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, '../blib/lib', > '../blib/arch')" t/*.t > t/00-signature.t skipped: Set the environment variable > TEST_SIGNATURE to enable this test. > # Testing CGI::Application::Plugin::Authentication::Driver::DBIC 0.02, Perl > 5.036000, /usr/bin/perl > t/01-load.t . > 1..1 > ok 1 - use CGI::Application::Plugin::Authentication::Driver::DBIC; > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate.t > 1..8 > ok 1 - missing credentials - login failure > ok 2 - missing credentials - username not set > ok 3 - successful login > ok 4 - successful login - username set > ok 5 - successful login - failed login count > ok 6 - login failure > ok 7 - login failure - username not set > ok 8 - login failure - failed login count > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate_crypt.t .. > 1..3 > ok 1 - successful login crypt > ok 2 - successful login crypt - username set > ok 3 - successful login crypt - failed login count > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate_md5.t > 1..3 > ok 1 - successful login MD5 > ok 2 - successful login MD5 - username set > ok 3 - successful login MD5 - failed login count > ok > t/pod-coverage.t skipped: Test::Pod::Coverage 1.04 required for > testing POD coverage > t/pod.t . skipped: Test::Pod 1.14 required for testing POD > All tests successful. > Files=7, Tests=15, 1 wallclock secs ( 0.02 usr 0.02 sys + 0.97 cusr 0.20 > csys = 1.21 CPU) > Result: PASS > make[3]: Leaving directory '/<>/driver-dbic' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/01_basic.t > 1..9 > ok 1 - require CGI::Application::Plugin::Authentication; > ok 2 - warning when the plugin is used in a non-CGIApp module > ok 3 - instance dies when called passed non CGI::App module > ok 4 - ->authen called as a class method works > ok 5 - An object of class 'CGI::Application::Plugin::Authentication' isa > 'CGI::Application::Plugin::Authentication' > ok 6 - An object of class 'CGI::Application::Plugin::Authentication' isa > 'CGI::Application::Plugin::Authentication' > ok 7 - Objects have same different address > ok 8 - Objects have same address > ok 9 - instance dies when called incorrectly > ok > t/02_config.t ... > 1..69 > ok 1 - All config parameters accepted > ok 2 - credentials set > ok 3 - An object of class > 'CGI::Application::Plugin::Authentication::Driver::Generic' isa > 'CGI::Application::Plugin::Authentication::Driver::Generic' > ok 4 - An object of class 'Store::Dummy' isa 'Store::Dummy' > ok 5 - All config parameters accepted > ok 6 - config dies when DRIVER is passed a hashref > ok 7 - config accepts single DRIVER without options > ok 8 - config accepts single DRIVER with options > ok 9 - config accepts multiple DRIVERs > ok 10 - config dies when STORE is passed a hashref > ok 11 - config accepts STORE without options > ok
Bug#1054973: marked as done (libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 04 Jan 2024 00:04:07 + with message-id and subject line Bug#1054973: fixed in libcgi-application-plugin-authentication-perl 0.23+~cs0.5-2.1 has caused the Debian Bug report #1054973, regarding libcgi-application-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 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 ow...@bugs.debian.org immediately.) -- 1054973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcgi-application-plugin-authentication-perl Version: 0.23+~cs0.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/driver-dbic' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, '../blib/lib', > '../blib/arch')" t/*.t > t/00-signature.t skipped: Set the environment variable > TEST_SIGNATURE to enable this test. > # Testing CGI::Application::Plugin::Authentication::Driver::DBIC 0.02, Perl > 5.036000, /usr/bin/perl > t/01-load.t . > 1..1 > ok 1 - use CGI::Application::Plugin::Authentication::Driver::DBIC; > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate.t > 1..8 > ok 1 - missing credentials - login failure > ok 2 - missing credentials - username not set > ok 3 - successful login > ok 4 - successful login - username set > ok 5 - successful login - failed login count > ok 6 - login failure > ok 7 - login failure - username not set > ok 8 - login failure - failed login count > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate_crypt.t .. > 1..3 > ok 1 - successful login crypt > ok 2 - successful login crypt - username set > ok 3 - successful login crypt - failed login count > ok > DBIx::Class::ResultSet::search_rs(): search( %condition ) is deprecated, use > search( \%condition ) instead at > /<>/driver-dbic/../blib/lib/CGI/Application/Plugin/Authentication/Driver/DBIC.pm > line 121 > t/authenticate_md5.t > 1..3 > ok 1 - successful login MD5 > ok 2 - successful login MD5 - username set > ok 3 - successful login MD5 - failed login count > ok > t/pod-coverage.t skipped: Test::Pod::Coverage 1.04 required for > testing POD coverage > t/pod.t . skipped: Test::Pod 1.14 required for testing POD > All tests successful. > Files=7, Tests=15, 1 wallclock secs ( 0.02 usr 0.02 sys + 0.97 cusr 0.20 > csys = 1.21 CPU) > Result: PASS > make[3]: Leaving directory '/<>/driver-dbic' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/01_basic.t > 1..9 > ok 1 - require CGI::Application::Plugin::Authentication; > ok 2 - warning when the plugin is used in a non-CGIApp module > ok 3 - instance dies when called passed non CGI::App module > ok 4 - ->authen called as a class method works > ok 5 - An object of class 'CGI::Application::Plugin::Authentication' isa > 'CGI::Application::Plugin::Authentication' > ok 6 - An object of class 'CGI::Application::Plugin::Authentication' isa > 'CGI::Application::Plugin::Authentication' > ok 7 - Objects have same different address > ok 8 - Objects have same address > ok 9 - instance dies when called incorrectly > ok > t/02_config.t ... > 1..69 > ok 1 - All config parameters accepted > ok 2 - credentials set > ok 3 - An object of class > 'CGI::Application::Plugin::Authentication::Driver::Generic' isa > 'CGI::Application::Plugin::Authentication::Driver::Generic' > ok 4 - An object of class 'Store::Dummy' isa 'Store::Dummy' > ok 5 - All config parameters accepted > ok 6 - config dies when DRIVER is passed a hashref > ok 7 - config accepts single DRIVER without options > ok 8 - config accepts single DRIVER with options > ok 9 - config accepts multiple DRIVERs > ok 10 - config dies when STORE is passed a hashref > ok 11 - config accepts STORE without options >
Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)
I disabled that the upstream changelog file is distributed in the debian package. The spread-sheet-widget provides two binary packages libspread-sheet-widget and libspread-sheet-widget-dev and both usually have the same changelog.gz which is derived from ChangeLog in the source directory. I noticed the 1970 date when I build this via pbuilder but the date was correct when I build via „debuild“. So I guess this might be a bug in the dh_installchangelog module. For now I just removed the upstream changelog. Thank you for your help!
Bug#1056891: Severity / marking of "uses cython3-legacy" bugs
Hi Rebecca (2024.01.03_21:27:49_+) > pandas and statsmodels are currently using cython3-legacy. I left their > cython 3.0 bugs open when I made this change, as I do want to actually > switch them to cython 3.x at some point. > > These bugs have now been raised to RC. Is this an intentional attempt to > remove cython3-legacy (which seems unlikely as there is no such bug on > cython3-legacy itself), or have they been mistaken for packages that still > depend on plain cython3 but don't build with cython3 3.x (which would be an > active FTBFS and hence RC)? > > If the second, how should such bugs be marked to make them less confusing? > Is removing the usertag enough? I didn't review the bugs when I raised the severity, I just took everything that was usertagged. Sorry! I'd suggest lowering the severity again. You could add a separate usertag for using cython3-legacy, but we can also see that pretty easily by looking at reverse-depends. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1059913: marked as done (setuptools-scm fails it's autopkg tests)
Your message dated Wed, 03 Jan 2024 22:05:57 + with message-id and subject line Bug#1059913: fixed in setuptools-scm 8.0.4-2 has caused the Debian Bug report #1059913, regarding setuptools-scm fails it's autopkg tests 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 ow...@bugs.debian.org immediately.) -- 1059913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:setuptools-scm Version: 8.0.4-1 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 $ apt show python3-setuptools-scm|grep Depends Depends: python3-distutils, python3-pkg-resources, python3-packaging, python3-tomli | python3-supported-min (>= 3.11), python3-typing-extensions, python3:any I assume that needs python3-setuptools as a dependency now, python3-distutils doesn't exist anymore for python3.12. from https://ci.debian.net/data/autopkgtest/testing/amd64/s/setuptools-scm/41418646/log.gz [...] 70s autopkgtest [13:24:48]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import setuptools_scm; print(setuptools_scm)" ; done 70s autopkgtest [13:24:48]: test autodep8-python3: [--- 70s Testing with python3.11: 70s Traceback (most recent call last): 70s File "", line 1, in 70s File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 7, in 70s from ._config import Configuration 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_config.py", line 15, in 70s from ._integration.pyproject_reading import ( 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py", line 8, in 70s from .setuptools import read_dist_name_from_setup_cfg 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py", line 9, in 70s import setuptools 70s ModuleNotFoundError: No module named 'setuptools' 71s autopkgtest [13:24:49]: test autodep8-python3: ---] --- End Message --- --- Begin Message --- Source: setuptools-scm Source-Version: 8.0.4-2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of setuptools-scm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated setuptools-scm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jan 2024 17:45:29 -0400 Source: setuptools-scm Architecture: source Version: 8.0.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1059913 Changes: setuptools-scm (8.0.4-2) unstable; urgency=medium . * Team upload. * Explicitly depend on python3-setuptools (Closes: #1059913) * Depend on python3-build in the autopkgtest. * Skip test_get_version_blank_tag_regex in the autopkgtest. Checksums-Sha1: 0bfa3dfb7b58e84da800301279a6526f4556ccf5 1740 setuptools-scm_8.0.4-2.dsc b04505e7c259f5babe02cd18a0a5fac7ba7158d5 5840 setuptools-scm_8.0.4-2.debian.tar.xz aa3c282f53fd13eb06609f155864cb97dba3bad0 7403 setuptools-scm_8.0.4-2_source.buildinfo Checksums-Sha256: 6fae8f3af821dd1646c27a424b88edf2aab58103b98173b539272e8d9ac9a66d 1740 setuptools-scm_8.0.4-2.dsc dd05f9d07c6f294f1f367b97bad5709f9dcf6c1b43a0c5e7812bc59fee5aa1df 5840 setuptools-scm_8.0.4-2.debian.tar.xz feea30648198be1f3009254ad56c3f4110f3d61cefd562f7c7a587a4cb20c196 7403 setuptools-scm_8.0.4-2_source.buildinfo Files: deda5e1b39eacdcea39eb71aac9f879c 1740 python optional setuptools-scm_8.0.4-2.dsc d61eddd3f39564c1b0c2099a67992fbe 5840 python optional setuptools-scm_8.0.4-2.debian.tar.xz 9f383b36d852331db0edad900a340347 7403 python optional setuptools-scm_8.0.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZZXVkRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2I/RAQCQ2zOaCXq8kdVY5LR9URxjib4OGBHI yMJJg/In3lWi/gD/XpQUPIbdRJRTAr3cnvTA8jUj3nDPQypi2dDonxUetAI= =ZQ8Y -END PGP
Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)
Your message dated Wed, 03 Jan 2024 22:06:09 + with message-id and subject line Bug#1059923: fixed in spread-sheet-widget 0.10-3 has caused the Debian Bug report #1059923, regarding spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED 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 ow...@bugs.debian.org immediately.) -- 1059923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spread-sheet-widget Version: 0.10-1 Severity: serious On 2024-01-03 17:21, Debian FTP Masters wrote: > > > libspread-sheet-widget-dev_0.10-1_s390x.deb: has 1 file(s) with a timestamp > too far in the past: > usr/share/doc/libspread-sheet-widget-dev/changelog.gz (Thu Jan 1 00:00:00 > 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: spread-sheet-widget Source-Version: 0.10-3 Done: Friedrich Beckmann We believe that the bug you reported is fixed in the latest version of spread-sheet-widget, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Friedrich Beckmann (supplier of updated spread-sheet-widget package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jan 2024 22:39:46 +0100 Source: spread-sheet-widget Binary: libspread-sheet-widget libspread-sheet-widget-dbgsym libspread-sheet-widget-dev Architecture: source amd64 Version: 0.10-3 Distribution: unstable Urgency: medium Maintainer: Friedrich Beckmann Changed-By: Friedrich Beckmann Description: libspread-sheet-widget - shared library for GTK+ to view and manipulate two dimensional ta libspread-sheet-widget-dev - development files for the GTK+ spread sheet widget Closes: 1059923 Changes: spread-sheet-widget (0.10-3) unstable; urgency=medium . * Removed ChangeLog from being distributed (closes: #1059923) Checksums-Sha1: 31568cb4e4e6630de89cccef98771c5521debc6f 2039 spread-sheet-widget_0.10-3.dsc 44fcf1cef9ff5e5aea66a21384f5eeb32740b198 5592 spread-sheet-widget_0.10-3.debian.tar.xz 989203199a18056f19654452d70eba788465a005 159600 libspread-sheet-widget-dbgsym_0.10-3_amd64.deb 562e282336fad7852ffb5c38d2d68f9cfa7e2ae2 54380 libspread-sheet-widget-dev_0.10-3_amd64.deb 4b5338971aac5227dbb2f3e93172a7b6733efb6d 44676 libspread-sheet-widget_0.10-3_amd64.deb ba8027c6538d9646c058475ce06c3b5e47625e8e 14791 spread-sheet-widget_0.10-3_amd64.buildinfo Checksums-Sha256: 7854c59955778facb1fadf5d06d65bc2a0d9e21c6426ebd9955cfa8ad5f4cf3f 2039 spread-sheet-widget_0.10-3.dsc c8b2488ec0ac672830a45910c982c6e5d5d46a72c01cf23b7e15c8165df59566 5592 spread-sheet-widget_0.10-3.debian.tar.xz ddd1b57922bce3bf1a72c8fb8e3cf690d3b75d54320cc23970090dfc451bf590 159600 libspread-sheet-widget-dbgsym_0.10-3_amd64.deb 43520455780c802913c824ee9a35a61250eb28262f1b149a3c41aa97c95faabe 54380 libspread-sheet-widget-dev_0.10-3_amd64.deb 83c20488b926cd77ad894c6e23aa7206c303894137f4a9e6777fc0d463e52225 44676 libspread-sheet-widget_0.10-3_amd64.deb 6590c7acfbcd003f3924f6205bbe668b8e5526b729279aadd6e3f4741d5baccd 14791 spread-sheet-widget_0.10-3_amd64.buildinfo Files: 4f413b0c4d227190cbb9fde22ba0392b 2039 libs optional spread-sheet-widget_0.10-3.dsc 4e9eb31d3aecdd207d479f664eba075b 5592 libs optional spread-sheet-widget_0.10-3.debian.tar.xz b581097c2a3903cf7d3a98ea63a57e83 159600 debug optional libspread-sheet-widget-dbgsym_0.10-3_amd64.deb dd0c1020c0829dcdbdd129de5a19c535 54380 libdevel optional libspread-sheet-widget-dev_0.10-3_amd64.deb 92f0040d6e7f4bc201c86c4f2250df64 44676 libs optional libspread-sheet-widget_0.10-3_amd64.deb 53d6d0847fbdaade9a1d4ef0379dd014 14791 libs optional spread-sheet-widget_0.10-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEGp+TZe9/EUJidSaxzHnYClu3/FEFAmWV1VMACgkQzHnYClu3 /FFxnQgAoNvTn66/WVL2hMeZxrI4CwvgqWC8WtZkq4eHKuErepL76B5I4S7q5mAW 5jPk4lr5VO08GCfZ/XloesMbWPh1hYuZZAJBhchFfnSja1DQ4leARCmNodCdtQ4D
Processed: reopening 1059923
Processing commands for cont...@bugs.debian.org:
> reopen 1059923
Bug #1059923 {Done: Friedrich Beckmann }
[src:spread-sheet-widget] spread-sheet-widget_0.10-1_s390x-buildd.changes
REJECTED
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions spread-sheet-widget/0.10-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1059923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1059913 marked as pending in setuptools-scm
Processing control commands: > tag -1 pending Bug #1059913 [src:setuptools-scm] setuptools-scm fails it's autopkg tests Added tag(s) pending. -- 1059913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059913: marked as pending in setuptools-scm
Control: tag -1 pending Hello, Bug #1059913 in setuptools-scm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/setuptools-scm/-/commit/5dd92fba07814c9fd6c41f911e0bd1ba23828c8e Explicitly depend on python3-setuptools (Closes: #1059913) (this message was generated automatically) -- Greetings https://bugs.debian.org/1059913
Bug#1056828: Severity / marking of "uses cython3-legacy" bugs
pandas and statsmodels are currently using cython3-legacy. I left their cython 3.0 bugs open when I made this change, as I do want to actually switch them to cython 3.x at some point. These bugs have now been raised to RC. Is this an intentional attempt to remove cython3-legacy (which seems unlikely as there is no such bug on cython3-legacy itself), or have they been mistaken for packages that still depend on plain cython3 but don't build with cython3 3.x (which would be an active FTBFS and hence RC)? If the second, how should such bugs be marked to make them less confusing? Is removing the usertag enough?
Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote: > Hi Carsten, > [...] > > My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for > release, it should be enough to upgrade to 2.3.5 to address these unit test > failures. > [...] > > That doesn't make any sense to me. These deprecations are obviously in > werkzeug and not flask-login. Why would changes in flask-login fix them? > > Not saying flask-login shouldn't be updated, but that's not the right scope > for this bug report. Just to throw in: these werkzeug failures are also causing a similar FTBFS in debugpy; I've temporarily addressed it by skipping these unit tests, but that's not a great solution. I just took a quick look at upgrading the unstable/testing version of werkzeug to 2.3.8 in the meantime. It was pretty quick, and the package tests all pass. Shall I upload it to unstable? On salsa, I would push to debian/2.x for the Debian branch and to upstream-2.x for the upstream, so as not to prevent merging the experimental branch into debian/master later. Actually, it is probably OK to use the upstream branch for this update without causing problems, but might be better to be safe. (Incidentally, while doing this, I spotted one bug with the current experimental version: it is missing a Build-Depends on python3-markupsafe.) Best wishes, Julian
Bug#1058404: marked as done (python-graphviz: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Wed, 03 Jan 2024 21:07:09 +
with message-id
and subject line Bug#1058404: fixed in python-graphviz 0.20.1+20240103-1
has caused the Debian Bug report #1058404,
regarding python-graphviz: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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 ow...@bugs.debian.org
immediately.)
--
1058404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-graphviz
Version: 0.20.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:310: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/piping.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/__init__.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/quoting.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/_tools.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/exceptions.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/sources.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/copying.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/base.py ->
> /<>/.pybuild/cpython3_3.12_graphviz/build/graphviz
> copying graphviz/dot.py
Bug#1056473: marked as done (python-graphviz's autopkg test failures with Python 3.12)
Your message dated Wed, 03 Jan 2024 21:07:09 +
with message-id
and subject line Bug#1056473: fixed in python-graphviz 0.20.1+20240103-1
has caused the Debian Bug report #1056473,
regarding python-graphviz's autopkg test failures with Python 3.12
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 ow...@bugs.debian.org
immediately.)
--
1056473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-graphviz
Version: 0.20.1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-graphviz's autopkg test failures with Python 3.12:
[...]
424s === FAILURES
===
424s __ test_deprecated_escape[G]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'G'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
424s __ test_deprecated_escape[E]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'E'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
424s __ test_deprecated_escape[T]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'T'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
424s __ test_deprecated_escape[H]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'H'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
424s __ test_deprecated_escape[L]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'L'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
424s __ test_deprecated_escape[l]
___
424s
424s recwarn = WarningsRecorder(record=True), char = 'l'
424s
424s @pytest.mark.parametrize(
424s 'char', ['G', 'E', 'T', 'H', 'L', 'l'])
424s def test_deprecated_escape(recwarn, char):
424s warnings.simplefilter('always')
424s
424s escape = eval(rf'"\{char}"')
424s
424s assert len(recwarn) == 1
424s > w = recwarn.pop(DeprecationWarning)
424s E AssertionError: not found in
warning list
424s
424s test_quoting.py:17: AssertionError
--- End Message ---
--- Begin Message ---
Source: python-graphviz
Source-Version: 0.20.1+20240103-1
Done: Alexandre Detiste
We believe that the bug you reported is fixed in the latest version of
python-graphviz, which is due to be installed in the Debian FTP archive.
A summary of
Bug#1000005: marked as done (passwordmaker-cli: depends on obsolete pcre3 library)
Your message dated Wed, 03 Jan 2024 21:06:54 + with message-id and subject line Bug#105: fixed in passwordmaker-cli 1.5+dfsg-6 has caused the Debian Bug report #105, regarding passwordmaker-cli: depends on obsolete pcre3 library 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 ow...@bugs.debian.org immediately.) -- 105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: passwordmaker-cli Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: passwordmaker-cli Source-Version: 1.5+dfsg-6 Done: Cord Beermann We believe that the bug you reported is fixed in the latest version of passwordmaker-cli, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cord Beermann (supplier of updated passwordmaker-cli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jan 2024 20:27:02 +0100 Source: passwordmaker-cli Architecture: source Version: 1.5+dfsg-6 Distribution: unstable Urgency: low Maintainer: Cord Beermann Changed-By: Cord Beermann Closes: 105 Changes: passwordmaker-cli (1.5+dfsg-6) unstable; urgency=low . * add patch to replace pcre3 with the newer pcre2 (closes: 105) Checksums-Sha1: fb01e8328e5d587adbb8e13d54f8b94813c9 1851 passwordmaker-cli_1.5+dfsg-6.dsc e0bb64149c1ad335aabcc184b7096af83aabd70e 6828 passwordmaker-cli_1.5+dfsg-6.debian.tar.xz ccbdd6a80263edd27388bd6e00421ad433999eb1 6414 passwordmaker-cli_1.5+dfsg-6_amd64.buildinfo Checksums-Sha256: 754509e1b8b22997589dc7fca300ea6dd4338c301fbdf9693aec1dcd97d5a7e6 1851 passwordmaker-cli_1.5+dfsg-6.dsc 044399c1eacedaedbd4ce38460afaffa6ea36de3fc19589a4972370a4fa23838 6828 passwordmaker-cli_1.5+dfsg-6.debian.tar.xz eff69c73c4557dad28cdf856c1c1904afb0cf54691e64d70d49e4e13db5d77a9 6414 passwordmaker-cli_1.5+dfsg-6_amd64.buildinfo Files: af556b85392638f76e71b1d9251ae8db 1851 utils optional passwordmaker-cli_1.5+dfsg-6.dsc 670d0b7dceb4ae5e70effca9f4cb0ec7 6828 utils optional passwordmaker-cli_1.5+dfsg-6.debian.tar.xz 67ba8eb9da108c720d554d572a0224fc 6414 utils optional passwordmaker-cli_1.5+dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEs9WBfeo2KZ4m5tTmFYdLSUC/jkFAmWVxD8ACgkQmFYdLSUC /jlFLw/+NK4mgMz18lo8Fq9kW4vdottCuSFK6aXbup8dYCmPy+tGH6GWamei5j7s qQYpyyYBvTnGwzdSnBwq39lvdxT7XG1byNH2FtUk0SFuSxFVbYQqz5ZCMk4XomXH 0VAiOvPED/bdUHkzKW8PrHCWEE2beWEaGVHNNDFE+Sc1bHcJnq6lbKdcp3uL7gSV LfJ5yXHQtPoDwDDmbnpZaljvsIIJ6/7n9+1BRoyd6XF6ZgizRb2TzYnHl7SrQD8o VRVS3BurapPesEIX0OIlnRbn+7JqhIA+KXC/mMD/iqCXg+eBhePaFrlLcTzhgL75 NPASrO1nrgy4wLfIT3NnSF2fP1qe0d1qC8YnVzXYYNpkHhvGPYMfsE8fYWk2icR5 j/9JVl//32GGXXekSlKiaiIzffBI9MK63T+te2t/UVLquBqeB4/SL5PObaBHiuqS ODFNIW+Prt2RoHfGwdIbzcpkAt+ovUxfEpl8ELfOC7SWbN4s6XwxHUhNjdppr/nf vo7l6HNIcpb3s3QL+cx9C7nBroqjkaQY6C75KMd2PN4VXOpVB3T3vmSflvMx3P42 FFksEOGf15rB5ao+iUU7mDDQOjPfkNFCVC+Yb8nUie5GaeGdF1WZDAmc/oDPEj+o yrrqjOQwGh0XxGUj7gBnFfxKOoCuASg13nBRVyw5g1Y8ptDDHtw= =Jybr -END PGP SIGNATURE End Message ---
Bug#1056594: [Pkg-privacy-maintainers] Bug#1056594: mat2: test failure
Hi, On 03-01-2024 14:02, Georg Faerber wrote: Thanks for the upload, although I would have appreciated communication about this upfront. Of course. As a Release Manager, I would have appreciated a more timely handeling of an RC issue that blocks other packages. I followed DevRef guidance: """ Upload fixing only release-critical bugs older than 7 days, with no maintainer activity on the bug for 7 days and no indication that a fix is in progress: 0 days """ Could you please push the relevant changes to git? I doubt I have access. Also, it's probably easier for you to just apply my diff than it is for me to do it. I don't have your archive checked out, I used dgit [1]. With kind regards, Paul [1] https://browse.dgit.debian.org/mat2.git/ OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059885: makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127"
On 03/01/2024 20.13, Johannes Schauer Marin Rodrigues wrote: now that I know that BUILT_MODULE_NAME[0] and DEST_MODULE_LOCATION[0] break it, I found other packages via codesearch.d.n that use that syntax and I was wondering whether they break as well. I did the same test after seeing your bug report. Arg I'm pretty sure I ran install tests with all *-dkms packages from sid and dkms from experimental (-2 at that time) without seeing any issues ... but probably I messed up the test setup (or the chroot where I tested). I also tried installing all of the above packages with dkms from unstable patched with my patch from my last email and then they succeed to install again, thus indicating that this is all the same problem class. Thanks for your analysis which isolated the broken change. Since this problem is making several dozen packages in the archive uninstallable, I'm raising the severity of this bug to serious. Apologies if I'm wrong but better safe then sorry, right? Maybe this prevents users of apt-listbugs from installing dkms from unstable and have their dkms modules fail. Please lower the severity if I raised it in error. Apologies in that case. Perfectly fine. I decided working on the fixes (there was another regression reported, too) before playing with the bts :-) I'd also like to suggest the following patch to be included into the dkms package which would've spotted this problem early on: That was the first change I did today - making sure the problem is reproducible with the test packages. :-) I was really confused when you reported dkms-test-dkms working fine - which had a similarily trivial dkms.conf than your package (except for some supposedly irrelevant '[0]'). BTW, even if your package isn't in Debian, I'd suggest adding Testsuite: autopkgtest-pkg-dkms Andreas
Bug#1059885: marked as done (makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127")
Your message dated Wed, 03 Jan 2024 19:34:04 + with message-id and subject line Bug#1059885: fixed in dkms 3.0.12-4 has caused the Debian Bug report #1059885, regarding makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127" 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 ow...@bugs.debian.org immediately.) -- 1059885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dkms Version: 3.0.12-3 Severity: normal Hi, the problem appears since 3.0.12-3 and not with 3.0.12-1. The package that fails since this change in the dkms package is not part of Debian but its packaging source can be found here: https://source.mnt.re/reform/reform-tools/-/tree/main/debian?ref_type=heads It is entirely possible that the *.dkms files in that package are faulty and happened to work with 3.0.12-1 but fail with 3.0.12-3 and that it's not the dkms package at fault. Anyways, the installation fails since dkms 3.0.12-3 with the following message: Setting up reform2-lpc-dkms (1.34) ... Loading new reform2_lpc-1.34 DKMS files... dpkg: error processing package reform2-lpc-dkms (--configure): installed reform2-lpc-dkms package post-installation script subprocess returned error exit status 127 Can you give me some hints how to debug this? How do I get a better error message than this to try and figure out what went wrong? Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: dkms Source-Version: 3.0.12-4 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of dkms, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated dkms package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Jan 2024 20:16:57 +0100 Source: dkms Architecture: source Version: 3.0.12-4 Distribution: unstable Urgency: medium Maintainer: Dynamic Kernel Module System Team Changed-By: Andreas Beckmann Closes: 637877 755942 762061 918918 951404 968763 1059885 1059895 1059900 Changes: dkms (3.0.12-4) unstable; urgency=medium . * common.postinst: Use bash for extracting AUTOINSTALL from dkms.conf. (Closes: #1059885) * Stop recommending linux-headers-*. (Closes: #1059895, #918918, #968763, #637877, #755942, #762061, #951404) * postinst: Be less greedy and don't remove module source while cleaning up module builds with empty $arch from the dkms tree. (Closes: #1059900) Checksums-Sha1: 5760d37c03a4530f894cae0d1b5985ab10a7651c 2360 dkms_3.0.12-4.dsc c04d13446b36e1354a210e7b8cb7b406cd09fc66 33836 dkms_3.0.12-4.debian.tar.xz 06963f1c2507bad785e8a67e30f99b26f39ee217 5593 dkms_3.0.12-4_source.buildinfo Checksums-Sha256: e78eab2b640c9128b80e562b45a0dd5a5eb4abcb1034bed23ed92e1737ee697f 2360 dkms_3.0.12-4.dsc 919307f66f2255a851dd4663627ed9918e2eb5eb408b6f61bf68dbcf5697aab7 33836 dkms_3.0.12-4.debian.tar.xz 5ee734cc9bbe77c27c3abe8226cef54910fcf2bcc37265426360bb22908b4479 5593 dkms_3.0.12-4_source.buildinfo Files: 2ea05c66e93a68647ca90b1a36c7c284 2360 kernel optional dkms_3.0.12-4.dsc 832714e8138d6ac36d9e1f0a6bcf1cc2 33836 kernel optional dkms_3.0.12-4.debian.tar.xz f3d726031a58754d72e5db8401b02efa 5593 kernel optional dkms_3.0.12-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmWVszkQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCJOOD/46wH7wTxU1VPtpqC8e0pvDXTEyMPCT8qwd BO+bOVvjtZyG4jC2aV+WsT7XPbv36cHt3WsPXNGyEWccMaUIbcLaeZAIA9TxSszu kNlukhdSIueRitgV52CjJsXz3fjmX1+KEVa1AQKnujwZIAyl6dTY2fIHplJz+E3U auw6QhU/ZTrgD1Ouj8xtn/l1ini6IbJOrNC8Tlr1EALM+2mAZisOwR4HYGIbVLmC xPLNSoVvBma5dvRRf0tbmSSBeHjnN1/CJ7ybD5eey003jHa4+k1l3OoEKLV8efmR Edi5huCCRrYfksqeobaLXd/p0k3w4VmSnppIv/QJ2Gdr4GMoaKWjEAE71NG9h8zT DmBPcZPPPoa5Q/lslUswoGb/0v++0IZGoRTUesvS4w0CnfVp2ImchXpX2BWiPwSi jAbRywNVm/uYG7iEt0DPpy1/X9u+Dzqe3M9GmYkTIF8N9Wn6TYUaD0mWCEoQx4SM q7ESB2ZlQA82r5JMAmr1Ptf6Il27y0lYtvx/oUEJEukuF9ZXmhEneFlkAvgk9l6W +cIfTnaU03VErmIb8IWvCmWKvkrh2bHl7EobNwsJn+XbHRBCmjW0bfaCYgU5CSKR
Processed: Re: Bug#1059885: makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127"
Processing control commands: > severity -1 serious Bug #1059885 [dkms] makes dkms package postinst fail with "post-installation script subprocess returned error exit status 127" Severity set to 'serious' from 'normal' -- 1059885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)
Your message dated Wed, 03 Jan 2024 18:51:24 + with message-id and subject line Bug#1059923: fixed in spread-sheet-widget 0.10-2 has caused the Debian Bug report #1059923, regarding spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED 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 ow...@bugs.debian.org immediately.) -- 1059923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spread-sheet-widget Version: 0.10-1 Severity: serious On 2024-01-03 17:21, Debian FTP Masters wrote: > > > libspread-sheet-widget-dev_0.10-1_s390x.deb: has 1 file(s) with a timestamp > too far in the past: > usr/share/doc/libspread-sheet-widget-dev/changelog.gz (Thu Jan 1 00:00:00 > 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: spread-sheet-widget Source-Version: 0.10-2 Done: Friedrich Beckmann We believe that the bug you reported is fixed in the latest version of spread-sheet-widget, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Friedrich Beckmann (supplier of updated spread-sheet-widget package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jan 2024 19:02:39 +0100 Source: spread-sheet-widget Binary: libspread-sheet-widget libspread-sheet-widget-dbgsym libspread-sheet-widget-dev Architecture: source amd64 Version: 0.10-2 Distribution: unstable Urgency: medium Maintainer: Friedrich Beckmann Changed-By: Friedrich Beckmann Description: libspread-sheet-widget - shared library for GTK+ to view and manipulate two dimensional ta libspread-sheet-widget-dev - development files for the GTK+ spread sheet widget Closes: 1059923 Changes: spread-sheet-widget (0.10-2) unstable; urgency=medium . * Fixed debian build artefact (closes: #1059923) Checksums-Sha1: b04ba9e6326753becd962e17261356a75f64ee24 2039 spread-sheet-widget_0.10-2.dsc 1cf4a81a53ab7c371ccdcb4e78ae9d7cbe956470 5416 spread-sheet-widget_0.10-2.debian.tar.xz 65f9c5bc1efb23846f3792917db7a1e7f763e026 159600 libspread-sheet-widget-dbgsym_0.10-2_amd64.deb a4b6084888194cb566275171f6e22ce7e4fe8e13 58480 libspread-sheet-widget-dev_0.10-2_amd64.deb fb1a67c702d994a8ed15b79435d01beb857003d8 48748 libspread-sheet-widget_0.10-2_amd64.deb dbaabcb976fd024cf72c282b25f03e3f7babed91 14791 spread-sheet-widget_0.10-2_amd64.buildinfo Checksums-Sha256: 9f409d8cc707b396127e46c449cbba49a125c12f93c49b475af4515c36a135e3 2039 spread-sheet-widget_0.10-2.dsc 741b264769d8fd6545c17d52d3315e85b50b116acf9d877fd5678c9942dfc656 5416 spread-sheet-widget_0.10-2.debian.tar.xz 43402e81a8f70fdba74379535e833791f31564fb149fd8d1faebbee57b668e18 159600 libspread-sheet-widget-dbgsym_0.10-2_amd64.deb dec56ea15b2f7d4c8266e5b4e1eddf8553bcaaaf04ff92402a8c7eca97be3728 58480 libspread-sheet-widget-dev_0.10-2_amd64.deb 6bb6e6c0790bd2df4f16300d19f0f119497739b475c8dff6aafd3643da147176 48748 libspread-sheet-widget_0.10-2_amd64.deb 6e178c549cebcfaa08082d73e1ce240efed91a5b5e084812aff244ba6dd21f52 14791 spread-sheet-widget_0.10-2_amd64.buildinfo Files: 8b235a9345e17525e7a951fc807925a4 2039 libs optional spread-sheet-widget_0.10-2.dsc 9da4c3140b02b774f77082ef1f97924a 5416 libs optional spread-sheet-widget_0.10-2.debian.tar.xz 60e92252ff2cd5e0ac83bf2306b890e0 159600 debug optional libspread-sheet-widget-dbgsym_0.10-2_amd64.deb aabc77aee2013d6d08a3b7dc84566544 58480 libdevel optional libspread-sheet-widget-dev_0.10-2_amd64.deb 2a3a10a0c4c4522fa74c5a84fe4217c8 48748 libs optional libspread-sheet-widget_0.10-2_amd64.deb c8d6064a9d161a1405f53dd237bd56e1 14791 libs optional spread-sheet-widget_0.10-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEGp+TZe9/EUJidSaxzHnYClu3/FEFAmWVpvoACgkQzHnYClu3 /FFcKwgArXWlNxzmas/+KqJB7bv0YRtfxWF0hvQcMYYmsCpGtBdNTrkA/mgkawan 5OFGB20/nUG2YOhtadEyX8OvJvfmhTmb/gxML7tO47RItH/Pp+SpJZgM6K9SYqY4
Bug#1008205: marked as done (RM: gamin -- RoQA; dead upstream)
Your message dated Wed, 03 Jan 2024 17:41:39 + with message-id and subject line Bug#1057655: Removed package(s) from unstable has caused the Debian Bug report #1008205, regarding RM: gamin -- RoQA; dead upstream 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 ow...@bugs.debian.org immediately.) -- 1008205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gamin Version: 0.1.10-5 Severity: important Tags: upstream wontfix X-Debbugs-Cc: debian-...@lists.debian.org, debian-h...@lists.debian.org User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs unmaintained-upstream gamin is no longer maintained upstream, and has been moved to the Archive namespace on GNOME's Gitlab and marked read-only: https://gitlab.gnome.org/Archive/gamin If the Debian maintainers of gamin or the Hurd porters intend it to have a future, then someone will need to take over as its de facto upstream maintainer. Otherwise, dependent packages should probably move to a less dead implementation of filesystem monitoring. On Linux, the kernel-level file monitoring API is inotify, which can either be used directly, via a cross-platform wrapper like GLib (GFileMonitor), Qt (QFileSystemWatcher), libuv (uv_fs_event_t), libev (ev_stat) and so on, or via a Linux/inotify-specific convenience API like python3-pyinotify. On the kFreeBSD ports, the kernel-level file monitoring API is kqueue, which can either be used directly or via a cross-platform wrapper like the ones mentioned for Linux. On the Hurd port, according to #885011 there are filesystem server RPCs available to user-space (see server/gam_hurd_mach_notify.c in gamin, apaprently). This report was prompted by a GLib branch that removes fam/gamin support being merged upstream for GLib 2.73.x, which means that if Hurd users want it to still have a GFileMonitor backend, they have approximately 6 months to provide one, either in-tree in GLib itself, or out-of-tree in a separate source package (analogous to the way gvfs and glib-networking provide backends for other extension points, although not GFileMonitor). Packages that use gamin: - apachetop - codeblocks (codeblocks-contrib) - courier (courier-imap) - doodle (doodled) - gnubiff - glib2.0 [hurd-any only] - libsys-gamin-perl - and possibly some kFreeBSD- and/or Hurd-specific packages smcv --- End Message --- --- Begin Message --- Version: 0.1.10-6+rm Dear submitter, as the package gamin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1057655 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1042184: marked as done (chaussette: FTBFS: AssertionError: Lists differ: ['waitress', 'wsgiref'] != ['eventlet', 'waitress', 'wsgiref'])
Your message dated Wed, 03 Jan 2024 17:40:10 +
with message-id
and subject line Bug#1059887: Removed package(s) from unstable
has caused the Debian Bug report #1042184,
regarding chaussette: FTBFS: AssertionError: Lists differ: ['waitress',
'wsgiref'] != ['eventlet', 'waitress', 'wsgiref']
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 ow...@bugs.debian.org
immediately.)
--
1042184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chaussette
Version: 1.3.0+git20170419+82ac44a-0.4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> http_proxy="" dh_auto_test
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
> in use)
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.11_chaussette/build; python3.11 -m nose
> -v
> test_backends (chaussette.tests.test_backend.TestBackend) ... FAIL
> test_app (chaussette.tests.test_paste.TestPasteApp) ... SKIP: Only Python 2
> test_main (chaussette.tests.test_server.TestMain) ... ok
> Test all backends with default params ... SKIP: Not py3
> Check the spawn option for the backend that support it ... SKIP: Not py3
> test_create_socket (chaussette.tests.test_util.TestUtil.test_create_socket)
> ... ok
> test_import_string (chaussette.tests.test_util.TestUtil.test_import_string)
> ... ok
>
> ==
> FAIL: test_backends (chaussette.tests.test_backend.TestBackend)
> --
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.11_chaussette/build/chaussette/tests/test_backend.py",
> line 30, in test_backends
> self.assertEqual(_backends, expected)
> AssertionError: Lists differ: ['waitress', 'wsgiref'] != ['eventlet',
> 'waitress', 'wsgiref']
>
> First differing element 0:
> waitress
> eventlet
>
> Second list contains 1 additional elements.
> First extra element 2:
> wsgiref
>
> - ['waitress', 'wsgiref']
> + ['eventlet', 'waitress', 'wsgiref']
> ?
>
>
> --
> Ran 7 tests in 1.079s
>
> FAILED (SKIP=3, failures=1)
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.11_chaussette/build; python3.11 -m nose
> -v
> dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.11
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/chaussette_1.3.0+git20170419+82ac44a-0.4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.3.0+git20170419+82ac44a-0.4+rm
Dear submitter,
as the package chaussette has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1059887
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1056393: marked as done (radare2-cutter: Cannot debug binary: File '' does not have executable permissions.)
Your message dated Wed, 03 Jan 2024 17:37:02 + with message-id and subject line Bug#1059836: Removed package(s) from unstable has caused the Debian Bug report #1056393, regarding radare2-cutter: Cannot debug binary: File '' does not have executable permissions. 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 ow...@bugs.debian.org immediately.) -- 1056393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: radare2-cutter Version: 1.12.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: nathan.teodo...@canonical.com Dear Maintainer, 1. 'Cutter /bin/ls' or any other binary in your system. 2. Click start debug (F9). Expected Debugging starts. Observed A dialog window with "Cannot debug binary: File '' does not have executable permissions." appears. In stderr, r_config_get: variable 'file.path' not found appears. I can reproduce this both in Ubuntu 24.04 and Debian unstable. -- System Information: Debian Release: bookworm/sid APT prefers noble APT policy: (500, 'noble') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-9-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages radare2-cutter depends on: ii libc6 2.38-1ubuntu6 ii libcgraph6 2.42.2-7build3 ii libgcc-s1 13.2.0-6ubuntu1 ii libgvc62.42.2-7build3 ii libkf5syntaxhighlighting5 5.112.0-0ubuntu1 ii libpython3.11 3.11.6-3 ii libqt5core5a 5.15.10+dfsg-3 ii libqt5gui5 5.15.10+dfsg-3 ii libqt5network5 5.15.10+dfsg-3 ii libqt5svg5 5.15.10-2 ii libqt5widgets5 5.15.10+dfsg-3 ii libradare2-5.0.0 5.5.0+dfsg-1ubuntu1 ii libstdc++6 13.2.0-6ubuntu1 ii python33.11.4-5 ii python3-ipykernel 6.24.0-3 ii python3-jupyter-client 7.4.9-2 ii python3-notebook 6.4.12-2.2 ii python3-zmq24.0.1-4build1 radare2-cutter recommends no packages. radare2-cutter suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.12.0-2+rm Dear submitter, as the package radare2-cutter has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1059836 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1059923: spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED
Source: spread-sheet-widget Version: 0.10-1 Severity: serious On 2024-01-03 17:21, Debian FTP Masters wrote: > > > libspread-sheet-widget-dev_0.10-1_s390x.deb: has 1 file(s) with a timestamp > too far in the past: > usr/share/doc/libspread-sheet-widget-dev/changelog.gz (Thu Jan 1 00:00:00 > 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1059922: nut-server: upsd fails to start since version 2.8.1
Package: nut-server Version: 2.8.1-1 Severity: grave Dear Laurent Bigonville, with version 2.8.0-7 an EATON UPS connected to a debian computer via USB was working in standalone mode as expected. The only change in the config files was in /etc/nut/ups.conf where I added the following lines: [Eaton] driver = usbhid-ups port = auto vendorid = 0463 pollfreq = 30 After the upgrade to version 2.8.1-1 the upsd daemon would fail to start. The output in /var/log/syslog is upsd[12132]: not listening on ::1 port 3493 upsd[12132]: listening on 127.0.0.1 port 3493 upsd[12132]: no listening interface available instead of upsd[12553]: listening on 127.0.0.1 port 3493 upsd[12553]: not listening on ::1 port 3493 upsd[12553]: Connected to UPS [Eaton]: usbhid-ups-Eaton upsd[12555]: Startup successful for the working version 2.8.0. Any ideas? Regards, Jörg. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.9 (SMP w/16 CPU threads) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages nut-server depends on: ii adduser3.137 ii init-system-helpers1.66 ii libc6 2.37-12 ii libmodbus5 3.1.10-1 ii libnspr4 2:4.35-1.1 ii libnss32:3.96.1-1 ii libnutscan22.8.1-1 ii libupsclient6 2.8.1-1 ii libusb-1.0-0 2:1.0.26-1 ii libwrap0 7.6.q-32 ii nut-client 2.8.1-1 ii sysvinit-utils [lsb-base] 3.08-5 ii udev 255.2-2 nut-server recommends no packages.
Bug#1059921: intake: autopkgtest failure with Python 3.12
Source: intake Version: 0.6.6-2 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer intake's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/i/intake/testing/amd64/ 77s ERRORS 77s ERROR collecting test session _ 77s /usr/lib/python3/dist-packages/_pytest/config/__init__.py:641: in _importconftest 77s mod = import_path(conftestpath, mode=importmode, root=rootpath) 77s /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path 77s importlib.import_module(module_name) 77s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 77s return _bootstrap._gcd_import(name[level:], package, level) 77s :1387: in _gcd_import 77s ??? 77s :1360: in _find_and_load 77s ??? 77s :1331: in _find_and_load_unlocked 77s ??? 77s :935: in _load_unlocked 77s ??? 77s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:186: in exec_module 77s exec(co, module.__dict__) 77s intake/conftest.py:18: in 77s from intake.container import persist 77s intake/container/__init__.py:8: in 77s from .dataframe import RemoteDataFrame 77s intake/container/dataframe.py:7: in 77s from distutils.version import LooseVersion 77s E ModuleNotFoundError: No module named 'distutils' 77s === short test summary info 77s ERROR - ModuleNotFoundError: No module named 'distutils' 77s Interrupted: 1 error during collection 77s === 1 error in 0.30s ===
Bug#1030545: marked as done (qemu-(img|system-s390x) hang on s390x bullseye kernel)
Your message dated Wed, 3 Jan 2024 19:00:38 +0300 with message-id and subject line Re: qemu-(img|system-s390x) hang on s390x bullseye kernel has caused the Debian Bug report #1030545, regarding qemu-(img|system-s390x) hang on s390x bullseye kernel 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 ow...@bugs.debian.org immediately.) -- 1030545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qemu Version: 1:7.2+dfsg-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, While investigating recent s390x build failures of libguestfs, I noticed that variants of qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512 would hang in what appears a tight loop (100% CPU). Calling strace on those hanging processes or sending them TSTP and CONT signals causes them to continue. Later in the build process, libguestfs-test-tool runs qemu-system-s390x a few times. Those processes also hang and they can also be "cured" by sending them TSTP and CONT signals. Cheers, -Hilko --- End Message --- --- Begin Message --- On Sat, 13 May 2023 19:57:48 +0100 James Addison wrote: Followup-For: Bug #1030545 X-Debbugs-Cc: ben...@debian.org, dipak.zo...@ibm.com Hi Hilko (plus Dipak, fix author on cc for awareness), Debian kernel package 5.10.179-1 that includes a fix for this has been accepted into the stable-security (bullseye-security) suite today, and should resolve this bug. So let's close this bug report finally.. :) (Closing without a version tag since the prob wasn't in qemu to begin with) Thank you all for the good work! /mjt--- End Message ---
Processed: pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Processing control commands:
> tags -1 + fixed-upstream patch
Bug #1058417 [src:pytest-mock] pytest-mock: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) patch and fixed-upstream.
--
1058417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058417: pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Control: tags -1 + fixed-upstream patch This was fixed in the following upstream commit: https://github.com/pytest-dev/pytest-mock/commit/3d48ff90257daf6b3c50100bd5dd36faf34e70dc
Bug#1059913: setuptools-scm fails it's autopkg tests
Package: src:setuptools-scm Version: 8.0.4-1 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 $ apt show python3-setuptools-scm|grep Depends Depends: python3-distutils, python3-pkg-resources, python3-packaging, python3-tomli | python3-supported-min (>= 3.11), python3-typing-extensions, python3:any I assume that needs python3-setuptools as a dependency now, python3-distutils doesn't exist anymore for python3.12. from https://ci.debian.net/data/autopkgtest/testing/amd64/s/setuptools-scm/41418646/log.gz [...] 70s autopkgtest [13:24:48]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import setuptools_scm; print(setuptools_scm)" ; done 70s autopkgtest [13:24:48]: test autodep8-python3: [--- 70s Testing with python3.11: 70s Traceback (most recent call last): 70s File "", line 1, in 70s File "/usr/lib/python3/dist-packages/setuptools_scm/__init__.py", line 7, in 70s from ._config import Configuration 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_config.py", line 15, in 70s from ._integration.pyproject_reading import ( 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py", line 8, in 70s from .setuptools import read_dist_name_from_setup_cfg 70s File "/usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py", line 9, in 70s import setuptools 70s ModuleNotFoundError: No module named 'setuptools' 71s autopkgtest [13:24:49]: test autodep8-python3: ---]
Bug#1056594: [Pkg-privacy-maintainers] Bug#1056594: mat2: test failure
Hi Paul, On 24-01-01 10:24:46, Paul Gevers wrote: > On 01-01-2024 09:50, Paul Gevers wrote: > > I'm going to NMU with this patch shortly. @gregor, any reason why > > you didn't the upload to DELAYED after you built it already? > > I have uploaded the attached changes. Thanks for the upload, although I would have appreciated communication about this upfront. Could you please push the relevant changes to git? Thanks & all the best, Georg
Processed: affects 1059671
Processing commands for cont...@bugs.debian.org: > affects 1059671 + src:ropgadget Bug #1059671 [python3-capstone] python3-capstone: Python 3.12 has no module named 'distutils' Added indication that 1059671 affects src:ropgadget > thanks Stopping processing here. Please contact me if you need assistance. -- 1059671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ropgadget: autopkgtest failure with Python 3.12
Processing control commands: > reassign -1 python3-capstone Bug #1059671 [src:ropgadget] ropgadget: autopkgtest failure with Python 3.12 Bug reassigned from package 'src:ropgadget' to 'python3-capstone'. No longer marked as found in versions ropgadget/7.4+dfsg-1. Ignoring request to alter fixed versions of bug #1059671 to the same values previously set > retitle -1 python3-capstone: Python 3.12 has no module named 'distutils' Bug #1059671 [python3-capstone] ropgadget: autopkgtest failure with Python 3.12 Changed Bug title to 'python3-capstone: Python 3.12 has no module named 'distutils'' from 'ropgadget: autopkgtest failure with Python 3.12'. -- 1059671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059671: ropgadget: autopkgtest failure with Python 3.12
Control: reassign -1 python3-capstone Control: retitle -1 python3-capstone: Python 3.12 has no module named 'distutils' On Fri, 29 Dec 2023 23:25:28 +0200 Graham Inggs wrote: 36s from capstone import * 36s File "/usr/lib/python3/dist-packages/capstone/__init__.py", line 266, in 36s import distutils.sysconfig 36s ModuleNotFoundError: No module named 'distutils' 37s autopkgtest [20:09:36]: test autodep8-python3: ---] 37s autodep8-python3 FAIL non-zero exit status 1 The distutils import happens in python3-capstone, reassigning. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Processed: Re: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed
Processing control commands: > severity -1 normal Bug #1059899 [systemd] systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed Severity set to 'normal' from 'critical' > tags -1 moreinfo Bug #1059899 [systemd] systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed Added tag(s) moreinfo. -- 1059899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed
Control: severity -1 normal Control: tags -1 moreinfo On Wed, 03 Jan 2024 12:02:40 +0100 Corin Langosch wrote: > Package: systemd > Version: 247.3-7+deb11u4 > Severity: critical > File: systemd-resolved > Justification: breaks the whole system Your logs show that it restarts just fine after the oom kill, so it is most definitely not "grave". Also, you did not attach your local resolved.conf. Also, oldstable is old. Try with backports or with upgrading to stable. -- Kind regards, Luca Boccassi
Bug#1059894: dkms - fails autopkgtest with Linux 6.6
On Wed, Jan 03, 2024 at 11:41:51AM +0100, Andreas Beckmann wrote: > On 03/01/2024 09.49, Bastian Blank wrote: > > The dkms autopkgtest fails with Linux 6.6. The only output is: > > | 173s modinfo: ERROR: Module > > /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_test.ko not > > found. > Already fixed :-) > You recently enabled module compression which broke the dkms tests because > they used a hardcoded list of distro/compression combinations. I'm now > trying to parse that from .config (any only override it for distros that > handle it differently). Okay. Now my question would be: why do you need to know. And: if you really need to know, why do you not override it while installing the modules to be always one kind or another. Bastian -- Vulcans worship peace above all. -- McCoy, "Return to Tomorrow", stardate 4768.3
Bug#1055717: marked as done (python-multidict ftbfs with Python 3.12)
Your message dated Wed, 03 Jan 2024 11:35:16 + with message-id and subject line Bug#1055717: fixed in python-multidict 6.0.4-1.1 has caused the Debian Bug report #1055717, regarding python-multidict ftbfs with Python 3.12 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 ow...@bugs.debian.org immediately.) -- 1055717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-multidict Version: 6.0.4-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] tests/test_mutable_multidict.py::TestCIMutableMultiDict::test_add[multidict._multidict] Fatal Python error: Segmentation fault Current thread 0x7facee819040 (most recent call first): File "/<>/.pybuild/cpython3_3.12_multidict/build/tests/test_mutable_multidict.py", line 333 in test_add File "/usr/lib/python3/dist-packages/_pytest/python.py", line 194 in pytest_pyfunc_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1792 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 169 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 192 in console_main File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in File "", line 88 in _run_code File "", line 198 in _run_module_as_main Extension modules: multidict._multidict (total: 1) Segmentation fault (core dumped) E: pybuild pybuild:395: test: plugin distutils failed with: exit code=139: cd /<>/.pybuild/cpython3_3.12_multidict/build; python3.12 -m pytest tests --- End Message --- --- Begin Message --- Source: python-multidict Source-Version: 6.0.4-1.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python-multidict, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python-multidict package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing
Bug#1055696: marked as done (python3-rdkit: unusable with Python 3.12)
Your message dated Wed, 3 Jan 2024 13:35:13 +0200 with message-id and subject line Re: Bug#1055696: 1055696: more info has caused the Debian Bug report #1055696, regarding python3-rdkit: unusable with Python 3.12 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 ow...@bugs.debian.org immediately.) -- 1055696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parmed Version: 4.2.2+dfsg-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 parmed ftbfs with Python 3.12 in the tests, although I'm also seeing some test failures with 3.11, which are not seen in the last Debian build. [...] 3.12 === short test summary info FAILED test/test_parmed_formats.py::TestPDBStructure::test_download - socket FAILED test/test_parmed_formats.py::TestPDBStructure::test_download_save - so... FAILED test/test_parmed_formats.py::TestCIFStructure::test_download - socket FAILED test/test_parmedtools_actions.py::TestAmoebaParmActions::test_delete_bond = 4 failed, 734 passed, 177 skipped, 1 xfailed, 11933 warnings in 241.42s (0:04:01) = E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.12_parmed/build; python3.12 -m pytest test [...] 3.11 === short test summary info FAILED test/test_parmed_formats.py::TestPDBStructure::test_download - socket FAILED test/test_parmed_formats.py::TestPDBStructure::test_download_save - so... FAILED test/test_parmed_formats.py::TestCIFStructure::test_download - socket = 3 failed, 841 passed, 70 skipped, 1 xfailed, 1 xpassed, 12027 warnings in 314.67s (0:05:14) = E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.11_parmed/build; python3.11 -m pytest test complete build log at https://launchpadlibrarian.net/696985247/buildlog_ubuntu-noble-amd64.parmed_4.2.2+dfsg-1_BUILDING.txt.gz --- End Message --- --- Begin Message --- On Wed, 6 Dec 2023 18:21:17 +0200 Adrian Bunk wrote: On Fri, Nov 17, 2023 at 12:34:44PM +0200, Andrius Merkys wrote: > I have reassigned this issue to python3-rdkit as Python 3.12 specific issue > seems to be confined to python3-rdkit: >... parmed is built for all supported python3 versions, but uses rdkit that is only built for the default python3 version. That can obviously not work for non-default python3-versions, one of the packages has to be changed. This is correct, rdkit is built for default Python version only. Thus I made parmed build for default Python as well. Therefore there is no need to keep this bug open. Best, Andrius--- End Message ---
Bug#1059899:
I just disabled LLMNR by putting LLMNR=no in resolved.conf to see if it helps,
but it still crashes as before.
Jan 03 12:16:23 system1 systemd-resolved[863]: Got DNS stub UDP query packet
for id 10122
Jan 03 12:16:23 system1 systemd-resolved[863]: Looking up RR for
54.49.125.74.in-addr.arpa IN A.
Jan 03 12:16:23 system1 systemd-resolved[863]: Switching to system DNS server
192.168.0..
Jan 03 12:16:23 system1 systemd-resolved[863]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/resolve1
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=4 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jan 03 12:16:23 system1 systemd-resolved[863]: Cache miss for
54.49.125.74.in-addr.arpa IN A
Jan 03 12:16:23 system1 systemd-resolved[863]: Transaction 21270 for
<54.49.125.74.in-addr.arpa IN A> scope dns on */*.
Jan 03 12:16:23 system1 systemd-resolved[863]: Using feature level UDP+EDNS0
for transaction 21270.
Jan 03 12:16:23 system1 systemd-resolved[863]: Using DNS server 192.168.0. for
transaction 21270.
Jan 03 12:16:23 system1 systemd-resolved[863]: Sending query packet with id
21270 of size 54.
Jan 03 12:16:23 system1 systemd-resolved[863]: Processing query...
Jan 03 12:16:23 system1 systemd-resolved[863]: Processing incoming packet on
transaction 21270 (rcode=NXDOMAIN).
Jan 03 12:16:23 system1 systemd-resolved[863]: Verified we get a response at
feature level UDP+EDNS0 from DNS server 192.168.0..
Jan 03 12:16:23 system1 systemd-resolved[863]: Added NXDOMAIN cache entry for
54.49.125.74.in-addr.arpa IN ANY 1s
Jan 03 12:16:23 system1 systemd-resolved[863]: Transaction 21270 for
<54.49.125.74.in-addr.arpa IN A> on scope dns on */* now complete with
from network (unsigned).
Jan 03 12:16:25 system1 kernel: systemd-resolve invoked oom-killer:
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Jan 03 12:16:26 system1 kernel: CPU: 1 PID: 863 Comm: systemd-resolve Not
tainted 5.10.0-27-amd64 #1 Debian 5.10.205-2
Jan 03 12:16:26 system1 kernel: Hardware name: QEMU Standard PC (Q35 + ICH9,
2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Jan 03 12:16:26 system1 kernel: Call Trace:
Jan 03 12:16:26 system1 kernel: dump_stack+0x6b/0x83
Jan 03 12:16:26 system1 kernel: dump_header+0x4a/0x1f4
Jan 03 12:16:26 system1 kernel: oom_kill_process.cold+0xb/0x10
Jan 03 12:16:26 system1 kernel: out_of_memory+0x1bd/0x4e0
Jan 03 12:16:26 system1 kernel: __alloc_pages_slowpath.constprop.0+0xbcc/0xc90
Jan 03 12:16:26 system1 kernel: __alloc_pages_nodemask+0x2de/0x310
Jan 03 12:16:26 system1 kernel: pagecache_get_page+0x175/0x390
Jan 03 12:16:26 system1 kernel: filemap_fault+0x6a2/0x900
Jan 03 12:16:26 system1 kernel: ? xas_load+0x5/0x80
Jan 03 12:16:26 system1 kernel: ext4_filemap_fault+0x2d/0x50 [ext4]
Jan 03 12:16:26 system1 kernel: __do_fault+0x37/0x170
Jan 03 12:16:26 system1 kernel: handle_mm_fault+0x124d/0x1c00
Jan 03 12:16:26 system1 kernel: do_user_addr_fault+0x1b8/0x400
Jan 03 12:16:26 system1 kernel: exc_page_fault+0x78/0x160
Jan 03 12:16:26 system1 kernel: ? asm_exc_page_fault+0x8/0x30
Jan 03 12:16:26 system1 kernel: asm_exc_page_fault+0x1e/0x30
Jan 03 12:16:26 system1 kernel: RIP: 0033:0x7fafdd0896c0
Jan 03 12:16:26 system1 kernel: Code: Unable to access opcode bytes at RIP
0x7fafdd089696.
Jan 03 12:16:26 system1 kernel: RSP: 002b:7ffce16e3588 EFLAGS: 00010246
Jan 03 12:16:26 system1 kernel: RAX: 55d2218a9250 RBX: 7ffce16e35d8
RCX: 0010
Jan 03 12:16:26 system1 kernel: RDX: 0200 RSI:
RDI: 55d2218a9250
Jan 03 12:16:26 system1 kernel: RBP: R08: 55d2218a9250
R09: 7fafdd0f7be0
Jan 03 12:16:26 system1 kernel: R10: 006e R11: 0210
R12: 55d2218a9250
Jan 03 12:16:26 system1 kernel: R13: R14: 0028
R15: 55d2218a921c
Jan 03 12:16:26 system1 kernel: Mem-Info:
Jan 03 12:16:26 system1 kernel: active_anon:98 inactive_anon:417531
isolated_anon:0
active_file:22 inactive_file:7 isolated_file:0
unevictable:772 dirty:0 writeback:0
slab_reclaimable:2917 slab_unreclaimable:58826
mapped:15 shmem:923 pagetables:1262 bounce:0
free:13625 free_pcp:2 free_cma:0
Jan 03 12:16:26 system1 kernel: Node 0 active_anon:392kB
inactive_anon:1670124kB active_file:88kB inactive_file:28kB unevictable:3088kB
isolated(anon):0kB isolated(file):0kB mapped:60kB dirty:0kB
writeback:0kB shmem:3692kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp:
415744kB writeback_tmp:0kB kernel_stack:2256kB all_unreclaimable? yes
Jan 03 12:16:26 system1 kernel: Node 0 DMA free:8016kB min:360kB low:448kB
high:536kB reserved_highatomic:0KB active_anon:0kB inactive_anon:7620kB
active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:15992kB managed:15908kB
Processed: Bug#1055717 marked as pending in python-multidict
Processing control commands: > tag -1 pending Bug #1055717 [src:python-multidict] python-multidict ftbfs with Python 3.12 Added tag(s) pending. -- 1055717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055717: marked as pending in python-multidict
Control: tag -1 pending Hello, Bug #1055717 in python-multidict reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-multidict/-/commit/2d54ca0b1567c03256715b2bd6f41f0260216abb * Pull upstream patches for Python 3.12 compatibility. Closes: #1055717. (this message was generated automatically) -- Greetings https://bugs.debian.org/1055717
Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed
Package: systemd Version: 247.3-7+deb11u4 Severity: critical File: systemd-resolved Justification: breaks the whole system X-Debbugs-Cc: cor...@gmx.de Dear Maintainer, systemd-resolved takes up all memory on certain PTR queries within only a few milliseconds and is then oom-killed. This sometimes renders the whole system unusable. I can reliably reproduce the issue using this simple command: ~# host 54.49.125.74.in-addr.arpa ;; connection timed out; no servers could be reached I already tried to debug the issue a little, please find the details below. If you need more information please let me know. ~# systemd-resolve --version systemd 247 (247.3-7+deb11u4) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified ~# cat /etc/systemd/resolved.conf [Resolve] DNS=192.168.0.1 Domains=intern.xxx xxx.com ~# tcpdump -i any -n port 53 11:35:31.012308 loIn IP 127.0.0.1.58906 > 127.0.0.53.53: 28856+ A? 54.49.125.74.in-addr.arpa. (43) 11:35:31.014406 vlan4 Out IP x.x.x.x.50491 > 192.168.0.1.53: 29042+ [1au] A? 54.49.125.74.in-addr.arpa. (54) 11:35:31.033018 vlan4 In IP 192.168.0.1.53 > x.x.x.x.50491: 29042 NXDomain 0/1/1 (114) Jan 03 11:35:31 system1 systemd-resolved[40859]: SELinux enabled state cached to: disabled Jan 03 11:35:31 system1 systemd-resolved[40859]: Positive Trust Anchors: Jan 03 11:35:31 system1 systemd-resolved[40859]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jan 03 11:35:31 system1 systemd-resolved[40859]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Jan 03 11:35:31 system1 systemd-resolved[40859]: Using system hostname 'system1'. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link *, protocol dns, family * Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 9/vlan1000 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 8/vlan102 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 7/vlan101 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 6/vlan100 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 5/vlan98 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 4/vlan4 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 3/vlan3 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 2/vlan2 Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 1/lo Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan1000, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 3857 for scope llmnr on vlan1000/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 51270us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan102, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 15599 for scope llmnr on vlan102/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 51008us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan101, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 61000 for scope llmnr on vlan101/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 81403us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan100, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 62244 for scope llmnr on vlan100/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 72225us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan98, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 43244 for scope llmnr on vlan98/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 68513us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan4, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 65377 for scope llmnr on vlan4/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 79327us. Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan3, protocol llmnr, family AF_INET6 Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 41217 for scope llmnr on vlan3/INET6. Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr
Bug#1058270: marked as pending in python-schema-salad
Control: tag -1 pending Hello, Bug #1058270 in python-schema-salad reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-schema-salad/-/commit/2ef4a4e4b8f920efdbbf3051c04f1733b944b170 New version Closes: #1058270 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058270
Processed: Bug#1058270 marked as pending in python-schema-salad
Processing control commands: > tag -1 pending Bug #1058270 [src:python-schema-salad] python-schema-salad: FTBFS: mypy-stubs/mistune/scanner.pyi:19:52: error: Missing type parameters for generic type "Match" [type-arg] Added tag(s) pending. -- 1058270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059894: marked as done (dkms - fails autopkgtest with Linux 6.6)
Your message dated Wed, 3 Jan 2024 11:41:51 +0100 with message-id <800d2084-dd60-5747-6f39-b306e8003...@debian.org> and subject line Re: Bug#1059894: dkms - fails autopkgtest with Linux 6.6 has caused the Debian Bug report #1059894, regarding dkms - fails autopkgtest with Linux 6.6 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 ow...@bugs.debian.org immediately.) -- 1059894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dkms Version: 3.0.12-1 Severity: serious The dkms autopkgtest fails with Linux 6.6. The only output is: | 143s autopkgtest [15:40:46]: test run_test.sh: [--- | 143s Using kernel 6.6.9-amd64/x86_64 | 143s Preparing a clean test environment | 146s Test framework file hijacking | 146s Adding the test module by version (expected error) | 146s Adding the test module by directory | 148s Adding the test module again (expected error) | 148s Adding the test module by version (expected error) | 148s Building the test module | 154s Building the test module again | 155s Building the test module with bad sign_file path in framework file | 160s Building the test module with bad mok_signing_key path in framework file | 164s Building the test module with bad mok_certificate path in framework file | 168s Building the test module with path contains variables in framework file | 173s modinfo: ERROR: Module /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_test.ko not found. | 173s autopkgtest [15:41:16]: test run_test.sh: ---] | 173s run_test.sh FAIL non-zero exit status 1 For the full log, see https://ci.debian.net/packages/d/dkms/testing/amd64/41463228/ Bastian -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, "Metamorphosis", stardate 3219.8 --- End Message --- --- Begin Message --- Version: 3.0.12-3 On 03/01/2024 09.49, Bastian Blank wrote: The dkms autopkgtest fails with Linux 6.6. The only output is: | 173s modinfo: ERROR: Module /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_test.ko not found. Already fixed :-) You recently enabled module compression which broke the dkms tests because they used a hardcoded list of distro/compression combinations. I'm now trying to parse that from .config (any only override it for distros that handle it differently). Andreas--- End Message ---
Bug#1058250: marked as done (urwid: FTBFS: TypeError: list indices must be integers or slices, not Key)
Your message dated Wed, 03 Jan 2024 10:25:17 + with message-id and subject line Bug#1058250: fixed in urwid 2.1.2-4.2 has caused the Debian Bug report #1058250, regarding urwid: FTBFS: TypeError: list indices must be integers or slices, not Key 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 ow...@bugs.debian.org immediately.) -- 1058250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: urwid Version: 2.1.2-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs > build/html # HTML generator > Running Sphinx v7.2.6 > making output directory... done > WARNING: html_static_path entry 'tools/static' does not exist > building [mo]: targets for 0 po files that are out of date > writing output... > building [html]: targets for 29 source files that are out of date > updating environment: [new config] 29 added, 0 changed, 0 removed > [2Kreading sources... [ 3%] changelog > [2Kreading sources... [ 7%] examples/index > [2Kreading sources... [ 10%] index > [2Kreading sources... [ 14%] manual/canvascache > [2Kreading sources... [ 17%] manual/displayattributes > [2Kreading sources... [ 21%] manual/displaymodules > [2Kreading sources... [ 24%] manual/encodings > [2Kreading sources... [ 28%] manual/index > [2Kreading sources... [ 31%] manual/mainloop > [2Kreading sources... [ 34%] manual/overview > [2Kreading sources... [ 38%] manual/textlayout > [2Kreading sources... [ 41%] manual/userinput > [2Kreading sources... [ 45%] manual/widgets > [2Kreading sources... [ 48%] reference/attrspec > [2Kreading sources... [ 52%] reference/canvas > [2Kreading sources... [ 55%] reference/command_map > [2Kreading sources... [ 59%] reference/constants > [2Kreading sources... [ 62%] reference/deprecated > [2Kreading sources... [ 66%] reference/display_modules > [2Kreading sources... [ 69%] reference/exceptions > [2Kreading sources... [ 72%] reference/global_settings > [2Kreading sources... [ 76%] reference/index > [2Kreading sources... [ 79%] reference/list_walkers > [2Kreading sources... [ 83%] reference/main_loop > [2Kreading sources... [ 86%] reference/meta > [2Kreading sources... [ 90%] reference/signals > [2Kreading sources... [ 93%] reference/text_layout > [2Kreading sources... [ 97%] reference/widget > [2Kreading sources... [100%] tutorial/index > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > copying assets... copying static files... done > copying extra files... done > done > [2Kwriting output... [ 3%] changelog > [2Kwriting output... [ 7%] examples/index > [2Kwriting output... [ 10%] index > [2Kwriting output... [ 14%] manual/canvascache > [2Kwriting output... [ 17%] manual/displayattributes > [2Kwriting output... [ 21%] manual/displaymodules > [2Kwriting output... [ 24%] manual/encodings > [2Kwriting output... [ 28%] manual/index > [2Kwriting output... [ 31%] manual/mainloop > [2Kwriting output... [ 34%] manual/overview > [2Kwriting output... [ 38%] manual/textlayout > [2Kwriting output... [ 41%] manual/userinput > [2Kwriting output... [ 45%] manual/widgets > [2Kwriting output... [ 48%] reference/attrspec > [2Kwriting output... [ 52%] reference/canvas > [2Kwriting output... [ 55%] reference/command_map > [2Kwriting output... [ 59%] reference/constants > [2Kwriting output... [ 62%] reference/deprecated > [2Kwriting output... [ 66%] reference/display_modules > [2Kwriting output... [ 69%] reference/exceptions > [2Kwriting output... [ 72%] reference/global_settings > [2Kwriting output... [ 76%] reference/index > [2Kwriting output... [ 79%] reference/list_walkers > [2Kwriting output... [ 83%] reference/main_loop > [2Kwriting output... [ 86%] reference/meta > [2Kwriting output... [ 90%] reference/signals > [2Kwriting output... [ 93%] reference/text_layout > [2Kwriting output... [ 97%] reference/widget > [2Kwriting output... [100%] tutorial/index > > /<>/urwid/decoration.py:docstring of > urwid.decoration.WidgetDecoration.selectable:10: WARNING: more than one > target found for cross-reference 'keypress': urwid.Widget.keypress, > urwid.Edit.keypress, urwid.IntEdit.keypress, urwid.Button.keypress, > urwid.CheckBox.keypress,
Bug#1059785: marked as done (benchmark breaks ABI without SONAME bump)
Your message dated Wed, 03 Jan 2024 10:09:33 + with message-id and subject line Bug#1059785: fixed in benchmark 1.8.3-2 has caused the Debian Bug report #1059785, regarding benchmark breaks ABI without SONAME bump 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 ow...@bugs.debian.org immediately.) -- 1059785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: benchmark Control: found -1 benchmark/1.8.3-1 Severity: serious Tags: sid trixie Dear maintainer(s), With a recent upload of benchmark the autopkgtest of pytorch fails in testing when that autopkgtest is run with the binary packages of benchmark from unstable. It passes when run with only packages from testing. In tabular form: passfail benchmark from testing1.8.3-1 pytorchfrom testing2.0.1+dfsg-5 all others from testingfrom testing I copied some of the output at the bottom of this report. This looks very much like benchmark dropped a symbol from its shared library without a SONAME bump. Can you please investigate and clarify? Currently this is blocking the migration of benchmark to testing, as I reported in bug 1056202, but because benchmark is a key package, that didn't lead to its removal. The release team has also received a request to rebuild ros2-performance-test-fixture (bug 1057304), so it seems more packages are affected. Paul [1] https://qa.debian.org/excuses.php?package=benchmark https://ci.debian.net/data/autopkgtest/testing/arm64/p/pytorch/41359814/log.gz 1276s /usr/lib/libtorch-test/c10_intrusive_ptr_benchmark: symbol lookup error: /usr/lib/libtorch-test/c10_intrusive_ptr_benchmark: undefined symbol: _ZN9benchmark8internal9BenchmarkC2EPKc 1276s autopkgtest [08:27:24]: test 44_of_98__cpptest__c10_intrusive_ptr_benchmark OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: benchmark Source-Version: 1.8.3-2 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of benchmark, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated benchmark package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 Jan 2024 20:41:43 +0100 Source: benchmark Binary: libbenchmark-dev libbenchmark-tools libbenchmark1.8.3 libbenchmark1.8.3-dbgsym Architecture: source amd64 all Version: 1.8.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Description: libbenchmark-dev - Microbenchmark support library, development files libbenchmark-tools - Microbenchmark support library, tools and documentation libbenchmark1.8.3 - Microbenchmark support library, shared library Closes: 1059785 Changes: benchmark (1.8.3-2) unstable; urgency=medium . * [6670303] Update lib name from 1debian to 1.8.3. (Closes: #1059785) Checksums-Sha1: 6e77a04565b67d6ad23080c03275d356b28a64dc 2284 benchmark_1.8.3-2.dsc ca64ffdd3e981687c44e474253ee78c24c0fbe78 7396 benchmark_1.8.3-2.debian.tar.xz 69a424f68d9aeaf31a185b524b0163e6904dc419 8119 benchmark_1.8.3-2_amd64.buildinfo 3f016efeffec4156317924bbacd49711e242355f 93572 libbenchmark-dev_1.8.3-2_amd64.deb aede5f46956d374c856f9e6f40b390cc30c2a740 21336 libbenchmark-tools_1.8.3-2_all.deb 82001447f7eeabc69f565dbb2a567c79ee3d047f 1839072 libbenchmark1.8.3-dbgsym_1.8.3-2_amd64.deb caffd4239c9ccc450ca46777c357d3147d8b8c12 127896 libbenchmark1.8.3_1.8.3-2_amd64.deb Checksums-Sha256: 5a492ec4a00b3dd6ca87c0072b938f09f0e2443f3930b1c83fa4d6af31d90344 2284 benchmark_1.8.3-2.dsc cae234b78862b801d1d5e18279b464fc9316aa7db3b43ce6f6d1e608578686f0 7396 benchmark_1.8.3-2.debian.tar.xz cb700a9e7889fca02ec4c8988d7d1154ba6eb73905c7c009f461af9db0eca05d 8119 benchmark_1.8.3-2_amd64.buildinfo 2d477b569fde78406790f3f8f7bd3c7a34842a3ee1cd95c1f459d5d1bc25c7ab 93572 libbenchmark-dev_1.8.3-2_amd64.deb 42a72d3793c19d0b028a0e767fe7c309c1563af26357ca8655e5b272879f 21336
Processed: Bug#1058250 marked as pending in urwid
Processing control commands: > tag -1 pending Bug #1058250 [src:urwid] urwid: FTBFS: TypeError: list indices must be integers or slices, not Key Added tag(s) pending. -- 1058250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055564: marked as done (pyalsaaudio ftbfs with Python 3.12)
Your message dated Wed, 03 Jan 2024 09:53:59 + with message-id and subject line Bug#1055564: fixed in pyalsaaudio 0.10.0-0.1 has caused the Debian Bug report #1055564, regarding pyalsaaudio ftbfs with Python 3.12 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 ow...@bugs.debian.org immediately.) -- 1055564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyalsaaudio Version: 0.8.4-1.1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 pyalsaaudio ftbfs with Python 3.12: [...] I: pybuild base:310: cd '/<>/.pybuild/cpython3_3.12_alsaaudio/build'; python3.12 /<>/test.py -v Traceback (most recent call last): File "/<>/test.py", line 11, in import alsaaudio ImportError: /<>/.pybuild/cpython3_3.12_alsaaudio/build/alsaaudio.cpython-312-x86_64-linux-gnu.so: undefined symbol: PyUnicode_AS_DATA E: pybuild pybuild:395: test: plugin custom failed with: exit code=1: cd '/<>/.pybuild/cpython3_3.12_alsaaudio/build'; python3.12 /<>/test.py -v --- End Message --- --- Begin Message --- Source: pyalsaaudio Source-Version: 0.10.0-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of pyalsaaudio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated pyalsaaudio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jan 2024 09:59:33 +0100 Source: pyalsaaudio Architecture: source Version: 0.10.0-0.1 Distribution: unstable Urgency: medium Maintainer: Paul Brossier Changed-By: Matthias Klose Closes: 980244 1055564 Changes: pyalsaaudio (0.10.0-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version. Closes: #980244. - Ready for Python 3.12. Closes: #1055564. * Don't patch the current test to succeed in case of a missing sound card and mark it as flaky instead. Checksums-Sha1: 6fd09ebc873be2eab4999c0cbfd6d0e9f4eb492e 2080 pyalsaaudio_0.10.0-0.1.dsc 71227ab54c8d07d07636692aa4272910ff2ccdc7 637432 pyalsaaudio_0.10.0.orig.tar.gz 9d3c4f4aaccd2ba6946a2f910386b9a471c8f648 4780 pyalsaaudio_0.10.0-0.1.debian.tar.xz d440efbb3ed816bb50791cc942a4724c1ec6c482 8146 pyalsaaudio_0.10.0-0.1_source.buildinfo Checksums-Sha256: fef6ae859b661f8fbc6e9bd1fc27d79d1bb0b0bb9ecec60b41257d193ec4aeb0 2080 pyalsaaudio_0.10.0-0.1.dsc e21175500a2bd310ae3867e7991639defc1e2a5c92cf1b9f7083296b346738ab 637432 pyalsaaudio_0.10.0.orig.tar.gz 2040d5ccc5bcc3f35a83a17800f33f9395d20ae6436298ef4dc15c81b084c0c3 4780 pyalsaaudio_0.10.0-0.1.debian.tar.xz 75aa5b50e59ca2e56a36c749e00a9541a6e66c2f2ea7d8f460f4931b837af1f9 8146 pyalsaaudio_0.10.0-0.1_source.buildinfo Files: e94d2c1e742023b13f260b341c257843 2080 python optional pyalsaaudio_0.10.0-0.1.dsc 720b2e1a47a5fdb587ea1b4eabbd23e6 637432 python optional pyalsaaudio_0.10.0.orig.tar.gz 4b347fb2a63aa2b31ce0cfa3b42bb599 4780 python optional pyalsaaudio_0.10.0-0.1.debian.tar.xz 985998f95c0cbfec697a38dcd0e745b3 8146 python optional pyalsaaudio_0.10.0-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmWVJXIQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9cL4D/9sCejswPodeoMv4fr7lzqgtazzzBt6PhEM hBtysIRdKjXdRcf8//IY9FJqKjG3I8uIwgUIckhfBsa6qAUNhTrJ5dCKsHerT8YY JGLeeDmiOcvA/iuRazmilsjxB7eqU70K20NYza9v2TCxU19V0q6N+ShHK/g3tkSP 95eW1kyw+IH8bHifAanposOqYeG69f+2SpO09hjBe2FLiJQEjj6nbL4Vh5pjwpnG LpWE8UwOXge6MlZ1oRXgLx0GZFp/6p8dRJSF/TQjsW2BdRI02qGQq6VGhqlf/K+m 79F88Bwq1BzxL6trKSu4xf5USIHzmDvL5Mc0QDbS1fi3qbG8CkR0Qjxrb9QS7N8E H0mquZF/WRaHgaRBsUmSJJmOhVzT4gYf+SDvWoA3aoXVy3innY84y3ckZFjLjLhZ 5O3QRN9lu5OCKIgyXUAAGcUYZ0S9/uyh71xdPDfXP4CBuWOnup+Qse6WFkUzZOQH 7xJ9eZhWt80wKspW3OT3OKwwS7w0JvMpekUJREnJ63GIutnj+UtEDK7CBgm/3V2A 25E22fRlTF8ujt89JlFprEgI/l05mZxKdUyr6fREx7PknaX8hslm893OGiRnuwCy 5aT4Qrb8zNMaA5Ycmq8NgvKp0JNjtZlbMQiJFbPXhjKKqOqNzL8DjBGUzJyAOKcg MMnp1PgErw== =do7P -END PGP SIGNATURE End Message ---
Bug#1058250: marked as pending in urwid
Control: tag -1 pending Hello, Bug #1058250 in urwid reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/urwid/-/commit/fdd02a88bfab34fa5368b74f3b6c9f57068691bb * Pull more patches for Python 3.12 compatibility. Closes: #1058250. (this message was generated automatically) -- Greetings https://bugs.debian.org/1058250
Bug#1059894: dkms - fails autopkgtest with Linux 6.6
Package: dkms Version: 3.0.12-1 Severity: serious The dkms autopkgtest fails with Linux 6.6. The only output is: | 143s autopkgtest [15:40:46]: test run_test.sh: [--- | 143s Using kernel 6.6.9-amd64/x86_64 | 143s Preparing a clean test environment | 146s Test framework file hijacking | 146s Adding the test module by version (expected error) | 146s Adding the test module by directory | 148s Adding the test module again (expected error) | 148s Adding the test module by version (expected error) | 148s Building the test module | 154s Building the test module again | 155s Building the test module with bad sign_file path in framework file | 160s Building the test module with bad mok_signing_key path in framework file | 164s Building the test module with bad mok_certificate path in framework file | 168s Building the test module with path contains variables in framework file | 173s modinfo: ERROR: Module /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_test.ko not found. | 173s autopkgtest [15:41:16]: test run_test.sh: ---] | 173s run_test.sh FAIL non-zero exit status 1 For the full log, see https://ci.debian.net/packages/d/dkms/testing/amd64/41463228/ Bastian -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, "Metamorphosis", stardate 3219.8
