Bug#1001491: marked as done (astroscrappy: autopkgtest regression on armhf)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 07:48:37 + with message-id and subject line Bug#1001491: fixed in astroscrappy 1.1.0-2 has caused the Debian Bug report #1001491, regarding astroscrappy: autopkgtest regression on armhf to be marked as done. This means that you claim that the problem has be

Processed: Re: Bug#1004893: gmt: running gmt results in Segfault

2022-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1004893 unreproducible Bug #1004893 [gmt] gmt: running gmt results in Segfault Added tag(s) unreproducible. > severity 1004893 normal Bug #1004893 [gmt] gmt: running gmt results in Segfault Severity set to 'normal' from 'grave' > thanks Stopp

Bug#1004893: gmt: running gmt results in Segfault

2022-02-02 Thread Daniel Lakeland
Package: gmt Version: 6.3.0+dfsg-2+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: dlake...@street-artists.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Running gmt in any way induces a segfault: dlakelan@tintin:~$

Bug#997478: marked as done (pyls-black: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 04:22:01 + with message-id and subject line Bug#997478: fixed in pyls-black 0.4.6-3.1 has caused the Debian Bug report #997478, regarding pyls-black: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

2022-02-02 Thread Vincent Lefevre
On 2022-02-03 03:29:24 +0100, Vincent Lefevre wrote: > On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote: > > Any chance of getting a coredump? > > exim didn't leave a coredump. I could see that Mutt disables coredumps > after some time. I don't know under which condition. I've eventually found

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

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 02:38:21 + with message-id and subject line Bug#965431: fixed in bfbtester 2.0.1-7.2 has caused the Debian Bug report #965431, regarding bfbtester: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

2022-02-02 Thread Vincent Lefevre
On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote: > Yeah from exim's POV this workes out as designed. Something very much > unexpected happened, let's freeze the message and tell the admin. The > message is not lost. It is still in queue. Yes, once the issue occurs, exim works as designed. But

Bug#1002213: marked as done (dmitry: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested))

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 01:49:51 + with message-id and subject line Bug#1002213: fixed in dmitry 1.3a-1.2 has caused the Debian Bug report #1002213, regarding dmitry: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested) to be marked as

Bug#998920: marked as done (spacearyarya: missing required debian/rules targets build-arch and/or build-indep)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 01:22:04 + with message-id and subject line Bug#998920: fixed in spacearyarya 1.0.2-8 has caused the Debian Bug report #998920, regarding spacearyarya: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means tha

Bug#1004851: marked as done (nvidia-graphics-drivers-tesla-450: CVE-2022-21813, CVE-2022-21814)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Feb 2022 01:21:58 + with message-id and subject line Bug#1004851: fixed in nvidia-graphics-drivers-tesla-450 450.172.01-1 has caused the Debian Bug report #1004851, regarding nvidia-graphics-drivers-tesla-450: CVE-2022-21813, CVE-2022-21814 to be marked as done. Th

Processed: Re: Bugs closed in libtorrent-rasterbar 2.0.5

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 libtorrent-rasterbar/2.0.5-1 Bug #992575 {Done: Christian Marillat } [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on Raspberry Pi 3b Bug #999422 {Done: Christian Marillat } [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError Mar

Processed: Re: Bugs closed in libtorrent-rasterbar 2.0.5

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 libtorrent-rasterbar/2.0.5-1 Bug #999422 {Done: Christian Marillat } [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError Bug #992575 {Done: Christian Marillat } [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on Raspberry Pi 3b Mar

Bug#992575: Bugs closed in libtorrent-rasterbar 2.0.5

2022-02-02 Thread Paul Wise
Control: fixed -1 libtorrent-rasterbar/2.0.5-1 On Wed, 2022-02-02 at 15:50 +0100, Christian Marillat wrote: > Subject: Bugs closed in libtorrent-rasterbar 2.0.5 > Cc: 969780-cl...@bugs.debian.org, 992575-cl...@bugs.debian.org, > 856600-cl...@bugs.debian.org, 987120-cl...@bugs.debian.org, > 916399

Processed: Re: Bug#1004299: ruby-net-ssh: FTBFS in sid

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/net-ssh/net-ssh/issues/843 Bug #1004299 [ruby-net-ssh] ruby-net-ssh: FTBFS in sid Changed Bug forwarded-to-address to 'https://github.com/net-ssh/net-ssh/issues/843' from 'https://github.com/ruby/openssl/issues/483'. -- 1004299: ht

Bug#1004299: ruby-net-ssh: FTBFS in sid

2022-02-02 Thread Antonio Terceiro
Control: forwarded -1 https://github.com/net-ssh/net-ssh/issues/843 On Mon, Jan 24, 2022 at 03:35:35PM +0100, Cédric Boutillier wrote: > Package: ruby-net-ssh > Version: 1:6.1.0-2 > > Hi, > > When trying to rebuild ruby-net-ssh in sid, I get test failures related > to DSA cryptography. They all

Bug#1004230: marked as done (libgpuarray: please drop upstreamtestsclblas until bug 949767 is fixed)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 22:34:17 + with message-id and subject line Bug#1004230: fixed in libgpuarray 0.7.6-9 has caused the Debian Bug report #1004230, regarding libgpuarray: please drop upstreamtestsclblas until bug 949767 is fixed to be marked as done. This means that you claim

Bug#1003756: marked as done (squeekboard, build-depends unsatisfiable)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 21:21:24 + with message-id and subject line Bug#1003756: fixed in squeekboard 1.16.0-1 has caused the Debian Bug report #1003756, regarding squeekboard, build-depends unsatisfiable to be marked as done. This means that you claim that the problem has been de

Bug#1004736: marked as done (libgupnp-dlna-2.0-4: missing Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 0.12))

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 21:19:51 + with message-id and subject line Bug#1004736: fixed in gupnp-dlna 0.12.0-3 has caused the Debian Bug report #1004736, regarding libgupnp-dlna-2.0-4: missing Breaks+Replaces: libgupnp-dlna-2.0-3 (<< 0.12) to be marked as done. This means that you

Bug#1004875: python-fluids: autopkgtest regression on arm64, i386 and ppc64el:

2022-02-02 Thread Paul Gevers
Source: python-fluids Version: 1.0.9-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-fluids the autopkgtest of python-fluids fails in testing when that autopkgtest is run with t

Bug#1004873: python-django-netfields: autopkgtest regression: runuser: not found

2022-02-02 Thread Paul Gevers
Source: python-django-netfields Version: 1.2.4-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-django-netfields the autopkgtest of python-django-netfields fails in testing when

Processed: Bug#1003756 marked as pending in squeekboard

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1003756 [squeekboard] squeekboard, build-depends unsatisfiable Added tag(s) pending. -- 1003756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1003756: marked as pending in squeekboard

2022-02-02 Thread Arnaud Ferraris
Control: tag -1 pending Hello, Bug #1003756 in squeekboard 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/DebianOnMobile-team/squeekboard/-/commit/fcebac903533

Bug#1004870: python-xarray: autopkgtest regression on s390x

2022-02-02 Thread Graham Inggs
Source: python-xarray Version: 0.21.0-1 X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer python-xarray's autopkgtests are failing on the big-endian s390x architecture [1]. I've copied what

Bug#1004869: python-xarray: autopkgtest regression on i386

2022-02-02 Thread Graham Inggs
Source: python-xarray Version: 0.21.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer python-xarray's autopkgtests are failing on the i386 architecture [1]. I've copied what I hope is the relevant part of the log bel

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Julian Gilbey
On Wed, Feb 02, 2022 at 01:33:30PM +, Gordon Ball wrote: > ps, I had a search just now and it looks like someone else was working > 1 year ago on `ptvsd` (renamed `debugpy` later), but it doesn't look > like it was ever uploaded. But perhaps something to build upon. > > https://salsa.debia

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

2022-02-02 Thread Andreas Metzler
On 2022-02-01 Vincent Lefevre wrote: > On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote: > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to > > immutable memory) > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of > > 7 bytes (pipeheader) fr

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Julian Gilbey
On Wed, Feb 02, 2022 at 01:33:30PM +, Gordon Ball wrote: > On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > > Package: python3-ipykernel > > Version: 6.7.0-1 > > Severity: serious > > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > > > ps, I had a search just now and it looks

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Julian Gilbey
On Wed, Feb 02, 2022 at 01:06:56PM +, Gordon Ball wrote: > On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > > Package: python3-ipykernel > > Version: 6.7.0-1 > > Severity: serious > > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > > > > ipykernel depends on the debugpy packag

Bug#1004864: density-fitness FTBFS with libpdb-redo-dev 2.0.1

2022-02-02 Thread Adrian Bunk
Source: density-fitness Version: 1.0.0-4 Severity: serious Tags: ftbfs Forwarded: https://github.com/PDB-REDO/density-fitness/commit/cad04e1ac86037537c75bfaa67db49946f140b3c https://buildd.debian.org/status/logs.php?pkg=density-fitness&ver=1.0.0-4%2Bb1 ... dh_auto_build -a make -j4 ma

Bug#1004863: Bootstrapping a Fedora produces a system with an empty package database

2022-02-02 Thread Enrico Zini
Package: dnf Version: 4.5.2-6 Severity: serious Hello, thank you for packaging dnf in Debian! I'm trying to use dnf to bootstrap rpm-based chroots, which seems to work, but the rpm package database on the resulting distribution is empty, as in, `rpm -qa` returns no output, and `rpm -q` on any pa

Bug#1004748: guestfs-tools ftbfs with new ocaml

2022-02-02 Thread Stéphane Glondu
On Tue, 1 Feb 2022 16:23:47 +0100 Matthias Klose wrote: > Package: src:guestfs-tools > Version: 1.46.1-4 > Severity: serious > Tags: sid bookworm > > guestfs-tools ftbfs with new ocaml > > [...] > Use the equivalent signed form: +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3. > Hint: Enabling or disabling a wa

Bug#997367: virt-manager: FTBFS: AssertionError

2022-02-02 Thread Fabio Fantoni
Il 02/02/2022 11:56, Bastian Germann ha scritto: > On Tue, 25 Jan 2022 17:55:18 +0100 Fabio Fantoni wrote: >> Hi, I saw that remain few days for autoremoval from testing I prepared an MR with some upstream patch that solve current FTBFS with some tests and another small fix for a crash case:

Bug#999907: marked as done (libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 16:04:32 + with message-id and subject line Bug#07: fixed in galib 1:2.4.7-6 has caused the Debian Bug report #07, regarding libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a to be marked as done. This means that you claim

Bug#1004331: marked as done (pytorch: b-d on python3-all-dev, but not built for all supported Python3 versions)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 16:05:14 + with message-id and subject line Bug#1004331: fixed in pytorch 1.8.1-4 has caused the Debian Bug report #1004331, regarding pytorch: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means that y

Bug#1002548: marked as done (libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Feb 2022 16:35:25 +0100 with message-id <6953cc0f-8fcd-a0db-f246-33d84dc66...@alteholz.de> and subject line bug#1002548: fixed in libfli 2.0-2 has caused the Debian Bug report #1002548, regarding libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules to be marked as do

Bug#999422: marked as done (Deluge fails with ModuleNotFoundError)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 15:50:54 +0100 with message-id <87v8xx2ugh@christian.marillat.net> and subject line Bugs closed in libtorrent-rasterbar 2.0.5 has caused the Debian Bug report #992575, regarding Deluge fails with ModuleNotFoundError to be marked as done. This means that you

Bug#992575: marked as done (libtorrent-rasterbar10: import fails on Raspberry Pi 3b)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 15:50:54 +0100 with message-id <87v8xx2ugh@christian.marillat.net> and subject line Bugs closed in libtorrent-rasterbar 2.0.5 has caused the Debian Bug report #992575, regarding libtorrent-rasterbar10: import fails on Raspberry Pi 3b to be marked as done. Th

Processed: severity of 1004859 is normal

2022-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004859 normal Bug #1004859 [vim] vim : CVE-2022-0318 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1004859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10048

Bug#1004859: vim : CVE-2022-0318

2022-02-02 Thread YABUKI Yukiharu
Package: vim Version: 2:8.2.3995-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Dear Maintainer, You may already know vim has CVE-2022-0318 NVD - CVE-2022-0318 https://nvd.nist.gov/vuln/detail/CVE-2022-0318 And upstram has already

Bug#1004046: marked as done (python-aioamqp: autopkgtest regression: No module named 'pamqp.commands')

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 13:50:02 + with message-id and subject line Bug#1004046: fixed in python-aioamqp 0.14.0-5 has caused the Debian Bug report #1004046, regarding python-aioamqp: autopkgtest regression: No module named 'pamqp.commands' to be marked as done. This means that yo

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Gordon Ball
On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > Package: python3-ipykernel > Version: 6.7.0-1 > Severity: serious > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > ps, I had a search just now and it looks like someone else was working 1 year ago on `ptvsd` (renamed `debugpy` late

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Gordon Ball
On Wed, Feb 02, 2022 at 11:35:19AM +, Julian Gilbey wrote: > Package: python3-ipykernel > Version: 6.7.0-1 > Severity: serious > X-Debbugs-Cc: Julien Puydt , Gordon Ball > > > ipykernel depends on the debugpy package, as stated in setup.py. > However, within Debian build, python3-debugpy is

Processed: well, raising severity did not block migration

2022-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004710 normal Bug #1004710 [passwd] passwd: 4.11.1 breaks mmdebstrap testsuite by empty directories in /var/mail and /var/spool/mail Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you ne

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

2022-02-02 Thread Vincent Lefevre
On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote: > 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to > immutable memory) > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of 7 > bytes (pipeheader) from transport process 35015 for transport smtp A

Bug#1004855: python3-ipykernel: missing dependency on debugpy

2022-02-02 Thread Julian Gilbey
Package: python3-ipykernel Version: 6.7.0-1 Severity: serious X-Debbugs-Cc: Julien Puydt , Gordon Ball ipykernel depends on the debugpy package, as stated in setup.py. However, within Debian build, python3-debugpy is not listed in the Build-Depends, so the resulting binary package does not Depen

Bug#1002187: marked as done (junos-eznc: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 11:04:20 + with message-id and subject line Bug#1002187: fixed in junos-eznc 2.1.7-4 has caused the Debian Bug report #1002187, regarding junos-eznc: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 to be mar

Bug#997367: virt-manager: FTBFS: AssertionError

2022-02-02 Thread Bastian Germann
On Tue, 25 Jan 2022 17:55:18 +0100 Fabio Fantoni wrote: Hi, I saw that remain few days for autoremoval from testing I prepared an MR with some upstream patch that solve current FTBFS with some tests and another small fix for a crash case: https://salsa.debian.org/libvirt-team/virt-manager/-/m

Bug#1002187: marked as pending in junos-eznc

2022-02-02 Thread Benjamin Drung
Control: tag -1 pending Hello, Bug #1002187 in junos-eznc 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/python-team/packages/junos-eznc/-/commit/ba88629cf70ce

Processed: Bug#1002187 marked as pending in junos-eznc

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002187 [src:junos-eznc] junos-eznc: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1002187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002187 Debian Bug Tracki

Processed: nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 -3 -4 -5 -6 -7 Bug #1004847 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814 Bug 1004847 cloned as bugs 1004848-1004853 > reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Bug #1004848 [src:nvidia-graphics

Bug#1004847: nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814

2022-02-02 Thread Andreas Beckmann
Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-21813, CVE-2022-21814 Control: tag -2 + wontfix Co

Bug#998586: marked as done (libgxps: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg")

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 10:19:57 + with message-id and subject line Bug#998586: fixed in libgxps 0.3.2-2 has caused the Debian Bug report #998586, regarding libgxps: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg" to be marked as done. This means that you claim

Bug#998586: marked as pending in libgxps

2022-02-02 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #998586 in libgxps reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/libgxps/-/commit/d59208d95950ea4726f4e8fea6d827

Processed: Bug#998586 marked as pending in libgxps

2022-02-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998586 [src:libgxps] libgxps: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg" Added tag(s) pending. -- 998586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998586 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: severity of 1004843 is normal

2022-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004843 normal Bug #1004843 [iputils-ping] debina bullseye: ping (from iputils-ping) throwing inappropriate error message if IPv6 is disabled Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me

Processed: tagging 1004843, bug 1004843 is forwarded to https://github.com/iputils/iputils/issues/293

2022-02-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1004843 + upstream Bug #1004843 [iputils-ping] debina bullseye: ping (from iputils-ping) throwing inappropriate error message if IPv6 is disabled Added tag(s) upstream. > forwarded 1004843 https://github.com/iputils/iputils/issues/293 Bug #1

Bug#1004798: marked as done (libpdb-redo FTBFS with libcifpp 2.0.4)

2022-02-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Feb 2022 08:35:33 + with message-id and subject line Bug#1004798: fixed in libpdb-redo 2.0.1-3 has caused the Debian Bug report #1004798, regarding libpdb-redo FTBFS with libcifpp 2.0.4 to be marked as done. This means that you claim that the problem has been dealt