Bug#1057383: marked as done (mapclassify: Build-Depends on python3-libpysal which is not in testing)
Your message dated Wed, 22 May 2024 11:24:53 + with message-id and subject line Bug#1057383: fixed in mapclassify 2.6.1-5 has caused the Debian Bug report #1057383, regarding mapclassify: Build-Depends on python3-libpysal which is not in testing 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.) -- 1057383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mapclassify Version: 2.6.1-2 Severity: serious Tags: ftbfs Hi Maintainer mapclassify has a build-dependency on python3-libpysal which is no longer in testing. Please drop this build-dependency or help get python3-libpysal back into testing. In addition, if any of mapclassify's build-dependencies are only used for build-time tests, please annotate them with the build profile [1]. Regards Graham [1] https://wiki.debian.org/BuildProfileSpec --- End Message --- --- Begin Message --- Source: mapclassify Source-Version: 2.6.1-5 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of mapclassify, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated mapclassify package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 May 2024 13:07:05 +0200 Source: mapclassify Architecture: source Version: 2.6.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Michael R. Crusoe Closes: 1057383 Changes: mapclassify (2.6.1-5) unstable; urgency=medium . * Team upload. * d/control: mark docs- or test-only dependencies. Closes: #1057383 * Added intersphinx patch to connect to related documentation packages. Checksums-Sha1: de0280be4f766b691222bd1412458970a3e47370 2900 mapclassify_2.6.1-5.dsc 51d1a6d56aa1b7f837ed5efb9392b6213d01f9b5 185332 mapclassify_2.6.1-5.debian.tar.xz c50daf4ad98eaeba10a45b66828cf2af9475070e 8884 mapclassify_2.6.1-5_source.buildinfo Checksums-Sha256: 98d0b03e9725e9446483177256e29b4876f84f6f58e574e696b91a327725f65a 2900 mapclassify_2.6.1-5.dsc cb77da8da002f05f140c999cc0f2b6e2192c0ee4fdf8746418e24fa287b9f804 185332 mapclassify_2.6.1-5.debian.tar.xz e5579843e9ebbb8f576719fb19243b13765c10a0fa2378480da99a374f494cef 8884 mapclassify_2.6.1-5_source.buildinfo Files: 1b7d04d220a87afad7a390fce67b16da 2900 python optional mapclassify_2.6.1-5.dsc 86cbd0db992c4ebdcc15fd3d49b5c5d7 185332 python optional mapclassify_2.6.1-5.debian.tar.xz d048b47aefea314b7c5e05445eb9aab3 8884 python optional mapclassify_2.6.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmZN0w0ACgkQPCZ2P2xn 5uK8cg/+ILz+1LQ28VBnDnh549+C1C8Hs05SiCgLTWlCbXYim+FvrgpDHRhEstYp //i5q1HSga6pwRrXV+SiO1rkG/azxarB7QdWs5lCn4ymmmOPY8dQBxgyRuBx1qpc VsoAiDlbnYdz2o2S3xOZ7T1siRFsZwLKq6Gs7P134Rdj65cXLSwerwlULLuNIrEp BefTXfAhlKNJ1BFBlkmrlTWqrw5/O/MsxcK3ppytvUaxQ0RQNwglvjtAjYmahwjJ FHoepitZvF68OlS4DdBA+BmRddDVqHO3CMsPCQSLIJmdSvj96M8aMO8tIGd2Y8GU SUAMNIxApXju8lIQ6EAq9zDJITcUG1xi1mdvrHtZh5JUHTtpGbUS07JEg37Op5kS qSiQNMNr54G4sM0aM8Gy9w4d2hQa2wsUXCLbm0H81ToPCR31bi1F0HcEk5M2VKE9 j6JxqOoouCW+/G/bcXH2QOGUVmIYNzplXyN7mSwjqmQ2Jrzi91YqHhcmYHdGKLlv L+I1UdYZGqmtPrByDrH+8Hp8vHUCLmIFSSL4SRryIJZjJkRqwjfP71pBgxTBxg7+ f67ChZoJOreO8GcyKVN/dm8durnufxpuoya0BODQsLcP+jD3m4CjRn2w2yUTbKyU q/LacGDMw47yR/kX+lC7Rgs6IcaAi+v5NQiLapy88yhPWclu6JI= =BJ8K -END PGP SIGNATURE- pgpX5ffh2W6_m.pgp Description: PGP signature --- End Message ---
Bug#1071339: marked as done (qrisk2: FTBFS: include/clinrisk/utils.h:42:6: error: conflicting types for ‘strlcat’)
Your message dated Wed, 22 May 2024 08:59:58 + with message-id and subject line Bug#1071339: fixed in qrisk2 0.1.20150729-6 has caused the Debian Bug report #1071339, regarding qrisk2: FTBFS: include/clinrisk/utils.h:42:6: error: conflicting types for ‘strlcat’ 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.) -- 1071339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qrisk2 Version: 0.1.20150729-5 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/<>' mkdir -p lib mkdir -p executables dh_auto_build make -j2 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>' makedepend -- -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -- -I /usr/include/linux -I include c/Q80_model_4_0.c c/Q80_model_4_1.c c/utils.c gcc -I include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c c/Q80_model_4_0.c -o c/Q80_model_4_0.o makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 27): cannot find include file "bits/libc-header-start.h" not in /usr/include/linux/bits/libc-header-start.h not in include/bits/libc-header-start.h not in /usr/include/bits/libc-header-start.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 37): cannot find include file "bits/types.h" not in /usr/include/linux/bits/types.h not in include/bits/types.h not in /usr/include/bits/types.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 40): cannot find include file "bits/math-vector.h" not in /usr/include/linux/bits/math-vector.h not in include/bits/math-vector.h not in /usr/include/bits/math-vector.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 43): cannot find include file "bits/floatn.h" not in /usr/include/linux/bits/floatn.h not in include/bits/floatn.h not in /usr/include/bits/floatn.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 152): cannot find include file "bits/flt-eval-method.h" not in /usr/include/linux/bits/flt-eval-method.h not in include/bits/flt-eval-method.h not in /usr/include/bits/flt-eval-method.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 204): cannot find include file "bits/fp-logb.h" not in /usr/include/linux/bits/fp-logb.h not in include/bits/fp-logb.h not in /usr/include/bits/fp-logb.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 247): cannot find include file "bits/fp-fast.h" not in /usr/include/linux/bits/fp-fast.h not in include/bits/fp-fast.h not in /usr/include/bits/fp-fast.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 312): cannot find include file "bits/mathcalls-helper-functions.h" not in /usr/include/linux/bits/mathcalls-helper-functions.h not in include/bits/mathcalls-helper-functions.h not in /usr/include/bits/mathcalls-helper-functions.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 313): cannot find include file "bits/mathcalls.h" not in /usr/include/linux/bits/mathcalls.h not in include/bits/mathcalls.h not in /usr/include/bits/mathcalls.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 566): cannot find include file "bits/mathcalls-narrow.h" not in /usr/include/linux/bits/mathcalls-narrow.h not in include/bits/mathcalls-narrow.h not in /usr/include/bits/mathcalls-narrow.h makedepend: warning: c/Q80_model_4_0.c (reading /usr/include/math.h, line 587): cannot find include file "bits/mathcalls-narrow.h" not in /usr/include/linu
Bug#1071476: marked as done (neochat: Neochat will not start, due to old kirigami-addons)
Your message dated Wed, 22 May 2024 10:35:48 +0200 with message-id and subject line Re: neochat: Neochat will not start, due to old kirigami-addons has caused the Debian Bug report #1071476, regarding neochat: Neochat will not start, due to old kirigami-addons 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.) -- 1071476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: neochat Version: 23.08.5-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: ltw...@debian.org Dear Maintainer, neochat won't start. I have uploaded kirigami-addons, and made a new upload of neochat. This bug is so that it will not migrate. Best -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages neochat depends on: ii kio 5.115.0-5 ii libc6 2.38-11 ii libcmark0.30.2 0.30.2-6+b1 ii libkf5configcore5 5.115.0-2 ii libkf5configgui55.115.0-2 ii libkf5configwidgets55.115.0-2 ii libkf5coreaddons5 5.115.0-2 ii libkf5dbusaddons5 5.115.0-2 ii libkf5i18n5 5.115.1-2 ii libkf5kiocore5 5.115.0-5 ii libkf5kiogui5 5.115.0-5 ii libkf5kiowidgets5 5.115.0-5 ii libkf5kirigami2-5 5.115.0-2 ii libkf5notifications55.115.0-2 ii libkf5sonnetcore5 5.115.0-2 ii libkf5windowsystem5 5.115.0-2 ii libqt5core5t64 5.15.10+dfsg-7.2+b1 ii libqt5dbus5t64 5.15.10+dfsg-7.2+b1 ii libqt5gui5t64 5.15.10+dfsg-7.2+b1 ii libqt5keychain1 0.14.3-1 ii libqt5multimedia5 5.15.10-2+b2 ii libqt5network5t64 5.15.10+dfsg-7.2+b1 ii libqt5qml5 5.15.10+dfsg-2+b2 ii libqt5quick55.15.10+dfsg-2+b2 ii libqt5quickcontrols2-5 5.15.10+dfsg-2+b2 ii libqt5sql5-sqlite 5.15.10+dfsg-7.2+b1 ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1 ii libquotient0.8 0.8.1.2-2 ii libstdc++6 14.1.0-1 ii qml-module-org-kde-kirigami-addons-labs-mobileform 0.11.0-1 ii qml-module-org-kde-kirigami25.115.0-2 ii qml-module-org-kde-kitemmodels 5.115.0-2 ii qml-module-org-kde-kquickimageeditor0.3.0-1+b1 ii qml-module-org-kde-notifications5.115.0-2 ii qml-module-org-kde-purpose 5.115.0-2 ii qml-module-org-kde-qqc2desktopstyle 5.115.0-2 ii qml-module-org-kde-quickcharts 5.115.0-2 ii qml-module-org-kde-sonnet 5.115.0-2 ii qml-module-org-kde-syntaxhighlighting 5.115.0-2 ii qml-module-qt-labs-platform 5.15.10+dfsg-2+b2 ii qml-module-qt-labs-qmlmodels5.15.10+dfsg-2+b2 ii qml-module-qtlocation 5.15.10+dfsg-3+b2 ii qml-module-qtmultimedia 5.15.10-2+b2 ii qml-module-qtqml5.15.10+dfsg-2+b2 ii qml-module-qtqml-models25.15.10+dfsg-2+b2 ii qml-module-qtquick-controls25.15.10+dfsg-2+b2 ii qml-module-qtquick-layouts 5.15.10+dfsg-2+b2 ii qml-module-qtquick-particles2 5.15.10+dfsg-2+b2 ii qml-module-qtquick-window2 5.15.10+dfsg-2+b2 ii
Processed: Bug#1071339 marked as pending in qrisk2
Processing control commands: > tag -1 pending Bug #1071339 [src:qrisk2] qrisk2: FTBFS: include/clinrisk/utils.h:42:6: error: conflicting types for ‘strlcat’ Added tag(s) pending. -- 1071339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1063944 marked as pending in libcloud
Processing control commands: > tag -1 pending Bug #1063944 [libcloud] libcloud: autopkgtest regression with pytest 8 Added tag(s) pending. -- 1063944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066731 marked as pending in libcloud
Processing control commands:
> tag -1 pending
Bug #1066731 [src:libcloud] libcloud: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1066731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1070896 to libkf5kio-dev, fixed 1070896 in kio/5.115.0-5, closing 1070896
Processing commands for cont...@bugs.debian.org: > reassign 1070896 libkf5kio-dev kio/5.115.0-3 Bug #1070896 [src:labplot] labplot: FTBFS: dh_auto_configure fails Bug reassigned from package 'src:labplot' to 'libkf5kio-dev'. No longer marked as found in versions labplot/2.10.1-2. Ignoring request to alter fixed versions of bug #1070896 to the same values previously set Bug #1070896 [libkf5kio-dev] labplot: FTBFS: dh_auto_configure fails Marked as found in versions kio/5.115.0-3. > fixed 1070896 kio/5.115.0-5 Bug #1070896 [libkf5kio-dev] labplot: FTBFS: dh_auto_configure fails Marked as fixed in versions kio/5.115.0-5. > close 1070896 Bug #1070896 [libkf5kio-dev] labplot: FTBFS: dh_auto_configure fails Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1070896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > block 1054720 by 1071601 Bug #1054720 [src:jhbuild] jhbuild: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'hello' 1054720 was not blocked by any bugs. 1054720 was not blocking any bugs. Added blocking bug(s) of 1054720: 1071601 > thanks Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1054720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1071568
Processing commands for cont...@bugs.debian.org: > close 1071568 535.161.08-2~deb12u1~bpo11+1 Bug #1071568 [nvidia-kernel-dkms] nvidia-kernel-dkms: module (from backports) fails to build with 5.10.216-1 (ABI 29 kernel) in Debian bullseye Marked as fixed in versions nvidia-graphics-drivers/535.161.08-2~deb12u1~bpo11+1. Bug #1071568 [nvidia-kernel-dkms] nvidia-kernel-dkms: module (from backports) fails to build with 5.10.216-1 (ABI 29 kernel) in Debian bullseye Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1071568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: netplan.io: autopkgtest fails with systemd 256
Processing control commands: > tags -1 pending Bug #1071220 [src:netplan.io] netplan.io: autopkgtest fails with systemd 256 Added tag(s) pending. -- 1071220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051534: marked as done (analizo: Test failure in t/features.t during build and autopkgtests)
Your message dated Tue, 21 May 2024 19:34:19 + with message-id and subject line Bug#1051534: fixed in analizo 1.25.4-3 has caused the Debian Bug report #1051534, regarding analizo: Test failure in t/features.t during build and autopkgtests 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.) -- 1051534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: analizo Version: 1.25.4-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 analizo started to fail its autopkgtests recently in unstable: https://ci.debian.net/packages/a/analizo/ And the same test failure happens during build as well: # Failed test 'Then analizo must report that the project has total_abstract_classes = 1' # at t/features/metrics/abstract_classes.feature line 19. # in step at t/features/metrics/abstract_classes.feature line 19. # not ok # # Failed test at /build/analizo-1.25.4/t/features/step_definitions/analizo_steps.pl line 143. # # got: 2 # # expected: 1 # ok 3 - Step ran to completion # 1..2 # # Looks like you failed 1 test of 2. # Looks like you failed 1 test of 1008. t/features.t . # not ok 404 - Then analizo must report that the project has total_abstract_classes = 1 # 1..1008 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1008 subtests Test Summary Report - --- t/features.t (Wstat: 256 (exited 1) Tests: 1008 Failed: 1) Failed test: 404 Non-zero exit status: 1 Files=54, Tests=1627, 84 wallclock secs ( 0.36 usr 0.13 sys + 59.24 cusr 17.21 csys = 76.94 CPU) Result: FAIL Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmT8UndfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbF5xAAqTTdQbU4Kiqg6RTKeEWRH4tCmV1F+6dv1CoTsv03xDhvhNlgqYSttXqR 3WvK8ZE+ksXypXA8/Uvcouwbyh1mY2ZEC94Och7U51fSbcJJSjcwpWgu5GbOERG4 eLboschzr7yMfROHuhX30cJ7p1jK5LOv5zIFgGVmpK2FmlAPmIoN8xitA3aLZvzy RExQsvsFbqeKts+gPjx0WiC4Uamt0x+mLis34OQzjlWZVniL7A/MGKQlmVIr7zru ZC+eaWjo+Cg2gn131eREaN4HtulfkxxbIPtP0zic0eRc3mY8sDukFgaIQHsqQ3ou XsdyTVqg1eLDZ4GPJq9jVyntBhuqDeLdQa1PZWI8hf2ylzhK2WlrIm0aapAjHfHX qazv68rGzkCWgdqxzoqPiCnVHdx57niNEmXpII1+96RQog7n+JA7rdhVF+pFumrD OjlvzGhqQiIzXUEwxrpnhFPhh5GEDS3JbYn0wkrToEER5UdBQoW2eLe6FWBA6Dqq EVKOTlsFaayogN9kET0iugPYsJo9ZjFPS0fVCgQZWNvSeO3fdPh1Jq0ATka678Dx I9PtXWvMgOsOu4aU3ImZ1JCdujhz4C/CnNxbFsBScBaTGmd83j8zVL5JF71rhZX4 +lBWNk/xoGPDruSSP0Vz+TiaeoEiWt+zc7LVIKNX/ZuJZepyRlE= =E8iv -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: analizo Source-Version: 1.25.4-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of analizo, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated analizo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 May 2024 21:15:58 +0200 Source: analizo Architecture: source Version: 1.25.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Étienne Mollier Closes: 1051534 Changes: analizo (1.25.4-3) unstable; urgency=medium . * Team upload. * doxygen-1.9.8.patch: new: update test item. A discrepancy tolerated in initial test results went resolved in recent doxygen versions, so this patch updates the new expected test result. (Closes: #1051534) * Declare compliance with Debian Policy 4.7.0. Checksums-Sha1: b5949c76f7f268e2ef02709b66d583131b9a1072 3277 analizo_1.25.4-3.dsc fbfb6b069655ec8f045a7f566732c87c6db78b65 7560 analizo_1.25.4-3.debian.tar.xz Checksums-Sha256: 87e277a5598409f6a0e085e1e1e8f307cd1184fa3ed9e38d22f9502b80f3b733 3277 analizo_1.25.4-3.dsc
Processed: Bug#1051534 marked as pending in analizo
Processing control commands: > tag -1 pending Bug #1051534 [src:analizo] analizo: Test failure in t/features.t during build and autopkgtests Ignoring request to alter tags of bug #1051534 to the same tags previously set -- 1051534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1051534: analizo: Test failure in t/features.t during build and autopkgtests
Processing control commands: > tags -1 + confirmed patch pending upstream Bug #1051534 [src:analizo] analizo: Test failure in t/features.t during build and autopkgtests Added tag(s) pending, upstream, patch, and confirmed. -- 1051534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1071552 is important
Processing commands for cont...@bugs.debian.org: > # a bug which has a major effect on the usability of a package, without > rendering it completely unusable to everyone. > severity 1071552 important Bug #1071552 [gnupg] gnupg: Please upgrade GnuPG >= 2.4.4, current GnuPG break Emacs's EasyPG Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070002: marked as done (rust-alsa FTBFS on 32bit with 64bit time_t)
Your message dated Tue, 21 May 2024 16:32:32 +
with message-id
and subject line Bug#1070002: fixed in rust-alsa 0.8.1-4
has caused the Debian Bug report #1070002,
regarding rust-alsa FTBFS on 32bit with 64bit time_t
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.)
--
1070002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-alsa
Version: 0.8.1-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:rust-cpal
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/rust-alsa.html
https://buildd.debian.org/status/fetch.php?pkg=rust-cpal=armhf=0.15.2-3%2Bb1=1714250098=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1113:21
|
1113 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1119:21
|
1119 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1125:21
|
1125 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: could not compile `alsa` due to 3 previous errors
...
--- End Message ---
--- Begin Message ---
Source: rust-alsa
Source-Version: 0.8.1-4
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-alsa, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-alsa
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: Tue, 30 Apr 2024 05:40:48 +
Source: rust-alsa
Architecture: source
Version: 0.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 1070002
Changes:
rust-alsa (0.8.1-4) unstable; urgency=medium
.
* Team upload.
* Package alsa 0.8.1 from crates.io using debcargo 2.6.1
* Fix FTBFS with rust-libc crate patched for time64 (Closes: #1070002)
Checksums-Sha1:
73b8b4e3f3d458f07c26d604bdbed2ef7dc8266d 2308 rust-alsa_0.8.1-4.dsc
4e4d3be0158a7949bc87a8bd2b1d540480c8eedb 3852 rust-alsa_0.8.1-4.debian.tar.xz
78a71b3c801a01cdae98ec6fb165e92b7b3c25ac 8904
rust-alsa_0.8.1-4_source.buildinfo
Checksums-Sha256:
28e7ecb8e7dacaf11f3548bd7e59ca7a1b5a9f1f47a7099989252cca5a7da2c8 2308
rust-alsa_0.8.1-4.dsc
0e412b925c93101f727988272d6b984c5ce8a677b4da4c8741a85838cc23c834 3852
rust-alsa_0.8.1-4.debian.tar.xz
fde63def1570dcb26ecae482e14e5e766b46a806db4308069d3499e90f47e9ae 8904
rust-alsa_0.8.1-4_source.buildinfo
Files:
042d95164d5576c523fa5861ad246bac 2308 rust optional rust-alsa_0.8.1-4.dsc
e5b6a45893d1db86a4c8855d820379aa 3852 rust optional
rust-alsa_0.8.1-4.debian.tar.xz
b31f29b170f1e642a5bf71121acf5cbe 8904 rust optional
rust-alsa_0.8.1-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmZMxKUUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtnYRAAnIcvhPk9ZOo2pPWePjmMWpSAuyTE
9OuQncdhB+8ImoSj8fqHjZpAYYGXCkOJGhMR0WFhq26fLqvTRTKQNRFZsroqIBxw
980pI00va14EQnUu1yHBs7zhz5I9SzoA/ovneENSdVKlQ/0CDhjUtSFmyLQQV414
7VtCD5FOL2MS3z3Dn+1/oarG1J1CMez6WBgU7G8LsmtY7MWfE0lgipXujduVVlij
XQXNY5D4dE4B0tUUe2vtciQo9hLOJ3NtjuvQrUZJdOfabsfp09ENAEXPfpnM0J8J
9H57r2+TBiRrI9WZ2j6xCi3FimcnUutpy4Nkwjh5RxjU45CNiP2AQu7xnqIoyVdp
wKqiRwQK9N8tXwRrMzyBcqPdNMhqskzMk9EBOlYUtpirMae9HQQLLHXX89ULGjpz
Rwb1oK7jzTDWlSJlWvGzKMv50kt7sHV28SdIRWFLjEmMIV7ZiGL6DLRN440c5Fwl
57lZPqVkq/RiIPuwWCSITHRFFw+fYsB0iimmhoRcc/DVeJ470EhL7fz
Bug#1070895: marked as done (boxbackup: FTBFS: ERROR: SSL or crypto error: connecting: error:0A000086:SSL routines::certificate verify failed)
Your message dated Tue, 21 May 2024 16:19:23 + with message-id and subject line Bug#1070895: fixed in boxbackup 0.13~~git20231028.g3dd5194+ds-3 has caused the Debian Bug report #1070895, regarding boxbackup: FTBFS: ERROR: SSL or crypto error: connecting: error:0A86:SSL routines::certificate verify failed 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.) -- 1070895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:boxbackup Version: 0.13~~git20231028.g3dd5194+ds-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead debian/rules override_dh_autoreconf make[1]: Entering directory '/<>' echo "0.13~~git20231028.g3dd5194+ds-2" > VERSION.txt echo "boxbackup" >> VERSION.txt sh -x ./bootstrap + aclocal -I infrastructure/m4 + autoheader + autoconf configure.ac:12: warning: The macro `AC_CANONICAL_SYSTEM' is obsolete. [... snipped ...] == test_compare_detects_attribute_changes == WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel NOTICE: skipping test on this platform Waiting for server to die (pid 1933959): . done. NOTICE: test_compare_detects_attribute_changes passed == test_sync_new_files == WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: location path is not absolute: testfiles/TestDir1 WARNING: location path is not absolute: testfiles/TestDir1 WARNING: location path is not absolute: testfiles/TestDir1 WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. Waiting for server to die (pid 1933985): . done. NOTICE: test_sync_new_files passed == test_rename_operations == WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: location path is not absolute: testfiles/TestDir1 WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. WARNING: location path is not absolute: testfiles/TestDir1 WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. WARNING: Quick compare used -- file attributes are not checked. WARNING: location path is not absolute: testfiles/TestDir1 WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. Waiting for server to die (pid 1934065): . done. NOTICE: test_rename_operations passed == test_sync_files_with_timestamps_in_future == WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: location path is not absolute: testfiles/TestDir1 WARNING: location path is not absolute: testfiles/TestDir1 WARNING: Some files have modification times excessively in the future. Check clock synchronisation. Example file (only one shown): testfiles/TestDir1/sub23/in-the-future WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: Failed to determine the time of the last synchronisation -- checks not performed. Waiting for server to die (pid 1934170): . done. NOTICE: test_sync_files_with_timestamps_in_future passed == test_changing_client_store_marker_pauses_daemon == WARNING: SSLSecurityLevel set very low (0-1). Your connection may not be secure. See https://bit.ly/sslseclevel WARNING: SSLSecurityLevel set very low (0-1). Your conne
Processed: Bug#1069904 marked as pending in python-gnupg
Processing control commands: > tag -1 pending Bug #1069904 [python3-gnupg] Autopkgtests failed Added tag(s) pending. -- 1069904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061627: marked as done (jpeg-xl: 0.8 failing autopkgtest)
Your message dated Tue, 21 May 2024 13:49:20 + with message-id and subject line Bug#1061627: fixed in jpeg-xl 0.8.2-2 has caused the Debian Bug report #1061627, regarding jpeg-xl: 0.8 failing autopkgtest 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.) -- 1061627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpeg-xl Version: 0.8.2-1 Severity: serious jpeg-xl in Experimental has a failing autopkgtest. This will need to be fixed before it is possible for jpeg-xl 0.8.2 to reach Testing. Log excerpt --- Test - Lossless Roundtrip JPEG XL encoder v0.8.2 [AVX2,SSE4,SSSE3,SSE2] ./lib/extras/dec/color_hints.cc:54: No color_space/icc_pathname given, assuming sRGB Read 320x320 image, 1228816 bytes, 814.0 MP/s Encoding [Modular, lossless, effort: 7], ./lib/jxl/encode.cc:263: Only JXL_BIT_DEPTH_FROM_PIXEL_FORMAT is implemented for float types. ./lib/jxl/encode.cc:1848: Invalid input bit depth JxlEncoderAddImageFrame() failed. EncodeImageJXL() failed. Full logs --- https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/ Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: jpeg-xl Source-Version: 0.8.2-2 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of jpeg-xl, 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. Mathieu Malaterre (supplier of updated jpeg-xl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 May 2024 15:35:24 +0200 Source: jpeg-xl Architecture: source Version: 0.8.2-2 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Closes: 1061627 Changes: jpeg-xl (0.8.2-2) experimental; urgency=medium . * d/patches: Fix failing auto-test. Closes: #1061627 Checksums-Sha1: 9f82c62df0655c1d47cb676ffc86192c7aa1b3fa 3067 jpeg-xl_0.8.2-2.dsc 46ad535730289a31d81e68a870c65b067fa51975 24616 jpeg-xl_0.8.2-2.debian.tar.xz 9763de8ad03c2fa80bb45e96c9c8c921f119b7b2 14327 jpeg-xl_0.8.2-2_source.buildinfo Checksums-Sha256: b1ab973d52176d471bfaed3660fd6e8b1457db1a454451472d588f3828f3745a 3067 jpeg-xl_0.8.2-2.dsc d298c2039b70bd0c8b3b03e2fe424ae5a0ce475eb18655bfc98d2e8b46b06703 24616 jpeg-xl_0.8.2-2.debian.tar.xz 556565be0ea42e921ce660bb712ee6e335d629af9888339b50ddb0ca4987100b 14327 jpeg-xl_0.8.2-2_source.buildinfo Files: b686e3f164a19d470d6570c5b61c30b0 3067 graphics optional jpeg-xl_0.8.2-2.dsc 95055f3f878c01fbd535f4624363712c 24616 graphics optional jpeg-xl_0.8.2-2.debian.tar.xz cb42ea5eeba99c665082f847fc0433f7 14327 graphics optional jpeg-xl_0.8.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmZMo4YRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0XkYw/9EWHHJcv2qVeUoQMq7GUTjg5uFs/yhzXd Qoou+X04GM4+EnFhr2VUYRWYXOMkeRlpJaCvtx25RV77afPaABN/aWY2a049f8xb js2oIrxpL67SVYyd4ua1o4VmCko1YtRKcJmP+YsraEv9U3Tqq0WLVMm136nCfU6h Ttyh9QhulAIiAHw4hDVvoykah9OuPfcKBcR35qo4TBHVkYDM8wxGmIuqwYSCZFLY H2YWp32CXtqWfgaIeR+23BALU85H/xVEAxwclmmzZOIth+2pX8D/3voj77w+0u/B ImNuARv7rW9lSVsXA27HWtAC5Si5FQ1qoz/p1zRvyX+h6/7UvbR4DmNtMXmjFweM lrjiKeODTrZc2AoEETfJ/+FVaZ+PeFCeHJty3SWUYfuvMv2N212A8tFJSaka7mOs VyaubJet/H6wy0GCvBOJ8FPu9NKwlUQdn50Rn/gEY0KrJuANeZc93TSBBtmAviTo cxfa5W1M5SFWxApo0i6dAX7Jrl1E3zwQlZ1g6JdlGi+RpGUc6cSKht/IJEyLKVgE 52U4RZQMbyfZNWTqPZfXfS80/XW6YGrmi/tZY+fYG9VmDPteruDg3Mi93XtrMSj8 M610KrlYFWa6cEWXd4+sdyPw2PB7Nuyw/yaPlKFTYvH/COsAtXWT79KBLRnqgua0 CxuwZHF1TTk= =IqYr -END PGP SIGNATURE- pgpwwYi_FrrIs.pgp Description: PGP signature --- End Message ---
Bug#1071361: marked as done (rp-pppoe: FTBFS: if.c:462:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’?)
Your message dated Tue, 21 May 2024 13:34:29 + with message-id and subject line Bug#1071361: fixed in rp-pppoe 4.0-1 has caused the Debian Bug report #1071361, regarding rp-pppoe: FTBFS: if.c:462:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? 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.) -- 1071361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rp-pppoe Version: 3.15-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh_testdir test -f src/Makefile || (cd src && PPPD=/usr/sbin/pppd ./configure) checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for ranlib... ranlib checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking sys/dlpi.h usability... no checking sys/dlpi.h presence... no checking for sys/dlpi.h... no checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking for unistd.h... (cached) yes checking net/if_arp.h usability... yes checking net/if_arp.h presence... yes checking for net/if_arp.h... yes checking netinet/if_ether.h usability... yes checking netinet/if_ether.h presence... yes checking for netinet/if_ether.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking for fcntl.h... (cached) yes checking net/bpf.h usability... no checking net/bpf.h presence... no checking for net/bpf.h... no checking netpacket/packet.h usability... yes checking netpacket/packet.h presence... yes checking for netpacket/packet.h... yes checking net/ethernet.h usability... yes checking net/ethernet.h presence... yes checking for net/ethernet.h... yes checking asm/types.h usability... yes checking asm/types.h presence... yes checking for asm/types.h... yes checking linux/if_packet.h usability... yes checking linux/if_packet.h presence... yes checking for linux/if_packet.h... yes checking linux/if_ether.h usability... yes checking linux/if_ether.h presence... yes checking for linux/if_ether.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking net/if.h usability... yes checking net/if.h presence... yes checking for net/if.h... yes checking net/if_dl.h usability... no checking net/if_dl.h presence... no checking for net/if_dl.h... no checking net/if_ether.h usability... no checking net/if_ether.h presence... no checking for net/if_ether.h... no checking net/if_types.h usability... no checking net/if_types.h presence... no checking for net/if_types.h... no checking for netinet/if_ether.h... (cached) yes checking for net/if_types.h... (cached) no checking for net/if_dl.h... (cached) no checking for linux/if.h... yes checking for linux/if_pppox.h... yes checking for an ANSI C-conforming const... yes checking for pid_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct sockaddr_ll... yes checking fo
Processed: bug 1068782 is forwarded to https://github.com/libesmtp/libESMTP/issues/21
Processing commands for cont...@bugs.debian.org: > forwarded 1068782 https://github.com/libesmtp/libESMTP/issues/21 Bug #1068782 [libesmtp] libesmtp: fixes for t64 and new glibc Set Bug forwarded-to-address to 'https://github.com/libesmtp/libESMTP/issues/21'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068430: marked as done (libqt5-ukui-style1 dependencies unsatisfiable on 32-bit non-i386 architectures.)
Your message dated Tue, 21 May 2024 13:19:37 + with message-id and subject line Bug#1068430: fixed in qt5-ukui-platformtheme 1.0.8-3 has caused the Debian Bug report #1068430, regarding libqt5-ukui-style1 dependencies unsatisfiable on 32-bit non-i386 architectures. 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.) -- 1068430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt5-ukui-style1 Version: 1.0.8-1 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, libqt5-ukui-style1 depends on both libqt5widgets5 and libqt5widgets5. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu appear to have already fixed this. http://launchpadlibrarian.net/721518881/qt5-ukui-platformtheme_1.0.8-1build9_1.0.8-1ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: qt5-ukui-platformtheme Source-Version: 1.0.8-3 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of qt5-ukui-platformtheme, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. handsome_feng (supplier of updated qt5-ukui-platformtheme 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: Tue, 21 May 2024 20:57:06 +0800 Source: qt5-ukui-platformtheme Architecture: source Version: 1.0.8-3 Distribution: unstable Urgency: medium Maintainer: Kylin Team Changed-By: handsome_feng Closes: 1068430 Changes: qt5-ukui-platformtheme (1.0.8-3) unstable; urgency=medium . [Steve Langasek] * Add the missing changes: - Remove hard-coded dependencies on libqt5widgets5 and libgsettings-qt1. - Don't hard-code dependency on shared libglib library. (Closes: #1068430) Checksums-Sha1: 14b830198954f6067294e031966e3cda0b7aff28 2501 qt5-ukui-platformtheme_1.0.8-3.dsc 0a594e77c8e6f0050c7c8adb787821e4a84cd5e9 133915 qt5-ukui-platformtheme_1.0.8.orig.tar.gz c76f2f3a1f7a9be0611a4dfaecc57ceb6f7f0418 3172 qt5-ukui-platformtheme_1.0.8-3.debian.tar.xz ec983e60798646f48635320afff7b3d52e6b3d34 14345 qt5-ukui-platformtheme_1.0.8-3_source.buildinfo Checksums-Sha256: c7c212f00da1cc40ee55d88b9fb84f5f920ebea751c0d74260935309767f37d5 2501 qt5-ukui-platformtheme_1.0.8-3.dsc bbc868c81c5785b97aef4fd0eabe8334d89890e8936a1a52986aae913c71a797 133915 qt5-ukui-platformtheme_1.0.8.orig.tar.gz ae8ad29e90cdf25591c687383ee5e7abc063e990c1c77032b384a3902aed1cb3 3172 qt5-ukui-platformtheme_1.0.8-3.debian.tar.xz 309ced2b342bbcf9a89860a1bda282b4adf3153c1ce589ebaec29469706f8920 14345 qt5-ukui-platformtheme_1.0.8-3_source.buildinfo Files: 68ce121d0d0bb84f6a9b36b83d0b36ec 2501 libs optional qt5-ukui-platformtheme_1.0.8-3.dsc eac6cee451fbe1d8c21ad1d80c9c5a09 133915 libs optional qt5-ukui-platformtheme_1.0.8.orig.tar.gz 7f15fb6f005b3754747d3b5e7531dab5 3172 libs optional qt5-ukui-platformtheme_1.0.8-3.debian.tar.xz 50264189fb8ca2e6348101b7fd1f45e4 14345 libs optional qt5-ukui-platformtheme_1.0.8-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmZMm5EbHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8M4SgQAKR/hP9uQrrNgeJw9RbG NBxx+t1JJ9XquyRY45QEgAoiwWW7D32XnqTzjc9GL0MuJvrF2Dics9Wq37B2xTWI jLOXnIS4vUOhryd6feoZ6Kjq8DXfLWpOE/a8E4VP8rYBR3BJkx/zhkOlU5a05pz4 McKUChMtz1/nSlIhXXHxAvBXpEXMGJlwPW7Xgy5OEY83XpH9jtmgekZFIXImqi/i MclOslFYcmXoGrmV8qCw1kT5sYfbECgc2ana4r2Su/j7RKvTpTPwtOBGip0H9exX XTMHpPDi/LODpPE+f4zr67JjSEgSGg2uFfCKoJHC9kFkr/yh+/C1T/QQaV9TeLe8 J0gMkFqKR6lFKCSYtFX0j+qcpiYMEk++/ovEDACWvB9KKyJh3soDxoPD0n+wg/Ed UnaYIvvvOgMXi7OAYvACSErxlXBxJgHwV5ocgXHhFd4VFX8AOL/5RsXSc59LHZB0 V71yDs6RjLZqf0R4Z7xlLCUTHfueQiDLoTxi1l2vL44X67Q31elKnKzll2gN2C1J 3hX1RHBJyjBCkoPv5Jad8pa5F7ligBy+PKOtjUaGFvheerxZw/ZGkysrTA+KeJxw GJezVbFoqniPDjvfOZNLri/fjd4Nf07eTj/744rdr0b3Rzkx6SK7zub6ij3nRJ+5 aCvgDLPw086eiBDVpqHHIiCT =J6Ad -END PGP SIGNATURE- pgpSLBb2OrL8s.pgp Description: PGP signature --- End
Processed: tagging 1071268, severity of 1071268 is serious, found 1071559 in 9.011.00-4 ...
Processing commands for cont...@bugs.debian.org: > tags 1071268 + sid trixie Bug #1071268 [nat-rtsp-dkms] nat-rtsp-dkms: fails to build on kernel 6.8.9 Added tag(s) trixie and sid. > severity 1071268 serious Bug #1071268 [nat-rtsp-dkms] nat-rtsp-dkms: fails to build on kernel 6.8.9 Severity set to 'serious' from 'normal' > found 1071559 9.011.00-4 Bug #1071559 [r8125-dkms] linux-headers-6.8.9-amd64: error creating r8125 module with dkms Marked as found in versions r8125/9.011.00-4. > severity 1071559 serious Bug #1071559 [r8125-dkms] linux-headers-6.8.9-amd64: error creating r8125 module with dkms Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071268 1071559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: r-cran-metamix: FTBFS on armhf: tests fail
Processing control commands: > severity -1 important Bug #1069509 [src:r-cran-metamix] r-cran-metamix: FTBFS on armhf: tests fail Severity set to 'important' from 'serious' > tags -1 + moreinfo Bug #1069509 [src:r-cran-metamix] r-cran-metamix: FTBFS on armhf: tests fail Added tag(s) moreinfo. -- 1069509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1061627: jpeg-xl: 0.8 failing autopkgtest
Processing control commands: > tags -1 upstream patch fixed-upstream Bug #1061627 [src:jpeg-xl] jpeg-xl: 0.8 failing autopkgtest Added tag(s) upstream, patch, and fixed-upstream. > forwarded -1 https://github.com/libjxl/libjxl/issues/2391 Bug #1061627 [src:jpeg-xl] jpeg-xl: 0.8 failing autopkgtest Set Bug forwarded-to-address to 'https://github.com/libjxl/libjxl/issues/2391'. -- 1061627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070426: marked as done (ukui-power-manager: fails to install: ukui-power-manager.postinst: 5: glib-compile-schemas: not found)
Your message dated Tue, 21 May 2024 11:35:25 + with message-id and subject line Bug#1070426: fixed in ukui-power-manager 4.0.0.1-2 has caused the Debian Bug report #1070426, regarding ukui-power-manager: fails to install: ukui-power-manager.postinst: 5: glib-compile-schemas: not found 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.) -- 1070426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ukui-power-manager Version: 4.0.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up ukui-power-manager (4.0.0.1-1) ... /var/lib/dpkg/info/ukui-power-manager.postinst: 5: glib-compile-schemas: not found dpkg: error processing package ukui-power-manager (--configure): installed ukui-power-manager package post-installation script subprocess returned error exit status 127 cheers, Andreas ukui-power-manager_4.0.0.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ukui-power-manager Source-Version: 4.0.0.1-2 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of ukui-power-manager, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. handsome_feng (supplier of updated ukui-power-manager 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: Tue, 21 May 2024 19:09:06 +0800 Source: ukui-power-manager Architecture: source Version: 4.0.0.1-2 Distribution: unstable Urgency: medium Maintainer: kylin Team Changed-By: handsome_feng Closes: 1070426 Changes: ukui-power-manager (4.0.0.1-2) unstable; urgency=medium . * Add missing depends: libglib2.0-bin. (Closes: #1070426) Checksums-Sha1: 7349c62f28204e539ad7a4aac187ea3f1efb7689 2376 ukui-power-manager_4.0.0.1-2.dsc c046fbc29c533914986ab1d69a067a603aa2a754 100777 ukui-power-manager_4.0.0.1.orig.tar.gz 7c1668fda592090f449e590a7c14346a2a9be735 2884 ukui-power-manager_4.0.0.1-2.debian.tar.xz cf462d37e201f5c35d9c3846e09f07161d42b1fe 18411 ukui-power-manager_4.0.0.1-2_source.buildinfo Checksums-Sha256: 0be95a107503f9fb9ea6d6da20c0615d2fccf04b8f7dd0f3702b1211808eff7d 2376 ukui-power-manager_4.0.0.1-2.dsc b5ecc0664506649f831bae6823eaffd51ab8037094de00e61f163966a83b629b 100777 ukui-power-manager_4.0.0.1.orig.tar.gz 208229112e7cf6fd2977f617d05fb79691e6b057bd59054a643544eabecada97 2884 ukui-power-manager_4.0.0.1-2.debian.tar.xz 11e5264081aa93956b37cb96a32f85fb7850e91b80919e92ea9600d675814860 18411 ukui-power-manager_4.0.0.1-2_source.buildinfo Files: acbaeb924df43b00e18b02865460dcce 2376 x11 optional ukui-power-manager_4.0.0.1-2.dsc 0de75cd5e9efc539881b47b2800d7363 100777 x11 optional ukui-power-manager_4.0.0.1.orig.tar.gz 2d941a9d626a05a393239944928a75d1 2884 x11 optional ukui-power-manager_4.0.0.1-2.debian.tar.xz a4bbada8c3156d584f6103a94b0a7f1e 18411 x11 optional ukui-power-manager_4.0.0.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmZMgS8bHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MOQQQAJ8Rb8HbXudsPJ60GAng /N1cf9Y1W8qm7StoPj5O1sOdKgEKY3gmWAOLyvDClIMh/D8v86Y6mua5wDcRmCVR xgaz/9FWK6xIm49qojOt4ubG3jKbeO1tBAzUW1l9FVH9JS+fkZFlXt5Kbnr1Gdd/ XubjVBWyzRkPY/dpmM5Rh/dz7Cf2STXWW78pZD5SKwGYfxL2v2OU85Lk2S2K6nmi BJNEf6WSQbMcqMnhVsztIF+g2ae86m+d9Aqz173/CQGK3Wg17cBctu7u07XhyICx EPVbBKUSQz7wea4hLmNve3WADf9WNmu9LkGHAGr4nqnnVLjLkLGguir5mUNuPoGg nCjB+/bkmS+rOEi3cpmvlBYdZNmpgoh1V96ASX7+5p8b/eabFiqj3+oelHenuZ4O rJ+haU0UMBXijJk9NdSTU7Npn7GwYVGBD5uUu1JbGT2ggw2MDAPdEW5mBw6KaMGv zpMRFkWK5RdcyOhd12PrjQm5FlttALjUuXvUppP36+n9uFXcyqn962svELkYkVvi 9bGscwNT+3Er037FVvjFFg7kTaKWkIyneNwo8f/DLG9tSPMUfHjWrjAFl4u1kYpn Yc5fkAoxr4bS0OJV8+/jfhgkKd93K3p/NsSpaoJxUo+fjscT+WsDlTPkXkwAj51p Nufm+JyVrcI5sWTZdnPbOpt6 =lv9l -END PGP SIGNATURE- pgpMNL47TD
Bug#1062881: marked as done (mia: NMU diff for 64-bit time_t transition)
Your message dated Tue, 21 May 2024 10:24:29 +
with message-id
and subject line mia: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1062881,
regarding mia: NMU diff for 64-bit time_t transition
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.)
--
1062881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mia
Version: 2.4.7-13
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
mia as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for mia
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru mia-2.4.7/debian/changelog mia-2.4.7/debian/changelog
--- mia-2.4.7/debian/changelog 2023-08-29 09:00:00.0 +
+++ mia-2.4.7/debian/changelog 2024-02-03 20:51:49.0 +
@@ -1,3 +1,10 @@
+mia (2.4.7-13.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs Sat, 03 Feb 2024 20:51:49 +
+
mia (2.4.7-13) unstable; urgency=medium
* Team upload.
diff -Nru mia-2.4.7/debian/control mia-2.4.7/debian/control
--- mia-2.4.7/debian/control2023-08-29 09:00:00.0 +
+++ mia-2.4.7/debian/control2024-02-03 20:51:49.0 +
@@ -38,7 +38,10 @@
Homepage: https://mia.sourceforge.net
Rules-Requires-Root: no
-Package: libmia-2.4-4
+Package: libmia-2.4-4t64
+Provides: ${t64:Provides}
+Replaces: libmia-2.4-4
+Breaks: libmia-2.4-4 (<< ${source:Version})
Architecture: any
Section: libs
Depends: ${shlibs:Depends},
@@ -53,7 +56,7 @@
Package: libmia-2.4-dev
Architecture: any
Section: libdevel
-Depends: libmia-2.4-4 (= ${binary:Version}),
+Depends: libmia-2.4-4t64 (= ${binary:Version}),
mia-doctools (= ${source:Version}),
libitpp-dev,
libgsl-dev,
@@ -85,7 +88,7 @@
Package: mia-tools
Architecture: any
-Depends: libmia-2.4-4 (= ${binary:Version}),
+Depends: libmia-2.4-4t64 (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends}
Recommends: mia-tools-doc
diff -Nru mia-2.4.7/debian/libmia-2.4-4.install
mia-2.4.7/debian/libmia-2.4-4.install
--- mia-2.4.7/debian/libmia-2.4-4.install 2023-08-29 09:00:00.0
+
+++ mia-2.4.7/debian/libmia-2.4-4.install 1970-01-01 00:00:00.0
+
@@ -1,2 +0,0 @@
-usr/lib/*/lib*.so.*
-usr/lib/*/mia-2.4/plugins/*
diff -Nru mia-2.4.7/debian/libmia-2.4-4.lintian-overrides
mia-2.4.7/debian/libmia-2.4-4.lintian-overrides
--- mia-2.4.7/debian/libmia-2.4-4.lintian-overrides 2023-08-29
09:00:00.0 +
+++ mia-2.4.7/debian/libmia-2.4-4.lintian-overrides 1970-01-01
00:00:00.0 +
@@ -1,2
Bug#1061421: marked as done (Fails to start after an upgrade)
Your message dated Tue, 21 May 2024 19:16:51 +0900 with message-id <7fc80cb444df51d15c0b9d0b7e88a...@duckcorp.org> and subject line Re: Bug#1061421: Fails to start after an upgrade has caused the Debian Bug report #1061421, regarding Fails to start after an upgrade 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.) -- 1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wlgreet Version: 0.4.1-3 Severity: grave After a semi-recent upgrade (I'm not sure which one, as I don't reboot or restart my session after each one) of testing wlgreet no longer starts. Here is what I get when trying to start it under a manually launched sway session: RUST_BACKTRACE=full wlgreet thread 'main' panicked at 'internal error: entered unreachable code', src/app.rs:473:48 stack backtrace: 0: 0x562fb820dd27 - 1: 0x562fb81db7ef - 2: 0x562fb821a5d4 - 3: 0x562fb820d9cf - 4: 0x562fb8217dee - 5: 0x562fb8218960 - 6: 0x562fb820e194 - 7: 0x562fb820e126 - 8: 0x562fb82181f1 - 9: 0x562fb81c1822 - 10: 0x562fb81c187c - 11: 0x562fb829de53 - 12: 0x562fb8269b29 - 13: 0x7fb720bb9a4e - 14: 0x7fb720bb5bb1 - 15: 0x7fb720bb75ac - wl_display_dispatch_queue_pending 16: 0x7fb720bb7b5f - wl_display_roundtrip_queue 17: 0x562fb8298d69 - 18: 0x562fb81cfa3a - 19: 0x562fb82a01a3 - 20: 0x562fb81d225c - 21: 0x7fb7208eb6ca - 22: 0x7fb7208eb785 - __libc_start_main 23: 0x562fb81c7de1 - 24:0x0 - [wayland-client error] A handler for wl_surface panicked. The issue is reproducible under debvm as follows: debvm-create -o /tmp/debvm -r trixie -- --include=linux-image-amd64,wlgreet,greetd --hook-dir /usr/share/mmdebstrap/hooks/useradd && debvm-run -i /tmp/debvm -g Modify greetd config to start sway (comment out agreety, uncomment sway) and restart it, wlgreet fails with what looks like the same error message. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages wlgreet depends on: ii libc6 2.37-13 ii libgcc-s1 13.2.0-10 ii sway 1.9~debian.2bba8a86-2 wlgreet recommends no packages. wlgreet suggests no packages. -- Configuration Files: /etc/greetd/sway-config changed: exec "/usr/sbin/wlgreet; swaymsg exit" bindsym Mod4+shift+e exec swaynag \ -t warning \ -m 'What do you want to do?' \ -b 'Poweroff' 'systemctl poweroff -i' \ -b 'Reboot' 'systemctl reboot -i' include /etc/sway/config.d/* include /etc/greetd/sway-config.d/* -- no debconf information --- End Message --- --- Begin Message --- Version: 0.5.0-1 On 2024-05-18 03:22, Ryan Kavanagh wrote: The bug is also fixed for me with 0.5.0-1. Thanks for getting this fixed! Thanks for the feedback everyone. Regards. \_o< -- Marc Dequènes--- End Message ---
Bug#1070113: marked as done (kylin-nm: predictable filenames under /tmp with system())
Your message dated Tue, 21 May 2024 09:19:11 +
with message-id
and subject line Bug#1070113: fixed in kylin-nm 3.0.3.1-2
has caused the Debian Bug report #1070113,
regarding kylin-nm: predictable filenames under /tmp with system()
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.)
--
1070113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kylin-nm
Version: 3.0.3.1-1
Severity: grave
Tags: security
Justification: user security hole
Hi,
the kylin_network_get_activecon_info() function in
src/kylin-network-interface.c uses predictable filenames under /tmp
and invokes system() on it:
| activecon *kylin_network_get_activecon_info()
| {
| struct passwd *pwd;
| pwd = getpwuid(getuid());
| char *name = pwd->pw_name;
| char *tmpPrefix = "/tmp/kylin-nm-activecon-";
| char *chr = "nmcli connection show -active > ";
|
| char *cmd;
| asprintf(, "%s%s%s", chr, tmpPrefix, name);
| char *path;
| asprintf(, "%s%s", tmpPrefix, name);
| int status = system(cmd);
| if (status != 0)
| syslog(LOG_ERR, "execute 'nmcli connection show -active' in function
'kylin_network_get_activecon_info' failed");
| free(cmd);
Predictable filenames under /tmp and executing system() on it is
highly problematic and a potential security issue. It should instead
use e.g. mkstemp() and the execl-family of functions or similar.
FTR: the same code is present also in ukui-screensaver, which seems
to have a copy of the KylinNM source code included.
regards
-mika-
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kylin-nm
Source-Version: 3.0.3.1-2
Done: handsome_feng
We believe that the bug you reported is fixed in the latest version of
kylin-nm, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
handsome_feng (supplier of updated kylin-nm
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: Tue, 21 May 2024 16:53:40 +0800
Source: kylin-nm
Architecture: source
Version: 3.0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team
Changed-By: handsome_feng
Closes: 1070113
Changes:
kylin-nm (3.0.3.1-2) unstable; urgency=medium
.
* Add patch: fix-security-issue-predictable-filenames-with-system.
(Closes: #1070113)
Checksums-Sha1:
1e73f987dcf9fda731fc75d109e0dd12a926605c 2104 kylin-nm_3.0.3.1-2.dsc
33113de0280e90426bfe1c4b17e64d85b2ad5b35 329205 kylin-nm_3.0.3.1.orig.tar.gz
c3930e7891eb2f668fb1430efea1ba7f06c9cce4 4680 kylin-nm_3.0.3.1-2.debian.tar.xz
24b960db01d4b5de238ebce24ac0865171c8acee 12706
kylin-nm_3.0.3.1-2_source.buildinfo
Checksums-Sha256:
47dbbe0c64258dd9909de7d295da45ebfc56d9aabbf2a4c25008147d7aaf92d3 2104
kylin-nm_3.0.3.1-2.dsc
93152fedb61678724b8348c269cb6b670b77f1f5e973d818c3520a441b6a68ad 329205
kylin-nm_3.0.3.1.orig.tar.gz
2272ea8d2768584e137e86dacc47a13661ed7b81abcfd55cea59163e6d6a4ebf 4680
kylin-nm_3.0.3.1-2.debian.tar.xz
b9590a26ad653d5921c9d4b3526802642321bbd5064b681c99f3196b6d048cee 12706
kylin-nm_3.0.3.1-2_source.buildinfo
Files:
75d1278ed4609f450ee6dbc7a4f8fa97 2104 utils optional kylin-nm_3.0.3.1-2.dsc
3e501e67585da57e28c51d449806bd88 329205 utils optional
kylin-nm_3.0.3.1.orig.tar.gz
1d4cf2e972a3a0282acbfa958b9fc368 4680 utils optional
kylin-nm_3.0.3.1-2.debian.tar.xz
877dcd8dc01f2b5acad8facde08b02f3 12706 utils optional
kylin-nm_3.0.3.1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmZMYckbHGppYW5mZW5n
bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8M16gQAJubcnewwcXt41wAAceI
EYYK6E9VrR/R9mtvIDDCdJkMjXCHUdPi0xdgiRwg25c1tpMMZ9dqAt1fGCE1WqOD
8cBXS3Ga4Tc20huf5Jo2cwiD48yBALHP0mstxCD4POk3AX/AWnfiSofZHF4pgtvN
rH4ThaLRgoelh4mhQjO51TCehKpRVj16nhQ1Jmj55gyQmpUvBXltCUpzfLihduem
JI2XuuJ6rlxf7KxTQgPoG2/pBW07GUEUxX2484AeYQhibjKnkZJJkjGmayJ4Sl/Y
hElqkdmfGtXhhjjCeWZ7Lr4TWtNEXyQXrUBpeugpvorcQL8nCi/bxiKmAo2QexaH
mVeWQPBWYkngDqeDF07xDhdzZl9DJSc4UhsY18Zr4yZJyukR1q
Bug#1069408: marked as done (libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev)
Your message dated Tue, 21 May 2024 09:19:49 + with message-id and subject line Bug#1069408: fixed in libxcb 1.17.0-2 has caused the Debian Bug report #1069408, regarding libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev 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.) -- 1069408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kwin Version: 4:5.27.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > cd /<>/obj-aarch64-linux-gnu/src && /usr/bin/c++ > -DCMS_NO_REGISTER_KEYWORD=1 -DEGL_NO_PLATFORM_SPECIFIC_TYPES -DEGL_NO_X11 > -DKCOREADDONS_LIB -DMESA_EGL_NO_X11_HEADERS -DQT_CONCURRENT_LIB -DQT_CORE_LIB > -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB > -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS > -DQT_NO_URL_CAST_FROM_STRING -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB > -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB > -DQT_XKBCOMMON_SUPPORT_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE > -Dkwin_EXPORTS -I/<>/obj-aarch64-linux-gnu/src > -I/<>/src > -I/<>/obj-aarch64-linux-gnu/src/kwin_autogen/include > -I/<>/src/colors -I/<>/src/platformsupport > -I/<>/src/tabbox -I/<>/src/effects > -I/<>/src/libkwineffects > -I/<>/obj-aarch64-linux-gnu/src/wayland > -I/<>/obj-aarch64-linux-gnu/src/libkwineffects > -I/<>/src/platformsupport/scenes/qpainter > -I/<>/src/platformsupport/scenes/opengl > -I/<>/src/platformsupport/vsyncconvenience -isystem > /usr/include/KF5/KConfig -isystem /usr/include/KF5/KConfigCore -isystem > /usr/include/KF5 -isystem /usr/include/aarch64-linux-gnu/qt5 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore -isystem > /usr/lib/aarch64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KWindowSystem -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/aarch64-linux-gnu/qt5/QtConcurrent -isystem > /usr/include/aarch64-linux-gnu/qt5/QtDBus -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQuick -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQmlModels -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQml -isystem > /usr/include/aarch64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KWidgetsAddons > -isystem /usr/include/KF5/KConfigGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KCodecs > -isystem /usr/include/KF5/KAuthWidgets -isystem /usr/include/KF5/KAuthCore > -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KCrash -isystem > /usr/include/KF5/KGlobalAccel -isystem > /usr/include/aarch64-linux-gnu/qt5/QtX11Extras -isystem > /usr/include/KF5/KI18n -isystem /usr/include/KF5/KPackage -isystem > /usr/include/KF5/KService -isystem /usr/include/KDecoration2 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport/5.15.10/QtXkbCommonSupport > -isystem /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.10/QtGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.10/QtCore -isystem > /usr/include/KF5/KNotifications -isystem /usr/include/libdrm -isystem > /usr/include/KF5/KWayland -isystem /usr/include/KF5/KActivities -isystem > /usr/include/KScreenLocker -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -Wdate-time > -D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra > -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long > -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual > -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override > -Wlogical-op -std=gnu++20 -f
Bug#1071248: marked as done (crowdsec-firewall-bouncer: blocks wrong IPv4 and IPv6 addresses on LE systems (reversed byte order))
Your message dated Tue, 21 May 2024 08:34:31 + with message-id and subject line Bug#1071248: fixed in crowdsec-firewall-bouncer 0.0.25-4 has caused the Debian Bug report #1071248, regarding crowdsec-firewall-bouncer: blocks wrong IPv4 and IPv6 addresses on LE systems (reversed byte order) 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.) -- 1071248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: crowdsec-firewall-bouncer Version: 0.0.25-3 Severity: grave Tags: patch security Justification: renders package unusable X-Debbugs-Cc: Debian Security Team , debian.pack...@crowdsec.net Hi, This is the bouncer side of #1071247: golang-github-google-nftables up to version 0.1.0-3 ships a broken AddSet() function, which results in IPv4 and IPv6 addresses to be in reverse byte order at the nftables level on LE systems (i.e. all release architectures but s930x). This issue was confirmed to go away on LE systems once the bouncer gets rebuilt against a fixed golang-github-google-nftables-dev package, and not to regress on BE systems. Grave looks warranted as the package doesn't fulfill its purposes (blocking suspicious addresses), giving a false sense of security… while also blocking potentially harmless addresses. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ --- End Message --- --- Begin Message --- Source: crowdsec-firewall-bouncer Source-Version: 0.0.25-4 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of crowdsec-firewall-bouncer, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated crowdsec-firewall-bouncer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 May 2024 10:15:36 +0200 Source: crowdsec-firewall-bouncer Architecture: source Version: 0.0.25-4 Distribution: unstable Urgency: high Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Closes: 1071248 Changes: crowdsec-firewall-bouncer (0.0.25-4) unstable; urgency=high . * Set minimal version for the golang-github-google-nftables-dev build dependency to ensure a working AddSet() function, i.e. no longer reversing byte order for IPv4 and IPv6 addresses at the nftables level on little-endian architectures (Closes: #1071248, See: #1071247). Checksums-Sha1: e11fc3a45ceba91dec4bee14bb5cb35ea2c2e9b9 2602 crowdsec-firewall-bouncer_0.0.25-4.dsc 2051792153b25422adc11b215f101099220e4b7d 7600 crowdsec-firewall-bouncer_0.0.25-4.debian.tar.xz 112a3fd19cbef6c22021576738ca770d99d75d08 27724 crowdsec-firewall-bouncer_0.0.25-4_source.buildinfo Checksums-Sha256: 6ffb351d70d0ce06d8426618605979f878eb6b57207200d973f12eca01c22146 2602 crowdsec-firewall-bouncer_0.0.25-4.dsc 2c67ecd6d6c60ecbf1f26448c92874e300c5a8806ebb3d729a78774520bbd0dc 7600 crowdsec-firewall-bouncer_0.0.25-4.debian.tar.xz 1534cb45c8a10c0280a432eb165779582461f5ce169040c6b7db8832500ed6ed 27724 crowdsec-firewall-bouncer_0.0.25-4_source.buildinfo Files: ceb9df4ce30324299a3a625d89b766f9 2602 golang optional crowdsec-firewall-bouncer_0.0.25-4.dsc e25937243bdbfa6acba76a2a13ae7ac3 7600 golang optional crowdsec-firewall-bouncer_0.0.25-4.debian.tar.xz fb137f0b883404ee62443c9fd550d478 27724 golang optional crowdsec-firewall-bouncer_0.0.25-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmZMWkwQHGtpYmlAZGVi aWFuLm9yZwAKCRD/kUrwwrNVIDtRD/0f5JiMwEMwiDMIEm7GBCboGRCjI+tfCJ+g 5QUW46uRzEq6HlP+s1EbKuR3P5/qTmFEDYZs+7VFvBqaCw/qTUT5719XWVSw64YP raSGEvuj53TSJeWjdSwKp+atvJx22kywGsvrboYqmTsn5Hrye5KwRorgg0lMg/Yk mtm7grDTzh56l1CqmAMkGE6JFCazbvdlZ/dshqThaNwgACn0P6Khyu7ZfoGYQ1qK 9TnVDHfFX3gm5ipJTRUMFhZ+gk3OahrRwtN2tHKjPsqdXj/qkZ2piSaK3CR+pbFL pCqx00ApUzGiLpp7+/IkIDczWobm9fVLlp4mRiy5kFtDWq50Da0CIM9VnrHr3SMo IsucocHpc5IvMrkmVT9ovR76FIk1NEfZ6M3mv/q/AnMjnc5jHCgPjbkgDu7nrFAd WpZDfrAuoF+49+kQOxNFOX9F4MKQtGmWGZRTFclEkZ3h3A0RD6QfdO71PdD1ukXd sfSdeFFrdbuxobXWjEqjWm6OyWnwGW8iqr37oYINkbpSg7
Bug#1071247: marked as done (golang-github-google-nftables-dev: broken AddSet() on all little-endian systems)
Your message dated Tue, 21 May 2024 08:35:23 + with message-id and subject line Bug#1071247: fixed in golang-github-google-nftables 0.1.0-4 has caused the Debian Bug report #1071247, regarding golang-github-google-nftables-dev: broken AddSet() on all little-endian systems 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.) -- 1071247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-google-nftables-dev Version: 0.1.0-4 Severity: serious Tags: upstream security patch Justification: broken feature, security implications X-Debbugs-Cc: Debian Security Team , debian.pack...@crowdsec.net Hi, I was contacted by CrowdSec upstream about a bug report filed against the firewall bouncer, which is in charge of applying rules at the firewall level based on decisions passed on by the crowdsec engine: https://github.com/crowdsecurity/cs-firewall-bouncer/issues/368 I've been able to verify that despite correct IPv4 and IPv6 addresses getting logged by the bouncer (e.g. at debug level), all of them get added in reverse byte order at the nftables level. :( Upstream bug: https://github.com/google/nftables/issues/225 Upstream fix: https://github.com/google/nftables/pull/226 I confirmed that affects LE systems (e.g. amd64), both in stable and in unstable (same versions, modulo binNMUs). That doesn't affect BE systems (i.e. s390x, verified via debvm). I also verified that applying the golang-github-google-nftables patch and rebuilding crowdsec-firewall-bouncer against it fixes the problem on LE systems, and doesn't regress on BE systems. Security team, I've added the security tag (and you to Cc) because the consequence is that admins who installed crowdsec-firewall-bouncer have been thinking they were applying restrictions gathered by crowdsec, while they've actually been (1) not blocking offending addresses and (2) blocking possibly harmless ones. I was tempted to open a second bug on crowdsec-firewall-bouncer, referencing this one, and to upload both packages to unstable (this one with the upstream patch, the other one with a bumped build-dep to make sure it cannot be rebuilt against the broken package; there are a lot of binNMUs flying around already). Then to submit p-u requests to get the same updates into bookworm. But does that issue warrant a DSA? Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant --- End Message --- --- Begin Message --- Source: golang-github-google-nftables Source-Version: 0.1.0-4 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-google-nftables, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-google-nftables package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 May 2024 09:42:17 +0200 Source: golang-github-google-nftables Architecture: source Version: 0.1.0-4 Distribution: unstable Urgency: high Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Closes: 1071247 Changes: golang-github-google-nftables (0.1.0-4) unstable; urgency=high . * Backport upstream fix for the AddSet() function that's been reversing byte order on all little-endian architectures (Closes: #1071247), breaking crowdsec-firewall-bouncer (See: #1071248): - 0002-Implement-set-KeyByteOrder-226.patch Checksums-Sha1: 53abab784951635d6c6674b4a39f5685bc264467 2369 golang-github-google-nftables_0.1.0-4.dsc b468498f72badc8361586b0e5ebb7d967f7eaa16 4652 golang-github-google-nftables_0.1.0-4.debian.tar.xz 8bac2cd0bd8faf82a6906e6c4c68eee976a31661 7337 golang-github-google-nftables_0.1.0-4_source.buildinfo Checksums-Sha256: 01eb638fc77d21a86044fd4667ba2d21f6b40482e2501fe1a0d269455cad624e 2369 golang-github-google-nftables_0.1.0-4.dsc 88d448e2fb9b32ce5658615269e64b2e53610f72424c9f8c37ef975b6714849c 4652 golang-github-
Processed (with 1 error): tags ftbfs for 1070417
Processing commands for cont...@bugs.debian.org: > tags 1070417 ftbfs Bug #1070417 [src:rxtx] rxtx: FTBFS: src/RawImp.c:223:23: error: implicit declaration of function ‘inl’ [-Werror=implicit-function-declaration] Added tag(s) ftbfs. > thanks, Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1070417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071247 marked as pending in golang-github-google-nftables
Processing control commands: > tag -1 pending Bug #1071247 [golang-github-google-nftables-dev] golang-github-google-nftables-dev: broken AddSet() on all little-endian systems Added tag(s) pending. -- 1071247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071248 marked as pending in crowdsec-firewall-bouncer
Processing control commands: > tag -1 pending Bug #1071248 [crowdsec-firewall-bouncer] crowdsec-firewall-bouncer: blocks wrong IPv4 and IPv6 addresses on LE systems (reversed byte order) Added tag(s) pending. -- 1071248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: should not block migration to testing
Processing control commands: > severity -1 normal Bug #1062209 [android-libbase] android-libbacktrace (et al): identified for time_t transition but no ABI in shlibs Severity set to 'normal' from 'serious' -- 1062209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069382: marked as done (libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t')
Your message dated Tue, 21 May 2024 10:07:46 +0200 with message-id <826b7d28-4766-4e0e-9274-1a00d1f18...@debian.org> and subject line Re: Bug#1069382: libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t' has caused the Debian Bug report #1069382, regarding libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t' 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.) -- 1069382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.15-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build/src' > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xproto.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/bigreq.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xc_misc.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/composite.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/damage.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/dpms.xml > Traceback (most recent call last): > File "/<>/build/src/../../src/c_client.py", line 3394, in > > module.generate() > File "/usr/lib/python3/dist-packages/xcbgen/state.py", line 131, in generate > item.out(name) > File "/<>/build/src/../../src/c_client.py", line 3198, in > c_request > _c_request_helper(self, name, void=True, regular=False) > File "/<>/build/src/../../src/c_client.py", line 2273, in > _c_request_helper > if namecount[tname] > 1: >~^^^ > KeyError: 'xcb_redirect_t' > make[2]: *** [Makefile:1408: composite.c] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/libxcb_1.15-1_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 --- On 19/05/2024 04:45, Shmerl wrote: Is there any way to fix or work around this? It's been blocking new version of obs-studio from entering testing for a while. I don't understand, we've had libxcb 1.17-1 in sid for a while and that built properly on arm64. Your problem with obs-studio is that libxcb is not migrating due to #1069408, not because of this bug. I'm closing this one since libxcb now builds fine on arm64. Cheers, Emilio--- End Message ---
Bug#1071452: marked as done (dnsdbq FTBFS on 32bit with 64bit time_t)
Your message dated Tue, 21 May 2024 10:02:43 +0200
with message-id <7357c0e1-83d5-4012-8861-8d5b19001...@debian.org>
and subject line Re: Bug#1071452: dnsdbq FTBFS on 32bit with 64bit time_t
has caused the Debian Bug report #1071452,
regarding dnsdbq FTBFS on 32bit with 64bit time_t
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.)
--
1071452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnsdbq
Version: 2.6.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=dnsdbq=2.6.6-1
...
time.c: In function ‘timeval_str’:
time.c:83:36: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 3 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
83 | sprintf(dst, ".%03ld", src->tv_usec % 1000);
|^ ~~~
|||
|long int __suseconds64_t
{aka long long int}
|%03lld
time.c:85:36: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 3 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
85 | sprintf(dst, ".%06ld", src->tv_usec % 100);
|^ ~~
|||
|long int __suseconds64_t
{aka long long int}
|%06lld
cc1: all warnings being treated as errors
make[1]: *** [Makefile:76: time.o] Error 1
--- End Message ---
--- Begin Message ---
Fixed in 2.6.7-1.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#1060533: marked as done (cfengine3: Please switch Build-Depends to systemd-dev)
Your message dated Tue, 21 May 2024 00:34:46 + with message-id and subject line Bug#1060533: fixed in cfengine3 3.21.4-1.2 has caused the Debian Bug report #1060533, regarding cfengine3: Please switch Build-Depends to systemd-dev 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.) -- 1060533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cfengine3 Version: 3.21.0-3 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package cfengine3 declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: cfengine3 Source-Version: 3.21.4-1.2 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of cfengine3, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated cfengine3 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: Tue, 21 May 2024 02:16:43 +0200 Source: cfengine3 Architecture: source Version: 3.21.4-1.2 Distribution: unstable Urgency: medium Maintainer: CFEngine Team Changed-By: Andreas Beckmann Closes: 1060533 1070850 Changes: cfengine3 (3.21.4-1.2) unstable; urgency=medium . * Non-maintainer upload. * Switch B-D to systemd-dev. (Closes: #1060533) * Switch B-D to pkgconf. * Add B-D: passwd. (Closes: #1070850) Checksums-Sha1: 9258731228fb73e258d8f334f9178b191cc014a7 2448 cfengine3_3.21.4-1.2.dsc e733fc5d92cba83689987e971688a8826225ef93 21788 cfengine3_3.21.4-1.2.debian.tar.xz 7c480b0d67a9365fdb9d6af9c86170c093e15dbe 7379 cfengine3_3.21.4-1.2_source.buildinfo Checksums-Sha256: 2982d533c7b982aac7a51ee2f53157e8fe211d319902170c78b32d972dbef250 2448 cfengine3_3.21.4-1.2.dsc 9c04ed54b3f8d4eda256d4346ace0a08131a67d7874642d8e8633dc50df2cfcb 21788 cfengine3_3.21.4-1.2.debian.tar.xz 94e30d53c6bc029c41a26d911c22f3fddbcd1250a8d634e8068a3552a65dd558 7379 cfengine3_3.21.4-1.2_source.buildinfo Files: 6a48c8444352c5e7ef2561e7ee2a29d8 2448 admin optional cfengine3_3.21.4-1.2.dsc 5b0dd4484509869aef17c85882edf16f 21788 admin optional cfengine3_3.21.4-1.2.debian.tar.xz 0495117c2ecf09f86f3abc44e309c423 7379 admin optional cfengine3_3.21.4-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmZL6HwQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCEA8D/4kw7DF6YWiMgYlVP/UHss3q4w543f6TeKB TfS8oH/D/Ir3LnN/LV6HWSrJ4oX+hYqNQgCgGisviQGMBFWNS7fehtnXiuxPAd8d rWnscU2TkPJVUVGLIW8DAQtO3zfxVtatkCN+ooIuss4o3BoqWb2xodegkTQXpuBl xSAVGqBwQ24OqFGXC+YdeOjFC8JNK3iZ+3uoO3BgFldUhyk5ZDWP1V36T2O32CJH I+/Qhegb30cSYw7FntJ+xRsfOgWeGnVs3E5Fz4OiLNeu5Ji5PkGSbOa+oMV4tL/L lHRsuIOt0THya4vHe5fah9dS8YcZG
Processed: bug 1071541 is forwarded to https://github.com/exeldro/obs-source-clone/issues/24
Processing commands for cont...@bugs.debian.org: > forwarded 1071541 https://github.com/exeldro/obs-source-clone/issues/24 Bug #1071541 [obs-source-clone] FTBFS: obs-source-clone/audio-wrapper.c:134:25: error: ‘circlebuf_push_back’ is deprecated [-Werror=deprecated-declarations] Set Bug forwarded-to-address to 'https://github.com/exeldro/obs-source-clone/issues/24'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067439: marked as done (cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12)
Your message dated Mon, 20 May 2024 20:37:04 + with message-id and subject line Bug#1067439: fixed in cpu 1.4.3-14~deb11u1 has caused the Debian Bug report #1067439, regarding cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cpu Version: 1.4.3-13+b1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** It was working on Debian 11, but after upgrading to Debian 12 just calling the program make it crash: root@davis:~# cpu CPU_loadLibrary: dlopen(libcpu_ldap.so, RTLD_NOW) failed. CPU_loadLibrary: /lib/x86_64-linux-gnu/libcpu_ldap.so: undefined symbol: globalLdap There was an error loading the ldap library. Exiting. Regards Simone -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cpu depends on: ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9+deb12u4 ii libcrack2 2.9.6-5+b1 ii libcrypt1 1:4.4.33-2 ii libldap-2.5-0 2.5.13+dfsg-5 ii ucf3.0043+nmu1 cpu recommends no packages. cpu suggests no packages. -- debconf information: cpu/ldap/BIND_PASS: (password omitted) cpu/ldap/USER_BASE: ou=People,dc=truelite,dc=it cpu/ldap/BIND_DN: cn=admin,dc=truelite,dc=it cpu/ldap/GROUP_BASE: ou=Group,dc=truelite,dc=it cpu/ldap/LDAP_URI: ldap://localhost cpu/do_debconf: true --- End Message --- --- Begin Message --- Source: cpu Source-Version: 1.4.3-14~deb11u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of cpu, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated cpu 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: Tue, 14 May 2024 03:34:34 +0200 Source: cpu Architecture: source Version: 1.4.3-14~deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1067439 Changes: cpu (1.4.3-14~deb11u1) bullseye; urgency=medium . * QA upload. * Rebuild for bullseye. . cpu (1.4.3-14~deb12u1) bookworm; urgency=medium . * QA upload. * Rebuild for bookworm. . cpu (1.4.3-14) unstable; urgency=medium . * QA upload. * Actually provide a definition of globalLdap. (Closes: #1067439) * Add smoke test. Checksums-Sha1: b0676d4fe30d33ad85b63949ca508549985a2404 1883 cpu_1.4.3-14~deb11u1.dsc d9193b6df055ba24817446da7b520f5a06896e45 29848 cpu_1.4.3-14~deb11u1.debian.tar.xz 09c12cdd424eb00f00040c560d8e29cb52fcbef1 6178 cpu_1.4.3-14~deb11u1_source.buildinfo Checksums-Sha256: d763f05c39d8fc8c0e9b79225dac2118ababd7455ac35233f9f8e716bebc4c4d 1883 cpu_1.4.3-14~deb11u1.dsc 34dff03dfcbf0c1b4c283c58aab551646072b914624ee1576e8a72aeedf49389 29848 cpu_1.4.3-14~deb11u1.debian.tar.xz c55e635b4b90efa1952c11369a7c045c0db64a183f85bcc6f57396748b759d90 6178 cpu_1.4.3-14~deb11u1_source.buildinfo Files: c2a7fbf4c87f7bb1f794b22b221f8706 1883 admin optional cpu_1.4.3-14~deb11u1.dsc 0a78fe86995924cd25720d51bc0bf5a3 29848 admin optional cpu_1.4.3-14~deb11u1.debian.tar.xz 35b47c9d397ef793a189ca4d11da5096 6178 admin optional cpu_1.4.3-14~deb11u1_source.buildinfo -BEGIN PGP SIGNATURE
Bug#1067717: marked as done (emacs-common: Security issues with emacs; remote code execution in Gnus)
Your message dated Mon, 20 May 2024 20:34:02 + with message-id and subject line Bug#1067630: fixed in emacs 1:28.2+1-15+deb12u1 has caused the Debian Bug report #1067630, regarding emacs-common: Security issues with emacs; remote code execution in Gnus 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.) -- 1067630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs-common Version: 1:28.2+1-15 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Hello, https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29 describes some security issues addressed in emacs 29.3. Among them: ** Gnus now treats inline MIME contents as untrusted. To get back previous insecure behavior, 'untrusted-content' should be reset to nil in the buffer. ** LaTeX preview is now by default disabled for email attachments. To get back previous insecure behavior, set the variable 'org--latex-preview-when-risky' to a non-nil value. I don't see anything that would explicitly indicate if the version in stable, 1.28.2, is vulnerable but the nature of this leads me to think that it is. Thanks, John -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs-common depends on: ii emacs-el 1:28.2+1-15 ii emacsen-common 3.0.5 ii init-system-helpers 1.65.2 ii install-info 6.8-6+b1 emacs-common recommends no packages. Versions of packages emacs-common suggests: pn emacs-common-non-dfsg ii ncurses-term 6.4-4 -- no debconf information --- End Message --- --- Begin Message --- Source: emacs Source-Version: 1:28.2+1-15+deb12u1 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of emacs, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated emacs 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, 27 Apr 2024 10:49:04 +0100 Source: emacs Architecture: source Version: 1:28.2+1-15+deb12u1 Distribution: bookworm Urgency: high Maintainer: Rob Browning Changed-By: Sean Whitton Closes: 1067630 Changes: emacs (1:28.2+1-15+deb12u1) bookworm; urgency=high . * Fix CVE-2024-30202, CVE-2024-30203, CVE-2024-30204 & CVE-2024-30205 (Closes: #1067630). Checksums-Sha1: 3e85a9414e61ea4ab44cc26548923d98a0813049 3035 emacs_28.2+1-15+deb12u1.dsc 7481211825ed9b505f0f53544fb7a1eacd8fb5cf 129660 emacs_28.2+1-15+deb12u1.debian.tar.xz Checksums-Sha256: 9bf1e65532de80576ce1f547670af7c972824f627af91dd8d978ed3721eeed74 3035 emacs_28.2+1-15+deb12u1.dsc fbaa3e06234b648a4f309aec6d6372142758f1a666ca0e550bf776a86d1bf1a1 129660 emacs_28.2+1-15+deb12u1.debian.tar.xz Files: 1e522ffedefe6960e23d109a89f5811e 3035 editors optional emacs_28.2+1-15+deb12u1.dsc 9f2f96394a84acfe9d377b59322f96c8 129660 editors optional emacs_28.2+1-15+deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmYsys8ACgkQaVt65L8G YkAxQQ/9GAMIGsa99/GrCXm88eHIj4xK8ybSA5svssNWLlvdNVRWysR8NFLtulPD gtlzDpY4457iHrPMO28+YN4A3vpdeXGZYHiu5V+EEhp8qs1XhWpzIsgjMK4FEDlC W7SuIgQla1K8sqEFzJaoBlrQF4mqTu37PXjJ9HcMCHt/dgPmNQnOSpiooyu+5Lwp XidHbIBygZyfbRSncaJsb0tipPBPtHAfirWVZlsCPmiy7RcDGnjXw1rgPrFnQvwc jSBbD9I9ZvewrqXBD7g0+FoZoiIJnxKs6/+WaExmUxtjssWGhaE82fK6PLN2eSdJ 2qGXptjgFjMn2jVueS6SlJnomrS1gohP2lIb0e8M3UA4wFbVmqaNpzifSxyPnhZ9 XIHGxelVM2VKSrKLiGY3JtxQszYo7MZeAeTYLBJ0aDZQdcJ3g5Nol0cGsHh0zWw8 bOnm6VKU56oj92y4KFd8NVwZNx7HARsDdL8KQ9AcZgiGH0HoJjLztkah5CnF
Bug#1067630: marked as done (emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205)
Your message dated Mon, 20 May 2024 20:34:02 + with message-id and subject line Bug#1067630: fixed in emacs 1:28.2+1-15+deb12u1 has caused the Debian Bug report #1067630, regarding emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205 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.) -- 1067630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emacs Version: 29.2+1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team , debian-emac...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 According to the 29.3 release notes * Changes in Emacs 29.3 Emacs 29.3 is an emergency bugfix release intended to fix several security vulnerabilities described below. ** Arbitrary Lisp code is no longer evaluated as part of turning on Org mode. This is for security reasons, to avoid evaluating malicious Lisp code. ** New buffer-local variable 'untrusted-content'. When this is non-nil, Lisp programs should treat buffer contents with extra caution. ** Gnus now treats inline MIME contents as untrusted. To get back previous insecure behavior, 'untrusted-content' should be reset to nil in the buffer. ** LaTeX preview is now by default disabled for email attachments. To get back previous insecure behavior, set the variable 'org--latex-preview-when-risky' to a non-nil value. ** Org mode now considers contents of remote files to be untrusted. Remote files are recognized by calling 'file-remote-p'. - -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 6.6.15-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmYAhNIACgkQA0U5G1Wq FSEANg//cukjqohXxNRpkxbutqHHvOB1aAr3d78jowjP3Yb9ozAArNxUjuJHEdSZ 5HCASm269atf5753maZILjyx3VmF/qUihyGjbbWjqMwNrQkkQiuXBfYn1F4R76/V tyFile5NZVXIgYMykLb+rSHap6KMBnhjvLWSwNsDMuD8WB7OPH7KOI2xYqkUb7ue SIgkCr0GJ+LaHOAYlRKkAYok4qwIfijLBw41Bt7t9Tawh+5d5nDkNPDphFOB+bG+ 1hOQD8KVYWIceRK83wcDictSxbeTSo/cp6cEtVZX3yrDvBRbj3VKjKWL+0UIKfWO iGWQYn622B7WbBIwEddQMmla+nxa5rxEN9VMEE8N5xcpI1lnL0lVSxw0jbT0FopJ PmwFYmz1+pxB2fhRTv1T7ZTSAJS3BKQ9u2R8tuKO5ilSYp1zJrBBIazGPZ3Q+UBS EoPh4hy5G4IZ3X3yaE9cX76fdDMMGPQ7HIinkw5A7KWb8zHse5m3+WG+iPNuveHU GRwOB9pDDRTQrQVG8of2YVS0kLb9eu2jUD0sbi8As3P5Mr/gXHlrSgs5t1qg3HuA Kkg7m7PAONZu0LBZNZsItm/V0weDqBdE+LZsa/1LUk3H+zvswhctlNLuZ7Y4mKqh YpuwmZ2+cv1To2M/DKbBx2ngl5EiojF8hk5pGezcZ811NRFAQKc= =BxE4 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: emacs Source-Version: 1:28.2+1-15+deb12u1 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of emacs, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated emacs 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, 27 Apr 2024 10:49:04 +0100 Source: emacs Architecture: source Version: 1:28.2+1-15+deb12u1 Distribution: bookworm Urgency: high Maintainer: Rob Browning Changed-By: Sean Whitton Closes: 1067630 Changes: emacs (1:28.2+1-15+deb12u1) bookworm; urgency=high . * Fix CVE-2024-30202, CVE-2024-30203, CVE-2024-30204 & CVE-2024-30205 (Closes: #1067630). Checksums-Sha1: 3e85a9414e61ea4ab44cc26548923d98a0813049 3035 emacs_28.2+1-15+deb12u1.dsc 7481211825ed9b505f0f53544fb7a1eacd8fb5cf 129660 emacs_28.2+1-15+deb12u1.debian.tar.xz Checksums-Sha256: 9bf1e65532de80576ce1f547670af7c972824f627af91dd8d978ed3721eeed74 3035 emacs_28.2+1-15+deb12u1.dsc fbaa3e06234b648a4f309aec6d6372142758f1a666ca0e550bf776a86d1bf1a1 129660 emacs_28.2+1-15+deb12u1.debian.tar.xz Files: 1e522ffedefe6960e23d109a89f5811e 3035 edi
Bug#1034993: marked as done (software-properties-qt: missing Conflicts+Replaces for software-properties-kde when upgrading from bullseye)
Your message dated Mon, 20 May 2024 20:36:31 + with message-id and subject line Bug#1034993: fixed in software-properties 0.99.30-4.1~deb12u1 has caused the Debian Bug report #1034993, regarding software-properties-qt: missing Conflicts+Replaces for software-properties-kde when upgrading from bullseye 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.) -- 1034993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: software-properties-qt Version: 0.99.30-4 Severity: serious Justification: dpkg unpack error Attempting to unpack software-properties-qt/0.99.30-4 from Debian bookworm on a minimal Debian bullseye with software-properties-kde/0.96.20.2-2.1 installed, causes an unpack error from dpkg due to /usr/share/software-properties/designer/dialog_add.ui being contained in both packages. | Selecting previously unselected package software-properties-qt. | (Reading database ... 11560 files and directories currently installed.) | Preparing to unpack .../software-properties-qt_0.99.30-4_all.deb ... | Unpacking software-properties-qt (0.99.30-4) ... | dpkg: error processing archive ./software-properties-qt_0.99.30-4_all.deb (--unpack): | trying to overwrite '/usr/share/software-properties/designer/dialog_add.ui', which is also in package software-properties-kde 0.96.20.2-2.1 | Errors were encountered while processing: | ./software-properties-qt_0.99.30-4_all.deb Please ensure that software-properties-qt has sufficient Breaks and Replaces declarations. Helmut --- End Message --- --- Begin Message --- Source: software-properties Source-Version: 0.99.30-4.1~deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of software-properties, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated software-properties 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, 17 May 2024 14:23:15 +0200 Source: software-properties Architecture: source Version: 0.99.30-4.1~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Julian Andres Klode Changed-By: Andreas Beckmann Closes: 1034993 Changes: software-properties (0.99.30-4.1~deb12u1) bookworm; urgency=medium . * Non-maintainer upload. * Rebuild for bookworm. . software-properties (0.99.30-4.1) unstable; urgency=medium . * Non-maintainer upload. * software-properties-qt: Add Conflicts+Replaces: software-properties-kde for smoother upgrades from bullseye. (Closes: #1034993) Checksums-Sha1: e8f5dc2aa605f2ec1278db730d39d59928e4b2d6 3024 software-properties_0.99.30-4.1~deb12u1.dsc 6e539bb8afc314b3ab13986a9795c62e3ae552dc 45624 software-properties_0.99.30-4.1~deb12u1.debian.tar.xz 54955110e3b79087a61223021f92658029bc38ab 12420 software-properties_0.99.30-4.1~deb12u1_source.buildinfo Checksums-Sha256: dc74b81adf68df0b2ead4b8a011f48f003ec16ad2d1b4f98edf568ab78e17440 3024 software-properties_0.99.30-4.1~deb12u1.dsc 39b74df75ed188c4bdfaefd37f9bda1ff0de21c7259c3fbcd707f39be81ad55e 45624 software-properties_0.99.30-4.1~deb12u1.debian.tar.xz 362499f488ae25f58a8604645057cade97af9539978c173692d87b0d60fa97b3 12420 software-properties_0.99.30-4.1~deb12u1_source.buildinfo Files: fb63cf3fc9e114c3222ef7bb6b435f9f 3024 admin optional software-properties_0.99.30-4.1~deb12u1.dsc 33b12177396ca9a8f54fe9997ae27d19 45624 admin optional software-properties_0.99.30-4.1~deb12u1.debian.tar.xz 8bd069a37b1d75009828d4e64160df6c 12420 admin optional software-properties_0.99.30-4.1~deb12u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmZHTLQQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCA0eD/0bqfaM4I5nczXq1cQpTa+VRT8I8Cc7BFJh NoBe43XDvx7QjNaGBion42nyrFxugor5sQLxjvqtiOWoP9dVKV1ggFiHASkCmzx1 w8OSMVNBWoLNgJe8ts3hOmMYjr3AI4pIu7ObT+dg4Fb9O95FRvZjqjh/LTe8/UQl BQse+fqPPP2ms2IdKlIxRFFKyKXDyPWeTQHui7UzSP2EUqUZz3e017qrDztdS9Yg mogi7Rs5y9zDvKWuyHqRtlAZ7e6RsVE3jj7z6XvYSZT13JXtDuyeHTw6iOEP34EF
Bug#1068157: marked as done (siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT)
Your message dated Mon, 20 May 2024 22:17:42 +0200 with message-id <26d1ac6a-9508-45e2-8a9f-7d934a12a...@debian.org> and subject line Re: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT has caused the Debian Bug report #1068157, regarding siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT 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.) -- 1068157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: siridb-server Version: 2.0.51-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=siridb-server=2.0.51-2%2Bb3=armhf=1711922161 Testing expr␛[32mOK␛[0m (8.519 ms) ==3276877== ==3276877== Process terminating with default action of signal 11 (SIGSEGV) ==3276877== Access not within mapped region at address 0xFEC4F704 ==3276877==at 0x495F6F0: pcre2_compile_8 (in /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2) ==3276877== If you believe this happened as a result of a stack ==3276877== overflow in your program's main thread (unlikely but ==3276877== possible), you can try to increase the size of the ==3276877== main thread stack using the --main-stacksize= flag. ==3276877== The main thread stack size used in this run was 8388608. ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Hi, On Mon, 1 Apr 2024 00:00:18 +0200 Sebastian Ramacher wrote: Justification: fails to build from source (but built successfully in the past) The binary on armhf has been removed. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: tags
Processing commands for cont...@bugs.debian.org: > tags 988512 + ftbfs Bug #988512 [ca-cacert] ca-cacert: class3 certificate will expire soon (on May 20 17:48:02 2021 GMT) Added tag(s) ftbfs. > tags 1035594 + ftbfs Bug #1035594 [eclipse-tracecompass] eclipse-tracecompass: depends on no longer available libeclipse-osgi-util-java,libequinox-p2-ui-sdk-java Added tag(s) ftbfs. > tags 1036167 + ftbfs Bug #1036167 [flask-appbuilder] flask-appbuilder: Fails to build against python3-flask-sqlalchemy 3.0.3-1 Added tag(s) ftbfs. > tags 1025825 + ftbfs Bug #1025825 [grip] ImportError: cannot import name 'safe_join' from 'flask' Added tag(s) ftbfs. > tags 950598 + ftbfs Bug #950598 [python3-jupyter-sphinx] python3-jupyter-sphinx: package relies on unavailable `ipywidgets.embed` module Added tag(s) ftbfs. > tags 1056839 + ftbfs Bug #1056839 [src:pyliblo] pyliblo: ftbfs with cython 3.0.x Added tag(s) ftbfs. > tags 1056874 + ftbfs Bug #1056874 [src:python-srsly] python-srsly: ftbfs with cython 3.0.x Added tag(s) ftbfs. > tags 1056887 + ftbfs Bug #1056887 [src:sfepy] sfepy: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025825 1035594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035594 1036167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036167 1056839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056839 1056874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056874 1056887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056887 950598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950598 988512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1058890
Processing commands for cont...@bugs.debian.org: > close 1058890 6.1.85-1 Bug #1058890 [src:linux] linux-image-6.1.0-16-amd64 breaks suspend Marked as fixed in versions linux/6.1.85-1. Bug #1058890 [src:linux] linux-image-6.1.0-16-amd64 breaks suspend Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1066632: djbdns: FTBFS: hier.c:10:3: error: implicit declaration of function ‘h’ [-Werror=implicit-function-declaration]
Processing control commands: > tags -1 + patch Bug #1066632 [src:djbdns] djbdns: FTBFS: hier.c:10:3: error: implicit declaration of function ‘h’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070369: marked as done (sssd: CVE-2023-3758)
Your message dated Mon, 20 May 2024 14:38:14 + with message-id and subject line Bug#1070369: fixed in sssd 2.9.5-1 has caused the Debian Bug report #1070369, regarding sssd: CVE-2023-3758 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.) -- 1070369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sssd Version: 2.9.4-2 Severity: grave Tags: security upstream Forwarded: https://github.com/SSSD/sssd/pull/7302 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for sssd. CVE-2023-3758[0]: | A race condition flaw was found in sssd where the GPO policy is not | consistently applied for authenticated users. This may lead to | improper authorization issues, granting or denying access to | resources inappropriately. 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-2023-3758 https://www.cve.org/CVERecord?id=CVE-2023-3758 [1] https://github.com/SSSD/sssd/pull/7302 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2223762 [3] https://github.com/SSSD/sssd/commit/e1bfbc2493c4194988acc3b2413df3dde0735ae3 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: sssd Source-Version: 2.9.5-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of sssd, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated sssd 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: Mon, 20 May 2024 16:36:50 +0300 Source: sssd Built-For-Profiles: noudeb Architecture: source Version: 2.9.5-1 Distribution: unstable Urgency: medium Maintainer: Debian SSSD Team Changed-By: Timo Aaltonen Closes: 1068063 1070369 Changes: sssd (2.9.5-1) unstable; urgency=medium . * New upstream release. (Closes: #1068063) - CVE-2023-3758 (Closes: #1070369) Checksums-Sha1: 55ace81ef79ae14458cbd4184ec1fefe30eb2b18 5125 sssd_2.9.5-1.dsc f6704a9df1303e154ef8526f9f21e2b72879c046 8001964 sssd_2.9.5.orig.tar.gz 97c93c192966f031eee0d96ff1d3c4479519bae9 833 sssd_2.9.5.orig.tar.gz.asc 7a46a85290f7dcc2b83495685ca2a3ac059cf19c 46192 sssd_2.9.5-1.debian.tar.xz 2e03d2db95d52c1056650f58474c64ca0f519449 10756 sssd_2.9.5-1_source.buildinfo Checksums-Sha256: 42829e8d6a0a90d4fb18fe96594d38c9b67d05e18696c210e2054eda746a2cf5 5125 sssd_2.9.5-1.dsc bf955cc26b6d215bbb9083eadb613f78d7b727fb023f39987aec37680ae40ae3 8001964 sssd_2.9.5.orig.tar.gz 2909ca4b0318378b8e7baa1d6620b307a5fb59b5fa1348b4c1c82d209a5bc2c8 833 sssd_2.9.5.orig.tar.gz.asc 6994b37e2d98294d0fbb9f70140307106ecbf8f1eefe259dab806c97eb873d75 46192 sssd_2.9.5-1.debian.tar.xz 794e38cfaa6c67621e5aa9812cc67607db6db4d6e4102c4a19e52befc55b8961 10756 sssd_2.9.5-1_source.buildinfo Files: a9c5dbc56e2c9e96089a8f4dc7a1047a 5125 utils optional sssd_2.9.5-1.dsc fb41a516f51d3f75855c7dd6f4c16c19 8001964 utils optional sssd_2.9.5.orig.tar.gz cbb4ca4872c19ca0130acc52575660aa 833 utils optional sssd_2.9.5.orig.tar.gz.asc 064f2def4a5862d0f9b296339a7b8cb8 46192 utils optional sssd_2.9.5-1.debian.tar.xz 58113394bef460507c81d3325d5ddbe3 10756 utils optional sssd_2.9.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZLUf4ACgkQy3AxZaiJ hNx9Qw//dOefPGod8HPE/c67EZ9diH47QHjkDmXicZ99Tsq2lsFBvluORNOssNNA LqNiEzDaVPzLQUQX0HScHlZbYdMu06l3PJz5n0xLB5CzfHrNIm64/YScgFhBzNHJ 1p9UOffbWpWj9QBBgyKg9q7t5Ezn5TXp51EdVsGyJxUUyTv5Y5eFfBKdsh5Y+g3O 5PsnkQIFflUdnELH3VZGBP+mKpyicBzjhLg/Vd7y72duMu8KN4UFeR77//tWGZh7 UPSzVzRLsh2SCCTfrv6dGJe7Sivk16A7grhdyAtf3UIkX/NooDdc57W9KE1kMleY bbylVmyKPcidW9lwMxRew10eJt+gTDiJB8uz6EH5cNH4fFml2wChLGqwuQGMZe8G kpPbteA3tX81ZXwSgDRKBnW44/uLiMlsjdlFQGaQVojjqipA4yr4XEB0kN3PFF8Q E5ZGTI13HXSLALYUxE6gwNnhGq94sXTLgbYA55/2y0aOHUmPAdaWpz4c+Eb1vYvl KG9vYmEuf+IqK2QAWIBCO
Bug#1068063: marked as done (sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x))
Your message dated Mon, 20 May 2024 14:38:14 + with message-id and subject line Bug#1068063: fixed in sssd 2.9.5-1 has caused the Debian Bug report #1068063, regarding sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x) 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.) -- 1068063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sssd Severity: serious Tags: ftbfs Control: found -1 2.9.4-1.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, sssd fails to build on armel, armhf. Though test suite failure was already reported, but target version is 1.11.5.1-1, not 2.x branch. so I've filed as a new bug to raise attension. sssd: FTBFS on many archs due to testsuite failures https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754618 FYI: https://buildd.debian.org/status/fetch.php?pkg=sssd=armel=2.9.4-1.1=1711454828=0 https://buildd.debian.org/status/fetch.php?pkg=sssd=armhf=2.9.4-1.1=1711455028=0 Regards, --- End Message --- --- Begin Message --- Source: sssd Source-Version: 2.9.5-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of sssd, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated sssd 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: Mon, 20 May 2024 16:36:50 +0300 Source: sssd Built-For-Profiles: noudeb Architecture: source Version: 2.9.5-1 Distribution: unstable Urgency: medium Maintainer: Debian SSSD Team Changed-By: Timo Aaltonen Closes: 1068063 1070369 Changes: sssd (2.9.5-1) unstable; urgency=medium . * New upstream release. (Closes: #1068063) - CVE-2023-3758 (Closes: #1070369) Checksums-Sha1: 55ace81ef79ae14458cbd4184ec1fefe30eb2b18 5125 sssd_2.9.5-1.dsc f6704a9df1303e154ef8526f9f21e2b72879c046 8001964 sssd_2.9.5.orig.tar.gz 97c93c192966f031eee0d96ff1d3c4479519bae9 833 sssd_2.9.5.orig.tar.gz.asc 7a46a85290f7dcc2b83495685ca2a3ac059cf19c 46192 sssd_2.9.5-1.debian.tar.xz 2e03d2db95d52c1056650f58474c64ca0f519449 10756 sssd_2.9.5-1_source.buildinfo Checksums-Sha256: 42829e8d6a0a90d4fb18fe96594d38c9b67d05e18696c210e2054eda746a2cf5 5125 sssd_2.9.5-1.dsc bf955cc26b6d215bbb9083eadb613f78d7b727fb023f39987aec37680ae40ae3 8001964 sssd_2.9.5.orig.tar.gz 2909ca4b0318378b8e7baa1d6620b307a5fb59b5fa1348b4c1c82d209a5bc2c8 833 sssd_2.9.5.orig.tar.gz.asc 6994b37e2d98294d0fbb9f70140307106ecbf8f1eefe259dab806c97eb873d75 46192 sssd_2.9.5-1.debian.tar.xz 794e38cfaa6c67621e5aa9812cc67607db6db4d6e4102c4a19e52befc55b8961 10756 sssd_2.9.5-1_source.buildinfo Files: a9c5dbc56e2c9e96089a8f4dc7a1047a 5125 utils optional sssd_2.9.5-1.dsc fb41a516f51d3f75855c7dd6f4c16c19 8001964 utils optional sssd_2.9.5.orig.tar.gz cbb4ca4872c19ca0130acc52575660aa 833 utils optional sssd_2.9.5.orig.tar.gz.asc 064f2def4a5862d0f9b296339a7b8cb8 46192 utils optional sssd_2.9.5-1.debian.tar.xz 58113394bef460507c81d3325d5ddbe3 10756 utils optional sssd_2.9.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZLUf4ACgkQy3AxZaiJ hNx9Qw//dOefPGod8HPE/c67EZ9diH47QHjkDmXicZ99Tsq2lsFBvluORNOssNNA LqNiEzDaVPzLQUQX0HScHlZbYdMu06l3PJz5n0xLB5CzfHrNIm64/YScgFhBzNHJ 1p9UOffbWpWj9QBBgyKg9q7t5Ezn5TXp51EdVsGyJxUUyTv5Y5eFfBKdsh5Y+g3O 5PsnkQIFflUdnELH3VZGBP+mKpyicBzjhLg/Vd7y72duMu8KN4UFeR77//tWGZh7 UPSzVzRLsh2SCCTfrv6dGJe7Sivk16A7grhdyAtf3UIkX/NooDdc57W9KE1kMleY bbylVmyKPcidW9lwMxRew10eJt+gTDiJB8uz6EH5cNH4fFml2wChLGqwuQGMZe8G kpPbteA3tX81ZXwSgDRKBnW44/uLiMlsjdlFQGaQVojjqipA4yr4XEB0kN3PFF8Q E5ZGTI13HXSLALYUxE6gwNnhGq94sXTLgbYA55/2y0aOHUmPAdaWpz4c+Eb1vYvl KG9vYmEuf+IqK2QAWIBCOBHWQ+FlXmOyBMc94x5vk3r6EwPP8xG2GPmsnj+JT9zA 9kC3ZAGk8CEQAGmcOAF9UyFcJeFRzlLmJ5ks2kqf/yhZZK0n53tTNLypINkNh41x Fs95W6ODY17Y5mjzqKNzDl6TDZjGfE8wQpNurddj7DeFHV+/FJM= =s50y -END PGP SIGNATURE- pgp6pkvOAcKWc.pgp Description: PGP signature --- End Message ---
Bug#1071520: marked as done (tp-smapi-dkms: (regression) breaks kernel versions 6.6.13-1~bpo12+1)
Your message dated Mon, 20 May 2024 16:19:20 +0200 with message-id and subject line Re: Bug#1071520: tp-smapi-dkms: (regression) breaks kernel versions 6.6.13-1~bpo12+1 has caused the Debian Bug report #1071520, regarding tp-smapi-dkms: (regression) breaks kernel versions 6.6.13-1~bpo12+1 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.) -- 1071520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Version: 0.43-3 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debbug.tp-smapi-d...@sideload.33mail.com Control: affects -1 linux-image-6.6.13+bpo-amd64 Kernel version 6.6.13-1~bpo12+1 fails to install because thinkpad_ec.c fails to build. This was originally filed as a bug against the kernel, but it’s actually a bug in tp-smapi-dkms. Transcript and logs are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467#22 Kernels 5.10.209-2 and earlier have no issues. Kernel versions 6.1.x are questionable. Kernel 6.1.x freezes. The tp-smapi-dkms modules were initially suspect, but kernel version 6.1.90-1 still froze when tp_smapi and thinkpad_ec modules were removed. In any case, thinkpad_ec.c is a non-starter for kernel 6.6.13-1~bpo12+1. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-28-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tp-smapi-dkms depends on: ii dkms 3.0.10-8+deb12u1 tp-smapi-dkms recommends no packages. tp-smapi-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.44-1~bpo12+1 On Mon, May 20, 2024 at 03:56:39PM +0200, Manny wrote: > Package: tp-smapi-dkms > Version: 0.43-3 > Severity: serious > Tags: upstream ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: debbug.tp-smapi-d...@sideload.33mail.com > Control: affects -1 linux-image-6.6.13+bpo-amd64 > > Kernel version 6.6.13-1~bpo12+1 fails to install because thinkpad_ec.c > fails to build. This was originally filed as a bug against the kernel, > but it’s actually a bug in tp-smapi-dkms. Transcript and logs are > here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467#22 > > Kernels 5.10.209-2 and earlier have no issues. Kernel versions 6.1.x > are questionable. Kernel 6.1.x freezes. The tp-smapi-dkms modules were > initially suspect, but kernel version 6.1.90-1 still froze when > tp_smapi and thinkpad_ec modules were removed. In any case, > thinkpad_ec.c is a non-starter for kernel 6.6.13-1~bpo12+1. This was reported and fixed in #1038207 If you're using a bpo kernel, I highly suggest to use kernel modules from bpo too. Evgeni--- End Message ---
Processed: cloning 1070113, reassign -1 to ukui-screensaver ...
Processing commands for cont...@bugs.debian.org: > clone 1070113 -1 Bug #1070113 [kylin-nm] kylin-nm: predictable filenames under /tmp with system() Bug 1070113 cloned as bug 1071521 > reassign -1 ukui-screensaver Bug #1071521 [kylin-nm] kylin-nm: predictable filenames under /tmp with system() Bug reassigned from package 'kylin-nm' to 'ukui-screensaver'. No longer marked as found in versions kylin-nm/3.0.3.1-1. Ignoring request to alter fixed versions of bug #1071521 to the same values previously set > retitle -1 ukui-screensaver: predictable filenames under /tmp with system() Bug #1071521 [ukui-screensaver] kylin-nm: predictable filenames under /tmp with system() Changed Bug title to 'ukui-screensaver: predictable filenames under /tmp with system()' from 'kylin-nm: predictable filenames under /tmp with system()'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070113 1071521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tp-smapi-dkms: (regression) breaks kernel versions 6.6.13-1~bpo12+1
Processing control commands: > affects -1 linux-image-6.6.13+bpo-amd64 Bug #1071520 [tp-smapi-dkms] tp-smapi-dkms: (regression) breaks kernel versions 6.6.13-1~bpo12+1 Added indication that 1071520 affects linux-image-6.6.13+bpo-amd64 -- 1071520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014539: marked as done (squirrel3: CVE-2022-30292)
Your message dated Mon, 20 May 2024 13:49:37 + with message-id and subject line Bug#1014539: fixed in squirrel3 3.1-8.2 has caused the Debian Bug report #1014539, regarding squirrel3: CVE-2022-30292 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.) -- 1014539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squirrel3 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for squirrel3. CVE-2022-30292[0]: | Heap-based buffer overflow in sqbaselib.cpp in SQUIRREL 3.2 due to | lack of a certain sq_reservestack call. https://github.com/albertodemichelis/squirrel/commit/a6413aa690e0bdfef648c68693349a7b878fe60d https://github.com/sprushed/CVE-2022-30292 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-2022-30292 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30292 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: squirrel3 Source-Version: 3.1-8.2 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of squirrel3, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated squirrel3 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: Mon, 13 May 2024 14:59:34 +0200 Source: squirrel3 Architecture: source Version: 3.1-8.2 Distribution: unstable Urgency: medium Maintainer: Fabian Wolff Changed-By: Matthias Geiger Closes: 1014539 Changes: squirrel3 (3.1-8.2) unstable; urgency=medium . * Non-maintainer upload. * Cherry-pick upstream commit as 03-fix-buffer-overflow.diff Closes: #1014539, CVE-2022-30292 Checksums-Sha1: e549b7bb3bee134a2cd73f07a27cdad3f8d7724e 2072 squirrel3_3.1-8.2.dsc 61ad8ea1de6abe992e91d368a8417bc6a0f74c58 7236 squirrel3_3.1-8.2.debian.tar.xz 7ded13b4277224edebdce4ea6e499278d66ba1c7 11318 squirrel3_3.1-8.2_amd64.buildinfo Checksums-Sha256: 8131d56d5d1c300d297b71bce54c5231f296a9c23826074c08174b4bac46f02f 2072 squirrel3_3.1-8.2.dsc c35a8a72ff0de510e73362c1767cec48c075ef9a861d140c9cc25736c06f182c 7236 squirrel3_3.1-8.2.debian.tar.xz 1717779437aa5aea4abd6e3862cca70184d85200cb4e5921df8c8ec7ad1e86ec 11318 squirrel3_3.1-8.2_amd64.buildinfo Files: bdee2b3a992e7ce5e8d8711446918fc9 2072 interpreters optional squirrel3_3.1-8.2.dsc ca1e958e9592005ded323d28d7e93864 7236 interpreters optional squirrel3_3.1-8.2.debian.tar.xz d422f2dcf8796b57a11178d80f3653e2 11318 interpreters optional squirrel3_3.1-8.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5CQeth7uIW7ehIz87iFbn7jEWwsFAmZCEFkACgkQ7iFbn7jE Wws5+BAAmxRgPoP+TwTJi9wLK9gvf9zfe+H1V23ZUp2tONeGaDzrqmZb/9XGK8zv MNqo5KiiwWCDeVcxy8Y5ILJpqfVHb4hnxPcy0fwBwvVHNX9yBPY2wdaTIRhULplR GXDM+K/ZcotE/DkZxEuaVNHyDY1fzuWesaKpt2XLp7o1v+RUoHkoooDLLhjZYakX pVNqKfay1KTdHYJVThMU8fVSFDbP2VyIRpgGwSGBsX+fsriZtG/kbbJMFbqQ/bku 57Q7SG3pNyvG9PYW51cN/nymYyudhjtHbv2zdmcEBA4iY31DZGlfuCKOuaQus9MT pm1M7uIbWySCxRHFwm1hXdX1zNTir5V8yP5IZBbbK4+e2+VDsj9Bn16G5/drI7/5 nbC1bXPL342VCGI1U+P9T6PJaLozbpcRx08AjFxaGB8XlbU8XZjzcNiZFGoSnyed zVTbbzghUyatt1Vy+X47oG97uLKNWBKuS6wSeh3o6cpxOWwGMRl0SXPof55bcBix NqCCv2z7EHLj9NhhIIi+ROpfflMyrScsuqyqTyR/8Yw8KwFm9Nx+kvC/RtLYuGOJ 1EPb1oVusXMGjjIthjvnoMmQ4lU2utiqtFH8t/eZUFfFVrNcf8cVMLx2c54PKgG3 xMlDHWBHu1Rx83kxqjEYldts+rhAj6blXjMIYgG78+mw5APCyJY= =ZDrf -END PGP SIGNATURE- pgp9L3HugZJxi.pgp Description: PGP signature --- End Message ---
Bug#1070956: marked as done (octave-fits FTBFS with Octave 9.1.0)
Your message dated Mon, 20 May 2024 13:08:37 + with message-id and subject line Bug#1071499: Removed package(s) from unstable has caused the Debian Bug report #1070956, regarding octave-fits FTBFS with Octave 9.1.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.) -- 1070956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-fits Version: 1.0.7-7 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=octave-fits=amd64=1.0.7-7%2Bb4=1715454563=0 ... g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-9.1.0/octave/.. -I/usr/include/octave-9.1.0/octave -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall save_fits_image_multi_ext.cc -o /tmp/oct-bxJQR8.o save_fits_image_multi_ext.cc: In function ‘octave_value_list Fsave_fits_image_multi_ext(const octave_value_list&, int)’: save_fits_image_multi_ext.cc:140:60: error: passing ‘const NDArray’ as ‘this’ argument discards qualifiers [-fpermissive] 140 | double * datap = const_cast( image.fortran_vec() ); | ~^~ In file included from /usr/include/octave-9.1.0/octave/../octave/Array-util.h:31, from /usr/include/octave-9.1.0/octave/../octave/MSparse.h:31, from /usr/include/octave-9.1.0/octave/../octave/MatrixType.h:33, from /usr/include/octave-9.1.0/octave/../octave/mx-base.h:33, from /usr/include/octave-9.1.0/octave/../octave/Matrix.h:34, from /usr/include/octave-9.1.0/octave/../octave/oct.h:33, from save_fits_image_multi_ext.cc:19: /usr/include/octave-9.1.0/octave/../octave/Array.h:666:20: note: in call to ‘T* Array::fortran_vec() [with T = double; Alloc = std::allocator]’ 666 | OCTARRAY_API T * fortran_vec (); |^~~ save_fits_image.cc: In function ‘octave_value_list Fsave_fits_image(const octave_value_list&, int)’: save_fits_image.cc:132:58: error: passing ‘const NDArray’ as ‘this’ argument discards qualifiers [-fpermissive] 132 | double * datap = const_cast( image.fortran_vec() ); | ~^~ In file included from /usr/include/octave-9.1.0/octave/../octave/Array-util.h:31, from /usr/include/octave-9.1.0/octave/../octave/MSparse.h:31, from /usr/include/octave-9.1.0/octave/../octave/MatrixType.h:33, from /usr/include/octave-9.1.0/octave/../octave/mx-base.h:33, from /usr/include/octave-9.1.0/octave/../octave/Matrix.h:34, from /usr/include/octave-9.1.0/octave/../octave/oct.h:33, from save_fits_image.cc:19: /usr/include/octave-9.1.0/octave/../octave/Array.h:666:20: note: in call to ‘T* Array::fortran_vec() [with T = double; Alloc = std::allocator]’ 666 | OCTARRAY_API T * fortran_vec (); |^~~ make[1]: *** [Makefile:9: save_fits_image_multi_ext.oct] Error 1 --- End Message --- --- Begin Message --- Version: 1.0.7-7+rm Dear submitter, as the package octave-fits has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1071499 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1070813: marked as done (src:camelot-py: fails to migrate to testing for too long: autopkgtest failure on ppc64el)
Your message dated Mon, 20 May 2024 12:49:12 +
with message-id
and subject line Bug#1070813: fixed in camelot-py 0.11.0-5
has caused the Debian Bug report #1070813,
regarding src:camelot-py: fails to migrate to testing for too long: autopkgtest
failure on ppc64el
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.)
--
1070813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camelot-py
Version: 0.11.0-3
Severity: serious
Control: close -1 0.11.0-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1063891
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:camelot-py has been trying to migrate for
86 days [2]. Hence, I am filing this bug. As you noticed yourself (in
bug 1063891) the autopkgtest fails on ppc64el. If you can't easily fix
it, I suggest you make the test failure on ppc64el not blocking. You can
do that by either using the Architecture field in d/t/control
("!ppc64el" works), but I don't recommend that because changes to the
results would go unnoticed and it would be harder to get a log.
Alternatively you can annotate the test with the flaky restriction, but
that would cause failure on !ppc64el to go unnoticed. So, I would
recommend using the skippable restriction and "exit 77" when the test
fails on ppc64el (but that's a bit more work to embed in the test).
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=camelot-py
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: camelot-py
Source-Version: 0.11.0-5
Done: Elena Grandi
We believe that the bug you reported is fixed in the latest version of
camelot-py, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Elena Grandi (supplier of updated camelot-py 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: Mon, 20 May 2024 14:20:38 +0200
Source: camelot-py
Architecture: source
Version: 0.11.0-5
Distribution: unstable
Urgency: medium
Maintainer: Elena Grandi
Changed-By: Elena Grandi
Closes: 1070813
Changes:
camelot-py (0.11.0-5) unstable; urgency=medium
.
* Make autopkgtests on ppc64el non blocking. Closes: #1070813
Checksums-Sha1:
a16afab424f4ac98351daa9b51500497881e97bd 2198 camelot-py_0.11.0-5.dsc
67a902bd07fe9f3e50993e4fb9465eb8fa2647df 4408 camelot-py_0.11.0-5.debian.tar.xz
832f62829426bdea5b6d718481247b8ac90fc995 19984
camelot-py_0.11.0-5_amd64.buildinfo
Checksums-Sha256:
cb04be0b531aa0dd3a5f90c045e79381aa839d222767dfd9c67d2be36cdae236 2198
camelot-py_0.11.0-5.dsc
fdfaaa199e563230747eb62ba3c621b89cc844581928b3a1f9daca49146c1b3c 4408
camelot-py_0.11.0-5.debian.tar.xz
bd6cb8d049818447f8495123e4ee34fb43489d84600b0b11b0625dbf7b6d7435 19984
camel
Bug#1071335: marked as done (pptpd: FTBFS: our_syslog.h:38:62: error: implicit declaration of function ‘strerror’)
Your message dated Mon, 20 May 2024 10:35:51 +
with message-id
and subject line Bug#1071335: fixed in pptpd 1.5.0-1
has caused the Debian Bug report #1071335,
regarding pptpd: FTBFS: our_syslog.h:38:62: error: implicit declaration of
function ‘strerror’
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.)
--
1071335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pptpd
Version: 1.4.0-13
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
autoreconf: warning: autoconf input should be named 'configure.ac', not
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
configure.in:3: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.in:3: You should use the 'AC_CONFIG_HEADERS' macro instead.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:745: AM_CONFIG_HEADER is expanded from...
configure.in:3: the top level
configure.in:4: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are
deprecated.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:429: AM_INIT_AUTOMAKE is expanded from...
configure.in:4: the top level
configure.in:153: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:153: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.in:153: the top level
configure.in:153: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:153: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2894: _AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2911: AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.in:153: the top level
configure.in:240: warning: The macro `AC_CHECKING' is obsolete.
configure.in:240: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.in:240: the top level
configure.in:296: warning: AC_OUTPUT should be used without arguments.
configure.in:296: You should run autoupdate.
autoheader: warning: autoconf input should be named 'configure.ac', not
'configure.in'
autoheader: warning: WARNING: Using auxiliary files such as 'acconfig.h',
'config.h.bot'
autoheader: WARNING: and 'config.h.top', to define templates for 'config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of 'AC_DEFINE_UNQUOTED' and
autoheader: WARNING: 'AC_DEFINE' allows one to define a template without
autoheader: WARNING: 'acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function 'main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
configure.in:4: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are
deprecated. For more info, see:
configure.in:4:
https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:109: installing './compile'
Makefile.am:7: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or
'*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--prefix=/usr \
--mandir=/usr/share/man \
--with-libwrap \
--enable-bcrelay
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --d
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org:
> reassign 1071494 debbugs
Bug #1071494 [apt] debbugs: Revert "Salsa-CI: Allow autopkgtest to fail for now"
Bug reassigned from package 'apt' to 'debbugs'.
Ignoring request to alter found versions of bug #1071494 to the same values
previously set
Ignoring request to alter fixed versions of bug #1071494 to the same values
previously set
> fixed 1053183 galera-4/26.4.18-1
Bug #1053183 {Done: Otto Kekäläinen } [src:galera-4] galera-4:
FTBFS on sparc64: one of sever post-build test fail
Marked as fixed in versions galera-4/26.4.18-1; no longer marked as fixed in
versions galera-4/26.4.18-1.
> tags 1069535 wontfix
Bug #1069535 [src:galera-3] galera-3: FTBFS on armel: dh_auto_test: error: cd
obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1
ARGS=--output-on-failure returned exit code 2
Ignoring request to alter tags of bug #1069535 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053183
1069535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069535
1071494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071160: marked as done (git: CVE-2024-32002 CVE-2024-32004 CVE-2024-32020 CVE-2024-32021 CVE-2024-32465)
Your message dated Mon, 20 May 2024 04:34:46 + with message-id and subject line Bug#1071160: fixed in git 1:2.45.1-1 has caused the Debian Bug report #1071160, regarding git: CVE-2024-32002 CVE-2024-32004 CVE-2024-32020 CVE-2024-32021 CVE-2024-32465 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.) -- 1071160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git Version: 1:2.43.0-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for git. CVE-2024-32002[0]: | Git is a revision control system. Prior to versions 2.45.1, 2.44.1, | 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with | submodules can be crafted in a way that exploits a bug in Git | whereby it can be fooled into writing files not into the submodule's | worktree but into a `.git/` directory. This allows writing a hook | that will be executed while the clone operation is still running, | giving the user no opportunity to inspect the code that is being | executed. The problem has been patched in versions 2.45.1, 2.44.1, | 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support | is disabled in Git (e.g. via `git config --global core.symlinks | false`), the described attack won't work. As always, it is best to | avoid cloning repositories from untrusted sources. CVE-2024-32004[1]: | Git is a revision control system. Prior to versions 2.45.1, 2.44.1, | 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare | a local repository in such a way that, when cloned, will execute | arbitrary code during the operation. The problem has been patched in | versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. | As a workaround, avoid cloning repositories from untrusted sources. CVE-2024-32020[2]: | Git is a revision control system. Prior to versions 2.45.1, 2.44.1, | 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up | hardlinking files into the target repository's object database when | source and target repository reside on the same disk. If the source | repository is owned by a different user, then those hardlinked files | may be rewritten at any point in time by the untrusted user. Cloning | local repositories will cause Git to either copy or hardlink files | of the source repository into the target repository. This | significantly speeds up such local clones compared to doing a | "proper" clone and saves both disk space and compute time. When | cloning a repository located on the same disk that is owned by a | different user than the current user we also end up creating such | hardlinks. These files will continue to be owned and controlled by | the potentially-untrusted user and can be rewritten by them at will | in the future. The problem has been patched in versions 2.45.1, | 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. CVE-2024-32021[3]: | Git is a revision control system. Prior to versions 2.45.1, 2.44.1, | 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local | source repository that contains symlinks via the filesystem, Git may | create hardlinks to arbitrary user-readable files on the same | filesystem as the target repository in the `objects/` directory. | Cloning a local repository over the filesystem may creating | hardlinks to arbitrary user-owned files on the same filesystem in | the target Git repository's `objects/` directory. When cloning a | repository over the filesystem (without explicitly specifying the | `file://` protocol or `--no-local`), the optimizations for local | cloning will be used, which include attempting to hard link the | object files instead of copying them. While the code includes checks | against symbolic links in the source repository, which were added | during the fix for CVE-2022-39253, these checks can still be raced | because the hard link operation ultimately follows symlinks. If the | object on the filesystem appears as a file during the check, and | then a symlink during the operation, this will allow the adversary | to bypass the check and create hardlinks in the destination objects | directory to arbitrary, user-readable files. The problem has been | patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, | and 2.39.4. CVE-2024-32465[4]: | Git is a revision control system. The Git project recommends to | avoid working in untrusted repositories, and instead to clone it | first with
Bug#1071145: marked as done (lxqt-menu-data: breaks lxqt-panel)
Your message dated Mon, 20 May 2024 00:20:05 + with message-id and subject line Bug#1071145: fixed in lxqt-panel 1.4.0-1 has caused the Debian Bug report #1071145, regarding lxqt-menu-data: breaks lxqt-panel 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.) -- 1071145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxqt-menu-data Version: 1.4.1-2 Severity: serious Hi, Your package breaks/replaces lxqt-panel (<< 1.4), however the latest lxqt-panel in sid is 1.3.0-1. This means that those packages cannot be co-installed atm, which is making lxqt-core uninstallable now. If the reason for this breaks/replaces was to take over some files from lxqt-panel, then a new version of lxqt-panel should be uploaded with a high enough version and without those files. In a fresh sid chroot: root@andromeda:/# apt install lxqt-core Unsatisfied dependencies: lxqt-menu-data : Breaks: lxqt-panel (< 1.4) but 1.3.0-1+b1 is to be installed Cheers, Emilio --- End Message --- --- Begin Message --- Source: lxqt-panel Source-Version: 1.4.0-1 Done: Andrew Lee (李健秋) We believe that the bug you reported is fixed in the latest version of lxqt-panel, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated lxqt-panel 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: Sun, 19 May 2024 13:36:09 +0200 Source: lxqt-panel Architecture: source Version: 1.4.0-1 Distribution: unstable Urgency: medium Maintainer: LXQt Packaging Team Changed-By: Andrew Lee (李健秋) Closes: 1071145 1071146 Changes: lxqt-panel (1.4.0-1) unstable; urgency=medium . [ ChangZhuo Chen (陳昌倬) ] * New upstream release (Closes: #1071145, #1071146). * Bump Standards-Version to 4.7.0. * d/control: Add Build-Depends lxqt-menu-data. . [ Andrew Lee (李健秋) ] * debian/control: build-deps on liblxqt1-dev (>= 1.4.0~). * debian/control: build-deps on liblxqt-globalkeys1-dev (>= 1.4.0~). * debian/control: build-deps on liblxqt-globalkeys-ui1-dev (>= 1.4.0~). * debian/control: improve package descriptions. * Clean up of group membership after two calls. Checksums-Sha1: eb48b661ce7e9611dfef76fdd3a64f149877b96f 2625 lxqt-panel_1.4.0-1.dsc f7f21b0b73ab3f7bef70236c26f0d4bbe5562596 612012 lxqt-panel_1.4.0.orig.tar.xz f402241658edd73f2f333f97bfd7477fa840a96e 10548 lxqt-panel_1.4.0-1.debian.tar.xz 0685d6f508099208c771e083a747374bc4f90b70 15876 lxqt-panel_1.4.0-1_amd64.buildinfo Checksums-Sha256: 3ac28a7b69b8e220c771711f25fdad9d837c1739470a858ec748f038aa8fe7e3 2625 lxqt-panel_1.4.0-1.dsc 0e660c0397c96a28f0fcf316b20c72d203c85793a884e1487b3b14e3790defc9 612012 lxqt-panel_1.4.0.orig.tar.xz 9826f92cd481c9e0335b6fdc989d1b5761d099ebadfbb7b6f7687a48124710dd 10548 lxqt-panel_1.4.0-1.debian.tar.xz d41cf133925305fb83e54397eac6c8370a74ba80fa4df62e01616313ea1b8f5e 15876 lxqt-panel_1.4.0-1_amd64.buildinfo Files: aafb9321ce616a4b28122565ca1a5ae0 2625 x11 optional lxqt-panel_1.4.0-1.dsc ac8d89f21fa96b73d61ba54715fb5969 612012 x11 optional lxqt-panel_1.4.0.orig.tar.xz 7eff8a2a56dc9d791617c1fc2f28150f 10548 x11 optional lxqt-panel_1.4.0-1.debian.tar.xz 12ea991808ccb6406ac7c18fc53c40da 15876 x11 optional lxqt-panel_1.4.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEugQ0bcLh/mPHkIeTzGWwzewnXVsFAmZKlA8ACgkQzGWwzewn XVu45g//YhUbwg14qB9bstUo9QidhfcX8bGm1aJYtOSIV6/c3Py3JP0Q8+joV5iS cGrom8C3VLh9XsKlCpUvmobZ9PvsWoJPVMrOdQEzh0XiQiZIKn1oyouLbGzw+Uly ljY3DO1QyxRseyz2HY67jueXuHWATGY/RPxqEkgP8b7kkFxag5MS2MVxfphBbYQD kLap3OWDqVNgUo9vq6pgr5MQ30ZjuR+1d279VWgykN4ZjfdtxSsEqyVak04Xn9eT Q3igYhb7XUg5I7OewmSNdjvSwAFF47Yyn2pxLQ8uk1cf0cqdj6dgiBa5wAhSMGlp QCu9ReygsSvxf/f9bkW8Rt4gEK5z5JD4hcF8i+QQHqbeJDlW8be5fsKvrgT+pLVg fyDuNzESfM/VBEwc91VWZu3oJavg+7dr7qi79kI+GETPqoyeQBXRk0h3sCLdJRkG jAqoEB7F0HxODLjCcZsrEbT5QNtzVZQf+5rq96xYMdwaAr7/dcoas9U9xwlS8RER BL1h7p7K1GIezAyHE/9lzm0E61nokHzg7hJn9BXIzrbjgjHv6H1YciX8fFMce8Oz W/YkFxD3hRgYOEy86D9cfbl/LYGhX2jkhrcarV20l2vEtS5V2Lx
Processed: Re: Bug#1071372: emacs: it hangs saving .gpg files (without using cpu)
Processing control commands: > found -1 1:29.3+1-2 Bug #1071372 [emacs] emacs: it hangs saving .gpg files (without using cpu) Marked as found in versions emacs/1:29.3+1-2. -- 1071372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041341: marked as done (html5lib: FTBFS on unstable)
Your message dated Sun, 19 May 2024 23:55:11 +0100 with message-id and subject line Re: Bug#1041341: html5lib: FTBFS on unstable has caused the Debian Bug report #1041341, regarding html5lib: FTBFS on unstable 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.) -- 1041341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: html5lib Version: 1.1-3 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-pyt...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, html5lib seems to fail to build due to a change in Traceback.filter() Relevant excerpt from build log: ../../../html5lib/tests/testdata/tokenizer/domjs.test ... INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 270, in wrap_session INTERNALERROR> session.exitstatus = doit(config, session) or 0 INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 324, in _main INTERNALERROR> config.hook.pytest_runtestloop(session=session) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ INTERNALERROR> return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/main.py", line 349, in pytest_runtestloop INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, nextitem=nextitem) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ INTERNALERROR> return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> ^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114, in pytest_runtest_protocol INTERNALERROR> runtestprotocol(item, nextitem=nextitem) INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133, in runtestprotocol INTERNALERROR> reports.append(call_and_report(item, "call", log)) INTERNALERROR>^^ INTERNALERROR> File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 224, in call_and_report INTERNALERROR> report: TestReport = hook.pytest_runtest_makereport(item=item, ca
Processed: Re: Bug#1071372: emacs: it hangs saving .gpg files (without using cpu)
Processing control commands: > severity -1 critical Bug #1071372 [emacs] emacs: it hangs saving .gpg files (without using cpu) Severity set to 'critical' from 'normal' -- 1071372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069321: marked as done (FTBFS: [Makefile:163: check] Error 1)
Your message dated Mon, 20 May 2024 00:05:06 +0200 with message-id <87e30dd9627baa75fefb02cf6cae3...@debian.org> and subject line Re: Bug#1069321 FTBFS: [Makefile:163: check] Error 1 has caused the Debian Bug report #1069321, regarding FTBFS: [Makefile:163: check] Error 1 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.) -- 1069321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hypre Version: 2.28.0-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=hypre=armhf=2.28.0-8%2Bb2=1713420980=0 I couldn't find the actual failing command. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Continues to build successfully, so closing this bug.--- End Message ---
Bug#1071367: marked as done (sway-notification-center: FTBFS: ../src/controlCenter/widgets/baseWidget.vala:114.22-114.24: error: Argument 1: Cannot convert from `pid_t' to `Posix.pid_t')
Your message dated Sun, 19 May 2024 21:19:36 + with message-id and subject line Bug#1071367: fixed in sway-notification-center 0.10.1-1 has caused the Debian Bug report #1071367, regarding sway-notification-center: FTBFS: ../src/controlCenter/widgets/baseWidget.vala:114.22-114.24: error: Argument 1: Cannot convert from `pid_t' to `Posix.pid_t' 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.) -- 1071367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sway-notification-center Version: 0.9.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure 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 The Meson build system Version: 1.4.0 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: sway-notificaton-center Project version: 0.9.0 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25) 13.2.0") C linker for the host machine: cc ld.bfd 2.42 Vala compiler for the host machine: valac (valac 0.56.17) Host machine cpu family: x86_64 Host machine cpu: x86_64 Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas) Program git found: NO Configuring constants.vala using configuration Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 Run-time dependency gio-2.0 found: YES 2.80.2 Run-time dependency gio-unix-2.0 found: YES 2.80.2 Run-time dependency gtk+-3.0 found: YES 3.24.41 Run-time dependency json-glib-1.0 found: YES 1.8.0 Run-time dependency libhandy-1 found: YES 1.8.3 Library gtk-layer-shell found: YES Library m found: YES Library posix found: YES Run-time dependency gee-0.8 found: YES 0.20.6 Run-time dependency libpulse found: YES 16.1 Run-time dependency libpulse-mainloop-glib found: YES 16.1 Dependency libhandy-1 found: YES 1.8.3 (cached) Run-time dependency gtk-layer-shell-0 found: YES 0.8.2 Dependency gio-2.0 found: YES 2.80.2 (cached) Program /usr/bin/glib-compile-resources found: YES (/usr/bin/glib-compile-resources) Configuring config.json using configuration Configuring org.erikreider.swaync.service using configuration Found CMake: /usr/bin/cmake (3.29.3) WARNING: CMake Toolchain: Failed to determine CMake compilers state Run-time dependency systemd found: NO (tried pkgconfig and cmake) Configuring swaync.service using configuration Run-time dependency bash-completion found: YES 2.14.0 Run-time dependency fish found: NO (tried pkgconfig and cmake) Build-time dependency scdoc found: YES 1.11.3 Program /usr/bin/scdoc found: YES (/usr/bin/scdoc) Message: share/man 1 share/man/man1 Message: share/man 5 share/man/man5 Message: share/man 1 share/man/man1 Build targets in project: 7 sway-notificaton-center 0.9.0 User defined options buildtype : plain libdir: lib/x86_64-linux-gnu localstatedir : /var prefix: /usr sysconfdir: /etc wrap_mode : nodownload python.bytecompile: -1 Found ninja-1.12.1 at /usr/bin/ninja dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/42] /usr/bin/glib-compile-resources ../src/sway_notification_center.gresource.xml --sourcedir ../src --c-name sway_notification_center --internal --generate --target src/sway_notification_center-resources.h [2/42] /usr/bin/glib-compile-resources ../src/sway_notification_center.gresource.xml --sourcedir ../src --c-name sway_notification_center --internal --generate --target src/sway_notification_center-resources.c --dependency-file src/sway_notification_center-resources.c.d [3/42] valac -C --enable-gobject-tracing --enable-checking -D WANT_SCRIPTING -D HAVE_LATEST_LIBHANDY -D HAVE_LATEST_GTK_LAYER_SHELL --pkg libpulse-mainloop-glib --pkg libpulse --pkg gee-0.8 --pkg posix --pkg libhandy-1 --pkg json-glib-1.0 --pkg gtk+-3.0 --pkg gio-unix-2.0 --pkg gio-2.0 --color=always --directory src/swaync-client.p --basedir ../src --target-glib=2.50 --pkg=GtkLayerShell-0.1 ../src/client.vala src/constants.vala [4/42] valac -C --enable-gobject-tracing --enable-checking -D WANT
Bug#1069834: marked as done (sccache FTBFS with itoa != 0.3.4)
Your message dated Sun, 19 May 2024 16:40:57 -0400 with message-id <75b30bce-f251-498c-a9a1-a13ca5682...@debian.org> and subject line Closing bugs manually after Debian infra problem has caused the Debian Bug report #1069834, regarding sccache FTBFS with itoa != 0.3.4 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.) -- 1069834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sccache Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sccache=0.8.0-1 ... test test_rust_cargo_cmd_readonly_preemtive_block ... FAILED failures: test_rust_cargo_cmd_readonly_preemtive_block stdout Error: Unexpected failure. code=101 stderr=`` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` ``` command=`cd "tests/test-crate" && CARGO_INCREMENTAL="0" CARGO_TARGET_DIR="/<>/debian/sccache_test_rust_cargoG4h5iT/cargo" RUSTC_WRAPPER="/<>/target/x86_64-unknown-linux-gnu/release/sccache" TEST_ENV_VAR="1" "/usr/bin/cargo" "build" "--color=never"` code=101 stdout="" stderr=``` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` Stack backtrace: 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: failures: test_rust_cargo_cmd_readonly_preemtive_block test result: FAILED. 2 passed; 1 failed; 5 ignored; 0 measured; 0 filtered out; finished in 11.18s error: test failed, to rerun pass `--test sccache_cargo` dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test returned exit code 101 make[1]: *** [debian/rules:29: override_dh_auto_test] Error 25 --- End Message --- --- Begin Message --- Hi, There was a mail infrastructure problem and as such, this bug wasn't closed automatically, as it should've been. Closing it manually now :) See BTS 1071469 for more info. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ --- End Message ---
Bug#1071326: marked as done (libnet-interface-perl: FTBFS: failing tests)
Your message dated Sun, 19 May 2024 20:34:29 + with message-id and subject line Bug#1071326: fixed in libnet-interface-perl 1.016-3 has caused the Debian Bug report #1071326, regarding libnet-interface-perl: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1071326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libnet-interface-perl Version: 1.016-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem=perl_makemaker dh_update_autotools_config -O--buildsystem=perl_makemaker cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf -O--buildsystem=perl_makemaker configure.ac:72: warning: The macro `AC_CONFIG_HEADER' is obsolete. configure.ac:72: You should run autoupdate. ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from... configure.ac:72: the top level configure.ac:217: warning: The macro `AC_HEADER_STDC' is obsolete. configure.ac:217: You should run autoupdate. ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from... configure.ac:217: the top level [... snipped ...] ok 40 ok 41 ok 42 ok 43 ok 44 ok 45 ok 46 ok 47 ok 48 ok 49 ok 50 ok 51 ok 52 ok 53 ok 54 ok 55 ok 56 ok 57 ok 58 ok 59 ok 60 ok 61 ok 62 ok 63 ok 64 ok 65 ok 66 ok 67 ok 68 ok 69 ok 70 ok 71 ok 72 ok 73 ok 74 ok 75 ok 76 ok 77 ok 78 ok 79 ok 80 ok 81 ok 82 ok 83 ok 84 ok 85 ok 86 ok 87 ok 88 ok 89 ok 90 ok 91 ok 92 ok 93 ok 94 ok 95 ok 96 ok 97 ok 98 ok 99 ok 100 ok 101 ok 102 ok 103 ok 104 ok 105 ok 106 ok 107 ok 108 ok 109 ok 110 ok 111 ok 112 ok 113 ok 114 ok 115 ok 116 ok 117 ok 118 ok 119 ok 120 ok 121 ok 122 ok 123 ok 124 ok 125 ok 126 ok 127 ok 128 ok 129 ok 130 ok 131 ok 132 ok 133 ok 134 ok 135 ok 136 ok 137 ok 138 ok 139 ok 140 ok 141 ok 142 ok 143 ok 144 ok 145 ok 146 ok 147 ok 148 ok 149 ok 150 ok 151 ok 152 ok 153 ok 154 ok 155 ok 156 ok 157 ok 158 ok 159 ok 160 ok 161 ok 162 ok 163 ok 164 ok 165 ok 166 ok 167 ok *** buffer overflow detected ***: terminated t/simplesets.t 1..2 ok 1 - use Net::Interface; Failed 1/2 subtests t/strlcpy.t ... 1..21 ok 1 - use Net::Interface; ok 2 - strlcpy -1, got: 0 ok 3 - copied 0 bytes, exp: [undef] ok 4 - strlcpy 0, got: 0 ok 5 - copied 0 bytes, exp: [undef] ok 6 - strlcpy 1, got: 1 ok 7 - copied 1 bytes, exp: [\0] ok 8 - strlcpy 2, got: 2 ok 9 - copied 2 bytes, exp: a\0 ok 10 - strlcpy 3, got: 3 ok 11 - copied 3 bytes, exp: ab\0 ok 12 - strlcpy 4, got: 4 ok 13 - copied 4 bytes, exp: abc\0 ok 14 - strlcpy 5, got: 5 ok 15 - copied 5 bytes, exp: abcd\0 ok 16 - strlcpy 6, got: 6 ok 17 - copied 6 bytes, exp: abcde\0 ok 18 - strlcpy 7, got: 7 ok 19 - copied 7 bytes, exp: abcdef\0 ok 20 - strlcpy 8, got: 7 ok 21 - copied 7 bytes, exp: abcdef\0 ok t/symbols.t ... ok 1 - use Net::Interface; ok 2 - require Net::Interface::NetSymbols; ok 3 - PF_UNSPEC = 0 found, unspec ok 4 - PF_INET = 2 found, inet ok 5 - AF_UNSPEC = 0 found, unspec ok 6 - AF_INET = 2 found, inet ok 7 - expected that _NI_AF_TEST is not implemented on this architecture ok 8 - IFHWADDRLEN = 6 found, 6 ok 9 - IF_NAMESIZE = 16 found, 16 ok 10 - IFNAMSIZ = 16 found, 16 ok 11 - netsymbols max value +1 = 2147483647 ok 12 - found PF_UNSPEC => 0 unspec ok 13 - found PF_LOCAL => 1 file ok 14 - found PF_INET => 2 inet ok 15 - found PF_AX25 => 3 ax25 ok 16 - found PF_IPX=> 4 ipx ok 17 - found PF_APPLETALK => 5 appletalk ok 18 - found PF_X25=> 9 x25 ok 19 - found PF_INET6 => 10 inet6 ok 20 - found PF_ROSE => 11 rose ok 21 - found PF_DECnet => 12 decnet ok 22 - found PF_PACKET => 17 packet ok 23 - found PF_ASH=> 18 ash ok 24 - found PF_ECONET => 19 econet ok 25 - found PF_MAX=> 46 max ok 26 - IFF_UP => 0x1 = up ok 27 - AF_INET => 0x2 = inet ok 28 - RFC2373_GLOBAL => 0xe = global-scope ok 29 - RFC2373_ORGLOCAL=> 0x8 = org-local ok 30 - RFC2373_SITELOCAL => 0x5 = site-local ok 31 - RFC2373_LINKLOCAL => 0x2 = link-local ok 32 - RFC2373_NODELOCAL => 0x1 = loopback ok 33 - IPV6_ADDR_ANY => 0x0 = addr-any ok 34 - IPV6_ADDR_UNICAST => 0x1 = unicast ok 35 - IPV6_ADDR_MULTICAST => 0x2 = multicast ok 36 - IPV6_ADD
Processed: Bug#1071326 marked as pending in libnet-interface-perl
Processing control commands: > tag -1 pending Bug #1071326 [src:libnet-interface-perl] libnet-interface-perl: FTBFS: failing tests Added tag(s) pending. -- 1071326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1071326 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=57413
Processing commands for cont...@bugs.debian.org: > forwarded 1071326 https://rt.cpan.org/Public/Bug/Display.html?id=57413 Bug #1071326 [src:libnet-interface-perl] libnet-interface-perl: FTBFS: failing tests Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=57413'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1071326
Processing commands for cont...@bugs.debian.org: > tags 1071326 + trixie sid Bug #1071326 [src:libnet-interface-perl] libnet-interface-perl: FTBFS: failing tests Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071467: linux-image-6.6.13+bpo-amd64: installation botched, tiny and corrupt deb file
Processing control commands: > tags -1 moreinfo Bug #1071467 [src:linux] linux-image-6.6.13+bpo-amd64: installation botched, tiny and corrupt deb file Added tag(s) moreinfo. > severity -1 normal Bug #1071467 [src:linux] linux-image-6.6.13+bpo-amd64: installation botched, tiny and corrupt deb file Severity set to 'normal' from 'grave' -- 1071467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071420: linux-image-6.8.9-1-amd64: cannot mount btrfs root partition
Processing control commands: > tags -1 moreinfo Bug #1071420 [src:linux] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Added tag(s) moreinfo. > severity -1 important Bug #1071420 [src:linux] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Severity set to 'important' from 'grave' -- 1071420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1071420 in 6.8.9-1, affects 1071420
Processing commands for cont...@bugs.debian.org: > found 1071420 6.8.9-1 Bug #1071420 [src:linux] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Marked as found in versions linux/6.8.9-1. > affects 1071420 src:systemd Bug #1071420 [src:linux] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Added indication that 1071420 affects src:systemd > thanks Stopping processing here. Please contact me if you need assistance. -- 1071420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: metadata
Processing commands for cont...@bugs.debian.org: > tags 1063527 + ftbfs Bug #1063527 [src:einsteinpy] einsteinpy: test_plotting fails to converge with scipy 1.11 Added tag(s) ftbfs. > tags 1040334 + ftbfs Bug #1040334 [facet-analyser] facet-analyser - build-depends on conflicting packages Added tag(s) ftbfs. > tags 1071043 + ftbfs Bug #1071043 [libpsml-dev] libpsml-dev: unsatisfiable (Build-)Depends: libxmlf90-dev Added tag(s) ftbfs. > tags 1012320 + ftbfs Bug #1012320 [src:materialize] materialize: build-depends on non-existing libjs-anime Added tag(s) ftbfs. > tags 1014605 + ftbfs Bug #1014605 [src:node-functional.js] node-functional.js: FTBFS, missing build-dependencies Added tag(s) ftbfs. > tags 1002847 + ftbfs Bug #1002847 [src:nttcp] nttcp: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) ftbfs. > tags 1071017 + ftbfs Bug #1071017 [obs-source-copy] FTBFS: source-copy.cpp:615:31: error: ‘void obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is deprecated [-Werror=deprecated-declarations] Added tag(s) ftbfs. > severity 1070545 serious Bug #1070545 [src:php-fig-log-test] php-fig-log-test: FTBFS with phpunit 11: build-dependency not installable: php-psr-log (>= 2.0) Severity set to 'serious' from 'normal' > tags 1019042 + ftbfs Bug #1019042 [src:qwertone] rust-qwertone: FTBFS - dep issue Added tag(s) ftbfs. > severity 1057677 serious Bug #1057677 [src:resteasy] resteasy: ftbfs due to the missing dependency org.jboss.resteasy:resteasy-jaxrs:jar:3.6.2.Final Severity set to 'serious' from 'important' > tags 1025094 + ftbfs Bug #1025094 [ruby-behance] ruby-behance fails to rebuild after new upstream of ruby-faraday Added tag(s) ftbfs. > tags 1025092 + ftbfs Bug #1025092 [ruby-faraday-middleware] ruby-faraday-middleware fails to rebuild after updating ruby-faraday Added tag(s) ftbfs. > tags 1025090 + ftbfs Bug #1025090 [ruby-gh] ruby-gh fails to rebuild on updating ruby-faraday Added tag(s) ftbfs. > tags 1037529 + ftbfs Bug #1037529 [ruby-jekyll-github-metadata] ruby-jekyll-github-metadata: FTBFS with test failures when there's no network Added tag(s) ftbfs. > tags 1050580 + ftbfs Bug #1050580 [src:ruby-roxml] ruby-roxml: broken by ruby-nokogiri 1.15.4 Added tag(s) ftbfs. > tags 1050097 + ftbfs Bug #1050097 [scrcpy] scrcpy: fails to build from source on arch:indep Added tag(s) ftbfs. > tags 1063827 + ftbfs Bug #1063827 [src:tahoe-lafs] tahoe-lafs: new package tahoe-lafs depends on python3-future which is pending removal Added tag(s) ftbfs. > severity 1063827 serious Bug #1063827 [src:tahoe-lafs] tahoe-lafs: new package tahoe-lafs depends on python3-future which is pending removal Severity set to 'serious' from 'important' > tags 1011492 + ftbfs Bug #1011492 [src:tika] tika: FTBFS cannot find symbols Added tag(s) ftbfs. > tags 1050355 + ftbfs Bug #1050355 [src:tiledarray] tiledarray has unfulfilled build dependencies Added tag(s) ftbfs. > tags 934977 + ftbfs Bug #934977 [src:verilog-mode] verilog-mode: unbuildable in testing due to missing B-D emacs25 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002847 1011492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011492 1012320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012320 1014605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014605 1019042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019042 1025090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025090 1025092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025092 1025094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025094 1037529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037529 1040334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040334 1050097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050097 1050355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050355 1050580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050580 1057677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057677 1063527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063527 1063827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063827 1070545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070545 1071017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071017 1071043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071043 934977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060608: marked as done (libnitrokey: Please switch Build-Depends to systemd-dev)
Your message dated Sun, 19 May 2024 17:05:55 + with message-id and subject line Bug#1060608: fixed in libnitrokey 3.7-2 has caused the Debian Bug report #1060608, regarding libnitrokey: Please switch Build-Depends to systemd-dev 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.) -- 1060608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnitrokey Version: 3.7-1.1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package libnitrokey declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: libnitrokey Source-Version: 3.7-2 Done: Patryk Cisek We believe that the bug you reported is fixed in the latest version of libnitrokey, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patryk Cisek (supplier of updated libnitrokey 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: Sun, 19 May 2024 09:02:22 -0700 Source: libnitrokey Binary: libnitrokey-common libnitrokey-dev libnitrokey3 libnitrokey3-dbgsym Architecture: source all amd64 Version: 3.7-2 Distribution: unstable Urgency: medium Maintainer: Patryk Cisek Changed-By: Patryk Cisek Description: libnitrokey-common - architecture independent files for libnitrokey libnitrokey-dev - library to communicate with Nitrokey stick devices (development) libnitrokey3 - library to communicate with Nitrokey stick devices Closes: 1060608 Changes: libnitrokey (3.7-2) unstable; urgency=medium . * Switching Build-Depends from udev to systemd-dev (Closes: #1060608) Checksums-Sha1: c78639ca22fd5d9983d052bae6f15539594fd8a0 1741 libnitrokey_3.7-2.dsc 56dad396d202ebfecec4e0fc39753e102446afc0 4872 libnitrokey_3.7-2.debian.tar.xz d5cdfc7a38f21ca70238ba6e2202d38106cf5a61 6268 libnitrokey-common_3.7-2_all.deb 3fa1a32ab7031cf53ba79e6488c5d5b5ed97af1e 39644 libnitrokey-dev_3.7-2_amd64.deb bed2bc9d26a2a5f023318942b4a317fbf8579d7a 4295776 libnitrokey3-dbgsym_3.7-2_amd64.deb 79473d20dea8a1f2d6d50e720e954f472af300be 263292 libnitrokey3_3.7-2_amd64.deb 0174c1f8479ae4d2070a914f60048e266e7d2362 9964 libnitrokey_3.7-2_amd64.buildinfo Checksums-Sha256: ca94c2531bbb673d3b6bc9655e3cf05c909b23e8427917bd904e50bd804ba609 1741 libnitrokey_3.7-2.dsc 5caa647339a18a0a55aaeac6cf2b683b5aff30b961cf2d20ae9517f202d3a8b4 4872 libnitrokey_3.7-2.debian.tar.xz fe1187b43580c15dae0f86192f40031ab4f73c988877085f595ec47ae3bd4cec 6268 libnitrokey-common_3.7-2_all.deb 587b70f5b461c5c5e8f1bc66f25d476a092b2ffa6ef32e6befd927cd6b819aba 39644 libnitrokey-dev_3.7-2_amd64.deb 89dc8af12c96b7977cebe9b0bf981e7e8da0c495382ef6660154fee9ea8b39a8 4295776 libnitrokey3-dbgsym_3.7-2_amd64.deb
Processed: affects 1068290 + src:doris
Processing commands for cont...@bugs.debian.org: > affects 1068290 + src:doris Bug #1068290 [python3-fastkml] python3-fastkml: ImportError since python3-pygeoif 1.4.0 Added indication that 1068290 affects src:doris > thanks Stopping processing here. Please contact me if you need assistance. -- 1068290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071358: marked as done (r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments)
Your message dated Sun, 19 May 2024 15:41:56 + with message-id and subject line Bug#1071375: Removed package(s) from unstable has caused the Debian Bug report #1071358, regarding r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments 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.) -- 1071358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-cran-rgeos Version: 0.6-4-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem R dh_update_autotools_config -O--buildsystem=R dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-rgeos/ -O--buildsystem=R I: R packages needed for DEP8: maptools (>= 0.8-5), testthat, xml, maps I: R Package: rgeos Version: 0.6-4 I: Building using R version 4.4.0-2 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Mon, 28 Aug 2023 13:41:22 +0200 mkdir -p /<>/debian/r-cran-rgeos/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-cran-rgeos/usr/lib/R/site-library --clean . "--built-timestamp='Mon, 28 Aug 2023 13:41:22 +0200'" * installing *source* package ‘rgeos’ ... file ‘DESCRIPTION’ has the wrong MD5 checksum ** using staged installation configure: CC: gcc configure: CXX: g++ -std=gnu++17 configure: rgeos: 0.6-4 checking for /usr/bin/svnversion... no configure: svn revision: 699 checking for geos-config... /usr/bin/geos-config checking geos-config usability... yes configure: GEOS version: 3.12.1 checking geos version at least 3.2.0... yes checking geos-config clibs... yes checking geos_c.h presence and usability... yes checking geos: linking with libgeos_c... yes configure: PKG_CPPFLAGS: -I/usr/include configure: PKG_LIBS: -L/usr/lib/x86_64-linux-gnu -lgeos_c configure: creating ./config.status config.status: creating src/Makevars ** libs using C compiler: ‘gcc (Debian 13.2.0-25) 13.2.0’ using C++ compiler: ‘g++ (Debian 13.2.0-25) 13.2.0’ make[1]: Entering directory '/<>/src' g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -I/usr/include -I'/usr/lib/R/site-library/sp/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c dummy.cc -o dummy.o cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ gcc -I"/usr/share/R/include" -DNDEBUG -I/usr/include -I'/usr/lib/R/site-library/sp/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c init.c -o init.o gcc -I"/usr/share/R/include" -DNDEBUG -I/usr/include -I'/usr/lib/R/site-library/sp/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c local_stubs.c -o local_stubs.o gcc -I"/usr/share/R/include" -DNDEBUG -I/usr/include -I'/usr/lib/R/site-library/sp/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c rgeos.c -o rgeos.o rgeos.c: In function ‘__warningHandler’: rgeos.c:102:13: error: format not a string literal and no format arguments [-Werror=format-security] 102 | warning(buf); | ^~~ cc1: some warnings being treated as errors make[1]: *** [/usr/lib/R/etc/Makeconf:195: rgeos.o] Error 1 make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' ERROR: compilation failed for package ‘rgeos’ * remo
Bug#1071357: marked as done (r-cran-randomfieldsutils: FTBFS: Basic_utils.h:81:41: error: format not a string literal and no format arguments)
Your message dated Sun, 19 May 2024 15:44:01 + with message-id and subject line Bug#1071376: Removed package(s) from unstable has caused the Debian Bug report #1071357, regarding r-cran-randomfieldsutils: FTBFS: Basic_utils.h:81:41: error: format not a string literal and no format arguments 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.) -- 1071357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-cran-randomfieldsutils Version: 1.2.5-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem R dh_update_autotools_config -O--buildsystem=R dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-randomfieldsutils/ -O--buildsystem=R I: R Package: RandomFieldsUtils Version: 1.2.5 I: Building using R version 4.4.0-2 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Wed, 18 May 2022 13:00:18 +0200 mkdir -p /<>/debian/r-cran-randomfieldsutils/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-cran-randomfieldsutils/usr/lib/R/site-library --clean . "--built-timestamp='Wed, 18 May 2022 13:00:18 +0200'" * installing *source* package ‘RandomFieldsUtils’ ... file ‘configure’ has the wrong MD5 checksum ** using staged installation checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C++... yes checking whether g++ -std=gnu++17 accepts -g... yes checking for g++ -std=gnu++17 option to enable C++11 features... none needed configure: value of 'CROSS' is 'noflags'. checking whether __cpuid is available... no checking whether cpuid works under asm... yes configure: 'USE_GPU' has not been set. checking SIMD options for some CC files... avx2 avx checking which downwards controls might be used... . configure: default compilation option is -DLINUXCPUID -DGPU_NEEDS=Igpu -DMEMisALIGNED=Nan configure: creating ./config.status config.status: creating src/Makevars ** libs using C compiler: ‘gcc (Debian 13.2.0-25) 13.2.0’ using Fortran compiler: ‘GNU Fortran (Debian 13.2.0-25) 13.2.0’ using C++ compiler: ‘g++ (Debian 13.2.0-25) 13.2.0’ make[1]: Entering directory '/<>/src' g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -fopenmp -DLINUXCPUID -DGPU_NEEDS=Igpu-DMEMisALIGNED=Nan -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c AutoRandomFieldsUtils.cc -o AutoRandomFieldsUtils.o cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -fopenmp -DLINUXCPUID -DGPU_NEEDS=Igpu-DMEMisALIGNED=Nan -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c beskf.cc -o beskf.o cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -fopenmp -DLINUXCPUID -DGPU_NEEDS=Igpu-DMEMisALIGNED=Nan -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c brdomain.cc -o brdomain.o cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG -fopenmp -DLINUXCPUID -DGPU_NEEDS=Igpu-DMEMisALIGNED=Nan -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base
Bug#1071356: marked as done (r-cran-randomfields: FTBFS: /usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:81:41: error: format not a string literal and no format arguments)
Your message dated Sun, 19 May 2024 15:43:29 +
with message-id
and subject line Bug#1071379: Removed package(s) from unstable
has caused the Debian Bug report #1071356,
regarding r-cran-randomfields: FTBFS:
/usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:81:41: error:
format not a string literal and no format arguments
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.)
--
1071356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:r-cran-randomfields
Version: 3.3.14-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --buildsystem R
dh_update_autotools_config -O--buildsystem=R
dh_autoreconf -O--buildsystem=R
dh_auto_configure -O--buildsystem=R
dh_auto_build -O--buildsystem=R
dh_auto_test -O--buildsystem=R
create-stamp debian/debhelper-build-stamp
dh_testroot -O--buildsystem=R
dh_prep -O--buildsystem=R
dh_auto_install --destdir=debian/r-cran-randomfields/ -O--buildsystem=R
I: R Package: RandomFields Version: 3.3.14
I: Building using R version 4.4.0-2
I: R API version: r-api-4.0
I: Using built-time from d/changelog: Sat, 12 Feb 2022 23:40:29 +0100
mkdir -p
/<>/debian/r-cran-randomfields/usr/lib/R/site-library
xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render
-noreset" R CMD INSTALL -l /<>/debian/r-cran-randomfields/usr/lib/R/site-library
--clean . "--built-timestamp='Sat, 12 Feb 2022 23:40:29 +0100'"
* installing *source* package ‘RandomFields’ ...
file ‘configure’ has the wrong MD5 checksum
** using staged installation
configure: creating ./config.status
config.status: creating src/Makevars
** libs
using C compiler: ‘gcc (Debian 13.2.0-25) 13.2.0’
using C++ compiler: ‘g++ (Debian 13.2.0-25) 13.2.0’
make[1]: Entering directory '/<>/src'
g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG
-I'/usr/lib/R/site-library/RandomFieldsUtils/include'-fopenmp -fpic -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c AutoRandomFields.cc -o AutoRandomFields.o
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’
is not valid for C++
g++ -std=gnu++17 -I"/usr/share/R/include" -DNDEBUG
-I'/usr/lib/R/site-library/RandomFieldsUtils/include'-fopenmp -fpic -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time
-D_FORTIFY_SOURCE=2 -c Brown.cc -o Brown.o
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’
is not valid for C++
In file included from Brown.cc:31:
Brown.cc: In function ‘int checkBrownResnickProc(model*)’:
/usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:81:41: error:
format not a string literal and no format arguments [-Werror=format-security]
81 | SPRINTF(E_AUX, M, A,B,C,D); RFERROR(E_AUX);}
| ^
/usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:227:5: note: in
expansion of macro ‘RFERROR4’
227 | RFERROR4("Severe error occured in function '%.50s' (file '%.50s', line
%d).%.200s", \
| ^~~~
Machine.h:287:74: note: in expansion of macro ‘BUG’
287 |/* || !equalsIsotropic(OWNISO(1)) */
)) BUG;}
|
^~~
Brown.cc:135:3: note: in expansion of macro ‘ASSERT_ONESYSTEM’
135 | ASSERT_ONESYSTEM;
| ^~~~
Brown.cc: In function ‘int init_BRorig(model*, gen_storage*)’:
/usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:81:41: error:
format not a string literal and no format arguments [-Werror=format-security]
81 | SPRINTF(E_AUX, M, A,B,C,D); RFERROR(E_AUX);}
| ^
/usr/lib/R/site-library/RandomFieldsUtils/include/Basic_utils.h:227:5: note: in
expansion of macro ‘RFERROR4’
227 | RFERROR4("Severe error occured in function '%.50s' (file
Bug#1071244: marked as done (dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install)
Your message dated Sun, 19 May 2024 15:36:08 + with message-id and subject line Bug#1071244: fixed in dracut 060+5-8 has caused the Debian Bug report #1071244, regarding dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install 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.) -- 1071244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut-install Version: 060+5-7 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + dracut-core dracut-install has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/dracut/dracut-install is contained in the packages * dracut-core/060+5-1 as present in trixie * dracut-install/060+5-7 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: dracut Source-Version: 060+5-8 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Sun, 19 May 2024 16:45:33 +0200 Source: dracut Architecture: source Version: 060+5-8 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1071182 1071208 1071244 Changes: dracut (060+5-8) unstable; urgency=low . * control: adjust breaks, replaces, Closes: #1071208, #1071244 * add patch taken from dracut-ng, Closes: #1071182 Checksums-Sha1: f77ba4330e2affebd64fa23b401e2ffc683b97dd 2688 dracut_060+5-8.dsc d5992a4d7a453606f6d50d8d91a58ddd5cf5cd85 19036 dracut_060+5-8.debian.tar.xz 1c54a8f82098a068a1c84b177837af0d32cfee02 9852 dracut_060+5-8_amd64.buildinfo Checksums-Sha256: 418048ed9bc669bbc941a48afd48f70ea6ad9f3124d78c97a8d5235e0f221747 2688 dracut_060+5-8.dsc d4f37a9d50e725fadd6f628de4ba4f60be9f0e9b3ef6a86f2f6ea4ce3d35fc23 19036 dracut_060+5-8.debian.tar.xz eb8b5d85cdbe52d4060119978a4564fc8f54d917cbaf114f097993fb1e7921b3 9852 dracut_060+5-8_amd64.buildinfo Files: 3e527f81aa1413b9fb8b30cca5e9594b 2688 utils optional dracut_060+5-8.dsc 5e4064035c3e4c90226b9d3f3981def0 19036 utils optional dracut_060+5-8.debian.tar.xz 6aa76c29b26e41b5d6a4730eef0d8a0b 9852 utils optional dracut_060+5-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZKEQMRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQgdhAAny+c3i4WoFNCDFGRblkRY72qQIh99oDs YfRK2luqsdGFefYwz0UghLdJUpU7GPtX4ZqCQS8GndSiWfv8B2P6HQ9R+16Lfzyl 2s8OfV06WpS+WDJhL/44eVJ7GKGA8crRU2plKr9qXdEl45VEG3G74mC39AkXzBiM Iq4yCrWU3z86wjVIKAn3dG5kZL/Qxs0nxVEBp7jyQ8TdFJX431iAeKsEj6wIsdOM eyZcQbqyTJzm9vURRXTHGF2oMMxHQuSErGqw3KLNszYwfRWrANTalO3iG+EXM3xC R3CcElFOC6YTKG+KWv24JJEU4l414/9WHZQqmPxSWDws57zsy6pwme+vb6eQ2RKX AxdlDBeiQ3AfK+RvOHH0IAeSyZBzX+SPVmHpmxm1tEzgGCwinA/o8CcCFABMYRdV rY2+PYG78L+YrvGPwKq+uRmw2eQo0ZMwxWU/XszR4RGk6aXcZwWlabuRNHre1539 LsWlUiVCNKsunvOQ/7I1mZzIevgemcS21QCrhhSJlE6yX4X6Tkr1+3XHNa5MCkrk SusxxWo0pulD7X1WFQGAG0l+xIStUvdpMxutEXoh/3/ZYLxGTooaHmWP76jR7mvW EvjqxlnMahYKQ58y+ZBsbDquhgq1vSISxHeXxIwG23yI1svFdfb4h3JbIQCujdi1 mRnY+PLZE4k= =9H8z -END PGP SIGNATURE- pgp7Np5Nk_rqQ.pgp Description: PGP signature --- End Message ---
Bug#1071208: marked as done (Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1)
Your message dated Sun, 19 May 2024 15:36:08 + with message-id and subject line Bug#1071208: fixed in dracut 060+5-8 has caused the Debian Bug report #1071208, regarding Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1 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.) -- 1071208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut-install Version: 060+5-7 Severity: serious Looks like dracut-install needs Replaces/Breaks versions adjusted, as dracut- core 060+5-1 (the previous unstable version) is also affected. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dracut-install depends on: ii libc6 2.38-11 ii libkmod2 32-1 dracut-install recommends no packages. dracut-install suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: dracut Source-Version: 060+5-8 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Sun, 19 May 2024 16:45:33 +0200 Source: dracut Architecture: source Version: 060+5-8 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1071182 1071208 1071244 Changes: dracut (060+5-8) unstable; urgency=low . * control: adjust breaks, replaces, Closes: #1071208, #1071244 * add patch taken from dracut-ng, Closes: #1071182 Checksums-Sha1: f77ba4330e2affebd64fa23b401e2ffc683b97dd 2688 dracut_060+5-8.dsc d5992a4d7a453606f6d50d8d91a58ddd5cf5cd85 19036 dracut_060+5-8.debian.tar.xz 1c54a8f82098a068a1c84b177837af0d32cfee02 9852 dracut_060+5-8_amd64.buildinfo Checksums-Sha256: 418048ed9bc669bbc941a48afd48f70ea6ad9f3124d78c97a8d5235e0f221747 2688 dracut_060+5-8.dsc d4f37a9d50e725fadd6f628de4ba4f60be9f0e9b3ef6a86f2f6ea4ce3d35fc23 19036 dracut_060+5-8.debian.tar.xz eb8b5d85cdbe52d4060119978a4564fc8f54d917cbaf114f097993fb1e7921b3 9852 dracut_060+5-8_amd64.buildinfo Files: 3e527f81aa1413b9fb8b30cca5e9594b 2688 utils optional dracut_060+5-8.dsc 5e4064035c3e4c90226b9d3f3981def0 19036 utils optional dracut_060+5-8.debian.tar.xz 6aa76c29b26e41b5d6a4730eef0d8a0b 9852 utils optional dracut_060+5-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZKEQMRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQgdhAAny+c3i4WoFNCDFGRblkRY72qQIh99oDs YfRK2luqsdGFefYwz0UghLdJUpU7GPtX4ZqCQS8GndSiWfv8B2P6HQ9R+16Lfzyl 2s8OfV06WpS+WDJhL/44eVJ7GKGA8crRU2plKr9qXdEl45VEG3G74mC39AkXzBiM Iq4yCrWU3z86wjVIKAn3dG5kZL/Qxs0nxVEBp7jyQ8TdFJX431iAeKsEj6wIsdOM eyZcQbqyTJzm9vURRXTHGF2oMMxHQuSErGqw3KLNszYwfRWrANTalO3iG+EXM3xC R3CcElFOC6YTKG+KWv24JJEU4l414/9WHZQqmPxSWDws57zsy6pwme+vb6eQ2RKX AxdlDBeiQ3AfK+RvOHH0IAeSyZBzX+SPVmHpmxm1tEzgGCwinA/o8CcCFABMYRdV rY2+PYG78L+YrvGPwKq+uRmw2eQo0ZMwxWU/XszR4RGk6aXcZwWlabuRNHre1539 LsWlUiVCNKsunvOQ/7I1mZzIevgemcS21QCrhhSJlE6yX4X6Tkr1+3XHNa5MCkrk SusxxWo0pulD7X1WFQGAG0l+xIStUvdpMxutEXoh/3/ZYLxGTooaHmWP76jR7mvW EvjqxlnMahYKQ58y+ZBsbDquhgq1vSISxHeXxIwG23yI1svFdfb4h3JbIQCujdi1 mRnY+PLZE4k= =9H8z -END PGP SIGNATURE- pgpHzbH24Hqt4.pgp Description: PGP signature --- End Message ---
Bug#1071208: marked as done (Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1)
Your message dated Sun, 19 May 2024 15:36:08 + with message-id and subject line Bug#1071244: fixed in dracut 060+5-8 has caused the Debian Bug report #1071244, regarding Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1 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.) -- 1071244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut-install Version: 060+5-7 Severity: serious Looks like dracut-install needs Replaces/Breaks versions adjusted, as dracut- core 060+5-1 (the previous unstable version) is also affected. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dracut-install depends on: ii libc6 2.38-11 ii libkmod2 32-1 dracut-install recommends no packages. dracut-install suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: dracut Source-Version: 060+5-8 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Sun, 19 May 2024 16:45:33 +0200 Source: dracut Architecture: source Version: 060+5-8 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1071182 1071208 1071244 Changes: dracut (060+5-8) unstable; urgency=low . * control: adjust breaks, replaces, Closes: #1071208, #1071244 * add patch taken from dracut-ng, Closes: #1071182 Checksums-Sha1: f77ba4330e2affebd64fa23b401e2ffc683b97dd 2688 dracut_060+5-8.dsc d5992a4d7a453606f6d50d8d91a58ddd5cf5cd85 19036 dracut_060+5-8.debian.tar.xz 1c54a8f82098a068a1c84b177837af0d32cfee02 9852 dracut_060+5-8_amd64.buildinfo Checksums-Sha256: 418048ed9bc669bbc941a48afd48f70ea6ad9f3124d78c97a8d5235e0f221747 2688 dracut_060+5-8.dsc d4f37a9d50e725fadd6f628de4ba4f60be9f0e9b3ef6a86f2f6ea4ce3d35fc23 19036 dracut_060+5-8.debian.tar.xz eb8b5d85cdbe52d4060119978a4564fc8f54d917cbaf114f097993fb1e7921b3 9852 dracut_060+5-8_amd64.buildinfo Files: 3e527f81aa1413b9fb8b30cca5e9594b 2688 utils optional dracut_060+5-8.dsc 5e4064035c3e4c90226b9d3f3981def0 19036 utils optional dracut_060+5-8.debian.tar.xz 6aa76c29b26e41b5d6a4730eef0d8a0b 9852 utils optional dracut_060+5-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZKEQMRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQgdhAAny+c3i4WoFNCDFGRblkRY72qQIh99oDs YfRK2luqsdGFefYwz0UghLdJUpU7GPtX4ZqCQS8GndSiWfv8B2P6HQ9R+16Lfzyl 2s8OfV06WpS+WDJhL/44eVJ7GKGA8crRU2plKr9qXdEl45VEG3G74mC39AkXzBiM Iq4yCrWU3z86wjVIKAn3dG5kZL/Qxs0nxVEBp7jyQ8TdFJX431iAeKsEj6wIsdOM eyZcQbqyTJzm9vURRXTHGF2oMMxHQuSErGqw3KLNszYwfRWrANTalO3iG+EXM3xC R3CcElFOC6YTKG+KWv24JJEU4l414/9WHZQqmPxSWDws57zsy6pwme+vb6eQ2RKX AxdlDBeiQ3AfK+RvOHH0IAeSyZBzX+SPVmHpmxm1tEzgGCwinA/o8CcCFABMYRdV rY2+PYG78L+YrvGPwKq+uRmw2eQo0ZMwxWU/XszR4RGk6aXcZwWlabuRNHre1539 LsWlUiVCNKsunvOQ/7I1mZzIevgemcS21QCrhhSJlE6yX4X6Tkr1+3XHNa5MCkrk SusxxWo0pulD7X1WFQGAG0l+xIStUvdpMxutEXoh/3/ZYLxGTooaHmWP76jR7mvW EvjqxlnMahYKQ58y+ZBsbDquhgq1vSISxHeXxIwG23yI1svFdfb4h3JbIQCujdi1 mRnY+PLZE4k= =9H8z -END PGP SIGNATURE- pgpFW0o9HBq3K.pgp Description: PGP signature --- End Message ---
Bug#1071244: marked as done (dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install)
Your message dated Sun, 19 May 2024 15:36:08 + with message-id and subject line Bug#1071208: fixed in dracut 060+5-8 has caused the Debian Bug report #1071208, regarding dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install 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.) -- 1071208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dracut-install Version: 060+5-7 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + dracut-core dracut-install has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/dracut/dracut-install is contained in the packages * dracut-core/060+5-1 as present in trixie * dracut-install/060+5-7 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: dracut Source-Version: 060+5-8 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Sun, 19 May 2024 16:45:33 +0200 Source: dracut Architecture: source Version: 060+5-8 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1071182 1071208 1071244 Changes: dracut (060+5-8) unstable; urgency=low . * control: adjust breaks, replaces, Closes: #1071208, #1071244 * add patch taken from dracut-ng, Closes: #1071182 Checksums-Sha1: f77ba4330e2affebd64fa23b401e2ffc683b97dd 2688 dracut_060+5-8.dsc d5992a4d7a453606f6d50d8d91a58ddd5cf5cd85 19036 dracut_060+5-8.debian.tar.xz 1c54a8f82098a068a1c84b177837af0d32cfee02 9852 dracut_060+5-8_amd64.buildinfo Checksums-Sha256: 418048ed9bc669bbc941a48afd48f70ea6ad9f3124d78c97a8d5235e0f221747 2688 dracut_060+5-8.dsc d4f37a9d50e725fadd6f628de4ba4f60be9f0e9b3ef6a86f2f6ea4ce3d35fc23 19036 dracut_060+5-8.debian.tar.xz eb8b5d85cdbe52d4060119978a4564fc8f54d917cbaf114f097993fb1e7921b3 9852 dracut_060+5-8_amd64.buildinfo Files: 3e527f81aa1413b9fb8b30cca5e9594b 2688 utils optional dracut_060+5-8.dsc 5e4064035c3e4c90226b9d3f3981def0 19036 utils optional dracut_060+5-8.debian.tar.xz 6aa76c29b26e41b5d6a4730eef0d8a0b 9852 utils optional dracut_060+5-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZKEQMRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQgdhAAny+c3i4WoFNCDFGRblkRY72qQIh99oDs YfRK2luqsdGFefYwz0UghLdJUpU7GPtX4ZqCQS8GndSiWfv8B2P6HQ9R+16Lfzyl 2s8OfV06WpS+WDJhL/44eVJ7GKGA8crRU2plKr9qXdEl45VEG3G74mC39AkXzBiM Iq4yCrWU3z86wjVIKAn3dG5kZL/Qxs0nxVEBp7jyQ8TdFJX431iAeKsEj6wIsdOM eyZcQbqyTJzm9vURRXTHGF2oMMxHQuSErGqw3KLNszYwfRWrANTalO3iG+EXM3xC R3CcElFOC6YTKG+KWv24JJEU4l414/9WHZQqmPxSWDws57zsy6pwme+vb6eQ2RKX AxdlDBeiQ3AfK+RvOHH0IAeSyZBzX+SPVmHpmxm1tEzgGCwinA/o8CcCFABMYRdV rY2+PYG78L+YrvGPwKq+uRmw2eQo0ZMwxWU/XszR4RGk6aXcZwWlabuRNHre1539 LsWlUiVCNKsunvOQ/7I1mZzIevgemcS21QCrhhSJlE6yX4X6Tkr1+3XHNa5MCkrk SusxxWo0pulD7X1WFQGAG0l+xIStUvdpMxutEXoh/3/ZYLxGTooaHmWP76jR7mvW EvjqxlnMahYKQ58y+ZBsbDquhgq1vSISxHeXxIwG23yI1svFdfb4h3JbIQCujdi1 mRnY+PLZE4k= =9H8z -END PGP SIGNATURE- pgpj3ahE9Snz9.pgp Description: PGP signature --- End Message ---
Bug#1071182: marked as done (dracut: requires changes for systemd 256; boot fails otherwise)
Your message dated Sun, 19 May 2024 15:36:08 + with message-id and subject line Bug#1071182: fixed in dracut 060+5-8 has caused the Debian Bug report #1071182, regarding dracut: requires changes for systemd 256; boot fails otherwise 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.) -- 1071182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dracut Version: 060+5-1 Severity: serious Tags: upstream X-Debbugs-Cc: Debian systemd Maintainers Hi, dracut requires two changes for systemd 256: 1. systemd 256 makes /usr read-only in initrd: - https://github.com/systemd/systemd/issues/32511 - https://github.com/dracut-ng/dracut-ng/issues/253 2. libkmod.so.2 might need to be installed manually: - https://github.com/systemd/systemd/issues/32508#issuecomment-2080063182 systemd should get a `Breaks: dracut (<< fixed-version-goes-here)` once a fixed version is uploaded. Ansgar -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (300, 'buildd-unstable'), (300, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: dracut Source-Version: 060+5-8 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Sun, 19 May 2024 16:45:33 +0200 Source: dracut Architecture: source Version: 060+5-8 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 1071182 1071208 1071244 Changes: dracut (060+5-8) unstable; urgency=low . * control: adjust breaks, replaces, Closes: #1071208, #1071244 * add patch taken from dracut-ng, Closes: #1071182 Checksums-Sha1: f77ba4330e2affebd64fa23b401e2ffc683b97dd 2688 dracut_060+5-8.dsc d5992a4d7a453606f6d50d8d91a58ddd5cf5cd85 19036 dracut_060+5-8.debian.tar.xz 1c54a8f82098a068a1c84b177837af0d32cfee02 9852 dracut_060+5-8_amd64.buildinfo Checksums-Sha256: 418048ed9bc669bbc941a48afd48f70ea6ad9f3124d78c97a8d5235e0f221747 2688 dracut_060+5-8.dsc d4f37a9d50e725fadd6f628de4ba4f60be9f0e9b3ef6a86f2f6ea4ce3d35fc23 19036 dracut_060+5-8.debian.tar.xz eb8b5d85cdbe52d4060119978a4564fc8f54d917cbaf114f097993fb1e7921b3 9852 dracut_060+5-8_amd64.buildinfo Files: 3e527f81aa1413b9fb8b30cca5e9594b 2688 utils optional dracut_060+5-8.dsc 5e4064035c3e4c90226b9d3f3981def0 19036 utils optional dracut_060+5-8.debian.tar.xz 6aa76c29b26e41b5d6a4730eef0d8a0b 9852 utils optional dracut_060+5-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZKEQMRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQgdhAAny+c3i4WoFNCDFGRblkRY72qQIh99oDs YfRK2luqsdGFefYwz0UghLdJUpU7GPtX4ZqCQS8GndSiWfv8B2P6HQ9R+16Lfzyl 2s8OfV06WpS+WDJhL/44eVJ7GKGA8crRU2plKr9qXdEl45VEG3G74mC39AkXzBiM Iq4yCrWU3z86wjVIKAn3dG5kZL/Qxs0nxVEBp7jyQ8TdFJX431iAeKsEj6wIsdOM eyZcQbqyTJzm9vURRXTHGF2oMMxHQuSErGqw3KLNszYwfRWrANTalO3iG+EXM3xC R3CcElFOC6YTKG+KWv24JJEU4l414/9WHZQqmPxSWDws57zsy6pwme+vb6eQ2RKX AxdlDBeiQ3AfK+RvOHH0IAeSyZBzX+SPVmHpmxm1tEzgGCwinA/o8CcCFABMYRdV rY2+PYG78L+YrvGPwKq+uRmw2eQo0ZMwxWU/XszR4RGk6aXcZwWlabuRNHre1539 LsWlUiVCNKsunvOQ/7I1mZzIevgemcS21QCrhhSJlE6yX4X6Tkr1+3XHNa5MCkrk SusxxWo0pulD7X1WFQGAG0l+xIStUvdpMxutEXoh/3/ZYLxGTooaHmWP76jR7mvW EvjqxlnMahYKQ58y+ZBsbDquhgq1vSISxHeXxIwG23yI1svFdfb4h3JbIQCujdi1 mRnY+PLZE4k= =9H8z -END PGP SIGNATURE- pgpe4sRdkBoUp.pgp Description: PGP signature --- End Message ---
Bug#1068349: marked as done (nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean)
Your message dated Sun, 19 May 2024 16:25:01 +0100 with message-id <7965f37c-8f2f-4b09-9b09-90b4c80e4...@zoho.com> and subject line Re: Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean has caused the Debian Bug report #1068349, regarding nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean 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.) -- 1068349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-nbconvert,python3-lxml Version: 6.5.3-4,5.2.0-1 Control: affects -1 src:pandas Control: affects -1 python3-nbsphinx Control: block 1068104 by -1 The pandas documentation fails to build in current unstable with: Running Sphinx v7.2.6 nbconvert not installed. Skipping notebooks. Extension error: Could not import extension nbsphinx (exception: lxml.html.clean module is now a separate project lxml_html_clean. Install lxml[html_clean] or lxml_html_clean directly.) Full log: https://salsa.debian.org/science-team/pandas/-/jobs/5538806 This probably makes nbconvert and nbsphinx fail to import at all, and started when lxml was upgraded to 5.2, but I haven't actually tested either of those: https://sources.debian.org/src/nbconvert/6.5.3-4/nbconvert/exporters/templateexporter.py/?hl=25#L25 https://sources.debian.org/src/lxml/5.2.0-1/PKG-INFO/?hl=83#L83 The obvious fix would be to package lxml_html_clean. --- End Message --- --- Begin Message --- Filing a bug against two packages means that it could be fixed in *either* of them, *not* that it requires changes to both of them. Hence, it is correct that this bug was closed. From codesearch, other packages that may need such a Depends are html-text, extruct, python-html-sanitizer, napari, readability, calibre, python-webob. extruct, calibre and readability have now added that dependency, and python-webob doesn't actually use it (only mentions it in documentation). I have filed separate bugs for napari, html-text and python-html-sanitizer.--- End Message ---
Processed: severity of 1062110 is normal
Processing commands for cont...@bugs.debian.org: > severity 1062110 normal Bug #1062110 [android-libboringssl] android-libboringssl: identified for time_t transition but no ABI in shlibs Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071420: linux-image-6.8.9-1-amd64: cannot mount btrfs root partition
Processing control commands: > reassign -1 src:linux Bug #1071420 [src:systemd] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Bug reassigned from package 'src:systemd' to 'src:linux'. Ignoring request to alter found versions of bug #1071420 to the same values previously set Ignoring request to alter fixed versions of bug #1071420 to the same values previously set > severity -1 grave Bug #1071420 [src:linux] linux-image-6.8.9-1-amd64: cannot mount btrfs root partition Severity set to 'grave' from 'important' -- 1071420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1060499 is serious
Processing commands for cont...@bugs.debian.org:
> severity 1060499 serious
Bug #1060499 {Done: Marco Trevisan (Treviño) }
[src:gnome-remote-desktop] gnome-remote-desktop: Please switch Build-Depends to
systemd-dev
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071310: marked as done (gitsome: FTBFS: ModuleNotFoundError: No module named 'pytz')
Your message dated Sun, 19 May 2024 14:42:48 + with message-id and subject line Bug#1071310: fixed in gitsome 0.8.0+ds-9 has caused the Debian Bug report #1071310, regarding gitsome: FTBFS: ModuleNotFoundError: No module named 'pytz' 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.) -- 1071310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gitsome Version: 0.8.0+ds-8 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: 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. running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /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. running build running build_py creating /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/test_completer.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/run_tests.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/test_web_viewer.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/test_config.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/compat.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/test_github.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/test_github_cli.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/mock_github_api.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/mock_pretty_date_time.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/__init__.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests copying tests/mock_feed_parser.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/tests creating /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/table.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/formatter.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/web_viewer.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/main.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/github.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/completer.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/completions.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/githubcli.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/utils.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/config.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/compat.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/completions_git.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/view_entry.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitsome/main_cli.py -> /<>/.pybuild/cpython3_3.11_gitsome/build/gitsome copying gitso
Bug#1071133: marked as done (firebird4.0: binary-all FTBFS)
Your message dated Sun, 19 May 2024 13:04:48 + with message-id and subject line Bug#1071133: fixed in firebird4.0 4.0.4.3010.ds6-3 has caused the Debian Bug report #1071133, regarding firebird4.0: binary-all FTBFS 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.) -- 1071133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: firebird4.0 Version: 4.0.4.3010.ds6-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=firebird4.0=all ... dh_lintian sed -i -e "s/TRIPLET/x86_64-linux-gnu/g" \ debian/libib-util/usr/share/lintian/overrides/libib-util sed: can't read debian/libib-util/usr/share/lintian/overrides/libib-util: No such file or directory make[1]: *** [debian/rules:185: override_dh_lintian] Error 2 --- End Message --- --- Begin Message --- Source: firebird4.0 Source-Version: 4.0.4.3010.ds6-3 Done: Damyan Ivanov We believe that the bug you reported is fixed in the latest version of firebird4.0, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov (supplier of updated firebird4.0 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: Sun, 19 May 2024 12:25:16 + Source: firebird4.0 Architecture: source Version: 4.0.4.3010.ds6-3 Distribution: experimental Urgency: medium Maintainer: Damyan Ivanov Changed-By: Damyan Ivanov Closes: 1071133 Changes: firebird4.0 (4.0.4.3010.ds6-3) experimental; urgency=medium . * replace build-dependency on pkg-config with pkgconf * fix arch=all build Closes: #1071133 Checksums-Sha1: 30b5d5994f2cd93af57e99533048a8025588c68b 2840 firebird4.0_4.0.4.3010.ds6-3.dsc d8a505efeb5f21c4ca5d80d7672752e41fe17a45 96460 firebird4.0_4.0.4.3010.ds6-3.debian.tar.xz Checksums-Sha256: ae4512cb04c1ececa8349c99fce1e19cc02b46a720de61dd082d512908086ca6 2840 firebird4.0_4.0.4.3010.ds6-3.dsc 1a6590cdc5f1a2c0a1317ac24714cda76baf634c1ff1d7d1da09e05e8ba2759d 96460 firebird4.0_4.0.4.3010.ds6-3.debian.tar.xz Files: b082b83ea7b16e95fdedebf1e9795866 2840 database optional firebird4.0_4.0.4.3010.ds6-3.dsc de1f465d1bad26fab8240513245b01e2 96460 database optional firebird4.0_4.0.4.3010.ds6-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmZJ9YoACgkQ276dTZnS oAQGXQ/+M4HW8LLoLZ5s1SZaR5tA51HOHK9Yerkgymoq3Cdne5tFswHZTscjbOVh ur52+77X5Y4feQCwc9HZyq5bobgfDbUYFdXdVqduchqdlFYfufX5bmFeGHgS59Gx ay/fmB4wJxTGofDdOoe5NKDDk5m3J5EsSxwS+Zf1ZtRHao/5m3wDVWngshj2eWky IUa2H2pQRUvfvUl06Nnxpp44M5b3r2Di3B04VfSFBt3zaoud7QjAX6aAHUfGXUfq HIMyOqS1JoIJUoaDLJz6QSkVmqKZrhF9Av6s9sikltOr1H6DkDsBoRaQ/VXEhRQb 0xC9CWVYsAhlyLGZXz5RbCkDAR/fZpZhpwHXji2gCnDHoQZHVmyPyMBpmdyDe1be cArfnTM1D1R29DLfiDRdOlE8yhZu93qI4wK28qt1RnUXAqpAeKGZ1ng7fbwFRoC9 zOX70vfpLUgPbJnsr3piSXlq9oApB1Zh/7gpXT4/2rUKxW0gxFyxoy1z8I0UTtt1 Ok/6HmtyKMkz4me29WMhA7Cf7RZm66EC54cmXOA4f/bQs+Sioh5GH4bO1sleuJ8B 3c0knWbrH7SSyCAkvRyoi9Flk45rsZXjeDy1uP2NisOh24aykTCh/eBxv2Yiovof jiJ/P0EYeqOk0YunBirDxM8ZB57uCVXENvi1rROtqdsdc/IlOcE= =J+Pn -END PGP SIGNATURE- pgpscmLKuZdmf.pgp Description: PGP signature --- End Message ---
Processed: Re: Bug#1038937: nq package out of date with upstream, 0.5 was released more than a year ago
Processing control commands: > block -1 by 1005961 Bug #1038937 [nq] nq package out of date with upstream, 0.5 was released more than a year ago 1038937 was not blocked by any bugs. 1038937 was not blocking any bugs. Added blocking bug(s) of 1038937: 1005961 -- 1038937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071225: marked as done (python-ase: FTBFS because of deprecated pytest.warns(None) usage)
Your message dated Sun, 19 May 2024 11:19:36 + with message-id and subject line Bug#1071225: fixed in python-ase 3.22.1-5 has caused the Debian Bug report #1071225, regarding python-ase: FTBFS because of deprecated pytest.warns(None) usage 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.) -- 1071225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-ase Version: 3.22.1-4 Severity: serious Tags: patch ftbfs User: debian-pyt...@lists.debian.org Usertags: pytest-8 User: debian-rele...@lists.debian.org Usertags: bsp-2024-05-mdc-ber -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, the python-ase fails to build with pytest 8+ because the deprecated pytest.warns(None) idiom has been removed. See the attached patch for an easy fix. Cheers Timo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmZGHy8ACgkQzIxr3RQD 9Mqm6xAArJlt0P2e5z/kvuQSkXiQpQSQ+pcAva6pC7q/T4RywOqBD18Ds6RzGL+V xhXb4hOjHtNYgfuM3UKeUQPUsw+sYrLTnMYvXpzlnW96UKdBpSlhmspKZa3ks81h cfLTXquZrux6cw0Fjq6FUvqZ1y+FOg+2skge5BADE3LWvjerSsqSxcf4f55x1sV+ 6tnCP43z8DNh2ZpwC+ioLoLy5hFeF0imdSBXoI1AXHvilYj0//xiB+HwB18V7tME zM3OXu4OV+M7sHqAYE3Z1YpVicXt/Hb81+W9BINLowVPrW/CJYO37M8lFtUM8dCe l4uXdHPWR0FiXTIwH3SNu79oW5Tsjw9+zQvYBBdRhrk0KD5bvmofk8CKsHNyqAia W85EECZpSo5fhxPIvxJxMQtJvHChRvXPag19jBYfc4GBfFHEy1782AsQxx/6WzK5 XEBQquHUXCRireZ2LKh4RGyZswa5drsfxEItLP2JGBcXQrKKC3qkSbmmtYbj4Qpx UKmdSDEaswk+2GBe1WUzMnskYti+WzsTBHIxsO94CkIQv4/WKJcp3dnIQMEGcrIs pYZN5jSlSkPldhsqnw9pOCiaCkDs1WAwc0LPB4R5Z21CSecGsU++zlHX1YgJqz0j IFBxyaela++n53Qh9szB/bQxmArK4yxV6bL+yDozfOpJYE+inLg= =4UTB -END PGP SIGNATURE- From: =?utf-8?q?Timo_R=C3=B6hling?= Date: Thu, 16 May 2024 16:43:29 +0200 Subject: Fix deprecated pytest.warns(None) --- ase/test/fio/test_netcdftrajectory.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ase/test/fio/test_netcdftrajectory.py b/ase/test/fio/test_netcdftrajectory.py index c51f385..9ecaa6e 100644 --- a/ase/test/fio/test_netcdftrajectory.py +++ b/ase/test/fio/test_netcdftrajectory.py @@ -100,7 +100,7 @@ def test_netcdftrajectory(co): # File is not created before first write co.set_pbc([True, False, False]) d = co.get_distance(0, 1) -with pytest.warns(None): +with pytest.warns(): t.write(co) del t # Check pbc --- End Message --- --- Begin Message --- Source: python-ase Source-Version: 3.22.1-5 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of python-ase, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated python-ase 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: Sun, 19 May 2024 11:01:13 + Source: python-ase Built-For-Profiles: noudeb Architecture: source Version: 3.22.1-5 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Graham Inggs Closes: 1071225 Changes: python-ase (3.22.1-5) unstable; urgency=medium . [ Timo Röhling ] * Avoid FTBFS with pytest 8+ (Closes: #1071225) Checksums-Sha1: 7e50ed8e5daa1fc8b3f4187a53d5660b3e49b381 2586 python-ase_3.22.1-5.dsc 416ed58a0179eada0ebf0397538056d90f62f339 15568 python-ase_3.22.1-5.debian.tar.xz Checksums-Sha256: 0052ee314684a547419ca67721a66316bde564d28d605a9ab856f50b85e500eb 2586 python-ase_3.22.1-5.dsc 2fd4927f5b95e4ee7faada5b8f7db67c3f48e611d67dfe1534086de89f311ad0 15568 python-ase_3.22.1-5.debian.tar.xz Files: 0fa3b28488d225b790757814222ab262 2586 science optional python-ase_3.22.1-5.dsc c3b90ceb701141f1dc97bc495e9f10d0 15568 science optional python-ase_3.22.1-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmZJ3U8ACgkQr8/sjmac 4cJUIA/+I+Ydy8rL9wV6T4AK7yQ6nbrbok4UFSMxjpk/khJWRbXJRn8dwyY/NK0A SoW3tw3Q/XzQsInU9KNCblsw33nbkBz4wF1Pp919K9gGj8mcU4i9PjAqzKJHXufF 5NWtCvRoSW3crTHMtg6gUX9hzXDBCx9DweX7bXQ/14aqVnXweVm3y0ChwJ27h3x7 lfunc/b5m6s05TP60rIo2xACtheb5klqxyNt+6hR7CenPiwn/duuI8NjCbtIiXF9 kh+ZqXHdIKsD87
Processed: Re: Bug#1069943: bullseye-pu: package emacs/27.1+1-3.1+deb11u3
Processing control commands: > tag -1 - moreinfo Bug #1031888 [src:emacs] emacs-nox: bullseye-security update fails to install on mips64el Ignoring request to alter tags of bug #1031888 to the same tags previously set -- 1031888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071325: marked as done (libmodbus: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)
Your message dated Sun, 19 May 2024 10:05:10 +
with message-id
and subject line Bug#1071325: fixed in libmodbus 3.1.10-2
has caused the Debian Bug report #1071325,
regarding libmodbus: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file
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.)
--
1071325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmodbus
Version: 3.1.10-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with autoreconf --exclude=.la
dh_update_autotools_config -O--exclude=.la
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
dh_autoreconf -O--exclude=.la
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:33: installing 'build-aux/compile'
configure.ac:32: installing 'build-aux/missing'
src/Makefile.am: installing 'build-aux/depcomp'
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --disable-silent-rules
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format...
func_convert_file_noop
checking fo
Processed: block tea-cli with go-git bug
Processing commands for cont...@bugs.debian.org: > block 1071398 by 1060701 Bug #1071398 [src:tea-cli] src:tea-cli: unsatisfied build dependency in testing: golang-github-go-git-go-git-dev 1071398 was not blocked by any bugs. 1071398 was not blocking any bugs. Added blocking bug(s) of 1071398: 1060701 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1071208
Processing commands for cont...@bugs.debian.org: > affects 1071208 dracut-core Bug #1071208 [dracut-install] Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1 Bug #1071244 [dracut-install] dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install Added indication that 1071208 affects dracut-core Added indication that 1071244 affects dracut-core > thanks Stopping processing here. Please contact me if you need assistance. -- 1071208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071208 1071244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1071208 1071244
Processing commands for cont...@bugs.debian.org: > forcemerge 1071208 1071244 Bug #1071208 [dracut-install] Tries to overwrite /usr/lib/dracut/dracut-install from dracut-core 060+5-1 Bug #1071244 [dracut-install] dracut-install has an undeclared file conflict on /usr/lib/dracut/dracut-install Removed indication that 1071244 affects dracut-core Merged 1071208 1071244 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071208 1071244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071313: marked as done (guestfs-tools: FTBFS: guestfsd: error: minix: /dev/sda1: mkfs: failed to execute mkfs.minix: No such file or directory)
Your message dated Sun, 19 May 2024 01:19:38 + with message-id and subject line Bug#1071313: fixed in libguestfs 1:1.52.0-6 has caused the Debian Bug report #1071313, regarding guestfs-tools: FTBFS: guestfsd: error: minix: /dev/sda1: mkfs: failed to execute mkfs.minix: No such file or directory 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.) -- 1071313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:guestfs-tools Version: 1.52.0-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf configure.ac: warning: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION or AM_GNU_GETTEXT_REQUIRE_VERSION libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' [... snipped ...] /dev/disk/by-diskseq: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 1 -> ../../sda lrwxrwxrwx 1 0 0 9 May 17 18:30 2 -> ../../sdb /dev/disk/by-id: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 scsi-0QEMU_QEMU_HARDDISK_appliance -> ../../sdb lrwxrwxrwx 1 0 0 9 May 17 18:30 scsi-0QEMU_QEMU_HARDDISK_hd0 -> ../../sda /dev/disk/by-path: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 pci-:00:02.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 0 0 9 May 17 18:30 pci-:00:02.0-scsi-0:0:1:0 -> ../../sdb /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 b6cf2551-a800-4675-b55b-ad7f7474d0ac -> ../../sdb /dev/input: total 0 crw--- 1 0 0 13, 63 May 17 18:30 mice /dev/mapper: total 0 crw--- 1 0 0 10, 236 May 17 18:30 control /dev/net: total 0 crw-rw-rw- 1 0 0 10, 200 May 17 18:30 tun /dev/pts: total 0 c- 1 0 0 5, 2 May 17 18:30 ptmx /dev/shm: total 0 /dev/snd: total 0 crw--- 1 0 0 116, 1 May 17 18:30 seq crw--- 1 0 0 116, 33 May 17 18:30 timer /dev/vfio: total 0 crw-rw-rw- 1 0 0 10, 196 May 17 18:30 vfio /dev/virtio-ports: total 0 lrwxrwxrwx 1 0 0 11 May 17 18:30 org.libguestfs.channel.0 -> ../vport2p1 + cat /proc/mounts /dev/root / ext2 rw,noatime 0 0 /proc /proc proc rw,relatime 0 0 /sys /sys sysfs rw,relatime 0 0 /dev /dev devtmpfs rw,relatime,size=616296k,nr_inodes=154074,mode=755,inode64 0 0 /dev/pts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 shmfs /dev/shm tmpfs rw,relatime,inode64 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=249604k,mode=755,inode64 0 0 + cat /proc/mdstat cat: /proc/mdstat: No such file or directory + lvm config + lvm pvs + lvm vgs + lvm lvs + ip a 1: \x1b[36mlo: \x1b[0m mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback \x1b[33m00:00:00:00:00:00\x1b[0m brd \x1b[33m00:00:00:00:00:00\x1b[0m inet \x1b[35m127.0.0.1\x1b[0m/8 brd \x1b[35m127.255.255.255 \x1b[0mscope host lo valid_lft forever preferred_lft forever inet6 \x1b[34m::1\x1b[0m/128 scope host proto kernel_lo valid_lft forever preferred_lft forever + ip r + cat /etc/resolv.conf cat: /etc/resolv.conf: No such file or directory + lsmod Module Size Used by dm_mod221184 0 sg 45056 0 virtio_snd 40960 0 snd_pcm 192512 1 virtio_snd snd_timer 53248 1 snd_pcm snd 155648 3 virtio_snd,snd_timer,snd_pcm soundcore 16384 1 snd libcrc32c 12288 0 crc8 12288 0 crc7 12288 0 crc_itu_t 12288 0 ext4 1130496 1 crc16 12288 1 ext4 mbcache16384 1 ext4 jbd2 196608 1 ext4 virtio_vdpa16384 0 vdpa 36864 1 virtio_vdpa virtio_mmio16384 0 virtio_mem 49152 0 virtio_input 16384 0 virtio_dma_buf 12288 0 virtio_balloon 32768 0 virtio_scsi
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> reopen -1 =
Bug #1071007 {Done: Josenilson Ferreira da Silva }
[sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
'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 sherlock/0.14.3+git20240515.0ecb496-1.
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py)
Your message dated Sat, 18 May 2024 23:34:18 + with message-id and subject line Bug#1071007: fixed in sherlock 0.14.3+git20240515.0ecb496-1 has caused the Debian Bug report #1071007, regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py 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.) -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sherlock Version: 0.14.3+git20240511.b83f5be-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + pycrc sherlock has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/__init__.py is contained in the packages * pycrc/0.10.0-2 as present in trixie|unstable * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: sherlock Source-Version: 0.14.3+git20240515.0ecb496-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of sherlock, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated sherlock 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, 18 May 2024 19:10:45 -0300 Source: sherlock Architecture: source Version: 0.14.3+git20240515.0ecb496-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Josenilson Ferreira da Silva Closes: 1071007 Changes: sherlock (0.14.3+git20240515.0ecb496-1) unstable; urgency=medium . * New upstream version 0.14.3+git20240515.0ecb496 * debian/control: - Bumped Standards-Version to 4.7.0 - Tags added for conflict resolution with pycrc package (Closes: #1071007) * debian/docs: - README.md moved to 'docs' directory in new version Checksums-Sha1: 145e81570257305a43fe391b9487c04799a49729 2431 sherlock_0.14.3+git20240515.0ecb496-1.dsc 5d47e02e0653bc25ac4dbf4876806a8675bf0ab5 187092 sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz 44a94897173d4bc3e64f9d30d07bf44d411bae58 5276 sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 06a5cc1f4d2c4fd827e2f2e35fb73379629911e5 9416 sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo Checksums-Sha256: 7c310f9af8145ad5bc7ed0095ccdadc911f168325ef92c5348461b34676e3c5a 2431 sherlock_0.14.3+git20240515.0ecb496-1.dsc d0ac603d7ac7d0a055686c85874ebd3aed5aab3097c56193f5f94a48eca7e555 187092 sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz 71bc18c8db59b0d2bb8a1f7f1548335ddc63f89b96ffcd91c00b43070672721c 5276 sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 6ec77ae7741ea83f0132954a8e87e47e95e7a724c4faf63c3cb97a1707c9 9416 sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo Files: 17e1ff96468cfecdb3862d398c8f0424 2431 misc optional sherlock_0.14.3+git20240515.0ecb496-1.dsc b097112bbb62b02fdbf42b5d963e053c 187092 misc optional sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz f5ec1b9c2a6ac82dcd07bd55a918bd3b 5276 misc optional sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 4084cc682d59780ef056cbf9f2565885 9416 misc optional sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmZJNiwACgkQB6n1YjE0 Rs2WSg/8CtUgKtL2+2xJ13KTx//9sijA8IdH17IPfvpqJlAOJXl0zeyjPjxbjEIo D1W7X1CEHoVyme6NH0vLbrwIkvBVGIwuMFLVoUwcLiAXHXhKKTUHhi7WBmF2WZsn KbYR6/wQH568PnLTBCHxZBVv8OEg3mtUSN8yJm5Roh
Processed: Re: linphone-desktop: chat messages
Processing control commands: > severity -1 important Bug #983365 [src:linphone] linphone-desktop: chat messages Severity set to 'important' from 'grave' -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
