Bug#1064554: jruby fails to build from source in unstable
Source: jruby Version: 9.4.5.0+ds-1 Severity: serious Dear Maintainer, When building jruby in unstable, the following error occurs: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install- plugin:3.1.1:install (default-install) on project jruby-parent: Failed to install artifact org.jruby:jruby-parent:pom:9.4.5.0: /<>/debian/maven-repo/org/jruby/jruby-parent/9.4.5.0/jruby- parent-9.4.5.0.pom (Permission denied) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<>/jruby-9.4.5.0\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/jruby-9.4.5.0\+ds/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings- debian.xml -Ddebian.dir=/<>/jruby-9.4.5.0\+ds/debian -Dmaven.repo.local=/<>/jruby-9.4.5.0\+ds/debian/maven-repo --batch- mode -Djruby.revision=9.4.5.0\+ds-1build1\~ppa2 -Pmain,complete,dist -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-02-24T07:14:56Z This is due to maven-repo-helper copying symlinks to jruby poms rather than poms themselves. One possible solution is to copy jruby poms manually in execute_after_dh_auto_configure: # copy jruby poms rather than links, because the build will try to patch them for p in jruby jruby-parent jruby-base jruby-core jruby-artifacts ; do \ rm debian/maven-repo/org/jruby/$$p/* ;\ mkdir debian/maven-repo/org/jruby/$$p/debian ; \ cp /usr/share/maven-repo/org/jruby/$$p/debian/* debian/maven- repo/org/jruby/$$p/debian/ ;\ done -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-17-generic (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1064553: libgdiplus: build-error on current sid (all warnings being treated as errors)
Source: libgdiplus
Version: 6.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
libgdiplus FTBFS on current sid:
make[7]: Entering directory '/dev/shm/x/libgdiplus-6.1+dfsg/gtest_build'
[ 12%] Building CXX object googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
In file included from
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-all.cc:42:
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:
In function 'bool testing::internal::StackGrowsDown()':
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1301:24:
error: 'dummy' may be used uninitialized [-Werror=maybe-uninitialized]
1301 | StackLowerThanAddress(, );
| ~^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1290:13:
note: by argument 1 of type 'const void*' to 'void
testing::internal::StackLowerThanAddress(const void*, bool*)' declared here
1290 | static void StackLowerThanAddress(const void* ptr, bool* result) {
| ^
/tmp/x/libgdiplus-6.1+dfsg/external/googletest/googletest/src/gtest-death-test.cc:1299:7:
note: 'dummy' declared here
1299 | int dummy;
| ^
cc1plus: all warnings being treated as errors
make[7]: *** [googletest/CMakeFiles/gtest.dir/build.make:76:
googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o] Error 1
cu Andreas
Processed: telepathy-farstream: diff for NMU version 0.6.2-1.2
Processing control commands: > tags 1060972 + patch Bug #1060972 [src:telepathy-farstream] telepathy-farstream: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: TelepathyFarstream-0.6.gir] Error 1 Added tag(s) patch. > tags 1060972 + pending Bug #1060972 [src:telepathy-farstream] telepathy-farstream: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: TelepathyFarstream-0.6.gir] Error 1 Added tag(s) pending. -- 1060972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060972: telepathy-farstream: diff for NMU version 0.6.2-1.2
Control: tags 1060972 + patch Control: tags 1060972 + pending Dear maintainer, I've prepared an NMU for telepathy-farstream (versioned as 0.6.2-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru telepathy-farstream-0.6.2/debian/changelog telepathy-farstream-0.6.2/debian/changelog --- telepathy-farstream-0.6.2/debian/changelog 2021-01-01 14:35:16.0 +0100 +++ telepathy-farstream-0.6.2/debian/changelog 2024-02-24 07:37:17.0 +0100 @@ -1,3 +1,11 @@ +telepathy-farstream (0.6.2-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add the gir1.2-glib-2.0-dev build dependency, needed for GObject-2.0.gir. +(Closes: #1060972) + + -- Pino Toscano Sat, 24 Feb 2024 07:37:17 +0100 + telepathy-farstream (0.6.2-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru telepathy-farstream-0.6.2/debian/control telepathy-farstream-0.6.2/debian/control --- telepathy-farstream-0.6.2/debian/control2014-09-16 20:02:51.0 +0200 +++ telepathy-farstream-0.6.2/debian/control2024-02-24 07:31:51.0 +0100 @@ -12,6 +12,7 @@ libfarstream-0.2-dev (>= 0.2.0), libtelepathy-glib-dev (>= 0.19.0), gobject-introspection, + gir1.2-glib-2.0-dev, gtk-doc-tools Standards-Version: 3.9.5 Homepage: http://telepathy.freedesktop.org/
Processed: severity of 1062097 is important, reopening 1062097, tagging 1062097
Processing commands for cont...@bugs.debian.org:
> severity 1062097 important
Bug #1062097 {Done: John Goerzen } [src:gensio] gensio:
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> reopen 1062097
Bug #1062097 {Done: John Goerzen } [src:gensio] gensio:
NMU diff for 64-bit time_t transition
'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 gensio/2.8.2-5.
> tags 1062097 + pending
Bug #1062097 [src:gensio] gensio: NMU diff for 64-bit time_t transition
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1064128: your mail
I'm working on upgrading with disabled gstreamer. Removing the optional dependency is not sufficient, which is how it used to work - it still fails at the same point. Either way, fixing this is not the only issue currently. ocaml-lastfm needs fixing first before liquidsoap can migrate to testing [1]. If upstream doesn't fix that soon, I'll just drop that and upload with a fixed/removed gstreamer [1] https://github.com/savonet/ocaml-lastfm/pull/3 Cheers Kyle 24 Feb 2024 06:27:27 Bo YU : > Hi, > On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote: >> ...and 2.2.4 also fails to build: >> https://github.com/savonet/liquidsoap/issues/3752 > > Thanks. >> >> $ make >> : warning: "_FORTIFY_SOURCE" redefined >> : note: this is the location of the previous definition >> : warning: "_FORTIFY_SOURCE" redefined >> : note: this is the location of the previous definition >> : warning: "_FORTIFY_SOURCE" redefined >> : note: this is the location of the previous definition >> : warning: "_FORTIFY_SOURCE" redefined >> : note: this is the location of the previous definition >> File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51: >> 314 | (Decoder.test_file ~log ~mimes:mime_types#get >> ^^ >> Error: This expression has type string list >> but an expression was expected of type string list option >> make: *** [Makefile:4: build] Error 1 > > Yeah, I got this error after upgrading 2.2.4 also. > And it seems upstream suggests to ship the package wihtout gstreamer: > https://github.com/savonet/liquidsoap/discussions/3751#discussioncomment-8524446 > > It will cost more time for me how to disable this on Debian packaging. > > > -- > Regards, > -- > Bo YU
Bug#1064128: your mail
Hi, On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote: ...and 2.2.4 also fails to build: https://github.com/savonet/liquidsoap/issues/3752 Thanks. $ make : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51: 314 | (Decoder.test_file ~log ~mimes:mime_types#get ^^ Error: This expression has type string list but an expression was expected of type string list option make: *** [Makefile:4: build] Error 1 Yeah, I got this error after upgrading 2.2.4 also. And it seems upstream suggests to ship the package wihtout gstreamer: https://github.com/savonet/liquidsoap/discussions/3751#discussioncomment-8524446 It will cost more time for me how to disable this on Debian packaging. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#919035: marked as done (elpa-persp-projectile: broken with recent elpa-perspective)
Your message dated Sat, 24 Feb 2024 04:04:55 + with message-id and subject line Bug#919035: fixed in persp-projectile 1:1.0.0+git20210618.4e374d7-1 has caused the Debian Bug report #919035, regarding elpa-persp-projectile: broken with recent elpa-perspective 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.) -- 919035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-persp-projectile Version: 1:0.2.0-2 Severity: grave `perspectives-hash' is now a function that returns something which does not pass `hash-table-p'. So patching is required. Since this package is up for adoption, I won't be doing that patching myself. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: persp-projectile Source-Version: 1:1.0.0+git20210618.4e374d7-1 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of persp-projectile, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated persp-projectile 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: Sat, 24 Feb 2024 11:51:42 +0800 Source: persp-projectile Architecture: source Version: 1:1.0.0+git20210618.4e374d7-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen Team Changed-By: Sean Whitton Closes: 919035 Changes: persp-projectile (1:1.0.0+git20210618.4e374d7-1) unstable; urgency=medium . * Team upload. . [ Nicholas D Steeves ] * Drop emacs24 from Enhances (package does not exist in bullseye). . [ Xiyue Deng ] * Team upload. * Sync to latest upstream head. - Fix compatibility with elpa-perspective. Closes: #919035. - Refresh patches. * Modernize d/watch. * Migrate from d/compat to debhelper-compat and update to version 13. * Fix typo in d/control. * Update Standards-Version to 4.6.2. No change needed. * Drop parameter "--parallel" in d/rules. * Drop Built-Using from binary package. This package has no relevant licensing requirements. * Drop unused and update renamed lintian overrides. * Update year and Upstream-Contact in d/copyright. * Add d/upstream/metadata. Checksums-Sha1: 0c5efd6768074d155f53e8670327c47df5bb982d 2306 persp-projectile_1.0.0+git20210618.4e374d7-1.dsc e5b02a83bfa541cc0407fdcce7a8f397f3a80e38 346204 persp-projectile_1.0.0+git20210618.4e374d7.orig.tar.xz ca658c2da738a533ac1d407ff1897c64225430aa 2748 persp-projectile_1.0.0+git20210618.4e374d7-1.debian.tar.xz Checksums-Sha256: 25c55ededf4533997da0dc03ad61127916f6b59f428814718c65210cf2c592b5 2306 persp-projectile_1.0.0+git20210618.4e374d7-1.dsc dbd55b7f4c8f6146ab144e9e77b9137e7ea72869f02f960072777b496c38fcaf 346204 persp-projectile_1.0.0+git20210618.4e374d7.orig.tar.xz cfe3e0a2e8675f4180c5141cecc5e99737a7958a13b5fab4b63940febf809856 2748 persp-projectile_1.0.0+git20210618.4e374d7-1.debian.tar.xz Files: ba2b82ba7cf35c800244dd02ed92a20e 2306 lisp optional persp-projectile_1.0.0+git20210618.4e374d7-1.dsc 6839aaed6ee55eb46b2bb1f18d658a2d 346204 lisp optional persp-projectile_1.0.0+git20210618.4e374d7.orig.tar.xz 6a23d53a0d0569955a00f6827f8ca60e 2748 lisp optional persp-projectile_1.0.0+git20210618.4e374d7-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmXZZ/oACgkQaVt65L8G YkBo6A/+NKtNaJYLdusSyg6EvHbsKKe1DyInlUb5LAw/hjNH1QY5mZ5PGY7uFwVm GwmUnH+bKdssqPYAbFMQYajAM+BAAfKX4k8s58NB5AhJtWwkDIfCdtm3H9JkWQsE BYfipoBDKYA/QkrLNLznDEK7FeqvREzeA/hmY2y8QfNjodRqLb3rsJMn4KPJjfsu 6yxxGKmwfNmQ7hNgwFgszBnkawnTnaD7eYT80ODspJ0IFVYYrM/BT2QEZfiGaCgr THA0PmDjglqTnDkSTj5Upj/prsYgGaC2ldlsCSTfpoHA2HXn7X3vepZvUZoa2oDf EzPSlg4dhe1xnOQv57N5nchmPEYunX4m4/BmRkfo6DFQA6XP6shDX0YiIHrirbvG G41lyJqB0VoUakDNm5tEO0AY8zYii8zqdR2aSkzCbwZMdtbxO30oikHfyFXTpbhS kCgl0E5qm7QHZ6efprrpo89Y3wuRJbaoT3QY9cRhKnm6dG3bq62YxHe4Tgamlg5W d9AEYqXE71wnTYFRhRdlhKfQDrmsUq5n5ps5AWJJnl/3ZnibSQeRfDu41j060Ee8 evQenoJ46pcPkbNmqEraoSSmAi3QIKjn4jSPyS3xLZwf8nvgsi3hYs/ryvJemfFC
Bug#1035903: marked as done (tracker: datetime build tests failing on 32-bit)
Your message dated Sat, 24 Feb 2024 03:21:32 + with message-id and subject line Bug#1035903: fixed in tracker 3.7~beta-2 has caused the Debian Bug report #1035903, regarding tracker: datetime build tests failing on 32-bit 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.) -- 1035903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tracker Version: 3.5.0-1 Severity: serious Tags: ftbfs Forwarded: https://gitlab.gnome.org/GNOME/tracker/-/issues/398 Tracker build tests are failing on 32-bit architectures. See the upstream issue for more details. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: tracker Source-Version: 3.7~beta-2 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of tracker, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated tracker 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: Fri, 23 Feb 2024 21:50:34 -0500 Source: tracker Built-For-Profiles: noudeb Architecture: source Version: 3.7~beta-2 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1035903 Changes: tracker (3.7~beta-2) experimental; urgency=medium . * Revert a commit & 2 fixups that broke build tests on 32-bit (Closes: #1035903) Checksums-Sha1: 7222c85e37e63d1b1c32c3f146164244e8e39831 2865 tracker_3.7~beta-2.dsc 06213cc611a5bccbcecb50c69f6db97eadebc735 26836 tracker_3.7~beta-2.debian.tar.xz c701c1d47c0f51b902ef15cdcd2908415dabc8ef 14322 tracker_3.7~beta-2_source.buildinfo Checksums-Sha256: 97eb70c3c1d899f118db5131e91f7fa8896c57f7af19f6eaea591c5df00274b8 2865 tracker_3.7~beta-2.dsc ec5b0ff4ae5c6ad7cfb2ba18c7c57b5e08b8752b1a1f02af7a2312df1cf2c547 26836 tracker_3.7~beta-2.debian.tar.xz 7d1f31a4a3770c3f1b44d9523a00b84766906f3efe3b8facc39eba020f404620 14322 tracker_3.7~beta-2_source.buildinfo Files: 47099b96df697f59cf998ead3fdace6f 2865 utils optional tracker_3.7~beta-2.dsc 4ceaf6bbcaeb45ca00e170ff62b3ee58 26836 utils optional tracker_3.7~beta-2.debian.tar.xz 83b2ac275eec89a6c35ae05e54ebe35d 14322 utils optional tracker_3.7~beta-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXZWbgACgkQ5mx3Wuv+ bH0QaQ/+LKnxs7z/2zWSEiCV22qPUAiP6CN+yMNiaBtGc5BRC/k69e0dLWpktLPa u18HiltkEVuODFppvs6p6j/15uyze4B+btAVBBXVNYz8ihCLulJjBwkG8u8+0n1U w0FfCJ9e5j6XsvgJodzTxkMHSYwaMz+/5q4gq3la+seFyyPUvhzZE0LAP3x23gKs zqNK2ThZGVttCitt/UIaJgnU2izrvQyKmcJXYmPqBH2bgbDfMdU1R7x0zfSUSx9G qr2C+VINztL7ZqUKnnrwO/5kv9lscrGezUYXSrKqMoToJbQfjNPzETrEmtS/k7Qe wsXJNs/GNYCDAIM6KXJViRQHUmQefNYmXXAasPG4SizHGk9JxCMcDyEFSlrtMb6q KRkkAg/MoNMR/pZTey0q9A8QrOJ5ZR9MvCXPouBihAbUAr1jXU6gGIJALpf5lxtC AlddETnX0OddLgr/flCTTPlRTwwGrQtivitPKR/TvGK2sO0IMjGxw8N9H/FjLwtS kdUuBMGnGLtAQ08CJGwoWGsNkmghkpJyrc8D3ocYwwoK9oJ4UpnG4xQxz8CqJLmE 1nQr0mzagACKJljrQ/xv9YInOUGhkEQolZAkxGSZyccBFgNBunb7tMXir6Hzvbjl U4Ekr50uv8ar2JoMXcatcSzXMCiKJy2anz00G5/grtAq3vSXl8o= =RGy6 -END PGP SIGNATURE- pgpWVOci7zp5e.pgp Description: PGP signature --- End Message ---
Processed: Bug#1035903 marked as pending in tracker
Processing control commands: > tag -1 pending Bug #1035903 [src:tracker] tracker: datetime build tests failing on 32-bit Added tag(s) pending. -- 1035903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035903: marked as pending in tracker
Control: tag -1 pending Hello, Bug #1035903 in tracker 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/gnome-team/tracker/-/commit/bb121d852a9babfd103d6e899753534d43d1629f Revert a commit & 2 fixups that broke build tests on 32-bit Closes: #1035903 (this message was generated automatically) -- Greetings https://bugs.debian.org/1035903
Bug#1064548: tracker-miners: bmp-basic-1 test fails on big-endian
Source: tracker-miners Version: 3.5.0~beta-1 Severity: serious Tags: ftbfs experimental help X-Debbugs-CC: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390x Forwarded: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/309 tracker-miners added new tests in 3.5.0.beta including bmp-basic-1. This test is failing on the big endian architectures s390x and ppc64. In Debian, we could ignore this test failure since this issue was only discovered via a brand new test. That function has likely been broken on those architectures in Debian for a long time. But it would be much nicer to see it fixed. Thank you, Jeremy Bícha
Bug#1061966: closed by Debian FTP Masters (reply to Steve Langasek ) (Bug#1061966: fixed in audit 1:3.1.2-2.1~exp2)
Thanks to discussion on debian-devel, it's become clear that a rename of libaudit1 is not required, only of libauparse0. Please find attached a follow-on patch for yet another NMU to experimental, reverting the libaudit package name change. On Fri, Feb 02, 2024 at 09:56:51AM -0800, Steve Langasek wrote: > Really-really-really > > On Fri, Feb 02, 2024 at 09:36:27AM -0800, Steve Langasek wrote: > > Helmut pointed out the preinst.in files didn't actually include the token to > > be substituted, but instead still had the hard-coded architecture path :/ > > > > Attached is the really-really-fixed-this-time NMU patch. > > > > > > On Fri, Feb 02, 2024 at 08:56:32AM -0800, Steve Langasek wrote: > > > By happenstance I noticed that I had mindlessly hard-coded the > > > amd64-specific multiarch path into the preinsts. > > > > > > Please find a really-fixed-this-time NMU patch for experimental. > > > > > > > > > On Wed, Jan 31, 2024 at 12:41:48PM -0800, Steve Langasek wrote: > > > > Sorry, and thanks for bearing with me. Uploaded to experimental again; > > > > updated full NMU debdiff attached. > > > > > > > > On Wed, Jan 31, 2024 at 09:31:25PM +0100, Helmut Grohne wrote: > > > > > Control: reopen -1 > > > > > > > > > > On Wed, Jan 31, 2024 at 10:12:03AM +, Debian Bug Tracking System > > > > > wrote: > > > > > > #1061966: file loss due to combining time64 + /usr-move > > > > > > > > > > > > It has been closed by Debian FTP Masters > > > > > > (reply to Steve Langasek > > > > > > ). > > > > > > > > > > I fear this is not fixed. > > > > > > > > > > > /usr/lib/x86_64-linux-gnu/libaudit.so.1 and > > > > > > > > > > This is fixed. > > > > > > > > > > > /usr/lib/x86_64-linux-gnu/libaudit.so.1.0.0 have been moved from > > > > > > > > > > This not. > > > > > > > > > > > libaudit1 to libaudit1t64 in this upload and these files have > > > > > > formerly > > > > > > been installed below /lib in bookworm. Hence, we are creating > > > > > > exactly > > > > > > the problem that the file move moratorium was meant to prevent. > > > > > > > > > > > > /usr/lib/x86_64-linux-gnu/libauparse.so.0 and > > > > > > > > > > This is fixed. > > > > > > > > > > > /usr/lib/x86_64-linux-gnu/libauparse.so.0.0.0 likewise move from > > > > > > > > > > This not. > > > > > > > > > > > libauparse0 to libauparse0t64 and create the same problem. > > > > > > > > > > > > DEP17 classifies this a P1 and proposed mitigations M7 and M8. In > > > > > > this > > > > > > case, I recommend not exercising Conflicts (M7), because they are > > > > > > known > > > > > > to be unreliable and libaudit1 is part of the the essential set > > > > > > (login > > > > > > depends on it). Instead, their respective preinst script should > > > > > > create > > > > > > protective diversions > > > > > > > > > > > > dpkg-divert --package libaudit1t64 --no-rename --divert > > > > > > /lib/x86_64-linux-gnu/libaudit.so.1.usr-is-merged > > > > > > /lib/x86_64-linux-gnu/libaudit.so.1 > > > > > > > > > > > > for each of the affected files with their aliased location. In this > > > > > > case > > > > > > - since we cannot use Conflicts - we cannot get rid of these > > > > > > diversions > > > > > > in postinst. We already have Breaks: libaudit1 (<< ...), but that > > > > > > allows > > > > > > concurrent unpack and hence still allows for the file loss > > > > > > scenario. The > > > > > > diversions should be cleaned up in forky's postinst. > > > > > > > > > > > > I appreciate another upload of audit to experimental to verify the > > > > > > mitigation. > > > > > > > > > > Helmut > > > > > > > > > > > > > -- > > > > Steve Langasek Give me a lever long enough and a Free > > > > OS > > > > Debian Developer to set it on, and I can move the > > > > world. > > > > Ubuntu Developer > > > > https://www.debian.org/ > > > > slanga...@ubuntu.com > > > > vor...@debian.org > > > > > > > diff -Nru audit-3.1.2/debian/changelog audit-3.1.2/debian/changelog > > > > --- audit-3.1.2/debian/changelog2024-01-24 15:05:18.0 > > > > + > > > > +++ audit-3.1.2/debian/changelog2024-01-31 20:39:17.0 > > > > + > > > > @@ -1,3 +1,19 @@ > > > > +audit (1:3.1.2-2.1~exp3) experimental; urgency=medium > > > > + > > > > + * Proper complete fix for usrmerge. Closes: #1061966. > > > > + > > > > + -- Steve Langasek Wed, 31 Jan 2024 20:39:17 + > > > > + > > > > +audit (1:3.1.2-2.1~exp2) experimental; urgency=medium > > > > + > > > > + * Non-maintainer upload. > > > > + * Rename libraries for 64-bit time_t transition. > > > > + * Fix uninstallable packages from the previous upload. > > > > + * Add usrmerge diversions in preinst to protect against file deletion > > > > +due to libraries moving between packages. Closes: #1061966. > > > > + > > > > + -- Steve Langasek Wed, 31 Jan 2024 08:49:07 + > >
Bug#1058670: marked as done (python3-poetry: fail with Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir)
Your message dated Fri, 23 Feb 2024 22:52:14 + with message-id and subject line Bug#1058670: fixed in poetry 1.8.0.dev0~git20240220.cff4d7d5+dfsg-1 has caused the Debian Bug report #1058670, regarding python3-poetry: fail with Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir 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.) -- 1058670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-poetry Version: 1.7.1+dfsg-1 Severity: normal Tags: upstream X-Debbugs-Cc: george.shuk...@gmail.com poetry fails to install packages (`poetry install` for an existing lock file) or to update it (`poetry update`): Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir at /usr/lib/python3/dist-packages/poetry/installation/chef.py:131 in _prepare 127│ ) -> Path: 128│ from subprocess import CalledProcessError 129│ 130│ with ephemeral_environment(self._env.python) as venv: → 131│ env = IsolatedEnv(venv, self._pool) 132│ builder = ProjectBuilder.from_isolated_env( 133│ env, directory, runner=quiet_subprocess_runner 134│ ) 135│ env.install(builder.build_system_requires) According to github bug: https://github.com/python-poetry/poetry/issues/8458 it is caused by conflict (interactions?) with python3-build package. python3-build 0.10.0-1 -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-poetry depends on: ii python3 [python3-supported-min] 3.11.6-1 ii python3-build0.10.0-1 ii python3-cachecontrol 0.13.1-1 ii python3-cleo 2.1.0-2 ii python3-crashtest0.4.1-1 ii python3-dulwich 0.21.6-1+b1 ii python3-fastjsonschema 2.19.0-1 ii python3-importlib-metadata 4.12.0-1 ii python3-installer0.7.0+dfsg1-2 ii python3-keyring 24.3.0-1 ii python3-lockfile 1:0.12.2-3 ii python3-packaging23.2-1 ii python3-pexpect 4.8.0-4 ii python3-pkginfo 1.8.2-2 ii python3-platformdirs 4.1.0-1 ii python3-poetry-core 1.8.1-1 ii python3-pyproject-hooks 1.0.0-2 ii python3-requests 2.31.0+dfsg-1 ii python3-requests-toolbelt1.0.0-2 ii python3-shellingham 1.5.4-1 ii python3-tomli2.0.1-2 ii python3-tomlkit 0.12.1-1 ii python3-trove-classifiers2023.9.19-1 ii python3-virtualenv 20.25.0+ds-1 python3-poetry recommends no packages. python3-poetry suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: poetry Source-Version: 1.8.0.dev0~git20240220.cff4d7d5+dfsg-1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of poetry, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated poetry 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: Thu, 22 Feb 2024 18:12:00 -0300 Source: poetry Architecture: source Version: 1.8.0.dev0~git20240220.cff4d7d5+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 1029480 1058670 1059356 Changes: poetry (1.8.0.dev0~git20240220.cff4d7d5+dfsg-1) experimental; urgency=medium . * New upstream version.
Bug#1058111: marked as done (cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Fri, 23 Feb 2024 22:50:54 +
with message-id
and subject line Bug#1058111: fixed in cmdtest 0.32.14.gcdfe14e-6
has caused the Debian Bug report #1058111,
regarding cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cmdtest
Version: 0.32.14.gcdfe14e-5
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):
> fakeroot debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 28, in
> import yarnlib
> File "/<>/yarnlib/__init__.py", line 22, in
> from .block_parser import BlockParser, BlockError
> File "/<>/yarnlib/block_parser.py", line 19, in
> import cliapp
> File "/usr/lib/python3/dist-packages/cliapp/__init__.py", line 45, in
>
> from .pluginmgr import PluginManager
> File "/usr/lib/python3/dist-packages/cliapp/pluginmgr.py", line 29, in
>
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/cmdtest_0.32.14.gcdfe14e-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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 ---
Source: cmdtest
Source-Version: 0.32.14.gcdfe14e-6
Done: Antonio Terceiro
We believe that the bug you reported is fixed in the latest version of
cmdtest, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro (supplier of updated cmdtest 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: Fri, 23 Feb 2024 16:10:17 -0300
Source: cmdtest
Architecture: source
Version: 0.32.14.gcdfe14e-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Antonio Terceiro
Closes: 1043688 1058111
Changes:
cmdtest (0.32.14.gcdfe14e-6) unstable; urgency=medium
.
[ Debian Janitor ]
* Update standards version to 4.6.1, no changes needed.
.
[ Antonio Terceiro ]
* Pull `imp` from python3-zombie-imp (Closes: #1058111)
.
[ Stefano Rivera ]
* Clean correctly. (Closes: #1043688)
Checksums-Sha1:
a121b15ff85c7b0c8a9d48e14aa917314a0f015a 1513 cmdtest_0.32.14.gcdfe14e-6.dsc
c2a30702e8617d3f964eb5d692b877311b4d209d 4532
cmdtest_0.32.14.gcdfe14e-6.debian.tar.xz
1dd315f740119d094ab0ed0f826569a06880 6917
cmdtest_0.32.14.gcdfe14e-6_source.buildinfo
Checksums-Sha256:
adf23ad79f8c93eeb8b03f3e61fc7b1ec6bc408d4a902881f8d0341376f84094 1513
cmdtest_0.32.14.gcdfe14e-6.dsc
d40886f8193c9cfa08aa3a6b1dd975d14dd09c27bb6bebe1ea1a8a42a82d28ee 4532
cmdtest_0.32.14.gcdfe14e-6.debian.tar.xz
76453858a285d5b0197992b3ff3939d72c159c72d41d0f807c0a15049faa098f 6917
cmdtest_0.32.14.gcdfe14e-6_source.buildinfo
Files:
2b2473315d1be9c1a49414f3dfe3d4dc 1513 devel
Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update
El 30/10/23 a las 18:29, Sven-Haegar Koch escribió:
> Package: isc-dhcp-client
> Version: 4.4.3-P1-4
> Severity: normal
>
> Dear Maintainer,
>
> I am using network manager with /etc/NetworkManager/NetworkManager.conf
>
> [main]
> dhcp=dhclient
>
> and thus using isc-dhcp-client as my DHCP client.
>
> With the update of network-manager 1.44.2-3 the nm-dhcp-helper moved
> from /usr/lib/NetworkManager/ to /usr/libexec/.
>
> Without a fix to /etc/apparmor.d/sbin.dhclient the system now fails to
> activate interfaces using DHCP, logging
>
> audit: type=1400 audit(1698680734.539:50): apparmor="DENIED" operation="exec"
> class="file" profile="/{,usr/}sbin/dhclient"
> name="/usr/libexec/nm-dhcp-helper" pid=7523 comm="dhclient"
> requested_mask="x" denied_mask="x" fsuid=0 ouid=0
>
> The following diff fixes it for me - just duplicating the existing
> rules to the new path:
>
> diff --git a/etc/apparmor.d/sbin.dhclient b/etc/apparmor.d/sbin.dhclient
> index 1acc6b92..b219d688 100644
> --- a/etc/apparmor.d/sbin.dhclient
> +++ b/etc/apparmor.d/sbin.dhclient
> @@ -69,6 +69,8 @@
># Support the new executable helper from NetworkManager.
>/usr/lib/NetworkManager/nm-dhcp-helper Pxrm,
>signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
> + /usr/libexec/nm-dhcp-helper Pxrm,
> + signal (receive) peer=/usr/libexec/nm-dhcp-helper,
>
># Site-specific additions and overrides. See local/README for details.
>#include
> @@ -101,6 +103,21 @@
>network inet6 dgram,
> }
>
> +/usr/libexec/nm-dhcp-helper {
> + #include
> + #include
> + /usr/libexec/nm-dhcp-helper mr,
> +
> + /run/NetworkManager/private-dhcp rw,
> + signal (send) peer=/sbin/dhclient,
> +
> + /var/lib/NetworkManager/*lease r,
> + signal (receive) peer=/usr/sbin/NetworkManager,
> + ptrace (readby) peer=/usr/sbin/NetworkManager,
> + network inet dgram,
> + network inet6 dgram,
> +}
> +
> /usr/lib/connman/scripts/dhclient-script {
>#include
>#include
>
>
> Greetings,
> Sven
Hi!
Really sorry, this has fallen through the cracks.
Could you please confirm the version available in this repo fixes the
issue:
https://debian.pages.debian.net/-/isc-dhcp/-/jobs/5350735/artifacts/aptly/index.html
Cheers,
-- Santiago
signature.asc
Description: PGP signature
Bug#1064369: gobject-introspection dropped versioned dependency on python3
Matthias, Since glib and gobject-introspection have migrated out of noble-proposed, is there still a need to keep this bug open? Thank you, Jeremy Bícha
Bug#1058340: marked as done (mkdocstrings-python-handlers: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 23 Feb 2024 20:59:08 +
with message-id
and subject line Bug#1058340: fixed in mkdocstrings-python-handlers 1.8.0-1
has caused the Debian Bug report #1058340,
regarding mkdocstrings-python-handlers: 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.)
--
1058340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocstrings-python-handlers
Version: 1.7.5-1
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 binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_mkdocstrings_handlers
> * Building wheel...
> - Adding src/mkdocstrings_handlers/py.typed -> mkdocstrings_handlers/py.typed
> - Adding src/mkdocstrings_handlers/python/__init__.py ->
> mkdocstrings_handlers/python/__init__.py
> - Adding src/mkdocstrings_handlers/python/debug.py ->
> mkdocstrings_handlers/python/debug.py
> - Adding src/mkdocstrings_handlers/python/handler.py ->
> mkdocstrings_handlers/python/handler.py
> - Adding src/mkdocstrings_handlers/python/rendering.py ->
> mkdocstrings_handlers/python/rendering.py
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/attribute.html ->
> mkdocstrings_handlers/python/templates/material/_base/attribute.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/children.html ->
> mkdocstrings_handlers/python/templates/material/_base/children.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/class.html ->
> mkdocstrings_handlers/python/templates/material/_base/class.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring.html ->
> mkdocstrings_handlers/python/templates/material/_base/docstring.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/admonition.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/admonition.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/attributes.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/attributes.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/classes.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/classes.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/examples.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/examples.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/functions.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/functions.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/modules.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/modules.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/other_parameters.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/other_parameters.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/parameters.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/parameters.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/raises.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/raises.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/receives.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/receives.html
> - Adding
> src/mkdocstrings_handlers/python/templates/material/_base/docstring/returns.html
> ->
> mkdocstrings_handlers/python/templates/material/_base/docstring/returns.html
> - Adding
>
Bug#1061395: marked as done (gnucash: Stop using webkit2gtk 4.0)
Your message dated Fri, 23 Feb 2024 15:33:51 -0500 with message-id and subject line Re: gnucash: Stop using webkit2gtk 4.0 has caused the Debian Bug report #1061395, regarding gnucash: Stop using webkit2gtk 4.0 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.) -- 1061395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnucash Version: 1.3.0-2 Severity: serious Tags: patch trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 Forwarded: https://salsa.debian.org/debian/gnucash/-/merge_requests/4 The webkit2gtk maintainers intend to stop building the 4.0 API soon. Please switch to using the 4.1 API which is the same as the 4.0 API except that it uses libsoup3 instead of libsoup2.4. I have prepared a merge request to fix this issue. Please upload the fix soon. On behalf of the webkit2gtk maintainers, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 1:5.5-1.1--- End Message ---
Processed: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere
Processing control commands: > close -1 4.0.0.0-1 Bug #1064533 [src:peony] src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere Marked as fixed in versions peony/4.0.0.0-1. Bug #1064533 [src:peony] src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere Marked Bug as done -- 1064533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064533: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere
Source: peony Version: 3.2.4-2 Severity: serious Control: close -1 4.0.0.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:peony has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable apparently has a new Build-Depends. It's not available on armel, armhf, i386, mips64el and ppc64el. If the Build-Depends can't be worked around, you'll need to request binary removals from those architectures from unstable $(reportbug ftp.debian.org). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=peony OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:dt-schema: fails to migrate to testing for too long: autopkgtest failure
Processing control commands: > close -1 2023.11-3 Bug #1064532 [src:dt-schema] src:dt-schema: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions dt-schema/2023.11-3. Bug #1064532 [src:dt-schema] src:dt-schema: fails to migrate to testing for too long: autopkgtest failure Marked Bug as done -- 1064532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064532: src:dt-schema: fails to migrate to testing for too long: autopkgtest failure
Source: dt-schema Version: 2022.08.2-5 Severity: serious Control: close -1 2023.11-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:dt-schema has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=dt-schema OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061765: Help needed to fix python-coverage-test-runner
Andreas Tille dijo [Fri, Feb 23, 2024 at 03:22:27PM +0100]: > HI Andrius, > > Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > > ModuleNotFoundError: No module named 'imp' > > > > I had a similar problem. I worked it around by depending on > > python3-zombie-imp, the original code did not require any modifications. > > Nice hint - implemented. Thank you very much for your work, Andreas!
Bug#1064531: src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev
Source: amberol Version: 0.10.3-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: found 1064514 in 2024.1.27+dfsg1-5
Processing commands for cont...@bugs.debian.org: > found 1064514 2024.1.27+dfsg1-5 Bug #1064514 [src:pymatgen] pymatgen: CVE-2024-23346 Marked as found in versions pymatgen/2024.1.27+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1064516 in 2.2.7-1
Processing commands for cont...@bugs.debian.org: > found 1064516 2.2.7-1 Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Marked as found in versions ruby-rack/2.2.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1058111 marked as pending in cmdtest
Processing control commands: > tag -1 pending Bug #1058111 [src:cmdtest] cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058111: marked as pending in cmdtest
Control: tag -1 pending Hello, Bug #1058111 in cmdtest 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/cmdtest/-/commit/dcf5b1bda3cb1ae41b23c23324f88023a993379f Pull `imp` from python3-zombie-imp Closes: #1058111 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058111
Bug#1058372: marked as done (mkdocstrings-python-legacy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 23 Feb 2024 19:43:38 +0100
with message-id
and subject line Re: Bug#1058372: mkdocstrings-python-legacy: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12
3.11" returned exit code 13
has caused the Debian Bug report #1058372,
regarding mkdocstrings-python-legacy: 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.)
--
1058372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocstrings-python-legacy
Version: 0.2.3-6
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 binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_mkdocstrings
> * Building wheel...
> /usr/lib/python3/dist-packages/pdm/pep517/metadata.py:410: PDMWarning: Field
> `includes` is renamed to `includes` under [tool.pdm.build] table, please
> update your pyproject.toml accordingly
> return self._compatible_get("includes", [])
> - Adding mkdocstrings_handlers/py.typed
> - Adding mkdocstrings_handlers/python/__init__.py
> - Adding mkdocstrings_handlers/python/handler.py
> - Adding mkdocstrings_handlers/python/rendering.py
> - Adding mkdocstrings_handlers/python/templates/material/attribute.html
> - Adding mkdocstrings_handlers/python/templates/material/attributes.html
> - Adding mkdocstrings_handlers/python/templates/material/children.html
> - Adding mkdocstrings_handlers/python/templates/material/class.html
> - Adding mkdocstrings_handlers/python/templates/material/docstring.html
> - Adding mkdocstrings_handlers/python/templates/material/examples.html
> - Adding mkdocstrings_handlers/python/templates/material/exceptions.html
> - Adding mkdocstrings_handlers/python/templates/material/function.html
> - Adding mkdocstrings_handlers/python/templates/material/keyword_args.html
> - Adding mkdocstrings_handlers/python/templates/material/method.html
> - Adding mkdocstrings_handlers/python/templates/material/module.html
> - Adding mkdocstrings_handlers/python/templates/material/parameters.html
> - Adding mkdocstrings_handlers/python/templates/material/properties.html
> - Adding mkdocstrings_handlers/python/templates/material/return.html
> - Adding mkdocstrings_handlers/python/templates/material/signature.html
> - Adding mkdocstrings_handlers/python/templates/material/style.css
> - Adding mkdocstrings_handlers/python/templates/material/yield.html
> - Adding mkdocstrings_handlers/python/templates/mkdocs/exceptions.html
> - Adding mkdocstrings_handlers/python/templates/mkdocs/keyword_args.html
> - Adding mkdocstrings_handlers/python/templates/mkdocs/parameters.html
> - Adding mkdocstrings_handlers/python/templates/mkdocs/return.html
> - Adding mkdocstrings_handlers/python/templates/mkdocs/style.css
> - Adding mkdocstrings_handlers/python/templates/mkdocs/yield.html
> - Adding mkdocstrings_handlers/python/templates/readthedocs/exceptions.html
> - Adding mkdocstrings_handlers/python/templates/readthedocs/keyword_args.html
> - Adding mkdocstrings_handlers/python/templates/readthedocs/parameters.html
> - Adding mkdocstrings_handlers/python/templates/readthedocs/return.html
> - Adding mkdocstrings_handlers/python/templates/readthedocs/style.css
> - Adding mkdocstrings_handlers/python/templates/readthedocs/yield.html
> - Adding mkdocstrings_python_legacy-0.2.3.dist-info/WHEEL
> - Adding mkdocstrings_python_legacy-0.2.3.dist-info/METADATA
> - Adding mkdocstrings_python_legacy-0.2.3.dist-info/licenses/LICENSE
> Successfully built mkdocstrings_python_legacy-0.2.3-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
>
Processed: Re: Bug#1056232: celery's autopkg tests fail with Python 3.12
Processing control commands: > reassign -1 python3-kombu Bug #1056232 [src:celery] celery's autopkg tests fail with Python 3.12 Bug reassigned from package 'src:celery' to 'python3-kombu'. No longer marked as found in versions celery/5.3.4-1. Ignoring request to alter fixed versions of bug #1056232 to the same values previously set > forwarded -1 https://github.com/celery/kombu/issues/1804 Bug #1056232 [python3-kombu] celery's autopkg tests fail with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/celery/kombu/issues/1804'. > affects -1 src:celery Bug #1056232 [python3-kombu] celery's autopkg tests fail with Python 3.12 Added indication that 1056232 affects src:celery > fixed -1 kombu/5.3.4-1 Bug #1056232 [python3-kombu] celery's autopkg tests fail with Python 3.12 Marked as fixed in versions kombu/5.3.4-1. > close -1 Bug #1056232 [python3-kombu] celery's autopkg tests fail with Python 3.12 Marked Bug as done -- 1056232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1064514, tagging 1064515, tagging 1064516, tagging 1064517
Processing commands for cont...@bugs.debian.org: > tags 1064514 + upstream Bug #1064514 [src:pymatgen] pymatgen: CVE-2024-23346 Added tag(s) upstream. > tags 1064515 + upstream Bug #1064515 [src:fastdds] fastdds: CVE-2023-50257 Added tag(s) upstream. > tags 1064516 + upstream Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Added tag(s) upstream. > tags 1064517 + upstream Bug #1064517 [src:texlive-bin] texlive-bin: CVE-2024-25262 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064514 1064515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064515 1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516 1064517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056232: celery's autopkg tests fail with Python 3.12
Control: reassign -1 python3-kombu Control: forwarded -1 https://github.com/celery/kombu/issues/1804 Control: affects -1 src:celery Control: fixed -1 kombu/5.3.4-1 Control: close -1 On Sun, Nov 19, 2023 at 12:08:09PM +0100, Matthias Klose wrote: > celery's autopkg tests fail with Python 3.12. All failing like: [...] > 544s self = > 544s instance = > 544s value = 0x73c86780> > 544s > 544s def __set__(self, instance, value): > 544s if instance is None: > 544s return self > 544s > 544s > with self.lock: > 544s E AttributeError: 'cached_property' object has no attribute > 'lock' > 544s > 544s /usr/lib/python3/dist-packages/kombu/utils/objects.py:37: > AttributeError This was https://github.com/celery/kombu/issues/1804, fixed in kombu 5.3.3, which has been in Debian for a few months now. (#1058317 is still a problem, but is a separate bug.) Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: tagging 1064377, tagging 1014566 ..., found 1064086 in 4.1.8-2, tagging 1049808, tagging 1043996 ...
Processing commands for cont...@bugs.debian.org:
> tags 1064377 + sid trixie
Bug #1064377 [tcl-expect] tcl-expect: identified for time_t transition but no
ABI in shlibs
Added tag(s) sid and trixie.
> tags 1014566 - sid bookworm
Bug #1014566 [src:massivethreads] massivethreads: FTBFS with glibc 2.34
Removed tag(s) sid and bookworm.
> retitle 1064086 libapache2-mod-netcgi-apache: breaks apache (undefined
> symbols)
Bug #1064086 [libapache2-mod-netcgi-apache]
/usr/share/doc/libapache2-mod-netcgi-apache/changelog.gz:
libapache2-mod-netcgi-apache break apache
Changed Bug title to 'libapache2-mod-netcgi-apache: breaks apache (undefined
symbols)' from '/usr/share/doc/libapache2-mod-netcgi-apache/changelog.gz:
libapache2-mod-netcgi-apache break apache'.
> found 1064086 4.1.8-2
Bug #1064086 [libapache2-mod-netcgi-apache] libapache2-mod-netcgi-apache:
breaks apache (undefined symbols)
Marked as found in versions ocamlnet/4.1.8-2.
> tags 1049808 + experimental
Bug #1049808 {Done: Andreas Tille } [src:biosquid] biosquid:
Fails to build binary packages again after successful build
Added tag(s) experimental.
> tags 1043996 + experimental
Bug #1043996 {Done: Andreas Tille } [src:biosquid] biosquid:
Fails to build source after successful build
Added tag(s) experimental.
> tags 1018136 + experimental - bookworm
Bug #1018136 {Done: Simon McVittie } [src:swell-foop]
swell-foop: depends on unmaintained clutter-1.0 and related libraries
Added tag(s) experimental.
Bug #1018136 {Done: Simon McVittie } [src:swell-foop]
swell-foop: depends on unmaintained clutter-1.0 and related libraries
Removed tag(s) bookworm.
> notfixed 1060400 0.09-5
Bug #1060400 {Done: Bo YU } [src:libapp-stacktrace-perl]
libapp-stacktrace-perl: FTBFS on riscv64: unthreaded.t failure
No longer marked as fixed in versions libapp-stacktrace-perl/0.09-5.
> notfixed 1063412 2.0.4-4
Bug #1063412 {Done: Étienne Mollier }
[src:virulencefinder] virulencefinder fails autopkg tests with Python 3.12
No longer marked as fixed in versions 2.0.4-4.
> reassign 1060777 python3-django-crispy-forms 1.14.0-4
Bug #1060777 {Done: Jérémy Lal } [src:django-filter]
django-filter: build dependency missing in testing: python3-django-crispy-forms
Bug reassigned from package 'src:django-filter' to
'python3-django-crispy-forms'.
No longer marked as found in versions django-filter/23.5-1.
No longer marked as fixed in versions django-filter/23.5-1 and
python-django-crispy-forms/2.1-1.
Bug #1060777 {Done: Jérémy Lal }
[python3-django-crispy-forms] django-filter: build dependency missing in
testing: python3-django-crispy-forms
Marked as found in versions python-django-crispy-forms/1.14.0-4.
> fixed 1060777 2.1-1
Bug #1060777 {Done: Jérémy Lal }
[python3-django-crispy-forms] django-filter: build dependency missing in
testing: python3-django-crispy-forms
Marked as fixed in versions python-django-crispy-forms/2.1-1.
> affects 1060777 + src:django-filter
Bug #1060777 {Done: Jérémy Lal }
[python3-django-crispy-forms] django-filter: build dependency missing in
testing: python3-django-crispy-forms
Added indication that 1060777 affects src:django-filter
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1014566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014566
1018136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018136
1043996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043996
1049808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049808
1060400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060400
1060777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060777
1063412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063412
1064086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064086
1064377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028212: marked as done (prometheus-node-exporter-collectors: APT update deadlock - prevents unattended security upgrades)
Your message dated Fri, 23 Feb 2024 17:32:31 +
with message-id
and subject line Bug#1028212: fixed in prometheus-node-exporter-collectors
0.0~git20230203.6f710f8-1+deb12u1
has caused the Debian Bug report #1028212,
regarding prometheus-node-exporter-collectors: APT update deadlock - prevents
unattended security upgrades
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.)
--
1028212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-node-exporter-collectors
Version: 0.0~git20221011.8f6be63-1
Severity: important
Tags: security
X-Debbugs-Cc: Salvatore Bonaccorso , steve+...@tecwec.eu,
Debian Security Team
As requested, by Salvatore lowering prio and avoiding embargo.
-
Hello, happy new year, and thanks.
This looks like an apt deadlock, which prevents updates, unattended upgrades,
and so critical security updates
for systems where they are enabled.
(Yes, we can just manually kill the offending apt_info.py process to
temporarily solve the issue - but this is not the good solution).
As it prevents security updates, and despite it unlikely to happen massively,
and be practically exploited, I feel this requires real attention.
Symptoms:
Persistent apt update locking error:
# apt update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 65553
(python3)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
# 1 hour later, same issue, same holding PID 65553
# Concerned processes:
# ps aux |grep pyth
root1259 0.0 0.1 121076 27528 ?Ssl Jan06 0:00
/usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgra>
root 65553 0.0 0.4 89640 76908 ?S12:09 0:03 python3
/usr/share/prometheus-node-exporter-collectors/apt_info.py
ee 70395 0.0 0.2 124164 42844 ?Sl 12:35 0:00
/bin/python3.11 /home/ee/.vscode-oss/extensions/ms-python.python> (not
suspected)
# ps aux |grep apt
root 65551 0.0 0.0 9552 4252 ?Ss 12:09 0:00 /bin/bash -c
/usr/share/prometheus-node-exporter-collectors/apt_>
root 65553 0.0 0.4 89640 76908 ?S12:09 0:03 python3
/usr/share/prometheus-node-exporter-collectors/apt_info.>
root 65554 0.0 0.0 2464 884 ?S12:09 0:00 sponge
/var/lib/prometheus/node-exporter/apt.prom
_apt 65814 0.0 0.0 27192 13204 ?S12:09 0:00
/usr/lib/apt/methods/https
_apt 65815 0.0 0.0 24420 10236 ?S12:09 0:00
/usr/lib/apt/methods/http
_apt 65816 0.0 0.0 27192 13204 ?S12:09 0:00
/usr/lib/apt/methods/https
_apt 65817 0.0 0.0 24420 10272 ?S12:09 0:00
/usr/lib/apt/methods/http
_apt 65819 0.0 0.0 17572 7624 ?S12:09 0:00
/usr/lib/apt/methods/gpgv
_apt 65826 0.0 0.0 27192 13464 ?S12:09 0:00
/usr/lib/apt/methods/https
_apt 65829 0.0 0.0 24420 10292 ?S12:09 0:00
/usr/lib/apt/methods/http
_apt 66110 0.0 0.0 17528 7500 ?S12:10 0:00
/usr/lib/apt/methods/store
_apt 66112 0.0 0.0 18436 8636 ?S12:10 0:00
/usr/lib/apt/methods/rred
_apt 66113 0.0 0.0 18576 8860 ?S12:10 0:00
/usr/lib/apt/methods/rred
The deadlock is obviously between the unattended-upgrade proc (1259), and the
prometheus tryptic: 65551/53/54.
# 65553 seems to be the culprit - as apt update tells us
# strace -p 65553
strace: Process 65553 attached
pselect6(29, [12 13 14 16 18 20 22 24 26 28], [], NULL, {tv_sec=0,
tv_nsec=499419645}, NULL) = 0 (Timeout)
pselect6(29, [12 13 14 16 18 20 22 24 26 28], [], NULL, {tv_sec=0,
tv_nsec=5}, NULL) = 0 (Timeout)
... repeats 'forever'
All fds are pipes, I could not get more info until the processed crashed due to
my diagnostic atttempts.
An apt/python/prom collector specialist should instantly identify these pipes
and make more deductions, from the following state:
# gdb -p 65553 and bt:
#0 0x7fa4bf65f794 in __GI___select (nfds=29, readfds=0x7ffc24f8e7c0,
writefds=0x7ffc24f8e840, exceptfds=0x0,
timeout=0x7ffc24f8e750) at ../sysdeps/unix/sysv/linux/select.c:69
#1 0x7fa4bebad338 in pkgAcquire::Run(int) () from
/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7fa4becb1485 in AcquireUpdate(pkgAcquire&, int, bool, bool) () from
/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7fa4becb1976 in
Processed: Re: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'
Processing control commands: > found -1 6.30.223.271-24~exp1 Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers' Marked as found in versions broadcom-sta/6.30.223.271-24~exp1. > tag -1 + patch Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers' Added tag(s) patch. -- 1057447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'
Followup-For: Bug #1057447 Control: found -1 6.30.223.271-24~exp1 Control: tag -1 + patch This issue is caused by a) version parsing that expects three numeric components (6.6.1-foo) and fails if there are only two (6.7-rc1) b) broken version comparison logic which turn on APICHOICE=FORCE_WEXT on kernels without CONFIG_WIRELESS_EXT Attached patch fixes that. Verified to be able to build a module for 6.7-cloud-amd64. Andreas Author: Andreas Beckmann Description: fix detection of LINUXVER_WEXT_ONLY - fix version parsing if there are only two numeric components (e.g. 6.7-rc1) - set SUBLEVEL to 0 if missing - fix version comparison logic - -a and -o don't have well defined precedence Bug-Debian: https://bugs.debian.org/1057447 --- a/amd64/Makefile +++ b/amd64/Makefile @@ -20,20 +20,22 @@ ifneq ($(KERNELRELEASE),) - VERSION := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/') - PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/') - SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/') + VERSION := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)\(.*\)/\1/') + PATCHLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)\(.*\)/\2/') + SUBLEVEL := $(shell echo $(KERNELRELEASE) | sed -e 's/\([0-9]*\)[.]\([0-9]*\)[.]\([0-9]*\)\(.*\)/\3/; s/\([0-9]*\)[.]\([0-9]*\)\(.*\)/0/') + # >= 2.6.32 LINUXVER_GOODFOR_CFG80211:=$(strip $(shell \ -if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge "32" -o "$(VERSION)" -ge "3" ]; then \ +if [ "$(VERSION).$(PATCHLEVEL)" = "2.6" -a "$(SUBLEVEL)" -ge "32" ] || [ "$(VERSION)" -eq "2" -a "$(PATCHLEVEL)" -ge "7" ] || [ "$(VERSION)" -ge "3" ]; then \ echo TRUE; \ else \ echo FALSE; \ fi \ )) + # < 2.6.17 LINUXVER_WEXT_ONLY:=$(strip $(shell \ -if [ "$(VERSION)" -ge "2" -a "$(PATCHLEVEL)" -ge "6" -a "$(SUBLEVEL)" -ge "17" ]; then \ +if [ "$(VERSION).$(PATCHLEVEL)" = "2.6" -a "$(SUBLEVEL)" -ge "17" ] || [ "$(VERSION)" -eq "2" -a "$(PATCHLEVEL)" -ge "7" ] || [ "$(VERSION)" -ge "3" ]; then \ echo FALSE; \ else \ echo TRUE; \
Bug#1063918: marked as done (geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable)
Your message dated Fri, 23 Feb 2024 17:05:42 + with message-id and subject line Bug#1063918: fixed in geary 44.1-2 has caused the Debian Bug report #1063918, regarding geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable 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.) -- 1063918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geary Version: 44.1-1 Severity: serious Tags: ftbfs trixie sid geary fails to build from source in unstable when enabling the nocheck build profile. Since trixie, such a failure is considered release-critical. A build ends with: | ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable | dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Drevno=Debian/44.1-1 -Dprofile=release returned exit code 1 | make[1]: *** [debian/rules:24: override_dh_auto_configure] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:21: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Consider dropping inappropriate annotations. Helmut --- End Message --- --- Begin Message --- Source: geary Source-Version: 44.1-2 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of geary, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated geary 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: Fri, 23 Feb 2024 12:00:15 -0500 Source: geary Built-For-Profiles: noudeb Architecture: source Version: 44.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1063918 Changes: geary (44.1-2) unstable; urgency=medium . * Stop using debian/control.in and dh-sequence-gnome * Drop erroneous nocheck from desktop-file-utils Build-Depends (Closes: #1063918) Checksums-Sha1: 89813401382c9cd3a310fc3f61dba99ae66ebfcb 2982 geary_44.1-2.dsc 706a9df650d0969c3dbf5a1f302f94acb9496d04 14804 geary_44.1-2.debian.tar.xz 53663f330c2fe297cb3e51e9fe98a3293e05edb4 19357 geary_44.1-2_source.buildinfo Checksums-Sha256: c9b5452a667536ee19a038ca7b029378f2bbd07fed2ae7c26056d6d7542defdd 2982 geary_44.1-2.dsc 5e9291e38f5371ac9c6d4fe7ce52c851ff98038a478d99764034632f034d5447 14804 geary_44.1-2.debian.tar.xz 6000ac9b005cc91b08e42365e44a1eee6ddec4f4acd9e45b8beced26e758ebe8 19357 geary_44.1-2_source.buildinfo Files: 229044bce8d3a0a7fa85bef06c81a63f 2982 mail optional geary_44.1-2.dsc d39ca6e0599c54de8ed145541856f674 14804 mail optional geary_44.1-2.debian.tar.xz 02457f5ad620c20e0df96ebae53bd151 19357 mail optional geary_44.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXYz0wACgkQ5mx3Wuv+ bH0WHA//aXHv1AxxBQ5fu6kyX+WcQF/0usE8q0XuXiYbMWhCZSK8Xa1aq3p8Fcql tUx1Z3463tB+OX9PG56x3f4xnzMwDwq8arXEa/IMgiy+c5vmAjU4oDXh5a0SKae5 p7e9FEsOe3+rNAgNJ40jBYspFrVH14rg3UCh5AcP/m5O3KoHS9sLXmqgn6mk0Mxr AYQ1NaP2jOub/TbiyWHVZmSA1rznN2EYiHqTxIkiJkX2SsN9ip5NsODZp8qZcH7E QAPYxBvKhp85HauUEcvfykvqTpq9zGPNSe0px/l0plYjy3xrfpe3xnX22Xci05QX 5YVlhraddWvlw7fRL3PemL+tpaSwFvFhBeo6m+B40S/1PD1kpor9R64xOjKQFDA3 5LVMRar2dGqxItIwbJxkGaZp0nnxlDwSVwTuKVhbkrUd7JVHOpsBP10RXCOCMMti tENdX77r+37i8sUh1FJ5AD6YdNoTjaMzRfPR2eztjy/xhePqh/SLDA0IygeaPzih VDY2TFy+qC34BboQoHnhGA4vgq9kjcUfBPJT5ONnhrxGmsJA+iWCRP5YjpRO8ZU9 q+WgtMahxLyrbXfHVTYSv2vqqP/qUo5YzkiFrx4xa9bQh0DZH4p+lmfdZTXIOOgl 7UKYEiZTrIqQPQQXgD4P4EyhQnKWCaEwChLsHWacN+XyGXv2nTA= =1fP2 -END PGP SIGNATURE- pgp78wchd1C8R.pgp Description: PGP signature --- End Message ---
Processed: Bug#1063918 marked as pending in geary
Processing control commands: > tag -1 pending Bug #1063918 [src:geary] geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable Added tag(s) pending. -- 1063918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063918: marked as pending in geary
Control: tag -1 pending Hello, Bug #1063918 in geary 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/gnome-team/geary/-/commit/57462d2b132f8cbb8185a47083f12edaff63d202 Drop erroneous nocheck from desktop-file-utils Build-Depends Closes: #1063918 (this message was generated automatically) -- Greetings https://bugs.debian.org/1063918
Bug#1044064: marked as done (pyranges: FTBFS with pandas 2.0)
Your message dated Fri, 23 Feb 2024 16:42:16 + with message-id and subject line Bug#1044064: fixed in pyranges 0.0.111+ds-7 has caused the Debian Bug report #1044064, regarding pyranges: FTBFS with pandas 2.0 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.) -- 1044064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyranges Version: 0.0.111+ds-4 Control: block 1043240 by -1 pyranges fails to build with pandas 2.0, currently in experimental. Build log: https://launchpadlibrarian.net/680704234/buildlog_ubuntu-mantic-amd64.pyranges_0.0.111+ds-4_BUILDING.txt.gz (This isn't just #1042046 - it fails more tests with pandas 2 than with pandas 1.5.) A common source of failures is that pandas.util.testing has been renamed to pandas.testing. Both names were available in all 1.x versions (and hence in Debian stable and oldstable), so Debian packages that were using this can immediately switch unconditionally. --- End Message --- --- Begin Message --- Source: pyranges Source-Version: 0.0.111+ds-7 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of pyranges, 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 1044...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated pyranges 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: Fri, 23 Feb 2024 15:39:01 +0100 Source: pyranges Architecture: source Version: 0.0.111+ds-7 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1044064 Changes: pyranges (0.0.111+ds-7) unstable; urgency=medium . [ Andreas Tille ] * Fix for Pandas 2.0 Closes: #1044064 . [ Étienne Mollier ] * fix-test_unary.patch: new. This patch fixes a remaining test failure affecting dtype conversion. Checksums-Sha1: 19100835db4c2e9a38272730bbb98ebbedd043f7 2428 pyranges_0.0.111+ds-7.dsc bbf602d834d8e2ce67c1029b2e561f00d39e8589 83796 pyranges_0.0.111+ds-7.debian.tar.xz Checksums-Sha256: 226b4356a2a4f0fc6e5b0fb96bf2b682c9e13918ba8c494c9ce1e6e76f688118 2428 pyranges_0.0.111+ds-7.dsc e03b1b53d8cc25d6e94ac62b0dc6eb455e56a8ab0c6018a106c43b07e36c429e 83796 pyranges_0.0.111+ds-7.debian.tar.xz Files: 4e1d5cfaf98a7783691a4ea61928fab5 2428 python optional pyranges_0.0.111+ds-7.dsc 31ddf7357517790430841c5fdcf32de1 83796 python optional pyranges_0.0.111+ds-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmXYxM0UHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrPihAAgRROfl78V3Lbrl3VhD1KRLbOo25F /OThXdqMvda08lPgvrcLFQMYQ8yRmEO9dN96MoKD8zCkTq7639kb5AKQceVoUuSx uzeL7O8dPxSJvPKg68kIFUBk+45YImLTT2FMGV/lQ9lSLMKZQJDZJ4BUAZBJiqlc Y5fQfF1Ej6h8RvQoeTTPfdu+msa4okti2oYtSzfaO3aaDok+I4zL8BuVYPBDC+QR PdOKWarvVDc1sIoswA/rc0SICmI+QBlAdzedkQnpYWLa66wgnovWJG/T73advd9f j/OVuqG7HMnAgdWKu2JxefkI0BxiL9eWwbJdYFZhq6ec3whf+8zkfGfVySeHvrhX ib5Z0O48P344siD5qZTaSZeow+Yrxw/n2TOIZ7RQT8ysjxqkbTTR6oZbQGVYAGF8 qet63wqWqvmFHcyKxliBmGIw2DCOeuLJmShzD0Ty+I2OBXGxXtGuBmtyFZ7vzPl9 D2Bn3qraJDwhbFEK8jndUPv/JuwCDiAjo5g5R1wFO7s7UgFYNzHA5xj6UJ6RhHab 8ThqejEqiRcymT2fU0JfNDM8AX9uejdbL3UBjkSnd6mhm9ia1ogHgXGRI/f3K5TH AkCkfYJUw2UYiPNOrpVjBeNafmv5/WhNn/TufhTUpQr8H1Oq3YfddP9YLo/u5ftc GGXJ2p9cs2jN0UI= =TKca -END PGP SIGNATURE- pgpKVxwyfcLNX.pgp Description: PGP signature --- End Message ---
Bug#1061765: marked as done (vmdb2 ftbfs with Python 3.12 as default)
Your message dated Fri, 23 Feb 2024 16:20:47 + with message-id and subject line Bug#1061765: fixed in vmdb2 0.28-2 has caused the Debian Bug report #1061765, regarding vmdb2 ftbfs with Python 3.12 as default 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.) -- 1061765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vmdb2 Version: 0.28-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails to build: [...] dh_auto_build I: pybuild base:305: /usr/bin/python3.11 setup.py build I: pybuild base:305: /usr/bin/python3 setup.py build bash format.sh [WARNING] Deprecated: --self-contained. use --embed-resources --standalone make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' ./check Running unit tests Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/lib/python3/dist-packages/CoverageTestRunner.py", line 22, in import imp ModuleNotFoundError: No module named 'imp' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-01-29T10:47:03Z --- End Message --- --- Begin Message --- Source: vmdb2 Source-Version: 0.28-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of vmdb2, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated vmdb2 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: Fri, 23 Feb 2024 16:58:18 +0100 Source: vmdb2 Architecture: source Version: 0.28-2 Distribution: unstable Urgency: medium Maintainer: Gunnar Wolf Changed-By: Andreas Tille Closes: 1061765 Changes: vmdb2 (0.28-2) unstable; urgency=medium . * Team upload. * Versioned (Test-)Depends python3-coverage-test-runner (>= 1.13.1-6~) Closes: #1061765 * Standards-Version: 4.6.2 (routine-update) * Reorder sequence of d/control fields by cme (routine-update) * Add upstream metadata (Debian Janitor) Checksums-Sha1: 9edf3b72e29d83eb4ad76a5e5c253d3c64763ba1 2011 vmdb2_0.28-2.dsc 92bee4a0e02c0b2ebc536da94e92156330032278 4824 vmdb2_0.28-2.debian.tar.xz 16553cff0022a46966233c16887b815af4e85bdb 7895 vmdb2_0.28-2_amd64.buildinfo Checksums-Sha256: 6be38471233ebee1ca70a8aaf62152f3aa4281354bd3a9d74c32c7ca3405f2f1 2011 vmdb2_0.28-2.dsc c15928ac82ba5ca6512e58d8e63c9524f9b98c58f56cce3be8918eaf0fcbe969 4824 vmdb2_0.28-2.debian.tar.xz 4a977e7be7c37ce39221d786e628c77d96a250842938a23d5a814808611b818e 7895 vmdb2_0.28-2_amd64.buildinfo Files: c79d45cc51dedba21f4b16dbc74b1496 2011 admin optional vmdb2_0.28-2.dsc 5f47f9af0fd18e612145e53065dbcfd1 4824 admin optional vmdb2_0.28-2.debian.tar.xz 1b9431d0b14cd524d361b6d1efe1d90b 7895 admin optional vmdb2_0.28-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXYwgARHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFA4g/+J1PJacFa3BMO4cUGBjRBGn7PenVzb1Tt LSRgM36mdP85qXDlJvbh+pvoZ+5zsHqf8RUDUAJANNje1JUcHSTklJ584P/OoGsf YvcCxR9gtzRQO4Td9eGozdf3SNn6yrkg8OAxQBq77ZMO9leUnonqvdwvuxs41vSe 5ARLQkto6GVFTJo2Rye9e1xrAMelRaNQwjRiicmUSwMeWlLhmegmC4eI9yGL0Quy dIEAAD1hUaUEfBkDvHDCrPHzcrjWTc2go9tEOsbRu+CTqGV68YCC3HdbLOMBuOmG NlfCXcGeRD0NbbP90icoW2WK3iUoavmBxDFEYqVtMPiT4BR9Y9ydBx+xW3GwIV9P BN85sQLWks3uLLtiC29g5KgMX0icr/G6KnRFtwYSnzqZz9GjxAKLsAVvBXdeiLdD jpIWR9vxhLONcRj5HocwWUxJguBlXrSdqvmg2JELmu6L+QdcH7H5QS1L0ErQe0FP NwjjmEm2Ps52l+2wX1MuHyVpodPREb8h5xRIviMWNg+MJxG+hegWE5EUKYEb3OBD Cg1w8uQsAhDtXAYx1jfoOhyzmiaZ9jWH9I5fkJFw56QUXBng5k1GQQAB18M61zfW OKmj32EOEc3v8WsF4MekV7Nd304KwzXysEMsQKViKEcnzNL1tQt0aHKjbyWz9YEX gM+gXcOu79s= =/Onl
Bug#1064128:
...and 2.2.4 also fails to build: https://github.com/savonet/liquidsoap/issues/3752 $ make : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition File "src/core/decoder/gstreamer_decoder.ml", line 314, characters 37-51: 314 | (Decoder.test_file ~log ~mimes:mime_types#get ^^ Error: This expression has type string list but an expression was expected of type string list option make: *** [Makefile:4: build] Error 1
Bug#1052869: marked as done (python-klein: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 23 Feb 2024 15:49:37 +
with message-id
and subject line Bug#1052869: fixed in python-klein 23.12.0-1
has caused the Debian Bug report #1052869,
regarding python-klein: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 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.)
--
1052869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-klein
Version: 21.8.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'extra_requires'
> warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84:
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are
> deprecated.
> !!
>
>
>
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
>
>
>
> !!
> dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265:
> UserWarning: Unknown distribution option: 'extra_requires'
> warnings.warn(msg)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/klein
> copying src/klein/_isession.py -> build/lib/klein
> copying src/klein/app.py -> build/lib/klein
> copying src/klein/_request.py -> build/lib/klein
> copying src/klein/_iform.py -> build/lib/klein
> copying src/klein/_imessage.py -> build/lib/klein
> copying src/klein/_session.py -> build/lib/klein
> copying src/klein/_interfaces.py -> build/lib/klein
> copying src/klein/_request_compat.py -> build/lib/klein
> copying src/klein/_version.py -> build/lib/klein
> copying src/klein/_resource.py -> build/lib/klein
> copying src/klein/_headers_compat.py -> build/lib/klein
> copying src/klein/_app.py -> build/lib/klein
> copying src/klein/_message.py -> build/lib/klein
> copying src/klein/_dihttp.py -> build/lib/klein
> copying src/klein/_form.py -> build/lib/klein
> copying src/klein/__init__.py -> build/lib/klein
> copying src/klein/resource.py -> build/lib/klein
> copying src/klein/interfaces.py -> build/lib/klein
> copying src/klein/_plating.py -> build/lib/klein
> copying src/klein/_headers.py -> build/lib/klein
> copying src/klein/_requirer.py -> build/lib/klein
> copying src/klein/_decorators.py -> build/lib/klein
> copying src/klein/_tubes.py -> build/lib/klein
> copying src/klein/_response.py -> build/lib/klein
> creating build/lib/klein/storage
> copying src/klein/storage/__init__.py -> build/lib/klein/storage
> copying src/klein/storage/_memory.py -> build/lib/klein/storage
> copying src/klein/storage/memory.py -> build/lib/klein/storage
> creating build/lib/klein/test
> copying src/klein/test/test_session.py -> build/lib/klein/test
> copying src/klein/test/test_exports.py -> build/lib/klein/test
> copying src/klein/test/_trial.py -> build/lib/klein/test
> copying src/klein/test/test_requirer.py -> build/lib/klein/test
> copying src/klein/test/test_headers_compat.py -> build/lib/klein/test
> copying src/klein/test/__init__.py ->
Bug#1064516: ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146
Source: ruby-rack X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for ruby-rack. CVE-2024-26141[0]: Reject Range headers which are too large https://github.com/rack/rack/releases/tag/v2.2.8.1 https://github.com/rack/rack/commit/62457686b26d33a15a254c7768c2076e8e02b48b (v2.2.8.1) CVE-2024-25126[1]: Fixed ReDoS in Content Type header parsing https://github.com/rack/rack/releases/tag/v2.2.8.1 CVE-2024-26146[2]: Fixed ReDoS in Accept header parsing https://github.com/rack/rack/releases/tag/v2.2.8.1 https://github.com/rack/rack/commit/e4c117749ba24a66f8ec5a08eddf68deeb425ccd (v2.2.8.1) If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-26141 https://www.cve.org/CVERecord?id=CVE-2024-26141 [1] https://security-tracker.debian.org/tracker/CVE-2024-25126 https://www.cve.org/CVERecord?id=CVE-2024-25126 [2] https://security-tracker.debian.org/tracker/CVE-2024-26146 https://www.cve.org/CVERecord?id=CVE-2024-26146 Please adjust the affected versions in the BTS as needed.
Bug#1064514: pymatgen: CVE-2024-23346
Source: pymatgen X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for pymatgen. CVE-2024-23346[0]: | Pymatgen (Python Materials Genomics) is an open-source Python | library for materials analysis. A critical security vulnerability | exists in the | `JonesFaithfulTransformation.from_transformation_str()` method | within the `pymatgen` library prior to version 2024.2.20. This | method insecurely utilizes `eval()` for processing input, enabling | execution of arbitrary code when parsing untrusted input. Version | 2024.2.20 fixes this issue. https://github.com/materialsproject/pymatgen/security/advisories/GHSA-vgv8-5cpj-qj2f https://github.com/materialsproject/pymatgen/commit/c231cbd3d5147ee920a37b6ee9dd236b376bcf5a If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-23346 https://www.cve.org/CVERecord?id=CVE-2024-23346 Please adjust the affected versions in the BTS as needed.
Bug#999931: marked as done (virtuoso-opensource: depends on obsolete pcre3 library)
Your message dated Fri, 23 Feb 2024 14:47:25 + with message-id and subject line Bug#31: fixed in virtuoso-opensource 7.2.5.1+dfsg1-0.6 has caused the Debian Bug report #31, regarding virtuoso-opensource: 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.) -- 31: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=31 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virtuoso-opensource 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: virtuoso-opensource Source-Version: 7.2.5.1+dfsg1-0.6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of virtuoso-opensource, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated virtuoso-opensource 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: Fri, 23 Feb 2024 14:07:47 +0100 Source: virtuoso-opensource Architecture: source Version: 7.2.5.1+dfsg1-0.6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Beckmann Closes: 31 Changes: virtuoso-opensource (7.2.5.1+dfsg1-0.6) unstable; urgency=medium . * Non-maintainer upload. . [ Yavor Doganov ] * Port to pcre2. (Closes: #31) Checksums-Sha1: 3d5518e997576e7b2c27fa810ef3d7c1474daf84 4050 virtuoso-opensource_7.2.5.1+dfsg1-0.6.dsc e739d28fc04bbdcdaf6d82ddb6320f7092607156 78136 virtuoso-opensource_7.2.5.1+dfsg1-0.6.debian.tar.xz fa4e331661351d0d08169924af2f7cdfe9b00e12 23078 virtuoso-opensource_7.2.5.1+dfsg1-0.6_source.buildinfo Checksums-Sha256: 91b2801083b802e22a29759480160a5add501a1dc7c55faa7f24a5e85d701485 4050 virtuoso-opensource_7.2.5.1+dfsg1-0.6.dsc a68d0334affe5a980acc9765e244830e099932d193d65789589d3afdff589301 78136 virtuoso-opensource_7.2.5.1+dfsg1-0.6.debian.tar.xz 41d56f955ba0fa1c5c98e327bacd158d2658447cf7fde223a45994773f6c9bb8 23078 virtuoso-opensource_7.2.5.1+dfsg1-0.6_source.buildinfo Files: 73f98d07d9473af1d3a1bd38c1c0d9dc 4050 database optional virtuoso-opensource_7.2.5.1+dfsg1-0.6.dsc 845b4e6d5fc1e169634eb360c7398bc2 78136 database optional virtuoso-opensource_7.2.5.1+dfsg1-0.6.debian.tar.xz 6ab653be75098126bd581f08efc54b63 23078 database optional virtuoso-opensource_7.2.5.1+dfsg1-0.6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXYo+sQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCG/9EACy0extKc2WqiRMphkCnPGrKNeufnSbT3LY KmutFH8THzsl/6Lh7m0JpwTExQQwZmDXvmcvOx6viWvidyrHFDU/KLLjANaLTWPq meZ8UOP4BdbRIwDdKk0T8DJU9eIOMWu6Apa9tzoAL6ezzTtQELpb1sGTJMII4GJp c+sXF1RR4Dsnef+5QdBiRHDgN6QsGEGRf8GnrbfZ7MgTEgT9A71Zg1iHl7FISiVd YtPkrL/HO2J02ZLkFgj3JIalXdTN94RyEeAmule/HzEOXQPMYr7gOG+HFmrkkevD sGCrtVwsy7uYg7n12DR8T7XJfulsovMS5XiufLsttOfPkEYaiUMPK11TO0Oa4iGd Ljw/wdapwpKcs39ceK3mmxxHwd9bCcFYDmZnnttFWC6WhxUan1J/IDACH+am8TtL 0Z4U3KoIXVwbYXKcO6n10vAx5IsTFHcZZdKZvmSyAocbkCx9XAnvYY1Ul/pdAbIY Ew95u0z5hryMTlfjZcgTnuOu+ywjv7fOF92ucCrMyMFCB6lExYaDRMceIts7moFd 0ONWiL4oMXayqSRq1jTpj019D/V9MUW/5CtGUwJ++4KLl17oBSxkkOHC6UcX/YLh
Bug#1058112: marked as done (python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Fri, 23 Feb 2024 14:44:30 +
with message-id
and subject line Bug#1058112: fixed in python-coverage-test-runner 1.13.1-5
has caused the Debian Bug report #1058112,
regarding python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module
named 'imp'
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.)
--
1058112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-coverage-test-runner
Version: 1.13.1-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):
> debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 22, in
> import CoverageTestRunner
> File "/<>/CoverageTestRunner.py", line 22, in
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-coverage-test-runner_1.13.1-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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 ---
Source: python-coverage-test-runner
Source-Version: 1.13.1-5
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
python-coverage-test-runner, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated
python-coverage-test-runner 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: Fri, 23 Feb 2024 14:47:31 +0100
Source: python-coverage-test-runner
Architecture: source
Version: 1.13.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1058112
Changes:
python-coverage-test-runner (1.13.1-5) unstable; urgency=medium
.
* Add fake watch file
* Move package to DPT
* Standards-Version: 4.6.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Testsuite: autopkgtest-pkg-python (routine-update)
* Use python3-zombie-imp to have imp functionality
Replace distutils
Closes: #1058112
Checksums-Sha1:
528b9aa3d8b022039b72ed111d2b9daebde9159b 2270
python-coverage-test-runner_1.13.1-5.dsc
6e41ccb26b23e83a6414955be4ed2c163674a812 3740
python-coverage-test-runner_1.13.1-5.debian.tar.xz
715a22de57e2d2c6307eb8de6ad8c699200c1762 7428
python-coverage-test-runner_1.13.1-5_amd64.buildinfo
Checksums-Sha256:
b50c21d6c2c126c3f7af054fb3461d519b3d1f3ebd743cd02559d6a20b96d43a 2270
python-coverage-test-runner_1.13.1-5.dsc
d103923efe55c76d97b63866c9eff6ae52aed4ee53e1a6f77a823f44c8bbf2ac 3740
python-coverage-test-runner_1.13.1-5.debian.tar.xz
c623da847faf6e19a838fa2159dce9a71b0adf33d0cbb1c106e872c304ae0450 7428
python-coverage-test-runner_1.13.1-5_amd64.buildinfo
Files:
ef19311dfd99d542961ee026e86345fb 2270 python optional
python-coverage-test-runner_1.13.1-5.dsc
24e7753dbc52cf4c5ced15e2c16f0e2e 3740 python
Bug#1064128:
Upstream fixed[1] this in 2.2.4. There are big commits that could be used as patches, but it's probably best to just update to 2.2.4. 1. https://github.com/savonet/liquidsoap/issues/3750
Bug#1061765: Help needed to fix python-coverage-test-runner
HI Andrius, Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > ModuleNotFoundError: No module named 'imp' > > I had a similar problem. I worked it around by depending on > python3-zombie-imp, the original code did not require any modifications. Nice hint - implemented. Thanks a lot Andreas. -- http://fam-tille.de
Processed: notfound 1064492 in 0.9.27
Processing commands for cont...@bugs.debian.org: > notfound 1064492 0.9.27 Bug #1064492 [libdemeter-perl] libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI There is no source info for the package 'libdemeter-perl' at version '0.9.27' with architecture '' Unable to make a source version for version '0.9.27' No longer marked as found in versions 0.9.27. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1064492 in 0.9.27+ds6-1
Processing commands for cont...@bugs.debian.org: > found 1064492 0.9.27+ds6-1 Bug #1064492 [libdemeter-perl] libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI Marked as found in versions libdemeter-perl/0.9.27+ds6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061764: marked as done (unattended-upgrades ftbfs with Python 3.12 as default)
Your message dated Fri, 23 Feb 2024 10:26:46 +0100 with message-id <5d9d2952-1dc1-481b-9161-a7d4c0657...@app.fastmail.com> and subject line Re: Bug#1061764: unattended-upgrades ftbfs with Python 3.12 as default has caused the Debian Bug report #1061764, regarding unattended-upgrades ftbfs with Python 3.12 as default 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.) -- 1061764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:unattended-upgrades Version: 2.9.1+nmu4 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails to build: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. --- End Message --- --- Begin Message --- With the most recent unattended-upgrade upload this should be fixed, a local test build with py3.12 worked fine. On Tue, Jan 30, 2024, at 11:33, Michael Vogt wrote: > Hey Doko, > > thanks for your bugreport. This is should be fixed in the git repo at > github, at least a test-build with the python3 from experimental on > debian/unstable build fine. I will look into a new release. > > Cheers, > Michael > > On Mon, Jan 29, 2024, at 13:54, Matthias Klose wrote: >> Package: src:unattended-upgrades >> Version: 2.9.1+nmu4 >> Severity: serious >> Tags: sid trixie ftbfs >> User: debian-pyt...@lists.debian.org >> Usertags: python3.12 >> >> With python3-defaults from experimental, the package fails to build: >> >> [...] >> Running ./test_pep484.py with python3 >> s >> -- >> Ran 0 tests in 0.000s >> >> NO TESTS RAN (skipped=1) >> make[2]: *** [Makefile:9: check] Error 5 >> make[2]: Leaving directory '/<>/test' >> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 >> >> 5 is a new exit value when all tests are skipped.--- End Message ---
Processed: found 1055067 in 4.4.3-P1-2
Processing commands for cont...@bugs.debian.org: > found 1055067 4.4.3-P1-2 Bug #1055067 [isc-dhcp-client] isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update Marked as found in versions isc-dhcp/4.4.3-P1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1055067 in 4.4.3-P1-5
Processing commands for cont...@bugs.debian.org: > found 1055067 4.4.3-P1-5 Bug #1055067 [isc-dhcp-client] isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update Marked as found in versions isc-dhcp/4.4.3-P1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053111: please upload DEP17-related patches
user helm...@debian.org severity 1059981 important tags 1059981 + trixie sid severity 1061274 important tags 1061274 + trixie sid severity 1060269 important tags 1060269 + trixie sid patch severity 1060270 important tags 1060270 + trixie sid patch severity 106 important usertags 106 + dep17m2 severity 1059534 important tags 1059534 + trixie sid severity 1059533 important tags 1059533 + trixie sid severity 1059919 important tags 1059919 + trixie sid severity 1060089 important tags 1060089 + trixie sid severity 1055959 important tags 1055959 + trixie sid severity 1060160 important tags 1060160 + trixie sid severity 1060139 important tags 1060139 + trixie sid thanks The number of packages installed by debootstrap containing files in aliased locations has been shrinking since a while. We're now down to 10 packages and I'd like to get them done by mid March to be able to move forward with uploading base-files/bash/dash/glibc/util-linux. Please upload the requested changes or reply to the bugs. In some cases (such as isc-dhcp, libtirpc and pam) these have been fixed in experimental and are expected to land in unstable soon. For others, I intend to upload delayed NMUs in agreement with the developers reference soon. I'm aware that the time64 transition is in progress, but there is little intersection except for libtirpc and pam, both of which will be moved as part of the time64 transition. Please let me know if you have questions or objections to moving forward. Helmut
Bug#1064495: sitecopy FTBFS: incompatible neon version
Source: sitecopy Version: 1:0.16.6-11 Severity: serious Tags: ftbfs sitecopy fails to build from source in unstable. I think the relevant part of the build log is: | checking for neon-config... /usr/bin/neon-config | checking linking against neon... yes | configure: incompatible neon library version 0.33.0: wanted 0.24 25 26 27 28 31 32 | configure: error: could not use external neon library | tail -v -n \+0 config.log Apparently, sitecopy is incompatible with neon >= 0.33. This quite definitely needs a sourceful upload of sitecopy. Helmut
