Bug#1007954: marked as done (galera-4 FTBFS on IPV6-only buildds)
Your message dated Wed, 18 Oct 2023 22:15:18 -0700 with message-id and subject line Re: [debian-mysql] Bug#1007954: Bug#1007954: galera-4 FTBFS on IPV6-only buildds has caused the Debian Bug report #1007954, regarding galera-4 FTBFS on IPV6-only buildds 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.) -- 1007954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: galera-4 Version: 26.4.8-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=galera-4=amd64 https://buildd.debian.org/status/logs.php?pkg=galera-4=armel https://buildd.debian.org/status/logs.php?pkg=galera-4=i386 ... Running suite(s): gu::asio terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://127.0.0.1:0: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://127.0.0.1:0: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://127.0.0.1:0: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://239.255.0.1:0: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://127.0.0.1:0: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 terminate called after throwing an instance of 'gu::Exception' what(): error opening datagram socketudp://239.255.0.1:0?socket.if_addr=127.0.0.1: 1 (Operation not permitted) at ./galerautils/src/gu_asio_datagram.cpp:resolve_and_open():107 90%: Checks: 80, Failures: 0, Errors: 8 ./galerautils/tests/gu_asio_test.cpp:1788:E:test_datagram_open:test_datagram_open:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1797:E:test_datagram_connect:test_datagram_connect:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1806:E:test_datagram_open_connect:test_datagram_open_connect:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1816:E:test_datagram_connect_multicast:test_datagram_connect_multicast:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1830:E:test_datagram_connect_multicast_local_if:test_datagram_connect_multicast_local_if:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1871:E:test_datagram_send_to_and_async_read:test_datagram_send_to_and_async_read:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1884:E:test_datagram_send_to_and_async_read_multicast:test_datagram_send_to_and_async_read_multicast:0: (after this point) Received signal 6 (Aborted) ./galerautils/tests/gu_asio_test.cpp:1897:E:test_datagram_write_multicast:test_datagram_write_multicast:0: (after this point) Received signal 6 (Aborted) Running suite(s): gu::DeqMap 100%: Checks: 11, Failures: 0, Errors: 0 Total tests failed: 8 Start 3: check_gcomm 3/7 Test #3: check_gcomm .. Passed0.99 sec Start 4: gcache_tests 4/7 Test #4: gcache_tests . Passed0.02 sec Start 5: gcs_tests 5/7 Test #5: gcs_tests Passed8.99 sec Start 6: galera_check 6/7 Test #6: galera_check . Passed1.98 sec Start 7: wsrep_test 7/7 Test #7: wsrep_test ... Passed0.01 sec 86% tests passed, 1 tests failed out of 7 Total Test time (real) = 17.00 sec The following tests FAILED:
Bug#1054141: marked as done (fd - incompatible with clap 4.4.6)
Your message dated Thu, 19 Oct 2023 04:51:29 + with message-id and subject line Bug#1054141: fixed in rust-fd-find 8.7.0-5 has caused the Debian Bug report #1054141, regarding fd - incompatible with clap 4.4.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-fd-find Version: 8.7.0-3 Severity: serious This bug affects both 8.7.0-3 in testing and 8.7.0-4 in unstable. I recently uploaded clap 4.4.6, since this was not a semver bump I was not expecting any breakage. Unfortunately it turns out it broke fd. There are (at least) two issues, the first is that the "unstable-grouped" feature was removed in clap 4.2.0 by the commit https://github.com/clap-rs/clap/commit/d5089b267235db72a6ea146ac4f1cb7f79a170a6 "fix!: Remove stablized unstable-grouped feature". By removing the reference to the "unstable-grouped" feature I was able to successfully build fd and run it's tests against clap versions 4.2.0 through 4.2.4. The second issue arises starting with clap version 4.2.5, a bunch of tests fail with errors like. test_custom_ignore_files stdout thread 'test_custom_ignore_files' panicked at '`fd --ignore-file custom.ignore foo` did not exit successfully. stdout: --- --- stderr: --- thread 'main' panicked at 'Command fd: Argument group 'execs' conflicts with non-existent 'has_results' id', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/clap_builder-4.2.5/src/builder/debug_asserts.rs:317:13 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---', tests/testenv/mod.rs:238:13 I'm not sure what should be done about this second issue. I've filed a bug upstream at https://github.com/sharkdp/fd/issues/1397 --- End Message --- --- Begin Message --- Source: rust-fd-find Source-Version: 8.7.0-5 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-fd-find, 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 1054...@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-fd-find 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: Thu, 19 Oct 2023 04:16:22 + Source: rust-fd-find Architecture: source Version: 8.7.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1054141 Changes: rust-fd-find (8.7.0-5) unstable; urgency=medium . * Team upload. * Package fd-find 8.7.0 from crates.io using debcargo 2.6.0 * Apply upstream patch for new clap. (Closes: #1054141) Checksums-Sha1: 359a5046999d95cba74b6795d032153519ad8078 3307 rust-fd-find_8.7.0-5.dsc 333cb158bff06f0593bbfa932e05c96de2e2b320 8004 rust-fd-find_8.7.0-5.debian.tar.xz 136805f0cd41139f1ae21dfb252781b3a437c7cd 14990 rust-fd-find_8.7.0-5_source.buildinfo Checksums-Sha256: aca92572a584384c9728ed22de8a4b546b0badfe670661fc7ae1b70cfc68e22c 3307 rust-fd-find_8.7.0-5.dsc 37505395bf975902814e62cce43736744e66cee576481a87ed4144e194043aca 8004 rust-fd-find_8.7.0-5.debian.tar.xz 65722c39e50350d9a3c3dfef518ba62632150a7b82ed80fe8f04ed8c0bfd55bf 14990 rust-fd-find_8.7.0-5_source.buildinfo Files: 63311a56a9e4ca3efbdcb528cd31b42d 3307 utils optional rust-fd-find_8.7.0-5.dsc 10fde46009b0939c949e9c098b1ece75 8004 utils optional rust-fd-find_8.7.0-5.debian.tar.xz 76137a111d69f4db1a2aa16772731c51 14990 utils optional rust-fd-find_8.7.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmUwsakUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xsmzw//SBwJTXrPAmKFlsPbZfNXePwtyw6u VN8aXyjXgdRUdnAt0B6lNm+8F0+Hpqk6TXFvlD9Eo/lSpATasdCEF8ofoWTou3WU A1yeXFTnsSICjuOwV/Z+xWFFulPM5wljCgFYt9K6SWFLMfvQbnxFtUM6pBtp4Y2N wa5l/8XdGj/Au/MQ6DqGZCCyDLia2yaSDM6Ok3TO15lULGfoOODiLd8HcboW3gxG fyZhEuReRmmJIEiOvX6s1bOKzWAU0j+10ZCYU3VyWjFmLZoNE9PDDjLEgdX5NIwE 0ufEHfklzcD4H6mRgSYbJs28tW7KEJc7jkyXqWQwnvoIGSWfiu/rd/ikGVlcaG/t JUWVKPRsKtmOBWvwWGNEfhj/mJuxnnzAY+hnJgLn1SE7DCn4wEaQa8d+KVordoHb
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org: > severity 1052838 normal Bug #1052838 [src:mariadb] mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port Severity set to 'normal' from 'serious' > retitle 1052838 mariadb: FTBFS multiple archs: Post-build tests randomly fail > on reserved port due to lacking builder isolation Bug #1052838 [src:mariadb] mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port Changed Bug title to 'mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port due to lacking builder isolation' from 'mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053010: marked as done (node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED)
Your message dated Thu, 19 Oct 2023 03:39:46 + with message-id and subject line Bug#1053010: fixed in node-jss 10.10.0+ds3+~0.3.1-1 has caused the Debian Bug report #1053010, regarding node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-jss Version: 10.10.0+ds1+~0.3.1-3 Severity: serious On 2023-09-26 16:19, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package node-css-initials, version 0.3.1~, > for all, > however unstable already has version 0.3.1~. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: node-jss Source-Version: 10.10.0+ds3+~0.3.1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-jss, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-jss package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Oct 2023 07:07:23 +0400 Source: node-jss Architecture: source Version: 10.10.0+ds3+~0.3.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1053010 Changes: node-jss (10.10.0+ds3+~0.3.1-1) unstable; urgency=medium . * Revert previous changes and fix versions (Closes: #1053010) Checksums-Sha1: ab919fcad18094ff6ebd069edee8f0d074a41b22 4214 node-jss_10.10.0+ds3+~0.3.1-1.dsc 6961159ec866bd065c05ee4d066896f47d0263fb 20616 node-jss_10.10.0+ds3+~0.3.1.orig-css-initials.tar.xz c5cef29b12ad66f1bc471ae7c0f06c3dfbaaae1a 368168 node-jss_10.10.0+ds3+~0.3.1.orig.tar.xz 6ea86556b871fdbb826224a2807b84281bf59e0f 6784 node-jss_10.10.0+ds3+~0.3.1-1.debian.tar.xz Checksums-Sha256: 4160b988accfb2fdb8e1b8ecb5475837fa0d2823713d804700e32d7f28695dc2 4214 node-jss_10.10.0+ds3+~0.3.1-1.dsc 878eabba32b255fc76788c9e236870bed83469244970fc0bdbf87c83abb4f319 20616 node-jss_10.10.0+ds3+~0.3.1.orig-css-initials.tar.xz 2b5e93e2ea92addb797236d130fbab3418362968ac66a092cf2aba6f4c9745cc 368168 node-jss_10.10.0+ds3+~0.3.1.orig.tar.xz f49be219cd494720fd5f721bd964b4f7878c663394ba1e7f240515d37687 6784 node-jss_10.10.0+ds3+~0.3.1-1.debian.tar.xz Files: b2a8dff84d0198aecd4731cfcca8ce1d 4214 javascript optional node-jss_10.10.0+ds3+~0.3.1-1.dsc 6f4d49e6f7b007f5cc9c318b128432f4 20616 javascript optional node-jss_10.10.0+ds3+~0.3.1.orig-css-initials.tar.xz 8d0e20bf63064db084d1b683e9f81dd9 368168 javascript optional node-jss_10.10.0+ds3+~0.3.1.orig.tar.xz 6cfad172fad25c19e076a2f6191a7597 6784 javascript optional node-jss_10.10.0+ds3+~0.3.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmUwnfgACgkQ9tdMp8mZ 7umfrA/6A1/vmmfzWOmyrWYeUSbP9w8mf8iWY1KewHxexzJfjAYI6zNsyD6Ka98P Scwx2Mftg4B9X5k2/L66898vYwlNNp9xyjHVRmIuS3VmhYVZrQYcPGs/YL/+9p91 34t9YdyAIupe7D0WaqNqV14NVwEML++I+jdjuFjGgV0JVlJ2dho7+ZAmyo25UMsu 0JuYS5MBc1ciBonKtn2zpH4WiGXT7AB5uIRG0qAju1vViqN0NcHctHrZAMXK8C7F yMZzC4QKRI2Z6MQzACTErXdVpJW59cMcsTKkMwgbkY5mgD98pKVcgXZhu8MNybvC 3G6DRdRM+dPetqCmeY/7Tnu0NfAhCJEYyzRrn5iaVdwxooBl4u+QgGe/ub6z6sEw TkozaSCKfnKp52kAoVZDj7U8BSRhPtFdUUYHAw7v64mhUUYk0IWLfa62Gl97pYPA WDJ7RXNb3Q6osp5SS/egEHMnG5ybGEfVQWj8H8mW6EUJRCqtjLavgxj17QrAuUJ5 gwHLUH3x64b8ABhs/uPeuB7zLwmqHbn/iDlbsxjW2T7FMnmDBMYdVHtMh+1ffIQg WVe7CpzsdDaduqvOg8oXTowTAW474gsIMTot1guaEwsyJPcteTAO690jcLmpUwqE HaILEA7w8Hfu7spWHezeNDP9rnmz5SQg8Mj/2PLfbtS/NgOe6Mw= =8tfB -END PGP SIGNATURE End Message ---
Bug#1053010: marked as done (node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED)
Your message dated Thu, 19 Oct 2023 03:04:55 + with message-id and subject line Bug#1053010: fixed in node-jss 10.10.0+ds2-1 has caused the Debian Bug report #1053010, regarding node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-jss Version: 10.10.0+ds1+~0.3.1-3 Severity: serious On 2023-09-26 16:19, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package node-css-initials, version 0.3.1~, > for all, > however unstable already has version 0.3.1~. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: node-jss Source-Version: 10.10.0+ds2-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-jss, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-jss package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Oct 2023 06:48:38 +0400 Source: node-jss Built-For-Profiles: nocheck Architecture: source Version: 10.10.0+ds2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1053010 Changes: node-jss (10.10.0+ds2-1) unstable; urgency=medium . * Drop component css-initials (Closes: #1053010) and repack Checksums-Sha1: 3cb339d89cf2e8e0ebd45cc03f5a47fb55bb6186 3794 node-jss_10.10.0+ds2-1.dsc c5cef29b12ad66f1bc471ae7c0f06c3dfbaaae1a 368168 node-jss_10.10.0+ds2.orig.tar.xz 1b2cb475330d6038a93cd438652e7bc059e25cc0 6084 node-jss_10.10.0+ds2-1.debian.tar.xz Checksums-Sha256: 1bc79e279942811ee4736849a78e7d508a23b50e4400d9daa09364bac43e651b 3794 node-jss_10.10.0+ds2-1.dsc 2b5e93e2ea92addb797236d130fbab3418362968ac66a092cf2aba6f4c9745cc 368168 node-jss_10.10.0+ds2.orig.tar.xz 6a6148a51fca3cf898fa34445c9c2a2db019ced38f07711a6e2916e3b2b5085e 6084 node-jss_10.10.0+ds2-1.debian.tar.xz Files: 42cae9b87c5cb992041307c530b1202e 3794 javascript optional node-jss_10.10.0+ds2-1.dsc 8d0e20bf63064db084d1b683e9f81dd9 368168 javascript optional node-jss_10.10.0+ds2.orig.tar.xz 8104706611d78163676f94ca934a0be8 6084 javascript optional node-jss_10.10.0+ds2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmUwmZwACgkQ9tdMp8mZ 7ulhLQ//QMHjIlLjCIgvfql8SBCjyJvQKPaD+TcJtxoomHNC0N0fzGWH+XbT+nT8 9MpELfgMlMpVR2SstBA+z2gIiPAsAz7/mxTdPeTyMxrELTOaXGpY5oAqQZwCc6Ll fPwgsH+Xkv4PB+RgSS0wMuTZi7bYKUtg5eTDODCGebdTm0oLDoDGrfbPFe8XZu6c HCuWRG4W9ns2AkRmX8evosGbvrk5hnqI5jvxRwxKYrZ5s46x2653WAuDExt0Kvbo EBP/vm7GXxUKLymM0cbTj2QiJNA0KOKioJ5Q/fNgv48sGWy9yF21ztfvdjGfJMMC FsM6DYhwq/LW6ffX/LCkmVb4TEV5a3RFY7bUx/5rnF1xidNJFdIiX7qW0DUN3QOm pJAYBvSVOVS4S8J16IZROzyFWiLhLlLBX7K+bIn6+4FDtRN61vMk/HeP3fiUrcWV uUiBXvsOY5MGdsqn+OJxPE9hcaKhx9QB3ivepLtHQShpirXAX5PwU6JfSacOmhAK jusvvcUs9VgMCBMRoAFpWUyj88Ljq3SXNkGY54et1H/gcq8U2cxCKv1GngMjkD2X LMyRKIlZVMbJ2eQdKAqhcgI5x/wOiNBfrmLIGwy2YQoWcM85B+ZvYLvtCozNiXNs 8LMhvvbdwioHx9mSn3mxI3jscr0z+yZH09yJh1cU2u9dnoSLzK8= =LRz1 -END PGP SIGNATURE End Message ---
Processed: Bug#1053010 marked as pending in node-jss
Processing control commands: > tag -1 pending Bug #1053010 [node-jss] node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED Added tag(s) pending. -- 1053010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053010: marked as pending in node-jss
Control: tag -1 pending Hello, Bug #1053010 in node-jss reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jss/-/commit/42393b0849d0ec9a603365387cd34f633536c75f Drop component css-initials Closes: #1053010 (this message was generated automatically) -- Greetings https://bugs.debian.org/1053010
Bug#1054198: marked as done (ncbi-entrez-direct FTBFS: No rule to make target '/<>/obj-aarch64-linux-gnu/src/golang.org/x/net', needed by '/<>/obj-aarch64-linux-gnu/src/githu
Your message dated Thu, 19 Oct 2023 02:39:54 + with message-id and subject line Bug#1054198: fixed in ncbi-entrez-direct 19.2.20230331+dfsg-3 has caused the Debian Bug report #1054198, regarding ncbi-entrez-direct FTBFS: No rule to make target '/<>/obj-aarch64-linux-gnu/src/golang.org/x/net', needed by '/<>/obj-aarch64-linux-gnu/src/github.com/klauspost/cpuid' 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.) -- 1054198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ncbi-entrez-direct Version: 19.2.20230331+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ncbi-entrez-direct=19.2.20230331%2Bdfsg-2%2Bb1 ... ln -s /usr/share/gocode/src/golang.org/x/crypto /<>/obj-aarch64-linux-gnu/src/golang.org/x/crypto make[1]: *** No rule to make target '/<>/obj-aarch64-linux-gnu/src/golang.org/x/net', needed by '/<>/obj-aarch64-linux-gnu/src/github.com/klauspost/cpuid'. Stop. make[1]: Leaving directory '/<>' make: *** [debian/rules:17: binary-arch] Error 2 --- End Message --- --- Begin Message --- Source: ncbi-entrez-direct Source-Version: 19.2.20230331+dfsg-3 Done: Aaron M. Ucko We believe that the bug you reported is fixed in the latest version of ncbi-entrez-direct, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aaron M. Ucko (supplier of updated ncbi-entrez-direct 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, 18 Oct 2023 21:34:22 -0400 Source: ncbi-entrez-direct Architecture: source Version: 19.2.20230331+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Aaron M. Ucko Closes: 1054198 Changes: ncbi-entrez-direct (19.2.20230331+dfsg-3) unstable; urgency=medium . * .gitignore: Drop "saved" again, slightly belatedly. * debian/control: Explicitly build-depend on golang-golang-x-net-dev. AFAICT, it had been coming in as an indirect dependency of golang-github-gin-gonic-gin-dev, most immediately via golang-golang-x-crypto-dev, which recently dropped its dependency to break a cycle. (Closes: #1054198.) Checksums-Sha1: 7f8315c60a4d6c9c25a29a392184f059b788e3cc 2736 ncbi-entrez-direct_19.2.20230331+dfsg-3.dsc 5fa88b5c75815f96f654bd9bd4ff0ab141d87dba 47456 ncbi-entrez-direct_19.2.20230331+dfsg-3.debian.tar.xz Checksums-Sha256: 46d3c9e47cd00838922873fb127ff8285034cc483408310c9213375ad02c232c 2736 ncbi-entrez-direct_19.2.20230331+dfsg-3.dsc df7316a6ba6ceec237280eb37d8755b8638c051e28a8352d40cfd0d269175d40 47456 ncbi-entrez-direct_19.2.20230331+dfsg-3.debian.tar.xz Files: a6196741b6f3b5741b092b5fd40ec61f 2736 science optional ncbi-entrez-direct_19.2.20230331+dfsg-3.dsc 8ecd9aa1db0d0d0b22dbe3fe84078029 47456 science optional ncbi-entrez-direct_19.2.20230331+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfDq5z9IwvTDdAJxZHnCRsfFKZKIFAmUwiMMACgkQHnCRsfFK ZKIZug/9EiB01nQWwMvJfW6xJvdFmiyec0aKGVW7FUZChnm3/HlY2D9MkunFx/wJ AF2YsTJ8FEC8o87ETw+26Zgt/SCkUZW9bW+edY9OMjPllBTSufrv/la0Th/emHvA 2nwMCcelqUQFv1g+Q7SZ5nJWk4INRjjRS/mEugB/hhatJfpIFCD5DsOUCRNFN5S2 27kAE6TD8rMLdbH6IFFua15FfY+gTkOk+0Rxu9tvQqJARKm4mpRvFnzU1++ztjTl hQOnjfBKESG71hPvLNik3uHNom2X4Wg05KcIS1uRoDbTprAxweBKhs1JnXTYbBj4 1P7SYyPRSgu10cqvJ0rJvXAdORkhZlk/CSrrM7lqK2x5ljl5jycSaRZLSM3hKoMT bla/ohZsjXsNjTx/AesQLbI0nAJo35Vqk37O48Bw1wyrquu8WocaQ4KUE20QR9qp +Pgog8SAmazJv9gFOh29aTcLp7x60vWJeMKaHVkxa1lPxC/055FcYUify2ntluch WmmQITZ/FnWGtwiYVIaBCBwbVLNO/DAmUGKm2hu35Cjphlu65YbVdTDPCBzHduJS l1g+oXpB1VFX6Avt4//279hbcZegVl7OAJQcv3o46gp7fFnoHF08k2dElW8+rRDz KeHz0acDi4g555Fr/BKfgzCPWuw8ws/j1X17lJD0YsA/Q03dMbE= =jXAm -END PGP SIGNATURE End Message ---
Bug#902810: marked as done (user-mode-linux: FTBFS in stretch (Hunk #1 FAILED in 07-remove-rpath.patch))
Your message dated Thu, 19 Oct 2023 01:15:51 +0200 with message-id <645f2cd8-c543-41ec-9fa3-28437cfda...@debian.org> and subject line Re: user-mode-linux: FTBFS in stretch (Hunk #1 FAILED in 07-remove-rpath.patch) has caused the Debian Bug report #902810, regarding user-mode-linux: FTBFS in stretch (Hunk #1 FAILED in 07-remove-rpath.patch) 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.) -- 902810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:user-mode-linux Version: 4.9-1um-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch + security + stretch-proposed-updates but it failed: [...] debian/rules build-arch tar -x -f /usr/src/linux-source-4.9.tar.xz touch unpack-stamp (cd linux-source-4.9 && QUILT_PATCHES=/<>/debian/patches quilt push -a) Applying patch /<>/debian/patches/02_x-terminal-emulator.patch patching file arch/um/drivers/xterm.c Applying patch /<>/debian/patches/03_uml_switch.patch patching file arch/um/drivers/daemon_kern.c Applying patch /<>/debian/patches/05_fix_static_build.patch patching file arch/um/Makefile Hunk #1 succeeded at 91 (offset 15 lines). Applying patch /<>/debian/patches/06-fix-linkage-on-386-arch.patch patching file arch/x86/um/Makefile Hunk #1 succeeded at 19 with fuzz 2. Applying patch /<>/debian/patches/07-remove-rpath.patch patching file arch/um/Makefile Hunk #1 FAILED at 107. 1 out of 1 hunk FAILED -- rejects in file arch/um/Makefile patching file arch/x86/Makefile.um Patch /<>/debian/patches/07-remove-rpath.patch does not apply (enforce with -f) debian/rules:54: recipe for target 'patch-stamp' failed make: *** [patch-stamp] Error 1 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 The build was made with "dpkg-buildpackage -B" in my autobuilder but it also fails with plain "dpkg-buildpackage" in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/user-mode-linux.html Thanks. --- End Message --- --- Begin Message --- Version: 5.10um3 Hi. I'm closing my own bug because stretch is no longer supported. Thanks.--- End Message ---
Bug#902810: user-mode-linux: FTBFS in stretch (Hunk #1 FAILED in 07-remove-rpath.patch)
Version: 5.10um3 Hi. I'm closing my own bug because stretch is no longer supported. Thanks.
Bug#902162: translate-toolkit: FTBFS in stretch (broken by change in Africa/Windhoek timezone)
Version: 2.3.1-3 I'm closing my own bug because stretch is no longer supported. Thanks.
Bug#902162: marked as done (translate-toolkit: FTBFS in stretch (broken by change in Africa/Windhoek timezone))
Your message dated Thu, 19 Oct 2023 01:08:42 +0200
with message-id
and subject line Re: translate-toolkit: FTBFS in stretch (broken by change in
Africa/Windhoek timezone)
has caused the Debian Bug report #902162,
regarding translate-toolkit: FTBFS in stretch (broken by change in
Africa/Windhoek timezone)
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.)
--
902162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:translate-toolkit
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
This package does no longer build from source in Debian stretch:
[...]
=== FAILURES ===
test_timezones
def test_timezones():
pofile = po.pofile()
# The following will only work on Unix because of tzset() and %z
if 'tzset' in time.__dict__:
os.environ['TZ'] = 'Asia/Kabul'
time.tzset()
assert time.timezone == -16200
# Typically "+0430"
assert poheader.tzstring() == time.strftime("%z")
os.environ['TZ'] = 'Asia/Seoul'
time.tzset()
assert time.timezone == -32400
# Typically "+0900"
assert poheader.tzstring() == time.strftime("%z")
os.environ['TZ'] = 'Africa/Johannesburg'
time.tzset()
assert time.timezone == -7200
# Typically "+0200"
assert poheader.tzstring() == time.strftime("%z")
os.environ['TZ'] = 'Africa/Windhoek'
time.tzset()
> assert time.timezone == -3600
E assert -7200 == -3600
E+ where -7200 = time.timezone
../../translate/storage/test_poheader.py:127: AssertionError
=== 1 failed, 2252 passed, 1 skipped, 51 xfailed, 6 xpassed in 10.48 seconds ===
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: cp -a
tests share /<>/.pybuild/pythonX.Y_2.7/build; cd
/<>/.pybuild/pythonX.Y_2.7/build;
PATH=/<>/debian/python-translate/usr/bin:$PATH python2.7 -m pytest
-v -rxs
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
debian/rules:42: recipe for target 'override_dh_install' failed
The above is from my own autobuilder, but it also happens here:
https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/translate-toolkit.html
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2.3.1-3
I'm closing my own bug because stretch is no longer supported.
Thanks.--- End Message ---
Bug#934036: sketch: FTBFS in stretch (LaTeX error)
Version: 1:0.3.7-11 Hi. Since stretch is no longer supported, I'm closing my own bug using buster version. Thanks.
Bug#1054202: prometheus-snmp-exporter FTBFS: FAIL: pg_setting_test.go:240: PgSettingSuite.TestMetric
Source: prometheus-postgres-exporter
Version: 0.14.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=prometheus-postgres-exporter=0.14.0-2%2Bb1
...
FAIL: pg_setting_test.go:240: PgSettingSuite.TestMetric
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_seconds_fixture_metric_seconds\", help: \"Server Parameter:
seconds_fixture_metric [Units converted to seconds.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_seconds_fixture_metric_seconds\", help: \"Server Parameter:
seconds_fixture_metric [Units converted to seconds.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_milliseconds_fixture_metric_seconds\", help: \"Server Parameter:
milliseconds_fixture_metric [Units converted to seconds.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_milliseconds_fixture_metric_seconds\", help: \"Server Parameter:
milliseconds_fixture_metric [Units converted to seconds.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_eight_kb_fixture_metric_bytes\", help: \"Server Parameter:
eight_kb_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_eight_kb_fixture_metric_bytes\", help: \"Server Parameter:
eight_kb_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_16_kb_real_fixture_metric_bytes\", help: \"Server Parameter:
16_kb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_16_kb_real_fixture_metric_bytes\", help: \"Server Parameter:
16_kb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_16_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
16_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_16_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
16_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_32_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
32_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_32_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
32_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_64_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
64_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_64_mb_real_fixture_metric_bytes\", help: \"Server Parameter:
64_mb_real_fixture_metric [Units converted to bytes.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName: \"pg_settings_bool_on_fixture_metric\",
help: \"Server Parameter: bool_on_fixture_metric\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName: \"pg_settings_bool_on_fixture_metric\",
help: \"Server Parameter: bool_on_fixture_metric\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName: \"pg_settings_bool_off_fixture_metric\",
help: \"Server Parameter: bool_off_fixture_metric\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName: \"pg_settings_bool_off_fixture_metric\",
help: \"Server Parameter: bool_off_fixture_metric\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
c.Check(m.Desc().String(), Equals, f.d)
... obtained string = "Desc{fqName:
\"pg_settings_special_minus_one_value_seconds\", help: \"Server Parameter:
special_minus_one_value [Units converted to seconds.]\", constLabels: {},
variableLabels: {}}"
... expected string = "Desc{fqName:
\"pg_settings_special_minus_one_value_seconds\", help: \"Server Parameter:
special_minus_one_value [Units converted to seconds.]\", constLabels: {},
variableLabels: []}"
pg_setting_test.go:254:
Bug#1038687: marked as done (radicale's autopkg tests fail with Python 3.11.4)
Your message dated Wed, 18 Oct 2023 21:49:29 +
with message-id
and subject line Bug#1038687: fixed in radicale 3.1.8-4
has caused the Debian Bug report #1038687,
regarding radicale's autopkg tests fail with Python 3.11.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.)
--
1038687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:radicale
Version: 3.1.8-2
Severity: serious
Tags: sid trixie
https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/radicale/34395011/log.gz
several tests fail with
[...]
hostname = '127.0.0.1'
def _check_bracketed_host(hostname):
if hostname.startswith('v'):
if not re.match(r"\Av[a-fA-F0-9]+\..+\Z", hostname):
raise ValueError(f"IPvFuture address is invalid")
else:
ip = ipaddress.ip_address(hostname) # Throws Value Error if not
IPv6 or IPv4
if isinstance(ip, ipaddress.IPv4Address):
> raise ValueError(f"An IPv4 address cannot be in brackets")
E ValueError: An IPv4 address cannot be in brackets
/usr/lib/python3.11/urllib/parse.py:448: ValueError[...]
this is a changed introduced in Python 3.11.4 and Python 3.12. The test cases
probably need some adjustments.
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 3.1.8-4
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
radicale, 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 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated radicale 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, 18 Oct 2023 23:22:24 +0200
Source: radicale
Architecture: source
Version: 3.1.8-4
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 1038687
Changes:
radicale (3.1.8-4) unstable; urgency=medium
.
* add patch cherry-picked from upstream pull-request
to remove brackets from IPv4 test hostnames;
closes: bug#1038687, thanks to Petter Reinholdtsen
* update copyright info: update coverage
Checksums-Sha1:
c5994b39407813367ac2ac3ee4b043ba91dd860b 2473 radicale_3.1.8-4.dsc
557e643bfaa958651a2c70953cef7cf0bb2bfc89 27372 radicale_3.1.8-4.debian.tar.xz
199338580b17ca230999d64332245b1dac341f6e 7839 radicale_3.1.8-4_amd64.buildinfo
Checksums-Sha256:
7ea8a6ef8e59b0a80faf09939e8f441c27a19bb5ff5fb2133dc7ea1f46136eeb 2473
radicale_3.1.8-4.dsc
7d2b4ed898bd7e243c83bc78d1381ee907156e536c534eff858ffe7b591a1c40 27372
radicale_3.1.8-4.debian.tar.xz
cccde8f81a1b31dc1d26899346910f34b95731c0b843b65e2d6309f6876dc139 7839
radicale_3.1.8-4_amd64.buildinfo
Files:
24625fab6adcd0c37941078592cbf7a0 2473 net optional radicale_3.1.8-4.dsc
61c9736597c6c20e8a18be33e941e2a8 27372 net optional
radicale_3.1.8-4.debian.tar.xz
7880fa6d4c83b5becda8cb146b250505 7839 net optional
radicale_3.1.8-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUwTU0ACgkQLHwxRsGg
ASHzBxAAkynFfoCo7WiDQZQ4IjJdRwiPnqt/uGFwkl9PGFlkYnOE6fTFe0ryPLoa
kfNvwiA1almrThvWu5e2BnZnocM+9MhdnZ3HswAX/7EE7SiEzQ3GBcJHqV2Xo8hh
n/dTN2x7TogLYZ3llDzpUFvvVs+NOeW26i8H1lYEccnoSO/0WrQfQ4vD9tY8xNEO
f6tJ+8iG1dmpjn4TwnFjE19rK8aI01algzhcrS1D/eoL3Ys9VK/hpmoufLnYhVMV
htzghXz3DUmEE3IWYCtB6JS3ercatehSefWxgX/Jpr0qcimw1yfmfEfBq6ATZwZ1
gEb85frlYwKwtK39Xjo1CMNG3TNXAuOovCwcVITNiIsn5DT1u/P7SRbH0BhhN+wy
yrvU5ZLF2IzCyyeJSXAXkekO5P4/YyC9uaTke0LzozxY7P2y4gxa4dJ0ZF8ZMarQ
WHtmQE/Z6TkhQZl5u729Sxtc/1RQkmGdFBIBhus6K7Nx/EnzeYiTXM0Z5IGqHWSs
Qcypm7FDUqyLWoZ7Ph3bVmZcumKedfZmzT1zEKQYs5Ub5V1zEcTJ4McbrWxYbYRN
BZnj891uDPj9l/M+ox34yBLNP7hd/163LMpIBuYovTxEaZtvIKk+LgSZ8s4mg9o7
V9RrpnvaHUR6NgOgkIOsRaGvK9MDmFekUzge+i9fBqzVpZ3gZcA=
=4t97
-END PGP SIGNATURE End Message ---
Bug#1054154: marked as done (python3-aiortc 1.5.0-2 autopkgtest autodep8-python3 failure)
Your message dated Wed, 18 Oct 2023 21:49:21 + with message-id and subject line Bug#1054154: fixed in python-aiortc 1.5.0-3 has caused the Debian Bug report #1054154, regarding python3-aiortc 1.5.0-2 autopkgtest autodep8-python3 failure 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.) -- 1054154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-aiortc Version: 1.5.0-2 Severity: serious X-Debbugs-Cc: bdr...@debian.org Dear Maintainer, python3-aiortc 1.5.0-2 introduces an autopkgtest regression for autodep8-python3: ``` Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aiortc/__init__.py", line 23, in from .rtcpeerconnection import RTCPeerConnection File "/usr/lib/python3/dist-packages/aiortc/rtcpeerconnection.py", line 9, in from . import clock, rtp, sdp File "/usr/lib/python3/dist-packages/aiortc/sdp.py", line 17, in from .rtcsctptransport import RTCSctpCapabilities File "/usr/lib/python3/dist-packages/aiortc/rtcsctptransport.py", line 25, in from crc32c import crc32c ModuleNotFoundError: No module named 'crc32c' ``` Please extend the package dependency to solve the import failure. -- Benjamin Drung Debian & Ubuntu Developer --- End Message --- --- Begin Message --- Source: python-aiortc Source-Version: 1.5.0-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of python-aiortc, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated python-aiortc 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, 18 Oct 2023 23:36:42 +0200 Source: python-aiortc Architecture: source Version: 1.5.0-3 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1054154 Changes: python-aiortc (1.5.0-3) unstable; urgency=medium . * fix: depend (not autopkgtest-depend) on python3-crc32c; closes: bug#1054154, thanks to Benjamin Drung Checksums-Sha1: 5ab4ab1bce87516129ea7bdb6aa682ac8a4c7525 2724 python-aiortc_1.5.0-3.dsc 7f22140ec3732051f66fa1d9a500b0842aaa1728 7184 python-aiortc_1.5.0-3.debian.tar.xz 91fc97279a31c260c7aaa0b82ea54fe9b1abcd3e 14902 python-aiortc_1.5.0-3_amd64.buildinfo Checksums-Sha256: 335ea054e8422a1fb082d6f0f76bb940fe2d4a98aaa141b011f2fb757376f5ac 2724 python-aiortc_1.5.0-3.dsc a84b24f791106fb428116e30aa74680bb61e0cba8b9ddcfe460571d01552cb6c 7184 python-aiortc_1.5.0-3.debian.tar.xz 84ab4179efd357c70faa710845fb89b4a866b2eafade6b97de16c51b7c7222a0 14902 python-aiortc_1.5.0-3_amd64.buildinfo Files: 0a85c494ce5c87080e200ea4342f2bd1 2724 python optional python-aiortc_1.5.0-3.dsc c35e2c33e14ddc82cdd14a37f842339e 7184 python optional python-aiortc_1.5.0-3.debian.tar.xz 6a25f40c165ad71f600107ae106a166f 14902 python optional python-aiortc_1.5.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUwUIQACgkQLHwxRsGg ASGYtQ//Q13RPfCDSIrQjcLwy+Vnku07coo3zEqOkDGb8z1KWWxG0X5cKjX59oC3 /ObDrB2AdnH3dBKQ8R1E1bHxmNr94ehR1FxAk4s6tTsBk8fNNwv+uIkg7Q3+AjkF khgSKZNqpOWQQeOYT7SKTj/XmHwhXqteIbKkoDHsNyT1hYt55NZaw/hZeJQpocOf Cni29ojp4gFlUWBME9HgAIj5zJrwmS3qYep447BX4Zsh30fp0K/ioh8PPXU0PdgM JsvDfP0qgmFptViMx4TeQ7+tEiFgHdSweKFxebLxvVNznvbJtwmdks1Gkpdy6X1O 0ZKDmyuF3Jps9HDvdUSisAQ7CsNqV54y/RAukhVs/C1nQhyJV3qLdyr824pNWQir puVGiaB2aTWLptxYJTRe09XzX5Oj+/Ak/nPWevZjDCZseUMQTMojM1VReJW5G2vz zWCKPm7dm8dBOuO5x/Tny8FXYQVvUaBtPWcvqbWuXlDX4pHXa90UbJNM+4/Qm1NV 4g1yh2sIZPZxCg6d1ypL4bmFSZBv65uigJd61lB0fgVcX/ng/JyC2c/zf8AktwSl fwfREfkGwq/mV/wkl91wDefBr1pyP8R/8b4TGAQqg0fC8/SEuKzypI+kNmyn1f2n AlfwZpoLLIbN5JRDizglkFSMTL28iU9WjF8VyRJXViBBs2+zmlo= =bPOY -END PGP SIGNATURE End Message ---
Bug#1054199: prometheus-snmp-exporter FTBFS: FAIL: TestPduToSample
Source: prometheus-snmp-exporter
Version: 0.24.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=prometheus-snmp-exporter=0.24.1-1%2Bb2
...
ok github.com/prometheus/snmp_exporter 0.021s
=== RUN TestPduToSample
collector_test.go:539: Got metric: Desc{fqName:
"TestMetricNameExtension", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: {}} gauge:{value:5}
collector_test.go:545: Expected metric: Desc{fqName:
"TestMetricNameExtension", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: []} gauge:{value:5}, but was not returned.
collector_test.go:539: Got metric: Desc{fqName:
"TestMetricNameStatus", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: {}} gauge:{value:5}
collector_test.go:545: Expected metric: Desc{fqName:
"TestMetricNameStatus", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: []} gauge:{value:5}, but was not returned.
collector_test.go:539: Got metric: Desc{fqName:
"TestMetricNameExtension", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: {}} gauge:{value:5}
collector_test.go:539: Got metric: Desc{fqName:
"TestMetricNameMultipleRegexes", help: "HelpText (regex extracted)",
constLabels: {}, variableLabels: {}} gauge:{value:999}
collector_test.go:539: Got metric: Desc{fqName:
"TestMetricNameTemplate", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: {}} gauge:{value:4.42}
collector_test.go:545: Expected metric: Desc{fqName:
"TestMetricNameExtension", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: []} gauge:{value:5}, but was not returned.
collector_test.go:545: Expected metric: Desc{fqName:
"TestMetricNameMultipleRegexes", help: "HelpText (regex extracted)",
constLabels: {}, variableLabels: []} gauge:{value:999}, but was not returned.
collector_test.go:545: Expected metric: Desc{fqName:
"TestMetricNameTemplate", help: "HelpText (regex extracted)", constLabels: {},
variableLabels: []} gauge:{value:4.42}, but was not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {}} counter:{value:2}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: []} counter:{value:2}, but was
not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {}} gauge:{value:2}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: []} gauge:{value:2}, but was
not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {test_metric}}
label:{name:"test_metric" value:"-2"} gauge:{value:1}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: [{test_metric }]}
label:{name:"test_metric" value:"-2"} gauge:{value:1}, but was not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {}} gauge:{value:3}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: []} gauge:{value:3}, but was
not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {}} gauge:{value:3}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: []} gauge:{value:3}, but was
not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {foo}} label:{name:"foo"
value:"AA"} gauge:{value:3}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: [{foo }]}
label:{name:"foo" value:"AA"} gauge:{value:3}, but was not returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {test_metric}}
label:{name:"test_metric" value:"4.5.6.7"} gauge:{value:1}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: [{test_metric }]}
label:{name:"test_metric" value:"4.5.6.7"} gauge:{value:1}, but was not
returned.
collector_test.go:539: Got metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: {test_metric}}
label:{name:"test_metric" value:"4.5.6.7"} gauge:{value:1}
collector_test.go:545: Expected metric: Desc{fqName: "test_metric", help:
"Help string", constLabels: {}, variableLabels: [{test_metric }]}
Bug#1054198: ncbi-entrez-direct FTBFS: No rule to make target '/<>/obj-aarch64-linux-gnu/src/golang.org/x/net', needed by '/<>/obj-aarch64-linux-gnu/src/github.com/klauspost/
Source: ncbi-entrez-direct Version: 19.2.20230331+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ncbi-entrez-direct=19.2.20230331%2Bdfsg-2%2Bb1 ... ln -s /usr/share/gocode/src/golang.org/x/crypto /<>/obj-aarch64-linux-gnu/src/golang.org/x/crypto make[1]: *** No rule to make target '/<>/obj-aarch64-linux-gnu/src/golang.org/x/net', needed by '/<>/obj-aarch64-linux-gnu/src/github.com/klauspost/cpuid'. Stop. make[1]: Leaving directory '/<>' make: *** [debian/rules:17: binary-arch] Error 2
Bug#1054197: hcloud-cli FTBFS: cannot use cert.ID (variable of type int64) as int value in argument to strconv.Itoa
Source: hcloud-cli Version: 1.30.3-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=hcloud-cli=1.30.3-1%2Bb8 ... # github.com/hetznercloud/cli/internal/hcapi src/github.com/hetznercloud/cli/internal/hcapi/certificate.go:27:24: cannot use cert.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/datacenter.go:27:24: cannot use dc.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/firewall.go:27:24: cannot use firewall.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/floatingip.go:27:24: cannot use fip.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/image.go:27:24: cannot use img.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/iso.go:28:24: cannot use iso.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/loadbalancer.go:36:24: cannot use lb.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/loadbalancer.go:57:23: cannot use lb.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/loadbalancer.go:98:13: cannot use lb.ID (variable of type int64) as int value in map index src/github.com/hetznercloud/cli/internal/hcapi/location.go:27:24: cannot use loc.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi/location.go:27:24: too many errors # github.com/hetznercloud/cli/internal/cmd/util src/github.com/hetznercloud/cli/internal/cmd/util/util.go:212:25: cannot use hcloud.Int(image.BoundTo.ID) (value of type *int) as *int64 value in assignment src/github.com/hetznercloud/cli/internal/cmd/util/util.go:212:36: cannot use image.BoundTo.ID (variable of type int64) as int value in argument to hcloud.Int # github.com/hetznercloud/cli/internal/hcapi2 src/github.com/hetznercloud/cli/internal/hcapi2/certificate.go:37:24: cannot use dc.ID (variable of type int64) as int value in argument to strconv.Itoa src/github.com/hetznercloud/cli/internal/hcapi2/client.go:63:46: cannot use (value of type *hcloud.CertificateClient) as CertificateClientBase value in argument to NewCertificateClient: *hcloud.CertificateClient does not implement CertificateClientBase (wrong type for method GetByID) have GetByID(context.Context, int64) (*hcloud.Certificate, *hcloud.Response, error) want GetByID(context.Context, int) (*hcloud.Certificate, *hcloud.Response, error) src/github.com/hetznercloud/cli/internal/hcapi2/client.go:72:44: cannot use (value of type *hcloud.DatacenterClient) as DatacenterClientBase value in argument to NewDatacenterClient: *hcloud.DatacenterClient does not implement DatacenterClientBase (wrong type for method GetByID) have GetByID(context.Context, int64) (*hcloud.Datacenter, *hcloud.Response, error) want GetByID(context.Context, int) (*hcloud.Datacenter, *hcloud.Response, error) src/github.com/hetznercloud/cli/internal/hcapi2/client.go:81:40: cannot use (value of type *hcloud.FirewallClient) as FirewallClientBase value in argument to NewFirewallClient: *hcloud.FirewallClient does not implement FirewallClientBase (wrong type for method GetByID) have GetByID(context.Context, int64) (*hcloud.Firewall, *hcloud.Response, error) want GetByID(context.Context, int) (*hcloud.Firewall, *hcloud.Response, error) src/github.com/hetznercloud/cli/internal/hcapi2/client.go:90:44: cannot use (value of type *hcloud.FloatingIPClient) as FloatingIPClientBase value in argument to NewFloatingIPClient: *hcloud.FloatingIPClient does not implement FloatingIPClientBase (wrong type for method GetByID) have GetByID(context.Context, int64) (*hcloud.FloatingIP, *hcloud.Response, error) want GetByID(context.Context, int) (*hcloud.FloatingIP, *hcloud.Response, error) src/github.com/hetznercloud/cli/internal/hcapi2/client.go:99:42: cannot use (value of type *hcloud.PrimaryIPClient) as PrimaryIPClientBase value in argument to NewPrimaryIPClient: *hcloud.PrimaryIPClient does not implement PrimaryIPClientBase (wrong type for method GetByID) have GetByID(context.Context, int64) (*hcloud.PrimaryIP, *hcloud.Response, error) want GetByID(context.Context, int) (*hcloud.PrimaryIP, *hcloud.Response, error) src/github.com/hetznercloud/cli/internal/hcapi2/client.go:108:34: cannot use (value of type *hcloud.ImageClient) as ImageClientBase value in argument to NewImageClient: *hcloud.ImageClient does not implement ImageClientBase (wrong type
Bug#1054195: cppgir FTBFS: ERROR could not find GIR for GObject-2.0
Source: cppgir Version: 0~git20231003.e856d76-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cppgir=0~git20231003.e856d76-1 ... [ 39%] Generating wrapper code for: GObject-2.0;Gio-2.0;Gst-1.0;Gtk-3.0 cd "/<>" && "/<>/obj-aarch64-linux-gnu/cppgir" --class --class-full --optional --ignore data/cppgir.ignore:data/cppgir_unix.ignore --output /tmp/gi GObject-2.0 Gio-2.0 Gst-1.0 Gtk-3.0 ERROR could not find GIR for GObject-2.0 make[3]: *** [CMakeFiles/wrappers.dir/build.make:78: /tmp/gi] Error 1
Bug#1054177: [Debichem-devel] Bug#1054177: src:cp2k: fails to migrate to testing for too long: no longer buildable on armel
Hi, On 18-10-2023 21:46, Michael Banck wrote: On Wed, Oct 18, 2023 at 07:28:14PM +0200, Paul Gevers wrote: 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. I am not sure it is out of my control or not, but the issue seems to be that armel is not able to run the dbcsr testsuite without timing out, so a cp2k Build-Depends is missing. If it *feels* out of control, you should just file a bug against ftp.debian.org and ask for the removal of the binaries of cp2k from armel. Once dbcsr is fixed, cp2k will be tried again on armel and might come back. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054177: [Debichem-devel] Bug#1054177: src:cp2k: fails to migrate to testing for too long: no longer buildable on armel
Hi, On Wed, Oct 18, 2023 at 07:28:14PM +0200, Paul Gevers wrote: > 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. I am not sure it is out of my control or not, but the issue seems to be that armel is not able to run the dbcsr testsuite without timing out, so a cp2k Build-Depends is missing. Michael
Processed: migration is blocked and the bug technically doesn't affect trixie
Processing commands for cont...@bugs.debian.org:
> tag 1052819 - trixie
Bug #1052819 {Done: Felix Geyer }
[src:golang-github-mattn-go-runewidth] golang-github-mattn-go-runewidth: FTBFS:
dh_auto_test: error: cd _build && go test -vet=off -v -p 8
github.com/mattn/go-runewidth returned exit code 1
Removed tag(s) trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054178: src:octave-ltfat: fails to migrate to testing for too long: FTBFS on armel
Source: octave-ltfat Version: 2.5.0+dfsg-2 Severity: serious Control: close -1 2.6.0+dfsg-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:octave-ltfat has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails to build from source on armel. 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=octave-ltfat OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:octave-ltfat: fails to migrate to testing for too long: FTBFS on armel
Processing control commands: > close -1 2.6.0+dfsg-1 Bug #1054178 [src:octave-ltfat] src:octave-ltfat: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions octave-ltfat/2.6.0+dfsg-1. Bug #1054178 [src:octave-ltfat] src:octave-ltfat: fails to migrate to testing for too long: FTBFS on armel Marked Bug as done -- 1054178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:cp2k: fails to migrate to testing for too long: no longer buildable on armel
Processing control commands: > close -1 2023.2-1 Bug #1054177 [src:cp2k] src:cp2k: fails to migrate to testing for too long: no longer buildable on armel Marked as fixed in versions cp2k/2023.2-1. Bug #1054177 [src:cp2k] src:cp2k: fails to migrate to testing for too long: no longer buildable on armel Marked Bug as done -- 1054177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054177: src:cp2k: fails to migrate to testing for too long: no longer buildable on armel
Source: cp2k Version: 2023.1-2 Severity: serious Control: close -1 2023.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:cp2k has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable can no longer be build on armel because libdbcsr-dev isn't build on armel. Please either help the dbcsr maintainer to build dbcsr on armel, or ask the ftp masters to remove cp2k from armel (in unstable). 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=cp2k OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1053776: marked as done (tuiwidgets: catch2 v3 breaks tests)
Your message dated Wed, 18 Oct 2023 17:22:24 + with message-id and subject line Bug#1053776: fixed in tuiwidgets 0.2-2 has caused the Debian Bug report #1053776, regarding tuiwidgets: catch2 v3 breaks 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.) -- 1053776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tuiwidgets Version: 0.2-1.1 Severity: serious Justification: debci catch2 v3 was recently uploaded and breaks tuiwidgets's tests The needed patch is likely to be simple, similar to the one prepared for termpaint --- End Message --- --- Begin Message --- Source: tuiwidgets Source-Version: 0.2-2 Done: Christoph Hueffelmann We believe that the bug you reported is fixed in the latest version of tuiwidgets, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Hueffelmann (supplier of updated tuiwidgets 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, 15 Oct 2023 22:22:39 +0200 Source: tuiwidgets Architecture: source Version: 0.2-2 Distribution: unstable Urgency: medium Maintainer: Christoph Hueffelmann Changed-By: Christoph Hueffelmann Closes: 1047905 1053776 Changes: tuiwidgets (0.2-2) unstable; urgency=medium . * Update salsa ci to enable build package twice and fix (Closes: #1047905) * catch2 v3 breaks tests (Closes: 1053776) * debian/libtuiwidgets0a.symbols: Add additional optional symbol from armhf build. Checksums-Sha1: 3a1059b8169649bf833b41fce72c2c52325787de 2284 tuiwidgets_0.2-2.dsc dc61a92834f6013577d5f6e5ba02ac3b4263 7988 tuiwidgets_0.2-2.debian.tar.xz 0def10132761df1136528d5ae610438a6410266f 11813 tuiwidgets_0.2-2_source.buildinfo Checksums-Sha256: 16adcc8f597989992baca6b8768beb979c84b33508e6707103c53bcb5d3a1c8a 2284 tuiwidgets_0.2-2.dsc bfd4ac56171812972e27936e6b7294dd50d65dca71bf5f7fd1925231418fad9f 7988 tuiwidgets_0.2-2.debian.tar.xz 8344a189e40f4d204b7853fde8ded9a64d5526745d2919e6c36cacc44e9a86f3 11813 tuiwidgets_0.2-2_source.buildinfo Files: 6a47a76a6b5919b1ec5a7e27d0827ea4 2284 libs optional tuiwidgets_0.2-2.dsc 3138c7231bacd1df595379f1913d428d 7988 libs optional tuiwidgets_0.2-2.debian.tar.xz 2f5a0da3795f58a596e9d034814279b1 11813 libs optional tuiwidgets_0.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUwEOEQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJApDAC7bhiXbQKo3axocBj8HYGRaY3KhX01E4F6 w1tSrO2IzK8l5uTKMGzssAHYbEtKMkWo52yH4Zflk+INsSA9JfCvRL74zuDLV9a5 SUmr1ZE3wEgmmudIGNpzobSHYPcvETelk4Gm/JYlmabHet40rxM560X2Qu6vGpDM osVNtTNUB3kY1krxWd/wBs/aQUcs3qbvgAQdDvWQwFmhnrCFXyD09g7ilpy6cLpc 19jxpRLoc3b4GGTBDoRsI7oa5gmT1iAKGIJGRbH3Y6stHahoRRgN9kZ+Ea8BI2zU b3DULZ2f5OrRMDxaGDmLwL+gHZCz8JI88K58QLSBust0pyvP1wRWq9j0VXxnVkg3 MhAdaSYaEnn4kUeymn3IztEuhICCINyU7KuIOJd/BhyG2lzzXh0gQTCXxniRLU95 gMXMdfM+SB7/Z2UNtgsBNxXyrt2b3UBzCiPHHm5W9u05k2egkjQPkEGdjsdqe5co juXHPj5XzpvCaEwsN2JiTV1ap8xvlME= =hdtP -END PGP SIGNATURE End Message ---
Bug#1054169: ares 132-1 fails to build on many architectures
Control: severity -1 important (this is not RC as it never has been built on those architectures before)
Processed: Re: Bug#1054169: ares 132-1 fails to build on many architectures
Processing control commands: > severity -1 important Bug #1054169 [src:ares] ares 132-1 fails to build on many architectures Severity set to 'important' from 'serious' -- 1054169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054042: marked as done (librandombytes-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librandombytes.a)
Your message dated Wed, 18 Oct 2023 16:36:37 +
with message-id
and subject line Bug#1054042: fixed in librandombytes 0~20230919-2
has caused the Debian Bug report #1054042,
regarding librandombytes-dev has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/librandombytes.a
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.)
--
1054042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librandombytes-dev
Version: 0~20230919-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libnacl-dev
librandombytes-dev has an undeclared file conflict. This may result in
an unpack error from dpkg.
The file /usr/lib/x86_64-linux-gnu/librandombytes.a is contained in the
packages
* libnacl-dev/20110221-12 as present in bookworm|trixie|unstable
* librandombytes-dev/0~20230919-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: librandombytes
Source-Version: 0~20230919-2
Done: Simon Josefsson
We believe that the bug you reported is fixed in the latest version of
librandombytes, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon Josefsson (supplier of updated librandombytes
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 18 Oct 2023 18:20:43 +0200
Source: librandombytes
Architecture: source
Version: 0~20230919-2
Distribution: unstable
Urgency: medium
Maintainer: Jan Mojžíš
Changed-By: Simon Josefsson
Closes: 1054042
Changes:
librandombytes (0~20230919-2) unstable; urgency=medium
.
[ Jan Mojžíš ]
* d/compiler/{gcc,clang}: add debian compiler wrappers. It adds Debian
specifific options distributed in $CC, $CFLAGS, $CPPFLAGS and $LDFLAGS
* d/control: add Conflicts: libnacl-dev (<< 20110221-13~)
The libnacl-dev package contained until version 20110221-12 the
/usr/lib//librandombytes.a file, which caused the conflict.
Since version 20110221-13 is the /usr/lib//librandombytes.a file
removed from libnacl-dev and libnacl-dev depends on librandombytes library.
(Closes: #1054042)
* d/control add Multi-Arch: same
* d/rules add DEB_BUILD_MAINT_OPTIONS = optimize=+lto
* d/rules add DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,noexecstack
* d/tests/ autopkg tests simplified, all tests uses randombytes-info source
Checksums-Sha1:
72f970c5d18ef335b3e47f07711ec4c51b52dac0 1608 librandombytes_0~20230919-2.dsc
986b78c4416ab5d88b5dd9c5e7a684e16c1351f0 4708
librandombytes_0~20230919-2.debian.tar.xz
b7642523e74c74ea6dd9a3101f39d4d90cc49a06 7012
librandombytes_0~20230919-2_amd64.buildinfo
Checksums-Sha256:
211e91ea58cfce80d343922a025a4452c80c1812e38814a6118e2efc0b3a8a6c 1608
librandombytes_0~20230919-2.dsc
a138a237319e47189365275144c2eb0f1ea93728fd0af79598cf8a774f5e9afd 4708
librandombytes_0~20230919-2.debian.tar.xz
3fae0dfda28fc3fe8cb2ae62c19f0f473036eec05da327fa19ec4719d8d21306 7012
librandombytes_0~20230919-2_amd64.buildinfo
Files:
73296f5951fbb477bfd1bffa8c4ee75c 1608 libs optional
librandombytes_0~20230919-2.dsc
3daa2fe06625bcace6f6152414227ea8 4708 libs optional
librandombytes_0~20230919-2.debian.tar.xz
589a121f4a8bbc9ff8c3c06dbbea4657 7012 libs optional
librandombytes_0~20230919-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iIoEARYIADIWIQSjzJyHC50xCrrUzy9RcisI/kdFogUCZTAGMxQcc2ltb25Aam9z
ZWZzc29uLm9yZwAKCRBRcisI/kdFop35AP0XUBw7iL6ODTvX6ONIE3Za6Pr2Odo2
Processed: found 1054167 in 2.0.0-3
Processing commands for cont...@bugs.debian.org: > found 1054167 2.0.0-3 Bug #1054167 [src:node-grunt-legacy-log] ftbfs: AssertionError in tests Marked as found in versions node-grunt-legacy-log/2.0.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1053880 in 7.4.5-1, fixed 1053880 in 7.12.12+~cs150.141.84-6+deb11u1 ...
Processing commands for cont...@bugs.debian.org:
> found 1053880 7.4.5-1
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7:
CVE-2023-45133
Marked as found in versions node-babel7/7.4.5-1.
> fixed 1053880 7.12.12+~cs150.141.84-6+deb11u1
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7:
CVE-2023-45133
Marked as fixed in versions node-babel7/7.12.12+~cs150.141.84-6+deb11u1.
> fixed 1053880 7.20.15+ds1+~cs214.269.168-3+deb12u1
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7:
CVE-2023-45133
Marked as fixed in versions node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054176: node-rollup-plugin-typescript: failing dh_auto_test
Source: node-rollup-plugin-typescript
Version: 11.1.2~ds+~1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sweetyf...@deepin.org
Hi,
During a rebuild of your package in unstable, your package fails to
build from source.
Full log can be accessed at:
https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-rollup-plugin-typescript/Debian_Unstable/aarch64
Tail of log for your package:
not ok 81 one.js
---
operator: ok
expected: true
actual: false
at: Test.
(/usr/src/packages/BUILD/packages/typescript/test/test.js:927:9)
stack: |-
Error: one.js
at Test.assert [as _assert]
(/usr/share/nodejs/tape/lib/test.js:312:48)
at Test.bound [as _assert]
(/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.assert (/usr/share/nodejs/tape/lib/test.js:431:7)
at Test.bound [as true]
(/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.
(/usr/src/packages/BUILD/packages/typescript/test/test.js:927:9)
...
not ok 82 /* eslint-disable */ function one() { console.log('one'); }
export { one };
---
operator: ok
expected: true
actual: false
at: Test.
(/usr/src/packages/BUILD/packages/typescript/test/test.js:928:9)
stack: |-
Error: /* eslint-disable */
function one() {
console.log('one');
}
export { one };
at Test.assert [as _assert]
(/usr/share/nodejs/tape/lib/test.js:312:48)
at Test.bound [as _assert]
(/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.assert (/usr/share/nodejs/tape/lib/test.js:431:7)
at Test.bound [as true]
(/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.
(/usr/src/packages/BUILD/packages/typescript/test/test.js:928:9)
...
...
1..105
# tests 105
# pass 103
# fail 2
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit
code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
Thanks!
Tianyu Chen @ deepin
Bug#1054175: node-require-main-filename: failing dh_auto_test
Source: node-require-main-filename
Version: 2.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sweetyf...@deepin.org
Hi,
During a rebuild of your package in unstable, your package fails to
build from source.
Full log can be accessed at:
https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-require-main-filename/Debian_Unstable/aarch64
Tail of log for your package:
# Subtest: should default to process.cwd() if require.main is
undefined
not ok 1 - expected '/usr/src/packages/BUILD' to match
/(?:.*autopkgtest.*|require-main-filename)/
---
stack: |
Test. (test.js:34:36)
Test.
(/usr/share/nodejs/tap/lib/mocha.js:93:20)
Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
/usr/share/nodejs/libtap/lib/test.js:369:21
Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
Test.runMain
(/usr/share/nodejs/libtap/lib/base.js:178:15)
/usr/share/nodejs/libtap/lib/test.js:490:13
Test.writeSubComment
(/usr/share/nodejs/libtap/lib/test.js:561:5)
Test.
(/usr/share/nodejs/libtap/lib/test.js:489:14)
loop (/usr/share/nodejs/function-loop/index.js:19:13)
Test.
(/usr/share/nodejs/libtap/lib/test.js:892:9)
loop (/usr/share/nodejs/function-loop/index.js:19:13)
TAP.runBeforeEach
(/usr/share/nodejs/libtap/lib/test.js:898:7)
Test.runBeforeEach
(/usr/share/nodejs/libtap/lib/test.js:891:19)
Test.processSubtest
(/usr/share/nodejs/libtap/lib/test.js:488:12)
Test.process
(/usr/share/nodejs/libtap/lib/test.js:405:14)
Test.sub (/usr/share/nodejs/libtap/lib/test.js:234:10)
Test.test (/usr/share/nodejs/libtap/lib/test.js:258:17)
it (/usr/share/nodejs/tap/lib/mocha.js:92:5)
Suite.fn (test.js:33:3)
Test.
(/usr/share/nodejs/tap/lib/mocha.js:33:24)
Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
/usr/share/nodejs/libtap/lib/test.js:369:21
Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
Test.runMain
(/usr/share/nodejs/libtap/lib/base.js:178:15)
/usr/share/nodejs/libtap/lib/test.js:490:13
TAP.writeSubComment
(/usr/share/nodejs/libtap/lib/test.js:561:5)
Test.
(/usr/share/nodejs/libtap/lib/test.js:489:14)
loop (/usr/share/nodejs/function-loop/index.js:19:13)
TAP.runBeforeEach
(/usr/share/nodejs/libtap/lib/test.js:898:7)
TAP.processSubtest
(/usr/share/nodejs/libtap/lib/test.js:488:12)
TAP.process
(/usr/share/nodejs/libtap/lib/test.js:405:14)
TAP.sub (/usr/share/nodejs/libtap/lib/test.js:234:10)
TAP.test (/usr/share/nodejs/libtap/lib/test.js:258:17)
Suite.run (/usr/share/nodejs/tap/lib/mocha.js:29:7)
new Suite (/usr/share/nodejs/tap/lib/mocha.js:24:10)
describe (/usr/share/nodejs/tap/lib/mocha.js:8:3)
Object. (test.js:8:1)
Module.replacementCompile
(/usr/share/nodejs/append-transform/index.js:60:13)
Object.
(/usr/share/nodejs/append-transform/index.js:64:4)
at:
line: 34
column: 36
file: test.js
function: Test.
type: AssertionError
showDiff: false
actual: /usr/src/packages/BUILD
expected: null
operator: strictEqual
tapCaught: testFunctionThrow
test: should default to process.cwd() if require.main is
undefined
source: >2
it('should default to process.cwd() if require.main
is undefined', function () {
requireMainFilename({}).should.match(/(?:.*autopkgtest.*|require-main-filename)/)
---^
})
})
...
1..1
# failed 1 test
not ok 4 - should default to process.cwd() if require.main is
undefined # time=55.202ms
1..4
# failed 1 of 4 tests
Bug#1054174: node-clean-css: failed dh_auto_test
Source: node-clean-css Version: 5.3.1+~5.6.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sweetyf...@deepin.org Hi, During a rebuild of your package in unstable, your package fails to build from source. Full log can be accessed at: https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-clean-css/Debian_Unstable/x86_64 Tail of log for your package: ✗ Errored » Asynchronous Error in protocol imports in test/protocol-imports-test.js/usr/src/packages/BUILD/test/protocol-imports-test.js:706 this.proxyServer.destroy(); ^ TypeError: Cannot read properties of undefined (reading 'destroy') at Object.teardown (/usr/src/packages/BUILD/test/protocol-imports-test.js:706:24) at runTeardown (/usr/share/nodejs/vows/lib/vows/suite.js:382:37) at Object.tryEnd (/usr/share/nodejs/vows/lib/vows/suite.js:362:17) at EventEmitter. (/usr/share/nodejs/vows/lib/vows.js:94:18) at EventEmitter.emit (node:events:525:35) at options.Emitter.emit (/usr/share/nodejs/vows/lib/vows.js:241:24) at /usr/share/nodejs/vows/lib/vows/context.js:31:52 at process.processTicksAndRejections (node:internal/process/task_queues:77:11) Node.js v18.13.0 dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Thanks! Tianyu Chen @ deepin
Processed: found 1053880 in 7.20.15+ds1+~cs214.269.168-4
Processing commands for cont...@bugs.debian.org:
> found 1053880 7.20.15+ds1+~cs214.269.168-4
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7:
CVE-2023-45133
Marked as found in versions node-babel7/7.20.15+ds1+~cs214.269.168-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1053880
Processing commands for cont...@bugs.debian.org:
> tags 1053880 + upstream
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7:
CVE-2023-45133
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1053238: marked as done (tracker-miners: Fails to build on many architectures, failed to load seccomp rules)
Your message dated Wed, 18 Oct 2023 15:53:11 + with message-id and subject line Bug#1053238: fixed in tracker-miners 3.4.5-3 has caused the Debian Bug report #1053238, regarding tracker-miners: Fails to build on many architectures, failed to load seccomp rules 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.) -- 1053238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tracker-miners Version: 3.4.5-1 Severity: serious Tags: ftbfs sid Forwarded: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/280 The latest version of tracker-miners fails to build on most of our architectures. Reported upstream. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: tracker-miners Source-Version: 3.4.5-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of tracker-miners, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated tracker-miners 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, 18 Oct 2023 10:37:25 -0400 Source: tracker-miners Built-For-Profiles: noudeb Architecture: source Version: 3.4.5-3 Distribution: unstable Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1053238 1053881 Changes: tracker-miners (3.4.5-3) unstable; urgency=high . * Cherry-pick proposed patches to fix build on various architectures (Closes: #1053238) * Update changelog entry for 3.4.5-1 to acknowledge CVE fix . tracker-miners (3.4.5-2) unstable; urgency=high . * Cherry-pick build fixes . tracker-miners (3.4.5-1) unstable; urgency=high . * New upstream bugfix release - Includes sandbox hardening to fix CVE-2023-5557 (Closes: #1053881) Checksums-Sha1: 76a55c8a34ecdcf392588adc9d1203e76e2bb769 3258 tracker-miners_3.4.5-3.dsc 8211f4804dd3a3090cfde1db36f5b525592ef780 18808 tracker-miners_3.4.5-3.debian.tar.xz 06327c79a287ce81fe65b7731bb96a7427439109 19293 tracker-miners_3.4.5-3_source.buildinfo Checksums-Sha256: 200b09cd73546db0d480bd9b6461b8da09ee80e63e90c54575d632e79d4ddee4 3258 tracker-miners_3.4.5-3.dsc 2e8a9f0beeb55639cc24bea243721e33de133b9b60d52310aa1675e71f1883b2 18808 tracker-miners_3.4.5-3.debian.tar.xz f1d0fa7380bd2edb12aca75a4c8d7a5956250a6f8aea7bcb42b8c11eba767392 19293 tracker-miners_3.4.5-3_source.buildinfo Files: cfbc4afb18202c590fa07ed708a65acc 3258 utils optional tracker-miners_3.4.5-3.dsc cdd6fd7526e71591cd2a3ee6fcc44e68 18808 utils optional tracker-miners_3.4.5-3.debian.tar.xz 87affdca5d6269f66f4f9e23cf9bb5ef 19293 utils optional tracker-miners_3.4.5-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmUv+ToACgkQ5mx3Wuv+ bH3YRBAAtS+3RrgPJrSC1bDJz762wCO2kKa0VMV07OCeXmRGz8XiEqKBWY3cIVau c3ySwyjBZTyPtHCQLJdOuHEOqt7np7bD/RKWmqUdFPVI5h2CFs4Z7ZXso0u6Xp4N u3RNju7GNH0SN7iE2rpxE/zNkzA9FS3KzejfWbd2RtxUq2a03fOUla/ofwbVNaD5 k63XEhyGZbSahZqX6Ym6TcOOYNGoRs2n59m5UqgzHisPnfBM+Ijbcq6Ksb2b+nq9 CofzLlzPh++ethgi1zr8bxlsYj3MwMzUfBvWQ1sqT02fPrykWYPqPPVOj+WcN4K/ ZtQPSlIUGU6OGdreFzu46zEnzeHaEOmflP27hH4hFOIo8lD29prqViBnjSnCw8gx v8F7v2zkgHTdZd7dgkICJjHrn2HQptbgXQcV2yz+upuFZ6uapwMzlaKpD69fUsrW U/owZP3yeQXRI4Kbxl3VYj/dvkBaoF3vufH6fqIUaJBGkpDtnZ6gobNOAc/f2uVA DZtBUBQNoz/YVnaCaDPKSWOhYI1r/nh+MTxUOFzUr+F7hoUrRr1lwFGlUdcrL64X jZXBHFzzBCz/T0J8X6/gspBKMQ9Fym/t5RKfhrbWWT+fBulsadiPufoaFh7EoobD aR4klCjl9HSbcR9HTlX3wFEyJVhRB4iufgNheikQ+wJ3OK+Ajns= =sME9 -END PGP SIGNATURE End Message ---
Bug#1054169: ares 132-1 fails to build on many architectures
Source: ares Version: 126-3 Severity: serious Justification: FTBFS X-Debbugs-Cc: bdr...@debian.org Dear Maintainer, ares 132-1 fails to build on many architectures (like armhf, i386, etc): ``` debian/rules clean dh clean --sourcedirectory=desktop-ui dh_auto_clean -O--sourcedirectory=desktop-ui cd desktop-ui && make -j4 distclean make[1]: Entering directory '/<>/desktop-ui' ../nall/GNUmakefile:123: *** unknown arch, please specify manually.. Stop. make[1]: Leaving directory '/<>/desktop-ui' ``` dh_auto_build is called with arch='$(ares_arch)'. So dh_auto_clean should be called with that parameter as well. -- Benjamin Drung Debian & Ubuntu Developer
Processed: retitle 1054157 to mdevctl: env-logger build dependency should be strict enough for the requirement
Processing commands for cont...@bugs.debian.org: > retitle 1054157 mdevctl: env-logger build dependency should be strict enough > for the requirement Bug #1054157 [src:mdevctl] mdevctl: env-logger should be strict enough for the requirement Changed Bug title to 'mdevctl: env-logger build dependency should be strict enough for the requirement' from 'mdevctl: env-logger should be strict enough for the requirement'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053238: marked as pending in tracker-miners
Control: tag -1 pending Hello, Bug #1053238 in tracker-miners reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/tracker-miners/-/commit/ad95ff72958b81cdea3c4bacd9c61500b117e0de Cherry-pick proposed patches to fix build on various architectures Closes: #1053238 (this message was generated automatically) -- Greetings https://bugs.debian.org/1053238
Processed: Bug#1053238 marked as pending in tracker-miners
Processing control commands: > tag -1 pending Bug #1053238 [src:tracker-miners] tracker-miners: Fails to build on many architectures, failed to load seccomp rules Added tag(s) pending. -- 1053238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053768: marked as done (posixsignalmanager: tests fail with catch2 v3)
Your message dated Wed, 18 Oct 2023 15:13:04 + with message-id and subject line Bug#1053768: fixed in posixsignalmanager 0.3-4 has caused the Debian Bug report #1053768, regarding posixsignalmanager: tests fail with catch2 v3 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.) -- 1053768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: posixsignalmanager Version: 0.3-3 Severity: serious Justification: debci Control: forwarded -1 https://github.com/textshell/posixsignalmanager/issues/2 Control: tags -1 patch catch2 v3 was recently uploaded, and breaks posixsignalmanager's tests Upstream has prepared a patch, https://github.com/textshell/posixsignalmanager/pull/3 --- End Message --- --- Begin Message --- Source: posixsignalmanager Source-Version: 0.3-4 Done: Christoph Hueffelmann We believe that the bug you reported is fixed in the latest version of posixsignalmanager, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Hueffelmann (supplier of updated posixsignalmanager 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, 15 Oct 2023 00:00:14 +0200 Source: posixsignalmanager Architecture: source Version: 0.3-4 Distribution: unstable Urgency: medium Maintainer: Christoph Hueffelmann Changed-By: Christoph Hueffelmann Closes: 1053768 Changes: posixsignalmanager (0.3-4) unstable; urgency=medium . * Add support for catch2 version-3.x (Closes: #1053768) * Update patch to support riscv from upstream. Checksums-Sha1: ae097ff0503656f547a2c76c32badcf79b56e817 2100 posixsignalmanager_0.3-4.dsc 7fae5a5321c91e0afe3b2fc3753a2474f25eb1ad 8240 posixsignalmanager_0.3-4.debian.tar.xz e5f2058c297f2004c078c7082c623d3a3c48f490 9759 posixsignalmanager_0.3-4_source.buildinfo Checksums-Sha256: 79dad3d18a72b6cbfed22a1cef85cb85df251849c517353d0497f969fc18 2100 posixsignalmanager_0.3-4.dsc 61492d8a99ae7c587c6c780e006d67a671f99858dd899c93385115f2e4bdc9f0 8240 posixsignalmanager_0.3-4.debian.tar.xz 68439ff4a7f9d1e707abfb757483c6991a3b3c182b5a4a0564aea26c6466ee4b 9759 posixsignalmanager_0.3-4_source.buildinfo Files: 27129f4d4853d4370908452b0546c5a2 2100 libs optional posixsignalmanager_0.3-4.dsc 5d5fc32a4a244457f778d901345973db 8240 libs optional posixsignalmanager_0.3-4.debian.tar.xz bbe230bbf4dbb23f5d6c92f24707ed4a 9759 libs optional posixsignalmanager_0.3-4_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUv7M4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFFTlC/9AafTAnKsdXe37V+ovp3YVZLFmTSJ93O0Q rUjHBQM0TQu3YLCWqmGQj6ulWw9PKWYmznxhCdNHt/vdD2lV4E/5FkgqVt5p7RPV LeCsyqaL9IkmhlUJzXquZOMxTYwiZcfo4VSiNbZYh3w0B4eBR9cq4RtYZ0zjAjQd VAaBNXVfli3q1WvM5CYPAtpU11nfrF+4IlAO1mDBjAk1Y/nZI5VfLDEPMM51lEPD 6Rdh8xQueNiWGC4VV2bH+6GN2oTHbmC4uIwYnUS1Uywx7SKlxhKaqOPnoO9olEfw mZM3D6R9cnOxUhj9aOXevfN8QjCvI4MEt8r4PjKCwAEMCBwj5cymhhHExTVbLvx+ 17lYvFXwNUYa+XEZ+0HgZINPH7MZ2YtXh75c2Qgj0nQpG+qX7QkFFbTiFIVhLSFY xqfx/MfARh1foML9uU1FA72+5XLFJLwVwlWgZznIwFoSL6oh87AU0u3I3aEurLjw VlJk1CRXzKz7tdEzEs+fW6gaUGiH6qg= =AVix -END PGP SIGNATURE End Message ---
Processed: fixed 1053769 in 1.57.0-1
Processing commands for cont...@bugs.debian.org: > fixed 1053769 1.57.0-1 Bug #1053769 [src:nghttp2] nghttp2: CVE-2023-44487 Marked as fixed in versions nghttp2/1.57.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1053769 in 1.52.0-1
Processing commands for cont...@bugs.debian.org: > found 1053769 1.52.0-1 Bug #1053769 [src:nghttp2] nghttp2: CVE-2023-44487 Marked as found in versions nghttp2/1.52.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1053769, bug 1053769 is forwarded to https://github.com/nghttp2/nghttp2/pull/1961
Processing commands for cont...@bugs.debian.org: > tags 1053769 + upstream Bug #1053769 [src:nghttp2] nghttp2: CVE-2023-44487 Added tag(s) upstream. > forwarded 1053769 https://github.com/nghttp2/nghttp2/pull/1961 Bug #1053769 [src:nghttp2] nghttp2: CVE-2023-44487 Set Bug forwarded-to-address to 'https://github.com/nghttp2/nghttp2/pull/1961'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1053801, found 1053801 in 9.2.2+ds-1
Processing commands for cont...@bugs.debian.org: > tags 1053801 + upstream Bug #1053801 [src:trafficserver] trafficserver: CVE-2023-44487 Added tag(s) upstream. > found 1053801 9.2.2+ds-1 Bug #1053801 [src:trafficserver] trafficserver: CVE-2023-44487 Marked as found in versions trafficserver/9.2.2+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051645: marked as done (dogecoin: FTBFS: error: ‘runtime_error’ is not a member of ‘std’)
Your message dated Wed, 18 Oct 2023 14:36:18 +
with message-id
and subject line Bug#1051645: fixed in dogecoin 1.14.6-3
has caused the Debian Bug report #1051645,
regarding dogecoin: FTBFS: error: ‘runtime_error’ is not a member of ‘std’
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.)
--
1051645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dogecoin
Version: 1.14.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
dogecoin fails to build from source. From my build log on amd64:
| g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../src/config -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=2 -I. -I./obj -pthread -I/usr/include -I./leveldb/include
-I./leveldb/helpers/memenv -I./secp256k1/include -I./univalue/include
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
-Wstack-protector -fstack-protector-all -fPIE -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o
support/libdogecoin_util_a-lockedpool.o `test -f 'support/lockedpool.cpp' ||
echo './'`support/lockedpool.cpp
| support/lockedpool.cpp: In member function ‘void Arena::free(void*)’:
| support/lockedpool.cpp:99:20: error: ‘runtime_error’ is not a member of ‘std’
|99 | throw std::runtime_error("Arena: invalid or double free");
| |^
| support/lockedpool.cpp:31:1: note: ‘std::runtime_error’ is defined in header
‘’; did you forget to ‘#include ’?
|30 | #include
| +++ |+#include
|31 |
| support/lockedpool.cpp: In member function ‘void LockedPool::free(void*)’:
| support/lockedpool.cpp:307:16: error: ‘runtime_error’ is not a member of ‘std’
| 307 | throw std::runtime_error("LockedPool: invalid address not
pointing to any arena");
| |^
| support/lockedpool.cpp:307:16: note: ‘std::runtime_error’ is defined in
header ‘’; did you forget to ‘#include ’?
| make[3]: *** [Makefile:6428: support/libdogecoin_util_a-lockedpool.o] Error 1
| make[3]: Leaving directory '/<>/src'
| make[2]: *** [Makefile:9818: all-recursive] Error 1
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:694: all-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:17: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=dogecoin=riscv64=1.14.6-2=1694349873=0
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: dogecoin
Source-Version: 1.14.6-3
Done: Bo YU
We believe that the bug you reported is fixed in the latest version of
dogecoin, 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.
Bo YU (supplier of updated dogecoin 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, 17 Oct 2023 11:16:04 +0800
Source: dogecoin
Architecture: source
Version: 1.14.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team
Changed-By: Bo YU
Closes: 1051645
Changes:
dogecoin (1.14.6-3) unstable; urgency=medium
.
* Team upload
* Fix gcc-13 build issue (Closes: #1051645)
* Applied compatibility with qt 5.15.8 and boost 1.81.0 from upstream
otherwise this will lead to ftbfs, see d/patches/0006-fix-boost-1-18.patch
* Update d/libdogecoinconsensus0.symbols.amd64
Checksums-Sha1:
eb77e67969964303bf79a11726c24e71cf04bd7a 2103 dogecoin_1.14.6-3.dsc
54360bec9714e964a5a73dd0cdb4f76c915cfc6b 13732 dogecoin_1.14.6-3.debian.tar.xz
243a3ff30eb33cf07598be2bcf708cf858ce05e4 11039
dogecoin_1.14.6-3_source.buildinfo
Checksums-Sha256:
44c4682df5e9680ac95a52cb56e4b891934ca9acd9011fd3d20acc42d1de4c2b 2103
dogecoin_1.14.6-3.dsc
258e4369340213466bd1c3414cfb156702d7163badb3bee55c985d7aaf148283 13732
Bug#1054167: ftbfs: AssertionError in tests
Source: node-grunt-legacy-log Version: 1.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sweetyf...@deepin.org Hi, During a rebuild of your package in unstable, your package fails to build from source. Full log can be accessed at: https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-grunt-legacy-log/Debian_Unstable/x86_64 Tail of log for your package: [31m✖ Log instance - writeflags[39m AssertionError: 'Flags: a, b\n' == 'Flags: \x1B[36ma\x1B[39m, \x1B[36mb\x1B[39m\n' at Object.equal (/usr/share/nodejs/nodeunit/lib/types.js:83:39) at stdoutEqual (/usr/src/packages/BUILD/test/index.js:26:8) at Object.writeflags (/usr/src/packages/BUILD/test/index.js:210:5) at /usr/share/nodejs/nodeunit/lib/core.js:232:20 at /usr/share/javascript/async/async.js:254:17 at /usr/share/javascript/async/async.js:157:25 at /usr/share/javascript/async/async.js:251:21 at /usr/share/javascript/async/async.js:615:34 at Object.setUp (/usr/src/packages/BUILD/test/index.js:57:5) at /usr/share/nodejs/nodeunit/lib/core.js:260:35 AssertionError: 'Prefix: a, b\n' == 'Prefix: \x1B[36ma\x1B[39m, \x1B[36mb\x1B[39m\n' at Object.equal (/usr/share/nodejs/nodeunit/lib/types.js:83:39) at stdoutEqual (/usr/src/packages/BUILD/test/index.js:26:8) at Object.writeflags (/usr/src/packages/BUILD/test/index.js:213:5) at /usr/share/nodejs/nodeunit/lib/core.js:232:20 at /usr/share/javascript/async/async.js:254:17 at /usr/share/javascript/async/async.js:157:25 at /usr/share/javascript/async/async.js:251:21 at /usr/share/javascript/async/async.js:615:34 at Object.setUp (/usr/src/packages/BUILD/test/index.js:57:5) at /usr/share/nodejs/nodeunit/lib/core.js:260:35 AssertionError: 'Prefix: a, b=false, c=0, d=null\n' == 'Prefix: \x1B[36ma\x1B[39m, \x1B[36mb=false\x1B[39m, \x1B[36mc=0\x1B[39m, \x1B[36md=null\x1B[39m\n' at Object.equal (/usr/share/nodejs/nodeunit/lib/types.js:83:39) at stdoutEqual (/usr/src/packages/BUILD/test/index.js:26:8) at Object.writeflags (/usr/src/packages/BUILD/test/index.js:216:5) at /usr/share/nodejs/nodeunit/lib/core.js:232:20 at /usr/share/javascript/async/async.js:254:17 at /usr/share/javascript/async/async.js:157:25 at /usr/share/javascript/async/async.js:251:21 at /usr/share/javascript/async/async.js:615:34 at Object.setUp (/usr/src/packages/BUILD/test/index.js:57:5) at /usr/share/nodejs/nodeunit/lib/core.js:260:35 Thanks! Tianyu Chen @ deepin
Bug#1054166: ruby-appraiser-rubocop 1.0.1-2 has invalid dependencies
Package: ruby-appraiser-rubocop Version: 1.0.1-2 Severity: serious Justification: uninstallable X-Debbugs-Cc: bdr...@debian.org Dear Maintainer, ruby-appraiser-rubocop 1.0.1-2 has invalid dependencies: ``` The following packages have unmet dependencies: ruby-appraiser-rubocop : Depends: ruby-rubocop (>= 0.9) but it is not installable Depends: ruby-ruby-appraiser (>= 1.0.3) but it is not installable ``` The dependencies should probably be rubocop and ruby-appraiser instead. -- Benjamin Drung Debian & Ubuntu Developer
Bug#1054164: libowasp-antisamy-java: CVE-2023-43643
Source: libowasp-antisamy-java Version: 1.5.3+dfsg-1.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libowasp-antisamy-java. Note: The severity is set to RC, though 'important' would better fit. It looks that in each supported version in Debian we are still at 1.5.3. Is the library still maintained within Debian? CVE-2023-43643[0]: | AntiSamy is a library for performing fast, configurable cleansing of | HTML coming from untrusted sources. Prior to version 1.7.4, there is | a potential for a mutation XSS (mXSS) vulnerability in AntiSamy | caused by flawed parsing of the HTML being sanitized. To be subject | to this vulnerability the `preserveComments` directive must be | enabled in your policy file and also allow for certain tags at the | same time. As a result, certain crafty inputs can result in elements | in comment tags being interpreted as executable when using | AntiSamy's sanitized output. This issue has been patched in AntiSamy | 1.7.4 and later. 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-43643 https://www.cve.org/CVERecord?id=CVE-2023-43643 [1] https://github.com/nahsra/antisamy/security/advisories/GHSA-pcf2-gh6g-h5r2 [2] https://github.com/nahsra/antisamy/commit/05c52b98bb845b8175b8406bd2f391ce334a05d6 Regards, Salvatore
Processed: reassign 1054133 to wnpp, reassign 1054035 to src:mpich, merging 1053973 1053974 ..., affects 1034251 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1054133 wnpp
Bug #1054133 [itp] ITP: bidscoin -- a toolkit to convert raw neuroimaging data
according to the BIDS standard
Warning: Unknown package 'itp'
Bug reassigned from package 'itp' to 'wnpp'.
Ignoring request to alter found versions of bug #1054133 to the same values
previously set
Ignoring request to alter fixed versions of bug #1054133 to the same values
previously set
> reassign 1054035 src:mpich 4.1.2-2
Bug #1054035 [src:mpch] mpich: FTBFS on ppc64 due to bogus architecture check
in debian/rules
Warning: Unknown package 'src:mpch'
Bug reassigned from package 'src:mpch' to 'src:mpich'.
No longer marked as found in versions mpch/4.1.2-2.
Ignoring request to alter fixed versions of bug #1054035 to the same values
previously set
Bug #1054035 [src:mpich] mpich: FTBFS on ppc64 due to bogus architecture check
in debian/rules
Marked as found in versions mpich/4.1.2-2.
> merge 1053973 1053974
Bug #1053973 {Done: Yogeswaran Umasankar } [a2d] a2d: New
upstream version available v2.0.1 -- APRS to DAPNET portal.
Warning: Unknown package 'a2d'
Bug #1053974 {Done: Yogeswaran Umasankar } [a2d] ITP:
a2d/2.0.1-1 New upstream version available v2.0.1 -- APRS to DAPNET portal
Merged 1053973 1053974
Warning: Unknown package 'a2d'
> reassign 1053974 wnpp
Bug #1053974 {Done: Yogeswaran Umasankar } [a2d] ITP:
a2d/2.0.1-1 New upstream version available v2.0.1 -- APRS to DAPNET portal
Bug #1053973 {Done: Yogeswaran Umasankar } [a2d] a2d: New
upstream version available v2.0.1 -- APRS to DAPNET portal.
Warning: Unknown package 'a2d'
Bug reassigned from package 'a2d' to 'wnpp'.
Bug reassigned from package 'a2d' to 'wnpp'.
No longer marked as found in versions 2.0.1-1.
No longer marked as found in versions 2.0.1-1.
Ignoring request to alter fixed versions of bug #1053974 to the same values
previously set
Ignoring request to alter fixed versions of bug #1053973 to the same values
previously set
> fixed 1003010 1:2.1.5-2
Bug #1003010 {Done: Debian FTP Masters }
[fonts-liberation2] fonts-liberation2: please Provides fonts-liberation
Marked as fixed in versions fonts-liberation/1:2.1.5-2.
> reassign 1034251 ansible-core 2.14.3-1
Bug #1034251 {Done: Lee Garrett } [ansible] ansible:
package should recommend python3-passlib
Bug reassigned from package 'ansible' to 'ansible-core'.
No longer marked as found in versions ansible/7.3.0+dfsg-1.
No longer marked as fixed in versions ansible-core/2.14.6-1.
Bug #1034251 {Done: Lee Garrett } [ansible-core] ansible:
package should recommend python3-passlib
Marked as found in versions ansible-core/2.14.3-1.
> affects 1034251 + src:ansible
Bug #1034251 {Done: Lee Garrett } [ansible-core] ansible:
package should recommend python3-passlib
Added indication that 1034251 affects src:ansible
> fixed 1034251 2.14.6-1
Bug #1034251 {Done: Lee Garrett } [ansible-core] ansible:
package should recommend python3-passlib
Marked as fixed in versions ansible-core/2.14.6-1.
> reassign 990538 src:testng7
Bug #990538 {Done: Vladimir Petko } [src:testng]
Please package a new testng version 7.x
Bug reassigned from package 'src:testng' to 'src:testng7'.
Ignoring request to alter found versions of bug #990538 to the same values
previously set
No longer marked as fixed in versions testng7/7.5-1.
> fixed 990538 7.5-1
Bug #990538 {Done: Vladimir Petko } [src:testng7]
Please package a new testng version 7.x
Marked as fixed in versions testng7/7.5-1.
> affects 990538 + src:testng
Bug #990538 {Done: Vladimir Petko } [src:testng7]
Please package a new testng version 7.x
Added indication that 990538 affects src:testng
> reassign 886098 drbl 2.20.11-1
Bug #886098 {Done: Georges Khaznadar } [clonezilla]
bios/mbr.bin: No such file or directory
Bug reassigned from package 'clonezilla' to 'drbl'.
No longer marked as found in versions clonezilla/3.27.16-1.
No longer marked as fixed in versions drbl/5.2.12-2.
Bug #886098 {Done: Georges Khaznadar } [drbl]
bios/mbr.bin: No such file or directory
Marked as found in versions drbl/2.20.11-1.
> fixed 886098 5.2.12-2
Bug #886098 {Done: Georges Khaznadar } [drbl]
bios/mbr.bin: No such file or directory
There is no source info for the package 'drbl' at version '5.2.12-2' with
architecture ''
Unable to make a source version for version '5.2.12-2'
Marked as fixed in versions 5.2.12-2.
> affects 886098 + src:clonezilla
Bug #886098 {Done: Georges Khaznadar } [drbl]
bios/mbr.bin: No such file or directory
Added indication that 886098 affects src:clonezilla
> reassign 1034062 src:preseed
Bug #1034062 {Done: Cyril Brulebois } [netcfg] netcfg prompts
for hostname even though preseeded, preventing unattended installation
Bug reassigned from package 'netcfg' to 'src:preseed'.
No longer marked as found in versions netcfg/1.184.
No longer marked as fixed in versions preseed/1.115.
> fixed 1034062 1.115
Bug #1034062 {Done: Cyril Brulebois } [src:preseed] netcfg
prompts for hostname even though preseeded, preventing
Bug#1052953: marked as done (pg-fact-loader: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Wed, 18 Oct 2023 14:09:00 +0200
with message-id
and subject line Re: Bug#1052953: pg-fact-loader: FTBFS: Error: debian/control
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #1052953,
regarding pg-fact-loader: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
1052953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pg-fact-loader
Version: 1.7.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f pg_fact_loader.so pg_fact_loader.o \
> pg_fact_loader.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2022-10-24 18:30:11.0 +
> +++ debian/control.9bLn6U 2023-09-26 06:43:17.232176210 +
> @@ -8,8 +8,8 @@
> Homepage: https://github.com/enova/pg_fact_loader
> Vcs-Git: https://github.com/enova/pg_fact_loader.git
>
> -Package: postgresql-15-pg-fact-loader
> +Package: postgresql-16-pg-fact-loader
> Architecture: any
> -Depends: postgresql-15, ${shlibs:Depends}, ${misc:Depends}
> +Depends: postgresql-16, ${shlibs:Depends}, ${misc:Depends}
> Description: Build fact tables asynchronously with Postgres
> - Use queue tables to build fact tables asynchronously for PostgreSQL 15.
> + Use queue tables to build fact tables asynchronously for PostgreSQL 16.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:10: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/pg-fact-loader_1.7.0-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 2.0.1-1
Re: Lucas Nussbaum
> > + Use queue tables to build fact tables asynchronously for PostgreSQL 16.
> > Error: debian/control needs updating from debian/control.in. Run
> > 'pg_buildext updatecontrol'.
> > If you are seeing this message in a buildd log, a sourceful upload is
> > required.
Fixed in the last upload.
Christoph--- End Message ---
Bug#1054157: mdevctl: env-logger should be strict enough for the requirement
Source: mdevctl Version: 1.2.0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mdevctl=arm64=1.2.0-4%2Bb3=1697626199=0 ... Merged Build-Depends: ..., librust-env-logger+default-dev, ... The following NEW packages will be installed: ... librust-env-logger-0.7+default-dev librust-env-logger-0.7-dev ... error: failed to select a version for the requirement `env_logger = "^0.10.0"` ... librust-env-logger-0.7+default-dev providing librust-env-logger+default-dev is also a bug (#1054156), but when mdevctl only accepts 0.10.0 the build dependency should express this by using librust-env-logger-0.10.0+default-dev instead of librust-env-logger+default-dev so that building is not even attempted with an incompatible version.
Bug#1054156: librust-env-logger-0.7+default-dev shouldn't provide librust-env-logger+default-dev
Package: librust-env-logger-0.7+default-dev Severity: serious https://buildd.debian.org/status/fetch.php?pkg=mdevctl=arm64=1.2.0-4%2Bb3=1697626199=0 ... Merged Build-Depends: ..., librust-env-logger+default-dev, ... The following NEW packages will be installed: ... librust-env-logger-0.7+default-dev librust-env-logger-0.7-dev ... error: failed to select a version for the requirement `env_logger = "^0.10.0"` ... This is due to: librust-env-logger+default-dev reverse Provides: librust-env-logger-0.7+default-dev 0.7.1-4 (= 0.7.1-4) librust-env-logger-dev 0.10.0-2 (= 0.10.0-2) I'll file a separate bug for mdevctl having a too loose build dependency.
Processed: Re: libxsimd-dev: arm64 error in xtensor: usage of batch type with unsupported type
Processing control commands: > severity 1053090 important Bug #1053090 [libxtensor-dev] libxsimd-dev: arm64 error in xtensor: usage of batch type with unsupported type Severity set to 'important' from 'serious' -- 1053090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053090: libxsimd-dev: arm64 error in xtensor: usage of batch type with unsupported type
Source: xtensor Version: 0.24.7-4 Followup-For: Bug #1053090 Control: severity 1053090 important xsimd support is optional for xtensor. Use of batch is apparently not expected to be routinely used anyway. See further discussion at https://github.com/xtensor-stack/xsimd/issues/945 In summary, xtensor can be run on arm64 (and armel) without xsimd, and batch support should not be considered release-critical. For these reasons I'm downgrading this bug to Severity: important. It wouldn't be constructive to remove xtensor from testing.
Bug#1053870: CVE-2023-42118: integer underflow in libspf2 resulting in RCE
Dear Salvatore, I don't disagree with your statement. However, many have already tried to reach ZDI and have not received clear communication. Perhaps Debain can add to the pressure to get more clarity? While the ZDI webpage on this CVE claims they contacted the developer, it's unclear whether they contacted exim or libspf2 and exactly what information they shared. However, this does not take away that the current pull request fixes a potential RCE (whether it's part of this CVE or not) that should, with some urgency, get packaged and released. Many other distros have already done so, and Debian is lagging behind. This is even more serious considering exim is the default MTA on Debian, while many other distros opt for postfix. Kind regards, Bert Van de Poel On 18/10/2023 11:56, Salvatore Bonaccorso wrote: Hi, On Fri, Oct 13, 2023 at 12:05:19PM +0200, Bert Van de Poel wrote: Package: libspf2-2 Version: 1.2.10-7.1~deb11u1 Severity: critical Tags: security patch Justification: root security hole X-Debbugs-Cc: Debian Security Team As already outlined on https://security-tracker.debian.org/tracker/CVE-2023-42118 there's a known security issue in libspf2 found through a security review of Exim by the Zero Day Initiative. An integer underflow in libspf2 was found which can be used to perform RCEs. A patch on https://github.com/shevek/libspf2/pull/44 is available and has been merged into the main repository. All relevant links are already available on the Debian Security Tracker. Please note that as already outlined in the security-tracker and on the upstream issue there is still no confirmation from ZDI that the two issues are the same. So no, we cannot consider the pull/44 from upstream the fix for CVE-2023-42118. Better communication on that matter from the anonymous reporter would be very helpfull to clarify the libspf2 status. Regards, Salvatore
Bug#1054154: python3-aiortc 1.5.0-2 autopkgtest autodep8-python3 failure
Package: python3-aiortc Version: 1.5.0-2 Severity: serious X-Debbugs-Cc: bdr...@debian.org Dear Maintainer, python3-aiortc 1.5.0-2 introduces an autopkgtest regression for autodep8-python3: ``` Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aiortc/__init__.py", line 23, in from .rtcpeerconnection import RTCPeerConnection File "/usr/lib/python3/dist-packages/aiortc/rtcpeerconnection.py", line 9, in from . import clock, rtp, sdp File "/usr/lib/python3/dist-packages/aiortc/sdp.py", line 17, in from .rtcsctptransport import RTCSctpCapabilities File "/usr/lib/python3/dist-packages/aiortc/rtcsctptransport.py", line 25, in from crc32c import crc32c ModuleNotFoundError: No module named 'crc32c' ``` Please extend the package dependency to solve the import failure. -- Benjamin Drung Debian & Ubuntu Developer
Processed: tagging 1053870
Processing commands for cont...@bugs.debian.org: > tags 1053870 - patch Bug #1053870 [libspf2-2] CVE-2023-42118: integer underflow in libspf2 resulting in RCE Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1053870 is grave, tagging 1053870
Processing commands for cont...@bugs.debian.org: > severity 1053870 grave Bug #1053870 [libspf2-2] CVE-2023-42118: integer underflow in libspf2 resulting in RCE Severity set to 'grave' from 'critical' > tags 1053870 + moreinfo upstream Bug #1053870 [libspf2-2] CVE-2023-42118: integer underflow in libspf2 resulting in RCE Added tag(s) moreinfo and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053870: CVE-2023-42118: integer underflow in libspf2 resulting in RCE
Hi, On Fri, Oct 13, 2023 at 12:05:19PM +0200, Bert Van de Poel wrote: > Package: libspf2-2 > Version: 1.2.10-7.1~deb11u1 > Severity: critical > Tags: security patch > Justification: root security hole > X-Debbugs-Cc: Debian Security Team > > > As already outlined on > https://security-tracker.debian.org/tracker/CVE-2023-42118 there's a > known security issue in libspf2 found through a security review of > Exim by the Zero Day Initiative. An integer underflow in libspf2 was > found which can be used to perform RCEs. A patch on > https://github.com/shevek/libspf2/pull/44 is available and has been > merged into the main repository. All relevant links are already > available on the Debian Security Tracker. Please note that as already outlined in the security-tracker and on the upstream issue there is still no confirmation from ZDI that the two issues are the same. So no, we cannot consider the pull/44 from upstream the fix for CVE-2023-42118. Better communication on that matter from the anonymous reporter would be very helpfull to clarify the libspf2 status. Regards, Salvatore
Bug#1054153: yaml-cpp: FTBFS: dh_makeshlibs: error: failing due to earlier errors
Source: yaml-cpp
Version: 0.8.0+dfsg-4
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=yaml-cpp=amd64=0.8.0%2Bdfsg-4=1696872119=0
--- debian/libyaml-cpp0.8.symbols (libyaml-cpp0.8_0.8.0+dfsg-4_amd64)
+++ dpkg-gensymbolslh0zg7 2023-10-09 17:21:53.571506237 +
@@ -60,20 +60,27 @@
_ZN4YAML11KeyNotFoundD0Ev@Base 0.7.0
_ZN4YAML11KeyNotFoundD1Ev@Base 0.7.0
_ZN4YAML11KeyNotFoundD2Ev@Base 0.7.0
-
(subst)_ZN4YAML11NodeBuilder10OnMapStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}NS_12EmitterStyle5valueE@Base
0.8.0
+
_ZN4YAML11NodeBuilder10OnMapStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmNS_12EmitterStyle5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder10OnMapStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}NS_12EmitterStyle5valueE@Base
0.8.0
_ZN4YAML11NodeBuilder13OnDocumentEndEv@Base 0.8.0
_ZN4YAML11NodeBuilder13OnSequenceEndEv@Base 0.8.0
- (subst)_ZN4YAML11NodeBuilder14RegisterAnchorE{size_t}RNS_6detail4nodeE@Base
0.8.0
+ _ZN4YAML11NodeBuilder14RegisterAnchorEmRNS_6detail4nodeE@Base 0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder14RegisterAnchorE{size_t}RNS_6detail4nodeE@Base
0.8.0
_ZN4YAML11NodeBuilder15OnDocumentStartERKNS_4MarkE@Base 0.8.0
-
(subst)_ZN4YAML11NodeBuilder15OnSequenceStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}NS_12EmitterStyle5valueE@Base
0.8.0
+
_ZN4YAML11NodeBuilder15OnSequenceStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmNS_12EmitterStyle5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder15OnSequenceStartERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}NS_12EmitterStyle5valueE@Base
0.8.0
_ZN4YAML11NodeBuilder3PopEv@Base 0.8.0
- (subst)_ZN4YAML11NodeBuilder4PushERKNS_4MarkE{size_t}@Base 0.8.0
+ _ZN4YAML11NodeBuilder4PushERKNS_4MarkEm@Base 0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder4PushERKNS_4MarkE{size_t}@Base 0.8.0
_ZN4YAML11NodeBuilder4PushERNS_6detail4nodeE@Base 0.8.0
_ZN4YAML11NodeBuilder4RootEv@Base 0.8.0
- (subst)_ZN4YAML11NodeBuilder6OnNullERKNS_4MarkE{size_t}@Base 0.8.0
- (subst)_ZN4YAML11NodeBuilder7OnAliasERKNS_4MarkE{size_t}@Base 0.8.0
+ _ZN4YAML11NodeBuilder6OnNullERKNS_4MarkEm@Base 0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder6OnNullERKNS_4MarkE{size_t}@Base 0.8.0
+ _ZN4YAML11NodeBuilder7OnAliasERKNS_4MarkEm@Base 0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder7OnAliasERKNS_4MarkE{size_t}@Base 0.8.0
_ZN4YAML11NodeBuilder8OnMapEndEv@Base 0.8.0
-
(subst)_ZN4YAML11NodeBuilder8OnScalarERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}SB_@Base
0.8.0
+
_ZN4YAML11NodeBuilder8OnScalarERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmSB_@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML11NodeBuilder8OnScalarERKNS_4MarkERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE{size_t}SB_@Base
0.8.0
_ZN4YAML11NodeBuilderC1Ev@Base 0.8.0
_ZN4YAML11NodeBuilderC2Ev@Base 0.8.0
_ZN4YAML11NodeBuilderD0Ev@Base 0.8.0
@@ -101,21 +108,27 @@
_ZN4YAML12EmitterState15SetStringFormatENS_13EMITTER_MANIPENS_8FmtScope5valueE@Base
0.8.0
_ZN4YAML12EmitterState16SetOutputCharsetENS_13EMITTER_MANIPENS_8FmtScope5valueE@Base
0.8.0
_ZN4YAML12EmitterState17SetBoolCaseFormatENS_13EMITTER_MANIPENS_8FmtScope5valueE@Base
0.8.0
-
(subst)_ZN4YAML12EmitterState17SetFloatPrecisionE{size_t}NS_8FmtScope5valueE@Base
0.8.0
-
(subst)_ZN4YAML12EmitterState18SetDoublePrecisionE{size_t}NS_8FmtScope5valueE@Base
0.8.0
+ _ZN4YAML12EmitterState17SetFloatPrecisionEmNS_8FmtScope5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML12EmitterState17SetFloatPrecisionE{size_t}NS_8FmtScope5valueE@Base
0.8.0
+ _ZN4YAML12EmitterState18SetDoublePrecisionEmNS_8FmtScope5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML12EmitterState18SetDoublePrecisionE{size_t}NS_8FmtScope5valueE@Base
0.8.0
_ZN4YAML12EmitterState19SetBoolLengthFormatENS_13EMITTER_MANIPENS_8FmtScope5valueE@Base
0.8.0
-
(subst)_ZN4YAML12EmitterState19SetPreCommentIndentE{size_t}NS_8FmtScope5valueE@Base
0.8.0
-
(subst)_ZN4YAML12EmitterState20SetPostCommentIndentE{size_t}NS_8FmtScope5valueE@Base
0.8.0
+ _ZN4YAML12EmitterState19SetPreCommentIndentEmNS_8FmtScope5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML12EmitterState19SetPreCommentIndentE{size_t}NS_8FmtScope5valueE@Base
0.8.0
+ _ZN4YAML12EmitterState20SetPostCommentIndentEmNS_8FmtScope5valueE@Base
0.8.0+dfsg-4
+#MISSING: 0.8.0+dfsg-4#
(subst)_ZN4YAML12EmitterState20SetPostCommentIndentE{size_t}NS_8FmtScope5valueE@Base
0.8.0
_ZN4YAML12EmitterState21ClearModifiedSettingsEv@Base 0.8.0
Bug#1029342: marked as done (jexec: can't locate java: No such file or directory)
Your message dated Wed, 18 Oct 2023 08:30:31 + with message-id and subject line Bug#1029342: fixed in openjdk-17 17.0.9+9-1 has caused the Debian Bug report #1029342, regarding jexec: can't locate java: 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.) -- 1029342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: request-tracker5 Version: 5.0.3+dfsg-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > make: Circular configure <- build-stamp dependency dropped. > dh_testdir > # Update translations > debconf-updatepo > # Keep aside automatically generated files shipped in the upstream tarball > mkdir bak > find . -name '*.in' -print | egrep -v '\.pc|\.\/debian' | sed -e 's/\.in$//' > | while read f; do mkdir -p bak/`dirname $f`; mv -v $f bak/$f; done > renamed './etc/RT_Config.pm' -> 'bak/./etc/RT_Config.pm' > renamed './etc/upgrade/vulnerable-passwords' -> > 'bak/./etc/upgrade/vulnerable-passwords' > renamed './etc/upgrade/shrink-cgm-table' -> > 'bak/./etc/upgrade/shrink-cgm-table' > renamed './etc/upgrade/upgrade-authtokens' -> > 'bak/./etc/upgrade/upgrade-authtokens' > renamed './etc/upgrade/time-worked-history' -> > 'bak/./etc/upgrade/time-worked-history' > renamed './etc/upgrade/upgrade-articles' -> > 'bak/./etc/upgrade/upgrade-articles' > renamed './etc/upgrade/switch-templates-to' -> > 'bak/./etc/upgrade/switch-templates-to' > renamed './etc/upgrade/4.0-customfield-checkbox-extension' -> > 'bak/./etc/upgrade/4.0-customfield-checkbox-extension' > renamed './etc/upgrade/sanity-check-stylesheets' -> > 'bak/./etc/upgrade/sanity-check-stylesheets' > renamed './etc/upgrade/shrink-transactions-table' -> > 'bak/./etc/upgrade/shrink-transactions-table' > renamed './etc/upgrade/upgrade-sla' -> 'bak/./etc/upgrade/upgrade-sla' > renamed './etc/upgrade/upgrade-assets' -> 'bak/./etc/upgrade/upgrade-assets' > renamed './etc/upgrade/generate-rtaddressregexp' -> > 'bak/./etc/upgrade/generate-rtaddressregexp' > renamed './etc/upgrade/reset-sequences' -> 'bak/./etc/upgrade/reset-sequences' > renamed './etc/upgrade/3.8-ical-extension' -> > 'bak/./etc/upgrade/3.8-ical-extension' > renamed './etc/upgrade/upgrade-configurations' -> > 'bak/./etc/upgrade/upgrade-configurations' > renamed './t/data/configs/apache2.2+mod_perl.conf' -> > 'bak/./t/data/configs/apache2.2+mod_perl.conf' > renamed './t/data/configs/apache2.4+fcgid.conf' -> > 'bak/./t/data/configs/apache2.4+fcgid.conf' > renamed './t/data/configs/apache2.4+mod_perl.conf' -> > 'bak/./t/data/configs/apache2.4+mod_perl.conf' > renamed './t/data/configs/apache2.2+fastcgi.conf' -> > 'bak/./t/data/configs/apache2.2+fastcgi.conf' > renamed './t/data/configs/apache2.4+fastcgi.conf' -> > 'bak/./t/data/configs/apache2.4+fastcgi.conf' > renamed './lib/RT/Generated.pm' -> 'bak/./lib/RT/Generated.pm' > renamed './sbin/rt-dump-metadata' -> 'bak/./sbin/rt-dump-metadata' > renamed './sbin/rt-passwd' -> 'bak/./sbin/rt-passwd' > renamed './sbin/rt-shredder' -> 'bak/./sbin/rt-shredder' > renamed './sbin/rt-preferences-viewer' -> 'bak/./sbin/rt-preferences-viewer' > renamed './sbin/rt-search-attributes' -> 'bak/./sbin/rt-search-attributes' > renamed './sbin/rt-server.fcgi' -> 'bak/./sbin/rt-server.fcgi' > renamed './sbin/rt-serializer' -> 'bak/./sbin/rt-serializer' > renamed './sbin/rt-externalize-attachments' -> > 'bak/./sbin/rt-externalize-attachments' > renamed './sbin/rt-test-dependencies' -> 'bak/./sbin/rt-test-dependencies' > renamed './sbin/rt-setup-fulltext-index' -> > 'bak/./sbin/rt-setup-fulltext-index' > renamed './sbin/rt-server' -> 'bak/./sbin/rt-server' > renamed './sbin/rt-dump-initialdata' -> 'bak/./sbin/rt-dump-initialdata' > renamed './sbin/standalone_httpd' -> 'bak/./sbin/standalone_httpd' > renamed './sbin/rt-fulltext-indexer' -> 'bak/./sbin/rt-fulltext-indexer' > renamed './sbin/rt-ldapimport' -> 'bak/./sbin/rt-ldapimport' > renamed './sbin/rt-validate-aliases' -> 'bak/./sbin/rt-validate-aliases' > renamed './sbin/rt-attributes-viewer' -> 'bak/./sbin/rt-attributes-viewer' > renamed './sbin/rt-setup-database' -> 'bak/./sbin/rt-setup-database' > renamed './sbin/rt-importer' -> 'bak/./sbin/rt-importer' > renamed './sbin/rt-validator' -> 'bak/./sbin/rt-validator' > renamed './sbin/rt-clean-sessions' ->
Bug#1054150: surf: no longer display web pages after webkitgtk upgrades
Package: surf Version: 2.0+git20201107-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: dominique.marti...@atmark-techno.com Dear Maintainer, After upgrading my system to the latest security updates surf no longer displays anything. The pages actually load, hovering on links shows the cursor changing and links can be clicked, but the page is blank I've tested both in VMs on debian bullseye (this bug report) and debian stable on real hardware (2.1+git20221016-4), both exhibit the same issue. For bullseye, this package upgrade reliably triggers the issue, and installing old packages back makes surf work again: Unpacking libwebkit2gtk-4.0-37:amd64 (2.42.1-1~deb11u1) over (2.40.5-1~deb11u1) ... Unpacking libjavascriptcoregtk-4.0-18:amd64 (2.42.1-1~deb11u1) over (2.40.5-1~deb11u1) ... Thanks you -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf Kernel: Linux 5.10.0-25-amd64 (SMP w/4 CPU threads) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 surf depends on: ii libc62.31-13+deb11u7 ii libgcr-base-3-1 3.38.1-2 ii libgcr-ui-3-13.38.1-2 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4+deb11u3 ii libjavascriptcoregtk-4.0-18 2.42.1-1~deb11u1 ii libwebkit2gtk-4.0-37 2.42.1-1~deb11u1 ii libx11-6 2:1.7.2-1+deb11u2 Versions of packages surf recommends: ii curl 7.74.0-1.3+deb11u10 ii gnome-terminal [x-terminal-emulator] 3.38.3-1 ii suckless-tools46-1 ii x11-utils 7.7+5 ii xterm [x-terminal-emulator] 366-1+deb11u1 Versions of packages surf suggests: ii apparmor 2.13.6-10 -- no debconf information
Bug#1053830: marked as pending in kimageformats
Control: tag -1 pending Hello, Bug #1053830 in kimageformats reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/kimageformats/-/commit/6af4c440a4f8f796f8411baf8ceeaf03bfca7356 debian/rules: Specify -fexcess-precision=fast for i386 to avoid FTBFS due to GCC 13 changing its default behavior. (Closes: #1053830) (this message was generated automatically) -- Greetings https://bugs.debian.org/1053830
Processed: Bug#1053830 marked as pending in kimageformats
Processing control commands: > tag -1 pending Bug #1053830 [src:kimageformats] kimageformats FTBFS with gcc 13 on i386 Ignoring request to alter tags of bug #1053830 to the same tags previously set -- 1053830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1051570 is forwarded to https://github.com/mltframework/mlt/issues/930, tagging 1051570
Processing commands for cont...@bugs.debian.org: > forwarded 1051570 https://github.com/mltframework/mlt/issues/930 Bug #1051570 [src:mlt] mlt: FTBFS with RtAudio 6 Set Bug forwarded-to-address to 'https://github.com/mltframework/mlt/issues/930'. > tags 1051570 + upstream fixed-upstream Bug #1051570 [src:mlt] mlt: FTBFS with RtAudio 6 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
