Bug#1009383: marked as done (gromacs: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable')
Your message dated Sat, 23 Apr 2022 01:49:21 + with message-id and subject line Bug#1009383: fixed in gromacs 2022.1-1 has caused the Debian Bug report #1009383, regarding gromacs: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable' 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.) -- 1009383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gromacs Version: 2021.4-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): > make[4]: Entering directory '/<>/build/documentation' > cd /<>/build/documentation/docs/doxygen && /usr/bin/python3.10 > /<>/docs/doxygen/graphbuilder.py -S /<> -B > /<>/build/documentation --ignore-cycles > /<>/docs/doxygen/cycle-suppressions.txt -o > /<>/build/documentation/docs/doxygen/depgraphs > cd /<>/build/documentation/docs/doxygen && /usr/bin/cmake > -DDOCTYPE=user -P RunDoxygen.cmake > NOTE: You are using Doxygen version 1.9.1. The documentation is designed for > 1.8.5. Other versions may or may not work, but very likely produce extra > warnings. > Running Doxygen... > warning: Tag 'MSCGEN_PATH' at line 36 of file 'Doxyfile-common' has become > obsolete. > To avoid this warning please remove this line from your > configuration file or upgrade it using "doxygen -u" > Scanning source tree... > Reading source files... > Reading Doxygen XML files... > Traceback (most recent call last): > File "/<>/docs/doxygen/graphbuilder.py", line 562, in > main() > File "/<>/docs/doxygen/graphbuilder.py", line 538, in main > tree.load_xml(only_files=True) > File "/<>/docs/doxygen/gmxtree.py", line 819, in load_xml > if isinstance(only_files, collections.Iterable): > AttributeError: module 'collections' has no attribute 'Iterable' > make[4]: *** [docs/doxygen/CMakeFiles/dep-graphs-dot.dir/build.make:76: > docs/doxygen/dep-graphs-dot-timestamp.txt] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/gromacs_2021.4-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: gromacs Source-Version: 2022.1-1 Done: Nicholas Breen We believe that the bug you reported is fixed in the latest version of gromacs, 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. Nicholas Breen (supplier of updated gromacs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 22 Apr 2022 18:22:17 -0700 Source: gromacs Architecture: source Version: 2022.1-1 Distribution: experimental Urgency: medium Maintainer: Debichem Team Changed-By: Nicholas Breen Closes: 1009383 Changes: gromacs (2022.1-1) experimental; urgency=medium . * New upstream release. * Restore mdrun-test-timeout.patch, to handle slow double-precision tests on sparc64. * muparser 2.3.3 now in unstable. Build-Depend on >= 2.3 and remove muparser-version.patch. * python3-collections-iterable.patch: Replace calls to removed collections.Iterable with collections.abc. (Closes: #1009383) Checksums-Sha1: b49d36e3b3abc6ee62a981c165a293f935a442aa 3438 gromacs_2022.1-1.dsc cf52628800bae6357e9277845ac3f3fb7f29a55c 48613957
Bug#1008372: marked as done (sludge: FTBFS: configure: error: Package requirements (glew) were not met)
Your message dated Sat, 23 Apr 2022 01:35:23 + with message-id and subject line Bug#1008372: fixed in sludge 2.2.2-4 has caused the Debian Bug report #1008372, regarding sludge: FTBFS: configure: error: Package requirements (glew) were not met 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.) -- 1008372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sludge Version: 2.2.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking whether gcc understands -c and -o together... yes > checking dependency style of gcc... none > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for glew... no > configure: error: Package requirements (glew) were not met > > Package 'opengl', required by 'glu', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables GLEW_CFLAGS > and GLEW_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/sludge_2.2.2-3_unstable.log 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: sludge Source-Version: 2.2.2-4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of sludge, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated sludge package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Apr 2022 21:21:08 -0400 Source: sludge Architecture: source Version: 2.2.2-4 Distribution: unstable Urgency: high Maintainer: Debian Games Team Changed-By: Boyuan Yang Closes: 1008372 Changes: sludge (2.2.2-4) unstable; urgency=high . * Team upload. * debian/control: Apply "wrap-and-sort -abst". * debian/: Bump debhelper compat to v13. * debian/rules: Drop as-needed linker flag. * debian/control: + Bump Standards-Version to 4.6.0. + Mark sludge-doc as Multi-Arch: foreign. + Use secure URI for homepage information. * debian/patches: Backport upstream patches till 2022-01-14. + dont-include-glext.h.patch: Dropped, merged in upstream trunk. + 0001-Fix-compilation-errors-with-recent-glew-mesa-combos.patch: Fix FTBFS. (Closes: #1008372) * debian/watch: Update to v4 format. Checksums-Sha1: f5fada3d5698c21dd1b582945d10e290ceb03f54 2316 sludge_2.2.2-4.dsc 6356288da1161c3d3b2e4b3ca53d231cec506f2a 2579800 sludge_2.2.2.orig.tar.gz 182479c7418da4e9129dbe17e8f2154c1995cb32 76300 sludge_2.2.2-4.debian.tar.xz 5ffed8ee00a1fa05801903230fc59666e08fe835 15355 sludge_2.2.2-4_amd64.buildinfo Checksums-Sha256: ad495ec25735203ab64a0fd5105b1a2082dce37fd784ecaf564fb0baab0af30b 2316 sludge_2.2.2-4.dsc b8a0504993770b7a931905cc697834bd03b908f0f9b96fe9a1059d6621cf5176 2579800 sludge_2.2.2.orig.tar.gz a033a53924ef7d3f6a8ecae01b773f81cfcb4c71ab9e70a452c84075cafac1c0 76300 sludge_2.2.2-4.debian.tar.xz 64a95a86acc63b589e16fa8ec1f996938ae479065290aa917c6ad7fcabd33baa 15355 sludge_2.2.2-4_amd64.buildinfo Files: a6ab8f30e5fd8a2a8c958556e3b4e396 2316 games optional sludge_2.2.2-4.dsc d0ecf74328046e337b42b1659eceb1f2 2579800 games optional sludge_2.2.2.orig.tar.gz aca3799582dc15e6ea21eb79cd60c9b7 76300
Bug#1008424: audiofile: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2
On Mon, Apr 04, 2022 at 03:25:44PM +0200, Alberto Garcia wrote: > > During a rebuild of all packages in sid, your package failed to > > build on amd64. > > > > > FAIL: FLAC > > This started to happen after flac was updated from 1.3.3-2 to 1.3.4-1. I bisected the changes in flac and the problems started here: commit 159cd6c41a6ec17b36d74043c45a3aa64de90d5e Author: Robert Kausch Date: Thu Oct 29 20:37:40 2020 +0100 libFLAC/stream_decoder.c: Use current position as bound when seeking I submitted a bug report upstream: https://github.com/xiph/flac/issues/327 Berto
Processed: xtron: diff for NMU version 1.1a-14.2
Processing control commands: > tags 965910 + patch Bug #965910 [src:xtron] xtron: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965910 + pending Bug #965910 [src:xtron] xtron: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965910: xtron: diff for NMU version 1.1a-14.2
Control: tags 965910 + patch Control: tags 965910 + pending Dear maintainer, I've prepared an NMU for xtron (versioned as 1.1a-14.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u xtron-1.1a/debian/changelog xtron-1.1a/debian/changelog --- xtron-1.1a/debian/changelog +++ xtron-1.1a/debian/changelog @@ -1,3 +1,10 @@ +xtron (1.1a-14.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/compat: bumped compat level to 7. (Closes: #965910) + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 20:18:27 -0300 + xtron (1.1a-14.1) unstable; urgency=medium * Non-maintainer upload. diff -u xtron-1.1a/debian/compat xtron-1.1a/debian/compat --- xtron-1.1a/debian/compat +++ xtron-1.1a/debian/compat @@ -1 +1 @@ -5 +7
Processed: yasat: diff for NMU version 848-1.2
Processing control commands: > tags 965911 + patch Bug #965911 [src:yasat] yasat: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965911 + pending Bug #965911 [src:yasat] yasat: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965911: yasat: diff for NMU version 848-1.2
Control: tags 965911 + patch Control: tags 965911 + pending Dear maintainer, I've prepared an NMU for yasat (versioned as 848-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru yasat-848/debian/changelog yasat-848/debian/changelog --- yasat-848/debian/changelog 2021-01-03 15:56:33.0 -0300 +++ yasat-848/debian/changelog 2022-04-22 19:36:32.0 -0300 @@ -1,3 +1,16 @@ +yasat (848-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: #965911 + * debian/clean: created to remove some files created from the build process +and forgotten after this. This action will allow package to build twice. + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 19:36:32 -0300 + yasat (848-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru yasat-848/debian/clean yasat-848/debian/clean --- yasat-848/debian/clean 1969-12-31 21:00:00.0 -0300 +++ yasat-848/debian/clean 2022-04-22 19:36:32.0 -0300 @@ -0,0 +1,4 @@ +tests/test_rsa.pem +tests/test_rsa_password.pem +tests/yasat_global.advice +yasat.advices diff -Nru yasat-848/debian/compat yasat-848/debian/compat --- yasat-848/debian/compat 2014-01-24 11:29:46.0 -0200 +++ yasat-848/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru yasat-848/debian/control yasat-848/debian/control --- yasat-848/debian/control2016-08-30 06:04:43.0 -0300 +++ yasat-848/debian/control2022-04-22 19:36:32.0 -0300 @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Corentin LABBE -Build-Depends: debhelper (>= 7.0.50) +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.9.8 Homepage: http://yasat.sourceforge.net/
Bug#965922: zpspell: diff for NMU version 0.4.3-4.2
Control: tags 965922 + patch Control: tags 965922 + pending Dear maintainer, I've prepared an NMU for zpspell (versioned as 0.4.3-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u zpspell-0.4.3/debian/compat zpspell-0.4.3/debian/compat --- zpspell-0.4.3/debian/compat +++ zpspell-0.4.3/debian/compat @@ -1 +1 @@ -5 +7 diff -u zpspell-0.4.3/debian/changelog zpspell-0.4.3/debian/changelog --- zpspell-0.4.3/debian/changelog +++ zpspell-0.4.3/debian/changelog @@ -1,3 +1,10 @@ +zpspell (0.4.3-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/compat: bumped level to 7. (Closes: #965922) + + -- Joao Eriberto Mota Filho Fri, 22 Apr 2022 19:23:46 -0300 + zpspell (0.4.3-4.1) unstable; urgency=low * Non-maintainer upload.
Processed: zpspell: diff for NMU version 0.4.3-4.2
Processing control commands: > tags 965922 + patch Bug #965922 [src:zpspell] zpspell: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965922 + pending Bug #965922 [src:zpspell] zpspell: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965463: marked as done (cntlm: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 22 Apr 2022 19:03:55 + with message-id and subject line Bug#965463: fixed in cntlm 0.92.3-1.1 has caused the Debian Bug report #965463, regarding cntlm: 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.) -- 965463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cntlm Version: 0.92.3-1 Severity: normal Usertags: compat-5-6-removal Hi, The package cntlm 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: cntlm Source-Version: 0.92.3-1.1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of cntlm, 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 cntlm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 17 Apr 2022 15:10:54 -0300 Source: cntlm Architecture: source Version: 0.92.3-1.1 Distribution: unstable Urgency: medium Maintainer: David Watson Changed-By: Joao Eriberto Mota Filho Closes: 965463 Changes: cntlm (0.92.3-1.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. - debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the '-k' option is not supported since compat 12. - Closes: #965463 Checksums-Sha1: f447daa06367d192c7c5d811785492dedf829d8a 1778 cntlm_0.92.3-1.1.dsc c2b678e042f7285a6a19f87d4c2c0694e07d6618 5769 cntlm_0.92.3-1.1.diff.gz 8e4e3d88b490224e623f2984f3bd66a7bff8694d 5658 cntlm_0.92.3-1.1_source.buildinfo Checksums-Sha256: 4d32af9d42f30056126a9c41f8961b8ba34e51ff41d84facb6d4c7a6fe1b3e05 1778 cntlm_0.92.3-1.1.dsc dcd1f72c8f20ae715c3158286725c9b32a7fef213e9fc99524d60c7c75adae59 5769 cntlm_0.92.3-1.1.diff.gz 2b9b6b114ec5c895d3279c7717b99d1e60e8cd3cabdcc890208eca8f933ff203 5658 cntlm_0.92.3-1.1_source.buildinfo Files: fb148243a5afdac159f36bfa4dee3605 1778 net optional cntlm_0.92.3-1.1.dsc 8dda877c9917b9a5a241a93a844a0c23 5769 net optional cntlm_0.92.3-1.1.diff.gz ef24c047ff27a73e85ae3e60b79ca8d9 5658 net optional cntlm_0.92.3-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJcXJwACgkQ3mO5xwTr 6e/qnBAAiXj9MHYhxF/J7ScJsIYwNwjQbI64HWMK3LQt8dbMXwAGJ7s/H9XWDUf+ /i421ZZKR8/vWMfDSyExSeiGTLC/HObyj0s3ASNB8I5ifAzete+lpA//1bqL6j2R 9PRgGc1Di8CQXeIQizohL6Kz53VQ1sjzn/7b3FHCzzWHKAQ74VYieO5RdgkkQXEI ktR3rGSM8yuoNUULViwGDIGj2D7rhy+pDpu2Md11AJHnI+8r6H/Q9CCUs5a1d52M V66i3DPdHqspebTiVxfARA7iXtW9L+NGrB7yqTH1668wnA2Le4QcfU+Y4+pS3+Bd rnGD/qEf4DUfxMvL8RRMkWOfxQWxV5tCUPCAa9NN4Ag3/ifGbkca42SMDZISiI/q WIG4jXyX3pKbxQF2OwvOZceYp8W78N51/yrKCsW31e0YLxy6tR23v435dpkVDY9D Cv3hZqr7f+hVa5/AxE065GHkaOet2NbOy6vSEPn2bmJws4AVhnzkJLO+4QLekNIE
Bug#1009473: marked as done (claws-mail: FTBFS: perl.h:736:25: error: expected expression before ‘do’)
Your message dated Fri, 22 Apr 2022 18:17:31 +0200 with message-id <20220422181731.4028b0ba@busgosu> and subject line Re: Bug#1009473: claws-mail: FTBFS: perl.h:736:25: error: expected expression before ‘do’ has caused the Debian Bug report #1009473, regarding claws-mail: FTBFS: perl.h:736:25: error: expected expression before ‘do’ 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.) -- 1009473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: claws-mail Version: 4.0.0-3 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): > /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../.. -I../../../src -I../../../src/common -I../../../src > -I../../../src/gtk -pthread -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -DGTK_DISABLE_SINGLE_INCLUDES -DGSEAL_ENABLE -pthread > -I/usr/include/enchant-2 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_REENTRANT -D_GNU_SOURCE > -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include > -D_LARGEFILE_SOURCE -I/usr/lib/x86_64-linux-gnu/perl/5.34/CORE -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -Wno-unused-function -Wno-pointer-sign -Wall -D_GNU_SOURCE -c -o > perl_la-perl_gtk.lo `test -f 'perl_gtk.c' || echo './'`perl_gtk.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src > -I../../../src/common -I../../../src -I../../../src/gtk -pthread > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -DGTK_DISABLE_SINGLE_INCLUDES -DGSEAL_ENABLE -pthread > -I/usr/include/enchant-2 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_REENTRANT -D_GNU_SOURCE > -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include > -D_LARGEFILE_SOURCE -I/usr/lib/x86_64-linux-gnu/perl/5.34/CORE -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -Wno-unused-function -Wno-pointer-sign -Wall -D_GNU_SOURCE -c perl_plugin.c > -fPIC -DPIC -o .libs/perl_la-perl_plugin.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src > -I../../../src/common -I../../../src -I../../../src/gtk -pthread > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu > -I/usr/include/libmount -I/usr/include/blkid
Bug#1009597: marked as done (node-recast: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Fri, 22 Apr 2022 16:19:19 + with message-id and subject line Bug#1009597: fixed in node-recast 0.21.0-3 has caused the Debian Bug report #1009597, regarding node-recast: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-recast Version: 0.21.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): > make[1]: Entering directory '/<>' > tsc > make[1]: Leaving directory '/<>' >dh_auto_test --buildsystem=nodejs > ln -s ../. node_modules/recast > /bin/sh -ex debian/tests/pkg-js/test > + mocha -r ts-node/register test/babel.ts > > > Babel > undefined basic printing (65ms) > undefined babel 6: should not wrap IIFE when reusing nodes > undefined should not disappear when surrounding code changes > undefined should not disappear when an import is added and `export` is > used inline > undefined should not disappear when an import is added and `export > default` is used inline > undefined should not print delimiters with type annotations > undefined should parenthesize ** operator arguments when lower precedence > undefined should parenthesize ** operator arguments as needed when same > precedence > undefined should be able to replace top-level statements with leading > empty lines > undefined should parse and print dynamic import(...) > undefined tolerates circular references (95ms) > undefined prints numbers in bases other than 10 without converting them > undefined prints the export-default-from syntax > undefined avoids extra semicolons on mutated blocks containing a 'use > strict' directive > undefined should print typescript class elements modifiers > > > 15 passing (230ms) > > + mocha -r ts-node/register test/comments.ts > > > comments > undefined [acorn] attachment and reprinting > undefined [acorn] TrailingComments > undefined [acorn] BodyTrailingComments > undefined [acorn] ParamTrailingComments > undefined [acorn] StatementTrailingComments > undefined [acorn] ProtoAssignComment > undefined [acorn] should correctly attach to concise methods > undefined [acorn] should attach comments as configurable > undefined [acorn] should be reprinted when modified > undefined [acorn] should preserve stray non-comment syntax > undefined [acorn] should be reprinted even if dangling > undefined [acorn] should attach to program.body[0] instead of program > undefined [acorn] should not collapse multi line function definitions > undefined [acorn] should be pretty-printable in illegal positions > undefined [acorn] should preserve correctness when a return expression > has a comment > undefined [acorn] should wrap in parens when the return expression has > nested leftmost comment > undefined [acorn] should not wrap in parens when the return expression > has an interior comment > undefined [acorn] should correctly handle a lonesome comment (alt 1) > undefined [acorn] should correctly handle a not-so-lonesome comment (alt > 2 - trailing whitespace) > undefined [acorn] should correctly handle a lonesome comment (alt 3 - > trailing whitespace) > undefined [acorn] should not reformat a return statement that is not > modified > undefined [acorn] should correctly handle a removing the argument from a > return > undefined [acorn] should preserve comments attached to EmptyStatement > undefined [babel] attachment and reprinting > undefined [babel] TrailingComments > undefined [babel] BodyTrailingComments > undefined [babel] ParamTrailingComments > undefined [babel] StatementTrailingComments > undefined [babel] ProtoAssignComment > undefined [babel] should correctly attach to concise methods > undefined [babel] should attach comments as configurable > undefined [babel] should be reprinted when modified > undefined [babel] should preserve stray non-comment syntax > undefined [babel] should be reprinted even if dangling > undefined [babel] should attach to program.body[0] instead of program > undefined [babel] should not collapse multi line function definitions
Processed: tagging 1009598
Processing commands for cont...@bugs.debian.org: > tags 1009598 + help Bug #1009598 [src:node-katex] node-katex: FTBFS: TypeError: this.getOptions is not a function Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1009597 marked as pending in node-recast
Processing control commands: > tag -1 pending Bug #1009597 [src:node-recast] node-recast: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1009597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009597: marked as pending in node-recast
Control: tag -1 pending Hello, Bug #1009597 in node-recast 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-recast/-/commit/2c5743b9ae4ba7bf741672406d05e7488806de25 Drop typescript test Closes: #1009597 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009597
Bug#1009581: marked as done (node-zrender: FTBFS: @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation'.)
Your message dated Fri, 22 Apr 2022 15:33:47 + with message-id and subject line Bug#1009581: fixed in node-zrender 5.3.1+dfsg-2 has caused the Debian Bug report #1009581, regarding node-zrender: FTBFS: @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation'. 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.) -- 1009581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-zrender Version: 5.3.1+dfsg-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/@rollup/plugin-typescript -> > /usr/share/nodejs/@rollup/plugin-typescript > Link ./node_modules/tslib -> /usr/share/nodejs/tslib > Link ./node_modules/typescript -> /usr/share/nodejs/typescript > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/pretty-format -> ./node_modules/ > Copy /usr/share/nodejs/ts-jest -> ./node_modules/ > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/./build > cd ./. && sh -ex debian/nodejs/./build > + set -e > + node build/build.js --minify > @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type > 'GlobalCompositeOperation'. > [1/0]: index.ts > [2/0]: src/all.ts > [3/0]: src/zrender.ts > [4/0]: src/export.ts > [5/0]: src/canvas/Painter.ts > [6/0]: src/svg/Painter.ts > [7/0]: src/core/env.ts > [8/0]: src/core/util.ts > [9/0]: src/Handler.ts > [10/0]: src/Storage.ts > [11/0]: src/animation/Animation.ts > [12/0]: src/dom/HandlerProxy.ts > [13/0]: src/tool/color.ts > [14/0]: src/config.ts > [15/0]: src/graphic/Group.ts > [16/0]: src/core/matrix.ts > [17/0]: src/core/vector.ts > [18/0]: src/tool/path.ts > [19/0]: src/tool/parseSVG.ts > [20/0]: src/tool/morphPath.ts > [21/0]: src/core/Point.ts > [22/0]: src/Element.ts > [23/0]: src/graphic/Displayable.ts > [24/0]: src/graphic/Path.ts > [25/0]: src/graphic/Image.ts > [26/0]: src/graphic/CompoundPath.ts > [27/0]: src/graphic/TSpan.ts > [28/0]: src/graphic/IncrementalDisplayable.ts > [29/0]: src/graphic/Text.ts > [30/0]: src/graphic/shape/Arc.ts > [31/0]: src/graphic/shape/BezierCurve.ts > [32/0]: src/graphic/shape/Circle.ts > [33/0]: src/graphic/shape/Droplet.ts > [34/0]: src/graphic/shape/Ellipse.ts > [35/0]: src/graphic/shape/Heart.ts > [36/0]: src/graphic/shape/Isogon.ts > [37/0]: src/graphic/shape/Line.ts > [38/0]: src/graphic/shape/Polygon.ts > [39/0]: src/graphic/shape/Polyline.ts > [40/0]: src/graphic/shape/Rect.ts > [41/0]: src/graphic/shape/Ring.ts > [42/0]: src/graphic/shape/Rose.ts > [43/0]: src/graphic/shape/Sector.ts > [44/0]: src/graphic/shape/Star.ts > [45/0]: src/graphic/shape/Trochoid.ts > [46/0]: src/graphic/LinearGradient.ts > [47/0]: src/graphic/RadialGradient.ts > [48/0]: src/graphic/Pattern.ts > [49/0]: src/core/BoundingRect.ts > [50/0]: src/core/OrientedBoundingRect.ts > [51/0]: src/debug/showDebugDirtyRect.ts > [52/0]: src/core/platform.ts > [53/0]: src/canvas/Layer.ts > [54/0]: src/animation/requestAnimationFrame.ts > [55/0]: src/canvas/graphic.ts > [56/0]: src/graphic/constants.ts > [57/0]: src/canvas/helper.ts > [58/0]: src/svg/graphic.ts > [59/0]: src/svg/core.ts > [60/0]: src/svg/helper.ts > [61/0]: src/svg/patch.ts > [62/0]: src/mixin/Draggable.ts > [63/0]: src/core/Eventful.ts > [64/0]: src/core/event.ts > [65/0]: src/core/GestureMgr.ts > [66/0]: src/core/timsort.ts > [67/0]: src/animation/Animator.ts > [68/0]: src/core/LRU.ts > [69/0]: src/core/PathProxy.ts > [70/0]: src/tool/transformPath.ts > [71/0]: src/tool/parseXML.ts > [72/0]: src/core/curve.ts > [73/0]: src/core/Transformable.ts > [74/0]: src/tool/dividePath.ts > [75/0]: src/tool/convertPath.ts > [76/0]: src/contain/text.ts > [77/0]: src/contain/path.ts > [78/0]: src/graphic/helper/parseText.ts > [79/0]: src/graphic/helper/subPixelOptimize.ts > [80/0]: src/graphic/helper/poly.ts > [81/0]: src/graphic/helper/roundRect.ts > [82/0]: src/graphic/helper/roundSector.ts > [83/0]: src/graphic/Gradient.ts > [84/0]: src/graphic/helper/image.ts > [85/0]: src/canvas/dashStyle.ts > [86/0]: src/svg/SVGPathRebuilder.ts > [87/0]: src/svg/mapStyleToAttrs.ts
Bug#1009581: marked as pending in node-zrender
Control: tag -1 pending Hello, Bug #1009581 in node-zrender 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-zrender/-/commit/83469f4bb2028e806c420dfc84e47bf3d8918d75 Update typescript patch Closes: #1009581 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009581
Processed: Bug#1009581 marked as pending in node-zrender
Processing control commands: > tag -1 pending Bug #1009581 [src:node-zrender] node-zrender: FTBFS: @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation'. Added tag(s) pending. -- 1009581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009987: marked as done (bluez: Bluetooth service does not start)
Your message dated Fri, 22 Apr 2022 13:48:55 + with message-id and subject line Bug#1009987: fixed in bluez 5.64-2 has caused the Debian Bug report #1009987, regarding bluez: Bluetooth service does not start 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.) -- 1009987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bluez Version: 5.64-1 Severity: grave Justification: renders package unusable Hi, I installed testing non-free and immediately upgraded to unstable on a lenovo thinkbook in the last two day. After that bluetooth was not working. Note, that I did not test bluetooth while still being on testing. After many attempts to get latest firmware I eventually figured out the root cause: the bluetooth.service was not starting due to a missing /var/lib/bluetooth directory. Output for service status: × bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-04-21 19:56:46 CEST; 12min ago Docs: man:bluetoothd(8) Process: 2411 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE) Main PID: 2411 (code=exited, status=226/NAMESPACE) CPU: 4ms Apr 21 19:56:46 lenovo-ben systemd[1]: Starting Bluetooth service... Apr 21 19:56:46 lenovo-ben systemd[2411]: bluetooth.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such file or directory Apr 21 19:56:46 lenovo-ben systemd[2411]: bluetooth.service: Failed at step NAMESPACE spawning /usr/libexec/bluetooth/bluetoothd: No such file or directory Apr 21 19:56:46 lenovo-ben systemd[1]: bluetooth.service: Main process exited, code=exited, status=226/NAMESPACE Apr 21 19:56:46 lenovo-ben systemd[1]: bluetooth.service: Failed with result 'exit-code'. Calling install -m 700 -d /var/lib/bluetooth and restarting bluetooth service eventually fixed the issue. It cost me a couple of hours to find the solution, for a less tech-savy user bluetooth will be not usable. Therefore I set severity to grave. Regards Ben -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.0-1 ii init-system-helpers 1.62 ii kmod29-1 ii libasound2 1.2.6.1-2+b1 ii libc6 2.33-7 ii libdbus-1-3 1.14.0-1 ii libdw1 0.186-1 ii libglib2.0-02.72.1-1 ii libreadline88.1.2-1.2 ii libudev1250.4-1 ii lsb-base11.1.0 ii udev250.4-1 bluez recommends no packages. Versions of packages bluez suggests: pn pulseaudio-module-bluetooth -- no debconf information --- End Message --- --- Begin Message --- Source: bluez Source-Version: 5.64-2 Done: Nobuhiro Iwamatsu We believe that the bug you reported is fixed in the latest version of bluez, 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. Nobuhiro Iwamatsu (supplier of updated bluez package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 22 Apr 2022 21:18:22 +0900 Source: bluez Architecture: source Version: 5.64-2 Distribution: unstable Urgency: medium Maintainer: Debian Bluetooth Maintainers Changed-By: Nobuhiro Iwamatsu Closes: 1009987 Changes: bluez (5.64-2) unstable; urgency=medium . * Create /var/lib/bluetooth (Closes: #1009987) Add d/bluez.prerm d/bluez.preinst. Checksums-Sha1: b98efd5fb2bda3c83dc42ee8cb7a727eb75e48ca 2735
Bug#1009998: Thunar and Nautilus don't show login and password box before conect
Dear Maintainer, I tested on Thunar and Nautilus and the file systems do not show login and password box before connect. The system is passing wrong credentials to Windows file server.
Processed: severity of 1010000 is grave
Processing commands for cont...@bugs.debian.org: > # thanks, investigating. See conversation at > https://github.com/containers/podman/issues/13968#issuecomment-1106433824 > severity 101 grave Bug #101 [podman] podman run panics with "assignment to entry in nil map" Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997228: marked as done (dee: FTBFS: Dee-1.0.gir:1274.7-1274.42: error: `Dee.Filter' already contains a definition for `new')
Your message dated Fri, 22 Apr 2022 11:48:44 + with message-id and subject line Bug#997228: fixed in dee 1.2.7+17.10.20170616-7 has caused the Debian Bug report #997228, regarding dee: FTBFS: Dee-1.0.gir:1274.7-1274.42: error: `Dee.Filter' already contains a definition for `new' 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.) -- 997228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dee Version: 1.2.7+17.10.20170616-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/vapi' > /usr/bin/vapigen --pkg gio-2.0 --library dee-1.0 --metadatadir=. > ../src/Dee-1.0.gir Dee-1.0-custom.vala > Dee-1.0.gir:1180.7-1180.58: warning: Field `Dee.Filter.destroy' conflicts > with method of the same name > > > Dee-1.0.gir:1274.7-1274.42: error: `Dee.Filter' already contains a definition > for `new' > > > Dee-1.0-custom.vala:19.3-19.27: note: previous definition of `new' was here > public static Filter @new (Dee.StaticFilterMapFunc map_func, > owned Dee.FilterMapNotify map_notify); > ^ > Dee-1.0.gir:8618.7-8618.70: warning: Field `Dee.ModelReader.destroy' > conflicts with method of the same name > > > Generation failed: 1 error(s), 2 warning(s) > make[3]: *** [Makefile:568: dee-1.0.vapi] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/dee_1.2.7+17.10.20170616-6_unstable.log 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: dee Source-Version: 1.2.7+17.10.20170616-7 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of dee, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated dee 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: Sat, 09 Apr 2022 18:31:57 +0530 Source: dee Architecture: source Version: 1.2.7+17.10.20170616-7 Distribution: unstable Urgency: medium Maintainer: Kartik Mistry Changed-By: Kartik Mistry Closes: 997228 Changes: dee (1.2.7+17.10.20170616-7) unstable; urgency=medium . [ Debian Janitor ] * debian/control: + Remove constraints unnecessary since buster: * Build-Depends: Drop versioned constraint on gobject-introspection, libdbus-1-dev, libdbus-glib-1-dev, libglib2.0-dev and libicu-dev. * libdee-dev: Drop versioned constraint on libdbus-glib-1-dev and libglib2.0-dev in Depends. + Set debhelper-compat version in Build-Depends. + Drop unnecessary dependency on dh-autoreconf. + Apply multi-arch hints: * libdee-dev: Add Multi-Arch: same. * gir1.2-dee-1.0: Add Multi-Arch: same. . [ Kartik Mistry ] * debian/patches/vala-gir.patch: + Added patch to fix FTBFS (Closes: #997228) * Added patch descriptions. * debian/control: + Update standards version to 4.6.0 * debian/copyright: + Fixed globbing pattern. * Disable tests on riscv64. Checksums-Sha1: cc70b1cf427fcc088c47cd21b77c703be5fecc6b 2355 dee_1.2.7+17.10.20170616-7.dsc 968fc53197468e70de7d4a03eb28ec3637c63520 14084 dee_1.2.7+17.10.20170616-7.debian.tar.xz Checksums-Sha256: a4a2ff0720f78d260b37a7618e4102e27bc11d25ad63b068c601a9beac6d2bf7 2355
Bug#1009574: marked as done (node-transformers: FTBFS: TypeError: Cannot read property 'indexOf' of null)
Your message dated Fri, 22 Apr 2022 11:34:46 + with message-id and subject line Bug#1009574: fixed in node-transformers 3.1.0+~1.0.0-2 has caused the Debian Bug report #1009574, regarding node-transformers: FTBFS: TypeError: Cannot read property 'indexOf' of null 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.) -- 1009574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-transformers Version: 3.1.0+~1.0.0-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/jstransformer -> ../jstransformer >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 ../debian/tests/test_modules/is-browser node_modules/is-browser > ln -s ../debian/tests/test_modules/test-result node_modules/test-result > ln -s ../debian/tests/test_modules/testit node_modules/testit > ln -s ../debian/tests/test_modules/wtfnode node_modules/wtfnode > ln -s ../. node_modules/transformers > cd ./jstransformer && sh -ex ../debian/nodejs/jstransformer/test > + node test > /<>/debian/tests/test_modules/wtfnode/index.js:62 > stack[i].file.indexOf(path.sep) !== -1 && > ^ > > TypeError: Cannot read property 'indexOf' of null > at findCallsite > (/<>/debian/tests/test_modules/wtfnode/index.js:62:31) > at Socket.EventEmitter.init > (/<>/debian/tests/test_modules/wtfnode/index.js:175:28) > at Socket.EventEmitter (events.js:88:21) > at Socket.Stream (internal/streams/legacy.js:11:6) > at Socket.Readable (internal/streams/readable.js:188:10) > at Socket.Duplex (internal/streams/duplex.js:56:12) > at new Socket (net.js:315:17) > at createWritableStdioStream > (internal/bootstrap/switches/is_main_thread.js:72:18) > at process.getStdout [as stdout] > (internal/bootstrap/switches/is_main_thread.js:122:12) > at get () > dh_auto_test: error: cd ./jstransformer && sh -ex > ../debian/nodejs/jstransformer/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-transformers_3.1.0+~1.0.0-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 --- Source: node-transformers Source-Version: 3.1.0+~1.0.0-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-transformers, 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-transformers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Apr 2022 13:17:15 +0200 Source: node-transformers Architecture: source Version: 3.1.0+~1.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009574 Changes: node-transformers (3.1.0+~1.0.0-2) unstable; urgency=medium . * Fix test for chalk >= 5 (Closes: #1009574) Checksums-Sha1:
Bug#1009457: marked as done (python-imageio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)
Your message dated Fri, 22 Apr 2022 11:34:51 +
with message-id
and subject line Bug#1009457: fixed in python-imageio 2.4.1-5
has caused the Debian Bug report #1009457,
regarding python-imageio: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1009457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-imageio
Version: 2.4.1-4
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[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v4.5.0
> Special preparations for imageio docs:
> Prepare Format.Reader and Format.Writer for doc generation.
> Prepare imageio.core for doc generation.
> Create docs for creating plugins.
> Create documentation for the formats.
> Create documentation for imageio's standard images.
> making output directory... done
> [autosummary] generating autosummary for: cmdlinescripts.rst, devapi.rst,
> drop27.rst, envvariables.rst, examples.rst, format_avbin.rst,
> format_bmp-fi.rst, format_bmp-pil.rst, format_bsdf.rst, format_bufr-pil.rst,
> ..., index.rst, installation.rst, plugins.rst, releasenotes.rst, scipy.rst,
> sec_developer.rst, sec_gettingstarted.rst, sec_reference.rst,
> standardimages.rst, userapi.rst
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 112 source files that are out of date
> updating environment: [new config] 112 added, 0 changed, 0 removed
> reading sources... [ 0%] cmdlinescripts
> reading sources... [ 1%] devapi
> reading sources... [ 2%] drop27
> reading sources... [ 3%] envvariables
> reading sources... [ 4%] examples
> reading sources... [ 5%] format_avbin
> reading sources... [ 6%] format_bmp-fi
> reading sources... [ 7%] format_bmp-pil
> reading sources... [ 8%] format_bsdf
> reading sources... [ 8%] format_bufr-pil
> reading sources... [ 9%] format_clipboardgrab
> reading sources... [ 10%] format_cur-pil
> reading sources... [ 11%] format_cut-fi
> reading sources... [ 12%] format_dcx-pil
> reading sources... [ 13%] format_dds-fi
> reading sources... [ 14%] format_dds-pil
> reading sources... [ 15%] format_dib-pil
> reading sources... [ 16%] format_dicom
> reading sources... [ 16%] format_dummy
> reading sources... [ 17%] format_eps-pil
> reading sources... [ 18%] format_exr-fi
> reading sources... [ 19%] format_fei
> reading sources... [ 20%] format_ffmpeg
> reading sources... [ 21%] format_fits
> reading sources... [ 22%] format_fits-pil
> reading sources... [ 23%] format_fli-pil
> reading sources... [ 24%] format_fpx-pil
> reading sources... [ 25%] format_ftex-pil
> reading sources... [ 25%] format_g3-fi
> reading sources... [ 26%] format_gbr-pil
> reading sources... [ 27%] format_gdal
> reading sources... [ 28%] format_gif-fi
> reading sources... [ 29%] format_gif-pil
> reading sources... [ 30%] format_grib-pil
> reading sources... [ 31%] format_hdf5-pil
> reading sources... [ 32%] format_hdr-fi
> reading sources... [ 33%] format_icns-pil
> reading sources... [ 33%] format_ico-fi
> reading sources... [ 34%] format_ico-pil
> reading sources... [ 35%] format_iff-fi
> reading sources... [ 36%] format_im-pil
> reading sources... [ 37%] format_imt-pil
> reading sources... [ 38%] format_iptc-pil
> reading sources... [ 39%] format_itk
> reading sources... [ 40%] format_j2k-fi
> reading sources... [ 41%] format_jng-fi
> reading sources... [ 41%] format_jp2-fi
> reading sources... [ 42%] format_jpeg-fi
> reading sources... [ 43%] format_jpeg-pil
> reading sources... [ 44%] format_jpeg-xr-fi
> reading sources... [ 45%] format_jpeg2000-pil
> reading sources... [ 46%] format_koala-fi
> reading sources... [ 47%] format_lytro-f01-raw
> reading sources... [ 48%] format_lytro-illum-raw
> reading sources... [ 49%] format_lytro-lfp
> reading sources... [ 50%] format_lytro-lfr
> reading sources... [ 50%] format_mcidas-pil
> reading sources... [ 51%] format_mic-pil
> reading sources... [ 52%] format_mpo-pil
> reading sources... [ 53%] format_msp-pil
> reading sources... [ 54%] format_npz
> reading sources... [ 55%] format_pbm-fi
> reading sources... [ 56%] format_pbmraw-fi
> reading sources... [ 57%] format_pcd-fi
> reading sources... [ 58%]
Processed: Bug#1009574 marked as pending in node-transformers
Processing control commands: > tag -1 pending Bug #1009574 [src:node-transformers] node-transformers: FTBFS: TypeError: Cannot read property 'indexOf' of null Added tag(s) pending. -- 1009574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009574: marked as pending in node-transformers
Control: tag -1 pending Hello, Bug #1009574 in node-transformers 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-transformers/-/commit/8e02eef9164dbfc35fdf6b2377494180a0b8d1d9 Fix test for chalk >= 5 Closes: #1009574 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009574
Bug#1009484: marked as done (node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%))
Your message dated Fri, 22 Apr 2022 11:18:58 + with message-id and subject line Bug#1009484: fixed in node-copy-concurrently 1.0.5-9 has caused the Debian Bug report #1009484, regarding node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) 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.) -- 1009484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-copy-concurrently Version: 1.0.5-8 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/copy-concurrently > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test > > (node:4048760) DeprecationWarning: is() is deprecated, use equal() instead > (Use `node --trace-deprecation ...` to show where the warning was created) > test/copy.js > copy errors > > ✓ dest exists > > ✓ dest perm error > > ✓ source does not exist > > ✓ block devices unsupported > > ✓ char devices unsupported > > ✓ FIFOs unsupported > > ✓ sockets unsupported > > ✓ unknown unsupported > > copy file > > ✓ CHOWN uid:100 > > ✓ read errors propagate > > ✓ write errors propagate > > ✓ copy ok > > ✓ CHMOD: dest:chmod 33188 > > ✓ copy w/chmod ok > > ✓ copy w/chown ok > > copy symlink unix > > ✓ symlink type ../other/src:ok → dest:ok > > ✓ symlink type ../other/src:dir-ok → dest:ok > > ✓ file symlink ok > > ✓ dir symlink ok > > ✓ failed file symlink fails > > ✓ failed dir symlink fails > > copy symlink windows > > ✓ symlink type ../other/src:ok → dest:ok > > ✓ symlink type ../other/src:dir-ok → dest:ok > > ✓ symlink type ../other/src:junction-ok → dest:ok > > ✓ file symlink ok > > ✓ dir symlink ok > > ✓ failed file symlink fails > > ✓ dir junction fallback ok > > ✓ failed dir symlink fails > > (node:4048759) DeprecationWarning: is() is deprecated, use equal() instead > (Use `node --trace-deprecation ...` to show where the warning was created) > test/integration.js > setup > > 1) t.done is not a function > > copy > > ✓ copied symlink > > ✓ copied dir symlink > > ✓ won't overwrite symlinks > > 2) (unnamed test) > > 3) (unnamed test) > > 4) test unfinished > > 5) test count !== plan > > > 6) child test left in queue: t.test cleanup > > 7) test count !== plan > > 32 passing (1s) > 7 failing > > 1) test/integration.js setup t.done is not a function: > Error: t.done is not a function > at Test. (test/integration.js:59:5) > at Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40) > at /usr/share/nodejs/libtap/lib/test.js:369:21 > at Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7) > at Test.runMain (/usr/share/nodejs/libtap/lib/base.js:178:15) > at /usr/share/nodejs/libtap/lib/test.js:485:13 > at TAP.writeSubComment (/usr/share/nodejs/libtap/lib/test.js:556:5) > at Test. (/usr/share/nodejs/libtap/lib/test.js:484:14) > > 2) test/integration.js copy (unnamed test): > (unnamed test) > > > 3) test/integration.js copy (unnamed test): > (unnamed test) > > > 4) test/integration.js copy test unfinished: > Error: test unfinished > at Object. (test/integration.js:62:1) > at Module.replacementCompile > (/usr/share/nodejs/append-transform/index.js:60:13) > at Object. (/usr/share/nodejs/append-transform/index.js:64:4) > > 5) test/integration.js copy test count !== plan: > > test count !== plan > + expected - actual > > -6 > +7 > > > > 6) test/integration.js child test left in queue: t.test cleanup: > child test left in queue: t.test cleanup > > > 7) test/integration.js test count !== plan: > > test count !== plan > + expected - actual > > -3 > +2 > > > > ERROR: Coverage for lines (99.23%) does not meet global threshold (100%) > ERROR: Coverage for functions (96.42%)
Bug#1009042: marked as done (libtraceevent: FTBFS race condition on parallel build)
Your message dated Fri, 22 Apr 2022 11:04:16 + with message-id and subject line Bug#1009042: fixed in libtraceevent 1:1.5.3-1 has caused the Debian Bug report #1009042, regarding libtraceevent: FTBFS race condition on parallel build 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.) -- 1009042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtraceevent Version: 1:1.5.1-1 Severity: serious Tags: ftbfs upstream Justification: fails to build from source (but built successfully in the past) Dear Maintainer, the upstream version 1.5.1 has a race condition in the src/Makefile which breaks the build sporadically. This bug is hard to reproduce, but when running with sbuilder on a machine with 16 cores, it appears quite consistently. Attached a log from a failed build using sbuilder (from an internal build server, not the official debian ones). Please note, that the symbols that are missing vary from run to run. A similar bug has already been reported for libtracefs (#1008722). The root-cause might be the same, as the Makefiles of both projects look quite similar. Best regards, Felix Moessbauer Siemens AG dh_makeshlibs -a dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libtraceevent1/DEBIAN/symbols doesn't match completely debian/libtraceevent1.symbols --- debian/libtraceevent1.symbols (libtraceevent1_1:1.5.1-1_amd64) +++ dpkg-gensymbolsJfsqcz 2022-04-01 12:59:36.848775612 + @@ -146,15 +146,15 @@ tep_vprint@Base 1:1.3.0 tep_vwarning@Base 1:1.2.1 tep_warning@Base 1:1.2.1 - trace_seq_destroy@Base 5.4 - trace_seq_do_fprintf@Base 5.4 - trace_seq_do_printf@Base 5.4 - trace_seq_init@Base 5.4 - trace_seq_printf@Base 5.4 - trace_seq_putc@Base 5.4 - trace_seq_puts@Base 5.4 - trace_seq_reset@Base 5.4 - trace_seq_terminate@Base 5.4 - trace_seq_vprintf@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_destroy@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_do_fprintf@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_do_printf@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_init@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_printf@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_putc@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_puts@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_reset@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_terminate@Base 5.4 +#MISSING: 1:1.5.1-1# trace_seq_vprintf@Base 5.4 vpr_stat@Base 5.4 #MISSING: 1:1.2.1-1# warning@Base 5.4 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:14: binary] Error 25 -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, x32 Kernel: Linux 5.10.0-13-amd64 (SMP w/16 CPU threads) 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 --- End Message --- --- Begin Message --- Source: libtraceevent Source-Version: 1:1.5.3-1 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of libtraceevent, 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. Sudip Mukherjee (supplier of updated libtraceevent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Apr 2022 11:33:06 +0100 Source: libtraceevent Architecture: source Version: 1:1.5.3-1 Distribution: unstable Urgency: medium Maintainer: Sudip Mukherjee Changed-By: Sudip Mukherjee Closes: 1009042 Changes: libtraceevent (1:1.5.3-1) unstable; urgency=medium . * New upstream version 1.5.3 * Disable parallel builds. (Closes: #1009042) Checksums-Sha1: 54d4fac7973e022488ef78f2994e515bbdc11af2 2125 libtraceevent_1.5.3-1.dsc 58439617f4ccb80af238600e533d408737483b82 109600 libtraceevent_1.5.3.orig.tar.xz a3f3b0c542c73700af0d358609fb51738e0ef7c6 3456 libtraceevent_1.5.3-1.debian.tar.xz
Bug#1009484: marked as pending in node-copy-concurrently
Control: tag -1 pending Hello, Bug #1009484 in node-copy-concurrently 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-copy-concurrently/-/commit/7164ebb5c9ad2d4c773f7ea9b47cf883020bac90 Fix test for tap >= 15 and require node-fs-write-stream-atomic >= 1.0.10-6~ Closes: #1009484 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009484
Processed: Bug#1009484 marked as pending in node-copy-concurrently
Processing control commands: > tag -1 pending Bug #1009484 [src:node-copy-concurrently] node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%) Added tag(s) pending. -- 1009484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 1009484, reassign -1 to node-fs-write-stream-atomic, affects -1 ..., fixed -1 in 1.0.10-6 ...
Processing commands for cont...@bugs.debian.org: > clone 1009484 -1 Bug #1009484 [src:node-copy-concurrently] node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%) Bug 1009484 cloned as bug 1010015 > reassign -1 node-fs-write-stream-atomic Bug #1010015 [src:node-copy-concurrently] node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%) Bug reassigned from package 'src:node-copy-concurrently' to 'node-fs-write-stream-atomic'. No longer marked as found in versions node-copy-concurrently/1.0.5-8. Ignoring request to alter fixed versions of bug #1010015 to the same values previously set > affects -1 node-copy-concurrently Bug #1010015 [node-fs-write-stream-atomic] node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%) Added indication that 1010015 affects node-copy-concurrently > retitle -1 drop patch that replace readable-stream Bug #1010015 [node-fs-write-stream-atomic] node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%) Changed Bug title to 'drop patch that replace readable-stream' from 'node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%)'. > fixed -1 1.0.10-6 Bug #1010015 [node-fs-write-stream-atomic] drop patch that replace readable-stream Marked as fixed in versions node-fs-write-stream-atomic/1.0.10-6. > close -1 Bug #1010015 [node-fs-write-stream-atomic] drop patch that replace readable-stream Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1009484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009484 1010015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009508: marked as done (node-help-me: FTBFS: ERROR: Coverage for statements (88.63%) does not meet global threshold (100%))
Your message dated Fri, 22 Apr 2022 10:04:12 +
with message-id
and subject line Bug#1009508: fixed in node-help-me 3.0.0-1
has caused the Debian Bug report #1009508,
regarding node-help-me: FTBFS: ERROR: Coverage for statements (88.63%) 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.)
--
1009508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-help-me
Version: 2.0.0-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 --with nodejs
>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/help-me
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> ok 1 - test.js # time=763.193ms {
> # show the doc/help.txt from the require.main folder if no options are
> passed
> ok 1 null
> ok 2 should be strictly equal
> # show a generic help.txt from a folder to a stream
> ok 3 null
> ok 4 should be strictly equal
> # custom help command with an array
> ok 5 null
> ok 6 should be strictly equal
> # custom help command without an ext
> ok 7 null
> ok 8 should be strictly equal
> # custom help command with a string
> ok 9 null
> ok 10 should be strictly equal
> # missing help file
> ok 11 should be strictly equal
> # custom help command with an array
> # abbreviates two words in one
> ok 12 null
> ok 13 should be strictly equal
> # abbreviates three words in two
> ok 14 null
> ok 15 should be strictly equal
> # abbreviates a word
> ok 16 null
> ok 17 should be strictly equal
> # abbreviates a word using strings
> ok 18 null
> ok 19 should be strictly equal
> # print a disambiguation
> ok 20 should be strictly equal
> # choose exact match over partial
> ok 21 should be strictly equal
> # support for help files organized in folders
> # passing an array
> ok 22 null
> ok 23 should be strictly equal
> # passing a string
> ok 24 null
> ok 25 should be strictly equal
>
> 1..25
> # tests 25
> # pass 25
>
> # ok
> }
>
> 1..1
> # time=788.45ms
> ERROR: Coverage for lines (90.47%) does not meet global threshold (100%)
> ERROR: Coverage for functions (81.81%) does not meet global threshold (100%)
> ERROR: Coverage for branches (87.5%) does not meet global threshold (100%)
> ERROR: Coverage for statements (88.63%) does not meet global threshold (100%)
> |-|--|-|-|---
> File| % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> |-|--|-|-|---
> All files | 88.63 | 87.5 | 81.81 | 90.47 |
> help-me.js | 88.63 | 87.5 | 81.81 | 90.47 | 18,73-76
> |-|--|-|-|---
> 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-help-me_2.0.0-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 ---
Source: node-help-me
Source-Version: 3.0.0-1
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-help-me, which is due to be installed in the Debian FTP archive.
A summary of the changes
Bug#1009792: marked as done (mpich: armci-mpi test error: MPIR_pmi_init(151)...: PMIX_Init returned -25)
Your message dated Fri, 22 Apr 2022 10:50:04 +0100 with message-id <2f15726b-1651-7514-9fd7-717955691...@debian.org> and subject line close has caused the Debian Bug report #1009792, regarding mpich: armci-mpi test error: MPIR_pmi_init(151)...: PMIX_Init returned -25 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.) -- 1009792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mpich Version: 4.0.2-1 Severity: serious Justification: FTBFS/debci debci tests for armci-mpi with the new mpich 4.0.2-1 are failing with the error: Abort(605670927): Fatal error in internal_Init: Other MPI error, error stack: internal_Init(59): MPI_Init(argc=0x7ffca340893c, argv=0x7ffca3408930) failed MPII_Init_thread(209): MPID_Init(359)...: MPIR_pmi_init(151)...: PMIX_Init returned -25 The problem is not as simple as just rebuilding armci-mpi (which builds static libraries) in a binNMU, since the same error occurs in build-time tests. The error also appears in nwchem (possibly via its use of armci-mpi), and in bagel tests. Is there an incompatibility between mpich 4.0.2 and libpmix ? -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpich depends on: ii hwloc 2.7.1-1 ii libc6 2.33-7 ii libhwloc15 2.7.1-1 ii libmpich12 4.0.2-1 ii libslurm37 21.08.6-1 Versions of packages mpich recommends: ii libmpich-dev 4.0.2-1 Versions of packages mpich suggests: ii mpich-doc 4.0.2-1 -- no debconf information --- End Message --- --- Begin Message --- close 1009792 thanks Closed in last upload -- Alastair McKinstry, mckins...@debian.org matrix: @sceal.ie:mckinstry GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5--- End Message ---
Processed: Bug#1009508 marked as pending in node-help-me
Processing control commands: > tag -1 pending Bug #1009508 [src:node-help-me] node-help-me: FTBFS: ERROR: Coverage for statements (88.63%) does not meet global threshold (100%) Added tag(s) pending. -- 1009508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009508: marked as pending in node-help-me
Control: tag -1 pending Hello, Bug #1009508 in node-help-me 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-help-me/-/commit/f8f6dc54ac46318c5b38c50bcee02ada73190a77 Fix test for tap >= 15 (--no-cov) Closes: #1009508 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009508
Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
forwarded 1009448 https://github.com/PhilterPaper/Perl-PDF-Builder/issues/184 thanks OpenPGP_signature Description: OpenPGP digital signature
Bug#1009585: marked as done (node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3)
Your message dated Fri, 22 Apr 2022 09:33:52 + with message-id and subject line Bug#1009585: fixed in node-fd-slicer 1.1.0+repack1-2 has caused the Debian Bug report #1009585, regarding node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 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.) -- 1009585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-fd-slicer Version: 1.1.0+repack1-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 ../debian/tests/test_modules/stream-equal > node_modules/stream-equal > ln -s ../debian/tests/test_modules/streamsink node_modules/streamsink > ln -s ../. node_modules/fd-slicer > /bin/sh -ex debian/tests/pkg-js/test > + mocha --check-leaks --timeout 1 > > > FdSlicer > (node:3356748) [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) > undefined reads a 20MB file (autoClose on) (253ms) > undefined reads 4 chunks simultaneously (216ms) > undefined writes a 20MB file (autoClose on) (143ms) > undefined writes 4 chunks simultaneously (128ms) > undefined throws on invalid ref > 1) write stream emits error when max size exceeded > undefined write stream does not emit error when max size not exceeded > 2) write stream start and end work together > undefined write stream emits progress events > undefined write stream unrefs when destroyed > undefined read stream unrefs when destroyed > undefined fdSlicer.read > undefined fdSlicer.write > > BufferSlicer > undefined invalid ref > undefined read and write > undefined createReadStream > 3) createWriteStream exceed buffer size > undefined createWriteStream ok > > > 15 passing (31s) > 3 failing > > 1) FdSlicer >write stream emits error when max size exceeded: > Error: Timeout of 1ms exceeded. For async tests and hooks, ensure > "done()" is called; if returning a Promise, ensure it resolves. > (/<>/test/test.js) > at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15) > at Test.Runnable._timeoutError > (/usr/share/nodejs/mocha/lib/runnable.js:431:10) > at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24) > at listOnTimeout (internal/timers.js:557:17) > at processTimers (internal/timers.js:500:7) > > 2) FdSlicer >write stream start and end work together: > Error: Timeout of 1ms exceeded. For async tests and hooks, ensure > "done()" is called; if returning a Promise, ensure it resolves. > (/<>/test/test.js) > at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15) > at Test.Runnable._timeoutError > (/usr/share/nodejs/mocha/lib/runnable.js:431:10) > at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24) > at listOnTimeout (internal/timers.js:557:17) > at processTimers (internal/timers.js:500:7) > > 3) BufferSlicer >createWriteStream exceed buffer size: > Error: Timeout of 1ms exceeded. For async tests and hooks, ensure > "done()" is called; if returning a Promise, ensure it resolves. > (/<>/test/test.js) > at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15) > at Test.Runnable._timeoutError > (/usr/share/nodejs/mocha/lib/runnable.js:431:10) > at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24) > at listOnTimeout (internal/timers.js:557:17) > at processTimers (internal/timers.js:500:7) > > > > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-fd-slicer_1.1.0+repack1-1_unstable.log All bugs filed during this archive rebuild are listed at:
Processed: severity of 1009568 is important
Processing commands for cont...@bugs.debian.org: > severity 1009568 important Bug #1009568 [jest] node-proper-lockfile: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1009568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009585: marked as pending in node-fd-slicer
Control: tag -1 pending Hello, Bug #1009585 in node-fd-slicer 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-fd-slicer/-/commit/7fd834f744c4ef03ea3178ae61190bf232499235 Fix test for Node.js >= 14 Closes: #1009585 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009585
Processed: Bug#1009585 marked as pending in node-fd-slicer
Processing control commands: > tag -1 pending Bug #1009585 [src:node-fd-slicer] node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 Added tag(s) pending. -- 1009585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 953032 is normal
Processing commands for cont...@bugs.debian.org:
> severity 953032 normal
Bug #953032 {Done: Timo Aaltonen } [x11-xkb-utils]
xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
Bug #994036 {Done: Timo Aaltonen } [x11-xkb-utils]
x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some
XF86* with xkb-data 2.33-1)
Bug #1009920 {Done: Timo Aaltonen } [x11-xkb-utils]
Internal error: Could not resolve keysym XF86EmojiPicker
Severity set to 'normal' from 'critical'
Severity set to 'normal' from 'critical'
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009920
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
994036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: cloning 1009585, severity of -1 is important ...
Processing commands for cont...@bugs.debian.org: > clone 1009585 -1 Bug #1009585 [src:node-fd-slicer] node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 Bug 1009585 cloned as bug 1010008 > severity -1 important Bug #1010008 [src:node-fd-slicer] node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 Severity set to 'important' from 'serious' > retitle -1 Stream behavior changed with Node.js 14, error are no more reported Bug #1010008 [src:node-fd-slicer] node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 Changed Bug title to 'Stream behavior changed with Node.js 14, error are no more reported' from 'node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009585 1010008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
To confirm - I've just put the 3 packages for gs 9.56.1 (and nothing else) from sid on my testing machine, and now I see the same failures. OpenPGP_signature Description: OpenPGP digital signature
Bug#1009685: Please close as resolved without package upload
As the transition to python3.10 is finished and the missing library /usr/lib/x86_64-linux-gnu/libpython3.10.so will now be there when running the autopkgtest, I believe the only thing preventing migration of opm-grid Version 2021.10-3, is this bug being open. The autpkgtests are green on [1]. I hope that we can simply close this bug without uploading a new package version with any changes. I abstained from closing it myself, as I am not sure whether that would be rude. I am happy to close it myself if that is ok. [1] https://qa.debian.org/excuses.php?package=opm-grid signature.asc Description: PGP signature
Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
My machine running testing currently has ghostscript 9.55.0, and there it still builds fine. So I'm guessing the problem is between 9.55.0 and 9.56.0. Indeed since the failure with 9.56.0, 9.56.1 has been uploaded. I've just tried building it with 9.56.1 but it still has the same two failures. I'll do some debugging. OpenPGP_signature Description: OpenPGP digital signature
Bug#1009537: marked as done (node-fs-write-stream-atomic: FTBFS: ERROR: Coverage for statements (91.86%) does not meet global threshold (100%))
Your message dated Fri, 22 Apr 2022 08:33:42 +
with message-id
and subject line Bug#1009537: fixed in node-fs-write-stream-atomic 1.0.10-6
has caused the Debian Bug report #1009537,
regarding node-fs-write-stream-atomic: FTBFS: ERROR: Coverage for statements
(91.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.)
--
1009537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-fs-write-stream-atomic
Version: 1.0.10-5
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/fs-write-stream-atomic
> /bin/sh -ex debian/tests/pkg-js/test
> + tap -J test
> TAP version 13
> (node:1750367) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1750371) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1750369) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1750372) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1750368) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> Error: ENOENT: no such file or directory, open
> '/<>/test/test.txt'
> at Object.openSync (fs.js:497:3)
> at Object.readFileSync (fs.js:393:35)
> at WriteStreamAtomic. (/<>/test/basic.js:43:20)
> at WriteStreamAtomic.apply [as emit] (events.js:400:28)
> at WriteStreamAtomic.emit (/<>/index.js:63:34)
> at emitCloseNT (internal/streams/destroy.js:87:10)
> at processTicksAndRejections (internal/process/task_queues.js:81:21)
> {
> name: 'TAP',
> errno: -2,
> syscall: 'open',
> code: 'ENOENT',
> path: '/<>/test/test.txt',
> tapCaught: 'uncaughtException',
> test: 'TAP'
> }
> Error: ENOENT: no such file or directory, open
> '/<>/test/test.txt'
> at Object.openSync (fs.js:497:3)
> at Object.readFileSync (fs.js:393:35)
> at WriteStreamAtomic. (/<>/test/basic.js:43:20)
> at WriteStreamAtomic.apply [as emit] (events.js:400:28)
> at WriteStreamAtomic.emit (/<>/index.js:63:34)
> at emitCloseNT (internal/streams/destroy.js:87:10)
> at processTicksAndRejections (internal/process/task_queues.js:81:21)
> {
> name: 'TAP',
> errno: -2,
> syscall: 'open',
> code: 'ENOENT',
> path: '/<>/test/test.txt',
> tapCaught: 'uncaughtException',
> test: 'TAP'
> }
> Error: ENOENT: no such file or directory, open
> '/<>/test/test.txt'
> at Object.openSync (fs.js:497:3)
> at Object.readFileSync (fs.js:393:35)
> at WriteStreamAtomic. (/<>/test/basic.js:43:20)
> at WriteStreamAtomic.apply [as emit] (events.js:400:28)
> at WriteStreamAtomic.emit (/<>/index.js:63:34)
> at emitCloseNT (internal/streams/destroy.js:87:10)
> at processTicksAndRejections (internal/process/task_queues.js:81:21)
> {
> name: 'TAP',
> errno: -2,
> syscall: 'open',
> code: 'ENOENT',
> path: '/<>/test/test.txt',
> tapCaught: 'uncaughtException',
> test: 'TAP'
> }
> Error: ENOENT: no such file or directory, open
> '/<>/test/test.txt'
> at Object.openSync (fs.js:497:3)
> at Object.readFileSync (fs.js:393:35)
> at WriteStreamAtomic. (/<>/test/basic.js:43:20)
> at WriteStreamAtomic.apply [as emit] (events.js:400:28)
> at WriteStreamAtomic.emit (/<>/index.js:63:34)
> at emitCloseNT (internal/streams/destroy.js:87:10)
> at processTicksAndRejections (internal/process/task_queues.js:81:21)
> {
> name: 'TAP',
> errno: -2,
> syscall: 'open',
> code: 'ENOENT',
> path: '/<>/test/test.txt',
> tapCaught: 'uncaughtException',
> test: 'TAP'
> }
> Error: ENOENT: no such file or directory, open
> '/<>/test/test.txt'
> at Object.openSync (fs.js:497:3)
> at
Bug#1009562: marked as done (node-fs.realpath: FTBFS: ERROR: Coverage for statements (21.46%) does not meet global threshold (100%))
Your message dated Fri, 22 Apr 2022 08:25:37 +
with message-id
and subject line Bug#1009562: fixed in node-fs.realpath 1.0.0-3
has caused the Debian Bug report #1009562,
regarding node-fs.realpath: FTBFS: ERROR: Coverage for statements (21.46%) 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.)
--
1009562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-fs.realpath
Version: 1.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/fs.realpath
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/monkeypatching.js test/symlinks.js
> TAP version 13
> (node:1007448) DeprecationWarning: notEqual() is deprecated, use not() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/monkeypatching.js # time=10.619ms {
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should not be equal
> ok 4 - should not be equal
> 1..4
> # time=10.619ms
> }
>
> ok 2 - test/symlinks.js # time=99.428ms {
> # Subtest: setup
> 1..0
> ok 1 - setup # time=3.463ms
>
> # Subtest: symlinks = 1
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 2 - symlinks = 1 # time=13.808ms
>
> # Subtest: symlinks = 128
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - symlinks = 128 # time=20.866ms
>
> # Subtest: symlinks = 256
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 4 - symlinks = 256 # time=51.85ms
>
> # Subtest: cleanup
> 1..0
> ok 5 - cleanup # time=0.615ms
>
> 1..5
> # time=99.428ms
> }
>
> 1..2
> # time=955.542ms
> ERROR: Coverage for lines (23.03%) does not meet global threshold (100%)
> ERROR: Coverage for functions (28.57%) does not meet global threshold (100%)
> ERROR: Coverage for branches (7.07%) does not meet global threshold (100%)
> ERROR: Coverage for statements (21.46%) does not meet global threshold (100%)
> --|-|--|-|-|
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> --|-|--|-|-|
> All files | 21.46 | 7.07 | 28.57 | 23.03 |
>
> index.js | 81.81 |33.33 | 100 | 81.81 | 26,35,44,50-53
>
> old.js |7.63 | 3.06 | 0 |8.33 |
> 34-66,74,81,88-179,184-301
> --|-|--|-|-|
> 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-fs.realpath_1.0.0-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-fs.realpath
Source-Version: 1.0.0-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-fs.realpath, 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
Processed: Bug#1009537 marked as pending in node-fs-write-stream-atomic
Processing control commands: > tag -1 pending Bug #1009537 [src:node-fs-write-stream-atomic] node-fs-write-stream-atomic: FTBFS: ERROR: Coverage for statements (91.86%) does not meet global threshold (100%) Added tag(s) pending. -- 1009537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009537: marked as pending in node-fs-write-stream-atomic
Control: tag -1 pending Hello, Bug #1009537 in node-fs-write-stream-atomic 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-fs-write-stream-atomic/-/commit/77b2efa9c9232b93612dbc63dc02fec30aff22bf Fix test for tap >= 15 (--no-cov) Closes: #1009537 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009537
Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Going through what changed between the previous successful build https://buildd.debian.org/status/fetch.php?pkg=libpdf-builder-perl=all=3.023-1=1631870648=0 and the failure: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdf-builder-perl.html I see the following changes in the dependency versions: libbrotli1_1.0.9-2+b2 -> b3 libfreetype6_2.10.4+dfsg-1 -> 2.11.1+dfsg-1 fontconfig-config_2.13.1-4.2 -> .4 libfontconfig1_2.13.1-4.2 -> .4 libaom0_1.0.0.errata1-3 -> libaom3_3.3.0-1 libdav1d5_0.9.2-1 -> +b1 libnuma1_2.0.12-1+b1 -> 2.0.14-3 libx265-192_3.4-2 -> -199_3.5-2 libheif1_1.12.0-2+b1 -> b3 libjpeg62-turbo_1%3a2.0.6-4 -> 1%3a2.1.2-1 libglib2.0-0_2.68.4-1 -> 2.72.1-1 libltdl7_2.4.6-15 -> 2.4.7-3 libopenjp2-7_2.4.0-3 -> -6 libdeflate0_1.7-2 -> 1.10-2 libwebp6_0.6.1-2.1 -> libwebp7_1.2.2-2+b1 libtiff5_4.3.0-2 -> -6 libwebpdemux2_0.6.1-2.1 -> 1.2.2-2+b1 libwebpmux3_0.6.1-2.1 -> 1.2.2-2+b1 libmd0_1.0.3-3 -> 1.0.4-1 libbsd0_0.11.3-1 -> 0.11.6-1 libx11-data_2%3a1.7.2-2 -> 2%3a1.7.5-1 libx11-6_2%3a1.7.2-2+b1 -> 2%3a1.7.5-1 libxml2_2.9.12+dfsg-4 -> 2.9.13+dfsg-1 libmagickcore-6.q16-6_8%3a6.9.11.60+dfsg-1.3 -> +b2 libmagickwand-6.q16-6_8%3a6.9.11.60+dfsg-1.3 -> +b2 imagemagick-6.q16_8%3a6.9.11.60+dfsg-1.3 -> +b2 libmagic-mgc_1%3a5.39-3 -> 1%3a5.41-3 libmagic1_1%3a5.39-3 -> 1%3a5.41-3 file_1%3a5.39-3 -> 1%3a5.41-3 autotools-dev_20180224.1+nmu1 -> 20220109.1 automake_1%3a1.16.4-2 -> 1%3a1.16.5-1.3 autopoint_0.21-4 -> -6 libdebhelper-perl_13.5.1 -> 13.7.1 libtool_2.4.6-15 -> 2.4.7-3 libfile-stripnondeterminism-perl_1.12.0-1 -> 1.13.0-1 dh-strip-nondeterminism_1.12.0-1 -> 1.13.0-1 libelf1_0.185-2 -> 0.186-1 gettext_0.21-4 -> -6 debhelper_13.5.1 -> 13.7.1 libgs9-common_9.54.0~dfsg-5 -> 9.56.0~dfsg-1 libgs9_9.54.0~dfsg-5 -> 9.56.0~dfsg-1 ghostscript_9.54.0~dfsg-5 -> 9.56.0~dfsg-1 libdbus-1-3_1.12.20-2 -> 1.14.0-1 libcups2_2.3.3op2-7 -> 2.4.1op1-2 libgd3_2.3.0-2 -> +b1 libgd-perl_2.73-1+b1 -> 2.76-2+b1 libgraphics-tiff-perl_16-1 -> 18-1+b1 libimage-png-libpng-perl_0.57-1 -> -2+b1 libpadwalker-perl_2.5-1+b1 -> b2 The libcms2 version is identical, so I don't think that is the problem. If I have interpreted the versioning correctly, the imagemagick change should be negligible. However, the ghostscript change is not, and indeed the error messages look like they come from ghostscript: Error: /typecheck in --runpdf-- Operand stack: --dict:6/14(L)-- --dict:6/14(L)-- --dict:6/14(L)-- MediaBox --nostringval-- 20.0 20.0 20.0 20.0 false 20.0 2 Execution stack: %interp_exit .runexec2 --nostringval-- runpdf --nostringval-- 2 %stopped_push --nostringval-- runpdf runpdf false 1 %stopped_push 1990 1 3 %oparray_pop 1989 1 3 %oparray_pop 1977 1 3 %oparray_pop 1978 1 3 %oparray_pop runpdf runpdf 2 1 1 runpdf %for_pos_int_continue runpdf runpdf runpdf Dictionary stack: --dict:765/1123(ro)(G)-- --dict:0/20(G)-- --dict:76/200(L)-- --dict:18/20(L)-- Current allocation mode is local Last OS error: No such file or directory OpenPGP_signature Description: OpenPGP digital signature
Bug#1009562: marked as pending in node-fs.realpath
Control: tag -1 pending Hello, Bug #1009562 in node-fs.realpath 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-fs.realpath/-/commit/4fbfeb608a7b032f792170edabda4a691e86526b Fix test for tap >= 15 (--no-cov) Closes: #1009562 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009562
Processed: Bug#1009562 marked as pending in node-fs.realpath
Processing control commands: > tag -1 pending Bug #1009562 [src:node-fs.realpath] node-fs.realpath: FTBFS: ERROR: Coverage for statements (21.46%) does not meet global threshold (100%) Added tag(s) pending. -- 1009562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009918: virtualbox memset symbol fix
control: fixed -1 6.1.34-dfsg-2
control: close -1
On Thu, 21 Apr 2022 03:37:12 +0200 Jan Nordholz wrote:
Hi,
the attached one-liner diff fixes the symbol issue and enables me to run
my Virtualbox VMs again. (However, I didn't check how the addition of
this flag to CXXFLAGS affects the rest of R0 compilation - on the other
hand, it's already there in CFLAGS.)
The missing 'memset' symbol is caused by a compiler-generated call to
memset(), not by an actual call in the source code - my guess is that
g++ emits it to optimize this loop that was added for 6.1.34:
=
--- ./virtualbox-6.1.32-dfsg/src/VBox/Devices/Network/DevE1000.cpp
2022-01-13 19:55:54.0 +0100
+++ ./virtualbox-6.1.34-dfsg/src/VBox/Devices/Network/DevE1000.cpp
2022-03-23 00:43:01.0 +0100
@@ -5462,6 +5543,17 @@
AssertMsgFailed(("Impossible descriptor type!"));
continue;
}
+if (fInvalidPacket)
+{
+for (int index = pThis->iTxDCurrent; index < i; ++index)
+pThis->afTxDValid[index] = false; /* Make sure all descriptors
for this packet are skipped by processing */
+LogFlow(("%s e1kLocateTxPacket: marked %d descriptors as invalid\n",
pThis->szPrf, i - pThis->iTxDCurrent));
+LogFlow(("%s e1kLocateTxPacket: RET true cbTxAlloc=%d
cbPacket=%d%s%s\n",
+ pThis->szPrf, pThis->cbTxAlloc, cbPacket,
+ pThis->fGSO ? " GSO" : "", fTSE ? " TSE" : ""));
+pTxdc->nextPacket = i;
+return true;
+}
if (pDesc->legacy.cmd.fEOP)
{
/*
=
Feel free to forward upstream.
Best regards
thanks for the patch, however a similar patch was already committed upstream.
G.
Processed: Re: virtualbox memset symbol fix
Processing control commands: > fixed -1 6.1.34-dfsg-2 Bug #1009918 [virtualbox] Virtualbox package is broken Marked as fixed in versions virtualbox/6.1.34-dfsg-2. > close -1 Bug #1009918 [virtualbox] Virtualbox package is broken Marked Bug as done -- 1009918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1010002: libgeos++-dev: Missing files or misconfigured build
Processing commands for cont...@bugs.debian.org: > severity 1010002 normal Bug #1010002 [libgeos++-dev] libgeos++-dev: Missing files or misconfigured build Severity set to 'normal' from 'grave' > tags 1010002 wontfix Bug #1010002 [libgeos++-dev] libgeos++-dev: Missing files or misconfigured build Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010002: libgeos++-dev: Missing files or misconfigured build
Package: libgeos++-dev
Version: 3.10.2-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: pierre.gergon...@gmail.com
Dear Maintainer,
libgeos++-dev is missing .inl files required to build programs with the
C++ interface.
When GEOS is built, the GEOS_INLINE macro is defined. If the package is
find and linked through CMake, this macro is defined as well. However,
building with this macro triggers the inclusion of .inl files which are
explicitly removed by the `rules` file of this package, therefore the
build file.
Looking through the package build history, it seems the GEOS_INLINE definition
has been used for a long time but was not necessary to link against the
library.
For example, compling the following program (main.cpp):
```
#include
int main()
{
geos::geom::Coordinate c;
c.setNull();
return 0;
}
```
Fails to compile with `g++ -o main main.cpp -lgeos` (but this works on
e.g. Debian stable)
On the other hand, adding `-DGEOS_INLINE` also fails because the .inl
files are not shipped with the package.
I think this can be fixed by either:
- removing the explicit removal of .inl files from the `rules` file
- passing `-DDISABLE_GEOS_INLINE:BOOL=ON` during the configuration
The second solution might be less disruptive as this won't require
existing builds to pass `-DGEOS_INLINE` if they are not relying on CMake
to find the correct compilation flags.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-107-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages libgeos++-dev depends on:
ii libgeos-dev3.10.2-1
ii libgeos3.10.2 3.10.2-1
libgeos++-dev recommends no packages.
Versions of packages libgeos++-dev suggests:
pn libgdal-doc
-- no debconf information
Processed: forcibly merging 953032 1009920
Processing commands for cont...@bugs.debian.org:
> forcemerge 953032 1009920
Bug #953032 {Done: Timo Aaltonen } [x11-xkb-utils]
xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
Bug #994036 {Done: Timo Aaltonen } [x11-xkb-utils]
x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some
XF86* with xkb-data 2.33-1)
Bug #1009920 [x11-xkb-utils] Internal error: Could not resolve keysym
XF86EmojiPicker
Severity set to 'critical' from 'normal'
Marked Bug as done
Added indication that 1009920 affects src:awesome
Marked as fixed in versions x11-xkb-utils/7.7+6.
Added tag(s) upstream and fixed-upstream.
Bug #994036 {Done: Timo Aaltonen } [x11-xkb-utils]
x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some
XF86* with xkb-data 2.33-1)
Merged 953032 994036 1009920
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009920
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
994036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997414: marked as done (debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')
Your message dated Fri, 22 Apr 2022 06:33:43 +
with message-id
and subject line Bug#997414: fixed in debomatic 0.25+git20210925-2
has caused the Debian Bug report #997414,
regarding debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debomatic
Version: 0.25-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/docs/_build/latex'
> latexmk -pdf -dvi- -ps- 'Deb-o-Matic.tex'
> Rc files read:
> /etc/LatexMk
> latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
> 'Deb-o-Matic.tex'
>
> Run number 1 of rule 'pdflatex'
>
>
> Running 'pdflatex -recorder "Deb-o-Matic.tex"'
>
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./Deb-o-Matic.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
>
> ! LaTeX Error: File `tgtermes.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.37 \usepackage
> {tgheros}^^M
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on Deb-o-Matic.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from
> following:
> '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
> pdflatex: Command for 'pdflatex' gave return code 1
> Refer to 'Deb-o-Matic.log' for details
> Latexmk: Use the -f option to force complete processing,
> unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'Deb-o-Matic.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[3]: *** [Makefile:29: Deb-o-Matic.pdf] Error 12
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/debomatic_0.25-2_unstable.log
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: debomatic
Source-Version: 0.25+git20210925-2
Done: Luca Falavigna
We believe that the bug you reported is fixed in the latest version of
debomatic, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)
Your message dated Fri, 22 Apr 2022 06:17:07 + with message-id and subject line Bug#1009168: fixed in gzip 1.10-4+deb11u1 has caused the Debian Bug report #1009168, regarding gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability 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.) -- 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xz-utils Version: 5.2.5-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: retitle -2 gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Control: reassign -2 src:gzip 1.10-4 Control: found -2 1.9-3 Hi, The following vulnerability was published for xz-utils and gzip, both have to date assigned the same CVE, and cloning this bug as well for one for gzip. CVE-2022-1271[0]: | zgrep, xzgrep: arbitrary-file-write vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1271 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271 [1] https://www.openwall.com/lists/oss-security/2022/04/07/8 [2] https://git.tukaani.org/?p=xz.git;a=commit;h=69d1b3fc29677af8ade8dc15dba83f0589cb63d6 [3] https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gzip Source-Version: 1.10-4+deb11u1 Done: Milan Kupcevic We believe that the bug you reported is fixed in the latest version of gzip, 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. Milan Kupcevic (supplier of updated gzip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Apr 2022 01:50:32 -0400 Source: gzip Architecture: source Version: 1.10-4+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Milan Kupcevic Closes: 1009168 Changes: gzip (1.10-4+deb11u1) bullseye-security; urgency=high . * zgrep: fix arbitrary-file-write vulnerability addressing CVE-2022-1271 (closes: #1009168) Checksums-Sha1: 594413de8fe673dd1b7d6f819455e5e5b973a902 1812 gzip_1.10-4+deb11u1.dsc 88ef05b5415b7124fdad9976cac8dd29cd915f69 1201421 gzip_1.10.orig.tar.gz 203d8a49717624ef22e35417cf590fd4cfcf5d5d 22952 gzip_1.10-4+deb11u1.debian.tar.xz 071a3f7bb8867017365bbda6aa20bc2b1d659d06 7569 gzip_1.10-4+deb11u1_amd64.buildinfo Checksums-Sha256: 0bcc813d124297ae741573b30db5faefec038aff92616d6ba014f859703f5acf 1812 gzip_1.10-4+deb11u1.dsc c91f74430bf7bc20402e1f657d0b252cb80aa66ba333a25704512af346633c68 1201421 gzip_1.10.orig.tar.gz 183338e989ad327fca8c3281e8452c571bafed0c3cca0b6cea269a34b8dc19d2 22952 gzip_1.10-4+deb11u1.debian.tar.xz d6eabc3167290e67f01f561a09146596a0896578fe86863f91f6cb9d1703e3ea 7569 gzip_1.10-4+deb11u1_amd64.buildinfo Files: 72ba9d8d8a976ecc709c4a2b0c6ed875 1812 utils required gzip_1.10-4+deb11u1.dsc cf9ee51aff167ff69844d5d7d71c8b20 1201421 utils required gzip_1.10.orig.tar.gz 7af1a1f7352fbfd60a24a98798eaab18 22952 utils required gzip_1.10-4+deb11u1.debian.tar.xz 2ee36dac9d3688847c823047eced8414 7569 utils required gzip_1.10-4+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHFBAEBCgAvFiEEVkf/m69krCYf+z+G6e1ngbRVCQ4FAmJUJmgRHG1pbGFuQGRl Ymlhbi5vcmcACgkQ6e1ngbRVCQ4lPAv+Pt76RpCVJJI6pYfaLeRButt3HXjgOm96 t4KttNiRkH5knRAP9cyS4RhPLe4sxTlEVd1zGHvL4zPr3xJLnyfEzB2mgmKngpci ILCf7uPv8p2iBB5CjfFfb2FRb0RJVwbxzCe9bqRHrK0BuIlKvfrIqXHuPSHTBRT8 DS34UVCQlQkj9u9IWTHsjuoYbF5MrfJ25R7Cj98snhYQhm9JQZYnbEM1WZ5ugAEM A5bS9xWhonQaDrhFFppneFBzZyWn/0FeXC2v7mw/TdF4bx/7m3AKP32FrO6fa4Wc QUQ51YX2LMccxUQoWQP/yaGBJzavRcJGOQiFskvap2H8Xfi6IlttdBYeg160r6nV 2gCcnT48CaR7xNAedESlx9ra7oGzk4iXalil51139iAi7PebnNp+fVaV95xpbApu 8FSVFXc9RWzty/obdZb0cyqz4zysFYld3wAAPa5E1jQwa03rRwoaZ6CQ+hUarpbN atY1KsmUb0NDxApZZhrIKE6tAZx62H8N =VdZY -END PGP SIGNATURE End
Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)
Your message dated Fri, 22 Apr 2022 06:17:10 + with message-id and subject line Bug#1009167: fixed in xz-utils 5.2.5-2.1~deb11u1 has caused the Debian Bug report #1009167, regarding xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability 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.) -- 1009167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xz-utils Version: 5.2.5-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: retitle -2 gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Control: reassign -2 src:gzip 1.10-4 Control: found -2 1.9-3 Hi, The following vulnerability was published for xz-utils and gzip, both have to date assigned the same CVE, and cloning this bug as well for one for gzip. CVE-2022-1271[0]: | zgrep, xzgrep: arbitrary-file-write vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1271 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271 [1] https://www.openwall.com/lists/oss-security/2022/04/07/8 [2] https://git.tukaani.org/?p=xz.git;a=commit;h=69d1b3fc29677af8ade8dc15dba83f0589cb63d6 [3] https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xz-utils Source-Version: 5.2.5-2.1~deb11u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of xz-utils, 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. Salvatore Bonaccorso (supplier of updated xz-utils 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, 11 Apr 2022 16:36:49 +0200 Source: xz-utils Architecture: source Version: 5.2.5-2.1~deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Jonathan Nieder Changed-By: Salvatore Bonaccorso Closes: 1009167 Changes: xz-utils (5.2.5-2.1~deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bullseye-security. . xz-utils (5.2.5-2.1) unstable; urgency=medium . * Non-maintainer upload. * xzgrep: Fix escaping of malicious filenames (ZDI-CAN-16587) (CVE-2022-1271) (Closes: #1009167) Checksums-Sha1: aeca0b891c1321ca6b01d9edadb1bda13d7e0e72 2681 xz-utils_5.2.5-2.1~deb11u1.dsc 0b9d1e06b59f7fe0796afe1d93851b9306b4a3b6 1148824 xz-utils_5.2.5.orig.tar.xz 603dd6d6ac39e20b3d1e79f2ead99d060b07c6e2 833 xz-utils_5.2.5.orig.tar.xz.asc c45283b5e9b7aeef049b46a5d9ab6a5c622dd5eb 34948 xz-utils_5.2.5-2.1~deb11u1.debian.tar.xz ed702f163bcb2b12ef8d1416e5c0d1271e6038ee 7033 xz-utils_5.2.5-2.1~deb11u1_source.buildinfo Checksums-Sha256: 68a2702d252ab75789130fc9d2f48b9b38fc0181990c42a947b0d923d9d1922a 2681 xz-utils_5.2.5-2.1~deb11u1.dsc 3e1e518ffc912f86608a8cb35e4bd41ad1aec210df2a47aaa1f95e7f5576ef56 1148824 xz-utils_5.2.5.orig.tar.xz 6efc0075a58912e640119d2b52ef7d1518b260d8720fadc73df21ab7fc727624 833 xz-utils_5.2.5.orig.tar.xz.asc 07627e4c7a50ef91d64c177626507afd6107f44e27f4aacb5e41151d1399ff4f 34948 xz-utils_5.2.5-2.1~deb11u1.debian.tar.xz 22cbe1cc589210d9c57230c2af41bc89ec0ffa6e961fbb540d6077c1f89c4c0b 7033 xz-utils_5.2.5-2.1~deb11u1_source.buildinfo Files: b9ab58414be08f6d0fc1fd6f0029c018 2681 utils optional xz-utils_5.2.5-2.1~deb11u1.dsc aa1621ec7013a19abab52a8aff04fe5b 1148824 utils optional xz-utils_5.2.5.orig.tar.xz aefee8195012884d039461b5073fbd7e 833 utils optional xz-utils_5.2.5.orig.tar.xz.asc 9a1aacd8445046da714369e9a3d49405 34948 utils optional xz-utils_5.2.5-2.1~deb11u1.debian.tar.xz 8dcff42dd049df7c83fe42e22948976f 7033 utils optional xz-utils_5.2.5-2.1~deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmJUPWNfFIAALgAo
Processed: Re: Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf
Processing control commands:
> tags 1009199 confirmed
Bug #1009199 {Done: Paul Gevers } [src:tcpreplay]
src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf
Added tag(s) confirmed.
--
1009199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf
Control: tags 1009199 confirmed Paul Gevers wrote... > 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:tcpreplay has been trying to migrate for 61 days [2]. > Hence, I am filing this bug. Your package fails to build from source on > armhf where it built successfully in the past. Indeed, there are two issues upstream that cause trouble on armhf (and sparc64 ought to be the same story): https://github.com/appneta/tcpreplay/issues/725 https://github.com/appneta/tcpreplay/issues/726 So I will wait a few more days in the hope Fred can take care of these. In case there is no quick solution, I will temporarily drop armhf from the list of architectures to build for, something that hopefully will be for a short time only. Christoph signature.asc Description: PGP signature
Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)
Your message dated Fri, 22 Apr 2022 06:02:29 + with message-id and subject line Bug#1009168: fixed in gzip 1.9-3+deb10u1 has caused the Debian Bug report #1009168, regarding gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability 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.) -- 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xz-utils Version: 5.2.5-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: retitle -2 gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Control: reassign -2 src:gzip 1.10-4 Control: found -2 1.9-3 Hi, The following vulnerability was published for xz-utils and gzip, both have to date assigned the same CVE, and cloning this bug as well for one for gzip. CVE-2022-1271[0]: | zgrep, xzgrep: arbitrary-file-write vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1271 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271 [1] https://www.openwall.com/lists/oss-security/2022/04/07/8 [2] https://git.tukaani.org/?p=xz.git;a=commit;h=69d1b3fc29677af8ade8dc15dba83f0589cb63d6 [3] https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gzip Source-Version: 1.9-3+deb10u1 Done: Milan Kupcevic We believe that the bug you reported is fixed in the latest version of gzip, 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. Milan Kupcevic (supplier of updated gzip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Apr 2022 14:16:55 -0400 Source: gzip Architecture: source Version: 1.9-3+deb10u1 Distribution: buster-security Urgency: high Maintainer: Bdale Garbee Changed-By: Milan Kupcevic Closes: 1009168 Changes: gzip (1.9-3+deb10u1) buster-security; urgency=high . * zgrep: fix arbitrary-file-write vulnerability addressing CVE-2022-1271 (closes: #1009168) * debian/rules: set execute mode bit on test scripts Checksums-Sha1: feb7374a5e034f3782e992c6001c8fdc45e4a01c 1842 gzip_1.9-3+deb10u1.dsc 7d32532059ff1fcec87cc44b86f9456719e0485f 1181937 gzip_1.9.orig.tar.gz 74b8550625dce878120f065390b58c0e2c0811ee 17984 gzip_1.9-3+deb10u1.debian.tar.xz a451a46e6ec7be97cfc3d27e31d2d3fa6dc1992e 6661 gzip_1.9-3+deb10u1_amd64.buildinfo Checksums-Sha256: 9d59e20581097941df44eff5cafb2ed8f3fd416278fbd08723048f6020ccc052 1842 gzip_1.9-3+deb10u1.dsc 5d2d3a3432ef32f24cdb060d278834507b481a75adeca18850c73592f778f6ad 1181937 gzip_1.9.orig.tar.gz 47e692e16f5e1d950fc7a259dc1418c7988dd33f659109e59af90a3384ec01ae 17984 gzip_1.9-3+deb10u1.debian.tar.xz 9b88ad72e38a6ffda804030b53902b9e840b04b11ba7d75764be061b70122839 6661 gzip_1.9-3+deb10u1_amd64.buildinfo Files: 789b70393726b2e2b4203a61da61d82b 1842 utils required gzip_1.9-3+deb10u1.dsc 929d6a6b832f75b28e3eeeafb30c1d9b 1181937 utils required gzip_1.9.orig.tar.gz 4671c1899db302a584e2f1f72bdf0856 17984 utils required gzip_1.9-3+deb10u1.debian.tar.xz 8691b98f7b3066854d7da26c89228621 6661 utils required gzip_1.9-3+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHFBAEBCgAvFiEEVkf/m69krCYf+z+G6e1ngbRVCQ4FAmJa6d4RHG1pbGFuQGRl Ymlhbi5vcmcACgkQ6e1ngbRVCQ4eSwwAkwPLIBj6EXQ7cK3uOWj8h4d0BmAj85u5 /lB3ti+iUUeBxrieDw6eU2moVWbob9uXVrzerJmD2H8P8G1a5UsGHO7yGh64zVt7 BaseqH2bhiLOnsKvQ+3Z+W+u3Q16T+bnSjQT6mRMzni8JEK0PaQYHdnMJ0LzVH5V j3/p2U30L+IcEwibz9lOr0qdetIdvOncZU+nLArU0dufl5PzLDst+WI88Q1C9c5H h96/gEXvvw1ypDzytzqgR/pmXuTT4Bb6ItO3B9wn+c2MLlYhGPo/gKA5kAc5ytHa ERgwAb64nDxveI2eXwShQWoE3BchM35v3QjN2y1sW9BZNTe8MXuaepoGrzenH9ul nlVTZ93DwxJ38UguUnjjFxsyjO8OpHJA8Kdi0X3Xp4+pfvaLvr9jEnm14Gb2hLbM LTSfq/1SEQc+cEGSJeWYnVPvziIPBSAtbycvayqwZFFUS63wiEpJehX73v/V/2d8 94spqtY/mQKOTXFWS2rHLWkAV456LXQc =VDTe
Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)
Your message dated Fri, 22 Apr 2022 06:02:33 + with message-id and subject line Bug#1009167: fixed in xz-utils 5.2.4-1+deb10u1 has caused the Debian Bug report #1009167, regarding xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability 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.) -- 1009167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xz-utils Version: 5.2.5-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: retitle -2 gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Control: reassign -2 src:gzip 1.10-4 Control: found -2 1.9-3 Hi, The following vulnerability was published for xz-utils and gzip, both have to date assigned the same CVE, and cloning this bug as well for one for gzip. CVE-2022-1271[0]: | zgrep, xzgrep: arbitrary-file-write vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1271 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271 [1] https://www.openwall.com/lists/oss-security/2022/04/07/8 [2] https://git.tukaani.org/?p=xz.git;a=commit;h=69d1b3fc29677af8ade8dc15dba83f0589cb63d6 [3] https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xz-utils Source-Version: 5.2.4-1+deb10u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of xz-utils, 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. Salvatore Bonaccorso (supplier of updated xz-utils 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, 11 Apr 2022 16:51:17 +0200 Source: xz-utils Architecture: source Version: 5.2.4-1+deb10u1 Distribution: buster-security Urgency: high Maintainer: Jonathan Nieder Changed-By: Salvatore Bonaccorso Closes: 1009167 Changes: xz-utils (5.2.4-1+deb10u1) buster-security; urgency=high . * Non-maintainer upload by the Security Team. * xzgrep: Fix escaping of malicious filenames (ZDI-CAN-16587) (CVE-2022-1271) (Closes: #1009167) Checksums-Sha1: 19e3aa08702827ad0cc2b3c9829661dd37be952d 2429 xz-utils_5.2.4-1+deb10u1.dsc 1d3a6910c28d40df0134f4a49e5570e8249120c5 1053868 xz-utils_5.2.4.orig.tar.xz 81f46b9cb92e2979fd7335e8ef6a5a01210f82f2 136768 xz-utils_5.2.4-1+deb10u1.debian.tar.xz 39efc04f540b17d41b567060103461178eafeb1b 7025 xz-utils_5.2.4-1+deb10u1_source.buildinfo Checksums-Sha256: 6da82f913d22a8385837b3bb4fb9a89a34a07dea21ea6e73d22b9e225a5c895f 2429 xz-utils_5.2.4-1+deb10u1.dsc 9717ae363760dedf573dad241420c5fea86256b65bc21d2cf71b2b12f0544f4b 1053868 xz-utils_5.2.4.orig.tar.xz fcf83de6468a928427734bca3a39d3813b6f0b6b5beeffaede35bba7f18e3746 136768 xz-utils_5.2.4-1+deb10u1.debian.tar.xz 95be31a5845ca12e0ff30b5b698f7863b3d17b093314701146eb8ecb3b3bb02a 7025 xz-utils_5.2.4-1+deb10u1_source.buildinfo Files: 5419d0cd232cf7f772f0915c56695aeb 2429 utils optional xz-utils_5.2.4-1+deb10u1.dsc 003e4d0b1b1899fc6e3000b24feddf7c 1053868 utils optional xz-utils_5.2.4.orig.tar.xz 651dfa15e015bd3f8d135551010cc394 136768 utils optional xz-utils_5.2.4-1+deb10u1.debian.tar.xz 453579e38bade63162dc0dda87ff615c 7025 utils optional xz-utils_5.2.4-1+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmJUQK5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EPSAP/jzpKk0sdO8RvIqY07jhptynhpNKAbmK MnxY/71vKuvGn6YOpMdmvTTKVLz4KjiXLRyOjDGdGfxFwfxuQrhhmsb2y94GYiL2 l0Vw1EMxj0VtevpqUCG1/McNkPZTlpPDDMuXPEcQsdWYdUxxMhjEBTkPIB36xpeW gXjWejIGScZ7j2G8SvwmwkVmd7xUfh6hHv4OxFKymrmi88ZJONhAmwcCJfVczSLR
