Bug#1005981: redet: diff for NMU version 8.26-1.5

2022-04-15 Thread Joao Eriberto Mota Filho
Control: tags 1005981 + patch Dear maintainer, I've prepared an NMU for redet (versioned as 8.26-1.5) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru redet-8.26/debian/changelog redet-8.26/debian/changelog ---

Processed: redet: diff for NMU version 8.26-1.5

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 1005981 + patch Bug #1005981 [src:redet] Please migrate away from dpatch Added tag(s) patch. -- 1005981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: iisemulator: diff for NMU version 0.95-3.4

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 998919 + patch Bug #998919 [src:iisemulator] iisemulator: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998919 + pending Bug #998919 [src:iisemulator] iisemulator: missing required debian/rules targets

Bug#998919: iisemulator: diff for NMU version 0.95-3.4

2022-04-15 Thread Joao Eriberto Mota Filho
Control: tags 998919 + patch Control: tags 998919 + pending Dear maintainer, I've prepared an NMU for iisemulator (versioned as 0.95-3.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -u iisemulator-0.95/debian/changelog

Bug#999268: vncsnapshot: diff for NMU version 1.2a-5.2

2022-04-15 Thread Joao Eriberto Mota Filho
Control: tags 999268 + patch Control: tags 999268 + pending Dear maintainer, I've prepared an NMU for vncsnapshot (versioned as 1.2a-5.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru vncsnapshot-1.2a/debian/changelog

Processed: vncsnapshot: diff for NMU version 1.2a-5.2

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 999268 + patch Bug #999268 [src:vncsnapshot] vncsnapshot: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999268 + pending Bug #999268 [src:vncsnapshot] vncsnapshot: missing required debian/rules targets

Processed: cadaver: diff for NMU version 0.23.3-2.2

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 668477 + pending Bug #668477 [cadaver] [PATCH] cadaver: Helping to update to packaging format 3.0 Ignoring request to alter tags of bug #668477 to the same tags previously set > tags 965443 + patch Bug #965443 [src:cadaver] cadaver: Removal of obsolete

Processed: cadaver: diff for NMU version 0.23.3-2.2

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 668477 + pending Bug #668477 [cadaver] [PATCH] cadaver: Helping to update to packaging format 3.0 Added tag(s) pending. > tags 965443 + patch Bug #965443 [src:cadaver] cadaver: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags

Bug#668477: cadaver: diff for NMU version 0.23.3-2.2

2022-04-15 Thread Joao Eriberto Mota Filho
Control: tags 668477 + pending Control: tags 965443 + patch Control: tags 965443 + pending Dear maintainer, I've prepared an NMU for cadaver (versioned as 0.23.3-2.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru

Bug#1008945: marked as done (salt: CVE-2022-22934 CVE-2022-22935 CVE-2022-22936 CVE-2022-22941)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 02:34:24 + with message-id and subject line Bug#1008945: fixed in salt 3004.1+dfsg-1 has caused the Debian Bug report #1008945, regarding salt: CVE-2022-22934 CVE-2022-22935 CVE-2022-22936 CVE-2022-22941 to be marked as done. This means that you claim that

Bug#1006350: marked as done (pidgin: crashes when typing past visible number of lines)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 01:19:04 + with message-id and subject line Bug#1006350: fixed in pidgin 2.14.8-3 has caused the Debian Bug report #1006350, regarding pidgin: crashes when typing past visible number of lines to be marked as done. This means that you claim that the problem

Bug#1006350: pidgin: crashes when typing past visible number of lines

2022-04-15 Thread Richard Laager
This has hopefully been fully fixed now (upstream). It will land in the 2.14.9 release, which should be coming next week. However, I've uploaded a backport of it now. -- Richard

Processed: Re: Bug#1006350: pidgin: crashes when typing past visible number of lines

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1006350 + upstream fixed-upstream pending Bug #1006350 [pidgin] pidgin: crashes when typing past visible number of lines Added tag(s) fixed-upstream and pending. > forwarded 1006350 https://issues.imfreedom.org/issue/PIDGIN-17413 Bug

Bug#1009733: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-04-15 Thread Michael Biebl
Dear arm porters, can you please take a look at this? Thanks, Michael Am 15.04.22 um 21:19 schrieb Paul Gevers: Source: exempi Version: 2.5.2-1 Severity: serious Control: close -1 2.6.1-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear

Bug#1009737: marked as done (pillow breaks pikepdf autopkgtest: assert im.getpixel((1, 1)) == rgb fails)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 22:05:02 + with message-id and subject line Bug#1009737: fixed in pikepdf 5.1.1+dfsg-1 has caused the Debian Bug report #1009737, regarding pillow breaks pikepdf autopkgtest: assert im.getpixel((1, 1)) == rgb fails to be marked as done. This means that

Bug#983961: advancecomp: diff for NMU version 2.1-2.2

2022-04-15 Thread Marcos Talau
Control: tags 983961 + pending Dear maintainer, I've prepared an NMU for advancecomp (versioned as 2.1-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru advancecomp-2.1/debian/changelog advancecomp-2.1/debian/changelog ---

Processed: advancecomp: diff for NMU version 2.1-2.2

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags 983961 + pending Bug #983961 [src:advancecomp] advancecomp: ftbfs with GCC-11 Added tag(s) pending. -- 983961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#979095: Legally problematic GPL-3+ readline dependency

2022-04-15 Thread Bastian Germann
On Thu, 14 Oct 2021 09:52:51 +0200 Bastian Germann wrote: On Sat, 2 Jan 2021 18:36:38 +0100 Bastian Germann wrote: > There is an easy solution to the problem: Replacing the build dependency > libreadline-dev with libeditreadline-dev links with the BSD-licensed > libedit library which is a

Bug#1009740: marked as done (nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 21:09:40 + with message-id and subject line Bug#1009740: fixed in nvidia-graphics-drivers-tesla-450 450.172.01-3 has caused the Debian Bug report #1009740, regarding nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't

Bug#1009462: marked as done (pyqi: FTBFS: Only Python 3.8 and 3.9 are supported.E: pybuild pybuild:369: configure: plugin distutils failed with: exit code=1: python3.10 setup.py config)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 20:48:42 + with message-id and subject line Bug#1009462: fixed in pyqi 0.3.2+dfsg-8 has caused the Debian Bug report #1009462, regarding pyqi: FTBFS: Only Python 3.8 and 3.9 are supported.E: pybuild pybuild:369: configure: plugin distutils failed with:

Bug#1009462: marked as pending in pyqi

2022-04-15 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #1009462 in pyqi 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#1009462 marked as pending in pyqi

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009462 [src:pyqi] pyqi: FTBFS: Only Python 3.8 and 3.9 are supported.E: pybuild pybuild:369: configure: plugin distutils failed with: exit code=1: python3.10 setup.py config Added tag(s) pending. -- 1009462:

Bug#1009462: I think we can remove pyqi (Was: Bug#1009462: pyqi: FTBFS: Only Python 3.8 and 3.9 are supported.E: pybuild pybuild:369: configure: plugin distutils failed with: exit code=1: python3.10 s

2022-04-15 Thread Nilesh Patra
On Wed, Apr 13, 2022 at 09:49:35AM +0200, Andreas Tille wrote: > Hi, > > if I remember correctly pyqi was packaged for qiime 1.x. > It has no rdepends any more and I think we should remove it. I got a few spare minutes so I fixed the RC bug. > Does anybody think differently? It is always good

Bug#1009741: mercurial: flaky autopkgtest which times out on amd64 regularly

2022-04-15 Thread Paul Gevers
Source: mercurial Version: 6.1.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up as a regression for the upload of

Bug#1009740: nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el

2022-04-15 Thread Paul Gevers
Hi Andreas, On 15-04-2022 22:24, Andreas Beckmann wrote: It's probably the same issue for all nvidia-graphics-driver-tesla-xxx. Hence I decided to stop after one bug report for now :). Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1009740: nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el

2022-04-15 Thread Andreas Beckmann
Working on it. It's probably the same issue for all nvidia-graphics-driver-tesla-xxx. Andreas

Processed: nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:dkms Bug #1009740 [src:nvidia-graphics-drivers-tesla-450] nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el Added indication that 1009740 affects src:dkms -- 1009740:

Bug#1009740: nvidia-graphics-drivers-tesla-450: new version of dkms seems to show the package doesn't work on arm64 and ppc64el

2022-04-15 Thread Paul Gevers
Source: nvidia-graphics-drivers-tesla-450 Version: 450.172.01-2 Severity: serious X-Debbugs-CC: d...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:dkms Dear maintainer(s), With a recent upload of dkms the autopkgtest of

Bug#1009739: python3.10 breaks yade autopkgtest on i386: Segmentation fault

2022-04-15 Thread Paul Gevers
Source: python3.10, yade Control: found -1 python3.10/3.10.4-3 Control: found -1 yade/2022.01a-7 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python3.10 the autopkgtest of yade fails in testing

Processed: python3.10 breaks yade autopkgtest on i386: Segmentation fault

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 python3.10/3.10.4-3 Bug #1009739 [src:python3.10, src:yade] python3.10 breaks yade autopkgtest on i386: Segmentation fault Marked as found in versions python3.10/3.10.4-3. > found -1 yade/2022.01a-7 Bug #1009739 [src:python3.10, src:yade] python3.10 breaks

Bug#1009737: pillow breaks pikepdf autopkgtest: assert im.getpixel((1, 1)) == rgb fails

2022-04-15 Thread Paul Gevers
Source: pillow, pikepdf Control: found -1 pillow/9.1.0-1 Control: found -1 pikepdf/5.0.1+dfsg-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of pillow the autopkgtest of pikepdf fails in testing

Processed: pillow breaks pikepdf autopkgtest: assert im.getpixel((1, 1)) == rgb fails

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 pillow/9.1.0-1 Bug #1009737 [src:pillow, src:pikepdf] pillow breaks pikepdf autopkgtest: assert im.getpixel((1, 1)) == rgb fails Marked as found in versions pillow/9.1.0-1. > found -1 pikepdf/5.0.1+dfsg-1 Bug #1009737 [src:pillow, src:pikepdf] pillow

Bug#1006815: marked as done (xmoto: autopkgtest often fails: Failed to connect to X-Moto: Connection refused)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 19:54:24 + with message-id and subject line Bug#1006815: fixed in xmoto 0.6.1+repack-8 has caused the Debian Bug report #1006815, regarding xmoto: autopkgtest often fails: Failed to connect to X-Moto: Connection refused to be marked as done. This means

Bug#1009736: python-django-netfields: autopkgtest regression: No module named 'django'

2022-04-15 Thread Paul Gevers
Source: python-django-netfields Version: 1.3.0-1 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 that autopkgtest is run with the binary

Processed: Bug#1006815 marked as pending in xmoto

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1006815 [src:xmoto] xmoto: autopkgtest often fails: Failed to connect to X-Moto: Connection refused Added tag(s) pending. -- 1006815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006815 Debian Bug Tracking System Contact

Bug#1006815: marked as pending in xmoto

2022-04-15 Thread Stephen Kitt
Control: tag -1 pending Hello, Bug #1006815 in xmoto 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#965852: marked as done (ucarp: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 19:22:25 + with message-id and subject line Bug#965852: fixed in ucarp 1.5.2-2.3 has caused the Debian Bug report #965852, regarding ucarp: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1009201: marked as done (toil: (autopkgtest) needs update for python3.10: No such file or directory: 'python3.9')

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 19:22:13 + with message-id and subject line Bug#1009201: fixed in toil 5.6.0-6 has caused the Debian Bug report #1009201, regarding toil: (autopkgtest) needs update for python3.10: No such file or directory: 'python3.9' to be marked as done. This means

Bug#957892: marked as done (ucarp: ftbfs with GCC-10)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 19:22:25 + with message-id and subject line Bug#957892: fixed in ucarp 1.5.2-2.3 has caused the Debian Bug report #957892, regarding ucarp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1009733: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-04-15 Thread Paul Gevers
Source: exempi Version: 2.5.2-1 Severity: serious Control: close -1 2.6.1-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Processed: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.6.1-1 Bug #1009733 [src:exempi] src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf Marked as fixed in versions exempi/2.6.1-1. Bug #1009733 [src:exempi] src:exempi: fails to migrate to testing for too long: FTBFS on armel and

Processed: src:ghdl: fails to migrate to testing for too long: ftbfs on armhf

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.0+dfsg-8 Bug #1009732 [src:ghdl] src:ghdl: fails to migrate to testing for too long: ftbfs on armhf Marked as fixed in versions ghdl/1.0.0+dfsg-8. Bug #1009732 [src:ghdl] src:ghdl: fails to migrate to testing for too long: ftbfs on armhf Marked Bug as

Bug#1009732: src:ghdl: fails to migrate to testing for too long: ftbfs on armhf

2022-04-15 Thread Paul Gevers
Source: ghdl Version: 1.0.0+dfsg-6 Severity: serious Control: close -1 1.0.0+dfsg-8 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more

Processed: libglu1-mesa-dev: pkg-config file glu.pc depends on opengl.pc

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > block 1008372 by -1 Bug #1008372 [src:sludge] sludge: FTBFS: configure: error: Package requirements (glew) were not met 1008372 was not blocked by any bugs. 1008372 was not blocking any bugs. Added blocking bug(s) of 1008372: 1009731 -- 1008372:

Bug#1009731: libglu1-mesa-dev: pkg-config file glu.pc depends on opengl.pc

2022-04-15 Thread Tobias Hansen
Package: libglu1-mesa-dev Version: 9.0.2-1 Severity: serious Control: block 1008372 by -1 Hi, recently sludge started to FTBFS with the following error, see #1008372: Package 'opengl', required by 'glu', not found I believe this is because glu.pc now depends on opengl.pc which means that

Bug#1009241: marked as done (sagemath: autokgtest regression on armhf)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 17:45:39 + with message-id and subject line Bug#1009241: fixed in sagemath 9.5-4 has caused the Debian Bug report #1009241, regarding sagemath: autokgtest regression on armhf to be marked as done. This means that you claim that the problem has been dealt

Processed: bug 1009408 is forwarded to https://gitlab.kitware.com/cmake/cmake/-/issues/23432

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1009408 https://gitlab.kitware.com/cmake/cmake/-/issues/23432 Bug #1009408 [cmake] Failed visibility checks with qa=+canary Set Bug forwarded-to-address to 'https://gitlab.kitware.com/cmake/cmake/-/issues/23432'. > thanks Stopping

Bug#1009421: marked as done (libktoblzcheck: FTBFS: dh_missing: error: missing files, aborting)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 15:50:46 + with message-id and subject line Bug#1009421: fixed in libktoblzcheck 1.53-3 has caused the Debian Bug report #1009421, regarding libktoblzcheck: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim

Bug#1009421: libktoblzcheck: FTBFS: dh_missing: error: missing files, aborting

2022-04-15 Thread Micha Lenk
Control: tags -1 bookworm This bug does not affect Debian bullseye.

Processed: Re: Bug#1009421: libktoblzcheck: FTBFS: dh_missing: error: missing files, aborting

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 bookworm Bug #1009421 [src:libktoblzcheck] libktoblzcheck: FTBFS: dh_missing: error: missing files, aborting Ignoring request to alter tags of bug #1009421 to the same tags previously set -- 1009421:

Bug#1000420: marked as done (irqtop output is messed up by ruby warning)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 15:35:45 + with message-id and subject line Bug#958973: fixed in ruby-curses 1.4.4-1 has caused the Debian Bug report #958973, regarding irqtop output is messed up by ruby warning to be marked as done. This means that you claim that the problem has been

Bug#958973: marked as done (ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", fixed upstream in 1.3.2)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 15:35:45 + with message-id and subject line Bug#958973: fixed in ruby-curses 1.4.4-1 has caused the Debian Bug report #958973, regarding ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", fixed upstream in 1.3.2 to be marked as done.

Bug#1009397: marked as done (solo-python: FTBFS: dh_usrlocal: error: debian/solo-python/usr/local/bin/solo is not a directory)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 15:35:53 + with message-id and subject line Bug#1009397: fixed in solo-python 0.1.1-2 has caused the Debian Bug report #1009397, regarding solo-python: FTBFS: dh_usrlocal: error: debian/solo-python/usr/local/bin/solo is not a directory to be marked as

Processed: Re: Bug#1009408: cubeb: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 cmake 3.23.0-1 Bug #1009408 [src:cubeb] cubeb: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Bug reassigned from package 'src:cubeb' to 'cmake'. No longer marked as found in versions

Bug#1009397: dh-python: Flit plugin suddenly installs to usr/local/ causing FTBFS

2022-04-15 Thread Stefano Rivera
Hi Philip (2022.04.15_14:06:28_+) > I think I found a way to fix it, just like you did it here > https://salsa.debian.org/python-team/tools/dh-python/-/commit/6137db4dc870672615c31c9d1c9535dafe5b0d2a > I'll create a MR later. Aha, of course. You can try to use the pyproject plugin, directly

Bug#1009397: dh-python: Flit plugin suddenly installs to usr/local/ causing FTBFS

2022-04-15 Thread Stefano Rivera
Hi Philip (2022.04.15_08:44:42_+) > I'm writing to the list as I'm not sure what the source of the problem is. It'll be something related to https://lists.debian.org/debian-python/2022/03/msg00039.html I'll have a more detailed look, later today. SR -- Stefano Rivera

Processed: Re: Bug#958973: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", fixed upstream in 1.3.2

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #958973 [ruby-curses] ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", fixed upstream in 1.3.2 Bug #1000420 [ruby-curses] irqtop output is messed up by ruby warning Severity set to 'serious' from 'important' Severity

Bug#1009434: marked as done (sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009445: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009445, regarding sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1009445: marked as done (sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009445: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009445, regarding sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10"

Bug#1009445: marked as done (sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009434: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009434, regarding sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10"

Bug#1009382: marked as done (sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009445: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009445, regarding sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1009434: marked as done (sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009434: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009434, regarding sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1009382: marked as done (sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009434: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009434, regarding sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1009445: marked as done (sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009382: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009382, regarding sphinxcontrib-serializinghtml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10"

Bug#1009382: marked as done (sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009382: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009382, regarding sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1009434: marked as done (sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:37:22 + with message-id and subject line Bug#1009382: fixed in sphinx 4.5.0-2 has caused the Debian Bug report #1009382, regarding sphinxcontrib-qthelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned

Bug#1008787: marked as done (NGINX FTBFS (mips64el, e390x): Lua dependencies missing)

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 11:23:11 + with message-id and subject line Bug#1008787: fixed in nginx 1.18.0-9 has caused the Debian Bug report #1008787, regarding NGINX FTBFS (mips64el, e390x): Lua dependencies missing to be marked as done. This means that you claim that the problem

Processed: Reassigning bugs to sphinx

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1009382 python3-sphinx 4.5.0-1 Bug #1009382 [src:sphinxcontrib-devhelp] sphinxcontrib-devhelp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13 Bug reassigned from package

Bug#1009721: gst-plugins-bad1.0 build-depends on obsolete package.

2022-04-15 Thread peter green
Package: gst-plugins-bad1.0 Version: 1.20.1-1 Severity: serious Justification: rc policy - "packages must be buildable within the same release" gst-plugins-bad1.0 build-depends on libwpewebkit-1.0-dev which is no longer built by the wpewebkit source package. It is still present in unstable as a

Bug#1009481: marked as done (gcc-mingw-w64: FTBFS: ../../../../src/libgfortran/runtime/error.c:145:22: error: ‘buffer’ undeclared (first use in this function))

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 10:51:13 + with message-id and subject line Bug#1009481: fixed in gcc-mingw-w64 24.4 has caused the Debian Bug report #1009481, regarding gcc-mingw-w64: FTBFS: ../../../../src/libgfortran/runtime/error.c:145:22: error: ‘buffer’ undeclared (first use in

Processed: raise severity of python3.10 bugs

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004446 serious Bug #1004446 [cdist] cdist: FTBFS against python 3.10 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1004446:

Processed: Re: Bug#1009682: ghostscript breaks openscad autopkgtest

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1009682 src:openscad Bug #1009682 [src:ghostscript, src:openscad] ghostscript breaks openscad autopkgtest Bug reassigned from package 'src:ghostscript, src:openscad' to 'src:openscad'. No longer marked as found in versions

Bug#1009682: ghostscript breaks openscad autopkgtest

2022-04-15 Thread Kristian Nielsen
Control: reassign Thanks for the report, I will upload shortly a fixed openscad package. - Kristian. Paul Gevers writes: > With a recent upload of ghostscript the autopkgtest of openscad fails > in testing when that autopkgtest is run with the binary packages of > ghostscript from unstable.

Processed: raise severity of python3.10 bugs

2022-04-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004913 serious Bug #1004913 [python-fysom] python-fysom: incompatible import from collections in py3.10 Severity set to 'serious' from 'normal' > severity 1005145 serious Bug #1005145 [oz] oz: FTBFS against python 3.10 Severity set to

Bug#1009607: marked as done (node-readable-stream: FTBFS: ERROR: Coverage for statements (94.31%) does not meet global threshold (100%))

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 07:20:18 + with message-id and subject line Bug#1009607: fixed in node-readable-stream 3.6.0+~cs3.0.0-2 has caused the Debian Bug report #1009607, regarding node-readable-stream: FTBFS: ERROR: Coverage for statements (94.31%) does not meet global threshold

Bug#1009607: marked as pending in node-readable-stream

2022-04-15 Thread Yadd
Control: tag -1 pending Hello, Bug #1009607 in node-readable-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009607 marked as pending in node-readable-stream

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009607 [src:node-readable-stream] node-readable-stream: FTBFS: ERROR: Coverage for statements (94.31%) does not meet global threshold (100%) Ignoring request to alter tags of bug #1009607 to the same tags previously set -- 1009607:

Bug#1009607: marked as pending in node-readable-stream

2022-04-15 Thread Yadd
Control: tag -1 pending Hello, Bug #1009607 in node-readable-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009607 marked as pending in node-readable-stream

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009607 [src:node-readable-stream] node-readable-stream: FTBFS: ERROR: Coverage for statements (94.31%) does not meet global threshold (100%) Added tag(s) pending. -- 1009607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009607 Debian

Bug#1009506: marked as done (node-require-inject: FTBFS: ERROR: Coverage for statements (96.15%) does not meet global threshold (100%))

2022-04-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Apr 2022 06:48:54 + with message-id and subject line Bug#1009506: fixed in node-require-inject 1.4.4-3 has caused the Debian Bug report #1009506, regarding node-require-inject: FTBFS: ERROR: Coverage for statements (96.15%) does not meet global threshold (100%) to

Bug#1009506: marked as pending in node-require-inject

2022-04-15 Thread Yadd
Control: tag -1 pending Hello, Bug #1009506 in node-require-inject 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#1009506 marked as pending in node-require-inject

2022-04-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009506 [src:node-require-inject] node-require-inject: FTBFS: ERROR: Coverage for statements (96.15%) does not meet global threshold (100%) Added tag(s) pending. -- 1009506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009506 Debian Bug