Bug#1009383: marked as done (gromacs: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable')

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1008372: marked as done (sludge: FTBFS: configure: error: Package requirements (glew) were not met)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1008424: audiofile: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2

2022-04-22 Thread Alberto Garcia
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

Processed: xtron: diff for NMU version 1.1a-14.2

2022-04-22 Thread Debian Bug Tracking System
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.

Bug#965910: xtron: diff for NMU version 1.1a-14.2

2022-04-22 Thread Joao Eriberto Mota Filho
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

Processed: yasat: diff for NMU version 848-1.2

2022-04-22 Thread Debian Bug Tracking System
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.

Bug#965911: yasat: diff for NMU version 848-1.2

2022-04-22 Thread Joao Eriberto Mota Filho
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

Bug#965922: zpspell: diff for NMU version 0.4.3-4.2

2022-04-22 Thread Joao Eriberto Mota Filho
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

Processed: zpspell: diff for NMU version 0.4.3-4.2

2022-04-22 Thread Debian Bug Tracking System
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)

Bug#965463: marked as done (cntlm: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009473: marked as done (claws-mail: FTBFS: perl.h:736:25: error: expected expression before ‘do’)

2022-04-22 Thread Debian Bug Tracking System
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:

Bug#1009597: marked as done (node-recast: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2022-04-22 Thread Debian Bug Tracking System
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

Processed: tagging 1009598

2022-04-22 Thread Debian Bug Tracking System
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:

Processed: Bug#1009597 marked as pending in node-recast

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009597: marked as pending in node-recast

2022-04-22 Thread Yadd
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:

Bug#1009581: marked as done (node-zrender: FTBFS: @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation'.)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009581: marked as pending in node-zrender

2022-04-22 Thread Yadd
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:

Processed: Bug#1009581 marked as pending in node-zrender

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009987: marked as done (bluez: Bluetooth service does not start)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009998: Thunar and Nautilus don't show login and password box before conect

2022-04-22 Thread Dramon Conte
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

2022-04-22 Thread Debian Bug Tracking System
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

Bug#997228: marked as done (dee: FTBFS: Dee-1.0.gir:1274.7-1274.42: error: `Dee.Filter' already contains a definition for `new')

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009574: marked as done (node-transformers: FTBFS: TypeError: Cannot read property 'indexOf' of null)

2022-04-22 Thread Debian Bug Tracking System
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

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)

2022-04-22 Thread Debian Bug Tracking System
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

Processed: Bug#1009574 marked as pending in node-transformers

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009574: marked as pending in node-transformers

2022-04-22 Thread Yadd
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:

Bug#1009484: marked as done (node-copy-concurrently: FTBFS: ERROR: Coverage for statements (97.91%) does not meet global threshold (100%))

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009042: marked as done (libtraceevent: FTBFS race condition on parallel build)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009484: marked as pending in node-copy-concurrently

2022-04-22 Thread Yadd
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:

Processed: Bug#1009484 marked as pending in node-copy-concurrently

2022-04-22 Thread Debian Bug Tracking System
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

Processed: cloning 1009484, reassign -1 to node-fs-write-stream-atomic, affects -1 ..., fixed -1 in 1.0.10-6 ...

2022-04-22 Thread Debian Bug Tracking System
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#1009508: marked as done (node-help-me: FTBFS: ERROR: Coverage for statements (88.63%) does not meet global threshold (100%))

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009792: marked as done (mpich: armci-mpi test error: MPIR_pmi_init(151)...: PMIX_Init returned -25)

2022-04-22 Thread Debian Bug Tracking System
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

Processed: Bug#1009508 marked as pending in node-help-me

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009508: marked as pending in node-help-me

2022-04-22 Thread Yadd
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:

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

2022-04-22 Thread Jeff
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)

2022-04-22 Thread Debian Bug Tracking System
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

Processed: severity of 1009568 is important

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009585: marked as pending in node-fd-slicer

2022-04-22 Thread Yadd
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:

Processed: Bug#1009585 marked as pending in node-fd-slicer

2022-04-22 Thread Debian Bug Tracking System
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

Processed: severity of 953032 is normal

2022-04-22 Thread Debian Bug Tracking System
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

Processed: cloning 1009585, severity of -1 is important ...

2022-04-22 Thread Debian Bug Tracking System
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]

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

2022-04-22 Thread Jeff
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

2022-04-22 Thread Markus Blatt
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

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

2022-04-22 Thread Jeff
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

Bug#1009537: marked as done (node-fs-write-stream-atomic: FTBFS: ERROR: Coverage for statements (91.86%) does not meet global threshold (100%))

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009562: marked as done (node-fs.realpath: FTBFS: ERROR: Coverage for statements (21.46%) does not meet global threshold (100%))

2022-04-22 Thread Debian Bug Tracking System
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

Processed: Bug#1009537 marked as pending in node-fs-write-stream-atomic

2022-04-22 Thread Debian Bug Tracking System
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:

Bug#1009537: marked as pending in node-fs-write-stream-atomic

2022-04-22 Thread Yadd
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:

Bug#1009448: libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

2022-04-22 Thread Jeff
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

Bug#1009562: marked as pending in node-fs.realpath

2022-04-22 Thread Yadd
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:

Processed: Bug#1009562 marked as pending in node-fs.realpath

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009918: virtualbox memset symbol fix

2022-04-22 Thread Gianfranco Costamagna
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

Processed: Re: virtualbox memset symbol fix

2022-04-22 Thread Debian Bug Tracking System
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:

Processed: Re: Bug#1010002: libgeos++-dev: Missing files or misconfigured build

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1010002: libgeos++-dev: Missing files or misconfigured build

2022-04-22 Thread Pierre Gergondet
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.

Processed: forcibly merging 953032 1009920

2022-04-22 Thread Debian Bug Tracking System
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

Bug#997414: marked as done (debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)

2022-04-22 Thread Debian Bug Tracking System
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

Processed: Re: Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf

2022-04-22 Thread Christoph Biedl
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,

Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)

2022-04-22 Thread Debian Bug Tracking System
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

Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)

2022-04-22 Thread Debian Bug Tracking System
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