Bug#1005686: marked as done (lexicon: FTBFS: tests failed)

Your message dated Thu, 31 Mar 2022 06:18:51 + with message-id and subject line Bug#1005686: fixed in lexicon 3.9.4-1 has caused the Debian Bug report #1005686, regarding lexicon: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#996068: gnome-shell-extension-panel-osd: does not declare compatibility with GNOME Shell 41

Source: gnome-shell-extension-panel-osd Version: 1.0.50.gc032923-1 Followup-For: Bug #996068 Possibly a patch: https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/-/merge_requests/32 (At least some commenter says it works with 41. Did not test myself.) -- tobi

Bug#990428: Info received (Add fixed package to upcoming 11.3?)

Debian 11.3 was released over the weekend, and the ifenslave fix in this bug report is still not included.

Bug#1006999: marked as done (python-plac: Non-determinstically FTBFS on amd64/unstable due to timing in tests)

Your message dated Thu, 31 Mar 2022 03:04:03 + with message-id and subject line Bug#1006999: fixed in python-plac 1.3.5-1 has caused the Debian Bug report #1006999, regarding python-plac: Non-determinstically FTBFS on amd64/unstable due to timing in tests to be marked as done. This means tha

Processed: gnome-icon-theme-yasis: diff for NMU version 0.4.2-1.2

Processing control commands: > tags 965560 + patch Bug #965560 [src:gnome-icon-theme-yasis] gnome-icon-theme-yasis: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965560 + pending Bug #965560 [src:gnome-icon-theme-yasis] gnome-icon-theme-yasis: Removal of obs

Bug#965560: gnome-icon-theme-yasis: diff for NMU version 0.4.2-1.2

Control: tags 965560 + patch Control: tags 965560 + pending Dear maintainer, I've prepared an NMU for gnome-icon-theme-yasis (versioned as 0.4.2-1.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -u gnome-icon-theme-yasis-0.4.2/debian/chang

Bug#1008670: marked as done (librust-structopt+lints-dev uninstallable due to change in clap 2.34)

Your message dated Wed, 30 Mar 2022 23:20:01 + with message-id and subject line Bug#1008670: fixed in rust-structopt 0.3.26-2 has caused the Debian Bug report #1008670, regarding librust-structopt+lints-dev uninstallable due to change in clap 2.34 to be marked as done. This means that you cla

Bug#1008669: marked as done (libsbml FTBFS with Python 3.10)

Your message dated Wed, 30 Mar 2022 22:50:47 + with message-id and subject line Bug#1008669: fixed in libsbml 5.19.0+dfsg-2 has caused the Debian Bug report #1008669, regarding libsbml FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1008700: [Pkg-electronics-devel] Bug#1008700: Should geda-gaf be removed?

Moritz Muehlenhoff writes: > Source: geda-gaf > Version: 1:1.8.2-11 > Severity: serious > > Your package came up as a candidate for removal from Debian: For the record, I've previously indicated that I consider lepton-eda a complete replacement for geda-gaf in Debian. It was forked some years a

Processed: tagging 1008708

Processing commands for cont...@bugs.debian.org: > tags 1008708 + sid bookworm Bug #1008708 [pysolfc] pysolfc: After installing python3.10, pysolfc cannot start Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008708: https://bugs.d

Bug#1008708: pysolfc: After installing python3.10, pysolfc cannot start

Package: pysolfc Version: 2.6.4-3 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, 1. Attempted to start pysolfc through the menus; it failed to start. 2. Attempted to start from the command line; it failed to start with the following messaging: $ pysolf

Processed: Bug#1008669 marked as pending in libsbml

Processing control commands: > tag -1 pending Bug #1008669 [src:libsbml] libsbml FTBFS with Python 3.10 Added tag(s) pending. -- 1008669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008639: marked as done (libsigrokdecode: FTBFS: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert')

Your message dated Wed, 30 Mar 2022 21:23:56 + with message-id and subject line Bug#1008639: fixed in libsigrokdecode 0.5.3-3 has caused the Debian Bug report #1008639, regarding libsigrokdecode: FTBFS: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert' to be marked as done.

Bug#1008669: marked as pending in libsbml

Control: tag -1 pending Hello, Bug #1008669 in libsbml 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/med-team/libsbml/-/commit/4651e5beb95a3cb6ad64199f6d3907f

Bug#1008611: marked as done (bambam autopkgtest failure with pygame 2.1)

Your message dated Wed, 30 Mar 2022 21:18:58 + with message-id and subject line Bug#1008611: fixed in bambam 1.1.2+dfsg-2 has caused the Debian Bug report #1008611, regarding bambam autopkgtest failure with pygame 2.1 to be marked as done. This means that you claim that the problem has been d

Bug#1008704: Sould astk be removed?

Source: astk Version: 1.13.1-2.1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Last maintainer upload in 2014 If you disagree and want to continue to maintain this package, please just close t

Bug#1008703: Should sortsmill-tools be removed?

Source: sortsmill-tools Version: 0.4-2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python and thus removed from testing since 2019 - Last upload in 2013 If you disagree and want to continue to maintain this package, please just close this bug

Bug#1008702: Should ketchup be removed?

Source: ketchup Version: 1.0.1+git20111228+e1c62066-2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Last upload in 2017 - Seems dead upstream (last commit from eight years ago) - Per #946203 do

Bug#1008701: Should broctl be removed?

Source: broctl Version: 1.4-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still uses Python 2.7 and thus removed from testing since 2019 - Last upload in 2015 If you disagree and want to continue to maintain this package, please just close this bug (and fix t

Bug#1008700: Should geda-gaf be removed?

Source: geda-gaf Version: 1:1.8.2-11 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Also uses outdated Guile - Last upload in 2018 If you disagree and want to continue to maintain this package,

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

JFTR: On Wed, Mar 30, 2022 at 10:00:26PM +0200, Florian Ernst wrote: > libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev > anymore, and as such this package here is now uninstallable due to a > Depends on it. [...] Some more background can be found in

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

Control: severity -1 important On 30/03/2022 21.55, Salvatore Bonaccorso wrote: Ha, nice race :) (#1008695 and 1008696). ;-) I'll take your choice of severity. Andreas

Processed: Re: Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

Processing control commands: > severity -1 important Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821 Bug #1008696 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE‑2022‑21821 Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' -- 1008

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 965511 0.3-4 Bug #965511 {Done: Guilherme Xavier } [src:etherpuppet] etherpuppet: Removal of obsolete debhelper compat 5 and 6 in bookworm Marked as fixed in versions etherpuppet/0.3-4. > End of message, stopping processing here. Please c

Processed: reassign 1008695 to src:nvidia-cuda-toolkit, tagging 1008695, forcibly merging 1008695 1008696 ...

Processing commands for cont...@bugs.debian.org: > reassign 1008695 src:nvidia-cuda-toolkit 4.0.13-1 Bug #1008695 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821 Bug reassigned from package 'nvidia-cuda-toolkit' to 'src:nvidia-cuda-toolkit'. No longer marked as found in versions nvidia-c

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

Package: libprelude-dev Version: 5.2.0-5+b2 Severity: grave Justification: renders package unusable Hello there, libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev anymore, and as such this package here is now uninstallable due to a Depends on it. For reference, libtool migr

Processed (with 1 error): forcibly merging 1008695 1008696

Processing commands for cont...@bugs.debian.org: > forcemerge 1008695 1008696 Bug #1008695 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821 Unable to merge bugs because: package of #1008696 is 'src:nvidia-cuda-toolkit' not 'nvidia-cuda-toolkit' Failed to forcibly merge 1008695: Did not al

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

Hi, On Wed, Mar 30, 2022 at 09:35:16PM +0200, Andreas Beckmann wrote: > Package: nvidia-cuda-toolkit > Version: 4.0.13-1 > Severity: serious > Tags: security > > https://nvidia.custhelp.com/app/answers/detail/a_id/5334 > > CVE-2022-21821NVIDIA CUDA Toolkit SDK contains an integer overflo

Processed: found 1008170 in 2.0.10+~2.0.2-3

Processing commands for cont...@bugs.debian.org: > found 1008170 2.0.10+~2.0.2-3 Bug #1008170 [node-openid] FTBFS: randomly test failures Marked as found in versions node-openid/2.0.10+~2.0.2-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008170: https://bugs

Processed: tagging 1008688

Processing commands for cont...@bugs.debian.org: > tags 1008688 + sid bookworm Bug #1008688 [src:cwiid] cwiid: FTBFS with Python 3.10 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008688: https://bugs.debian.org/cgi-bin/bugreport.

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

Your message dated Wed, 30 Mar 2022 16:42:18 -0300 with message-id and subject line Re: etherpuppet: Removal of obsolete debhelper compat 5 and 6 in bookworm has caused the Debian Bug report #965511, regarding etherpuppet: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as

Processed: reassign 1008650 to src:unbound, forcibly merging 1008641 1008650

Processing commands for cont...@bugs.debian.org: > # … now with the correct package name > reassign 1008650 src:unbound 1.13.1-1 Bug #1008650 [src:unbund] python3-unbound: Cannot install because of Python dependencies Warning: Unknown package 'src:unbund' Bug reassigned from package 'src:unbund'

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

Package: nvidia-cuda-toolkit Version: 4.0.13-1 Severity: serious Tags: security https://nvidia.custhelp.com/app/answers/detail/a_id/5334 CVE-2022-21821 NVIDIA CUDA Toolkit SDK contains an integer overflow vulnerability in cuobjdump.To exploit this vulnerability, a remote attacker would require a

Processed (with 1 error): Re: Bug#1008650: python3-unbound: Cannot install because of Python dependencies

Processing control commands: > reassign -1 src:unbund 1.13.1-1 Bug #1008650 [python3-unbound] python3-unbound: Cannot install because of Python dependencies Bug reassigned from package 'python3-unbound' to 'src:unbund'. Warning: Unknown package 'src:unbund' Warning: Unknown package 'src:unbund' N

Bug#1008650: python3-unbound: Cannot install because of Python dependencies

Control: reassign -1 src:unbund 1.13.1-1 Control: severity -1 serious Control: forcemerge 1008641 -1 On 2022-03-30 06:55:21 +, Stephane Bortzmeyer wrote: > Package: python3-unbound > Version: 1.13.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > % sudo

Bug#1008694: kdevelop-python: Build-Depends: python3.9-dev

Source: kdevelop-python Version: 5.6.2-2 Severity: serious Tags: ftbfs Forwarded: https://bugs.kde.org/show_bug.cgi?id=438206 User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer kdevelop-python has a hardcoded build-dependency on python3.9-dev. Changing this to the generic py

Bug#1008691: mkdocs-material: Depends: python3-pymdownx but it is not installable

Package: mkdocs-material Version: 8.2.5-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org mkdocs-material cannot be installed in unsable: $ apt install mkdocs-material Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be

Bug#1008690: cadabra2: FTBFS with Python 3.10

Source: cadabra2 Version: 2.3.6.8-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org cadabra2 FTBFS: [ 2%] Building CXX object core/CMakeFiles/cadabra2-cli.dir/cadabra2-cli.cc.o cd /<>/obj

Bug#1008688: cwiid: FTBFS with Python 3.10

Source: cwiid Version: 0.6.91-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org cwiid FTBFS: gcc -o wmgui main.o interface.o support.o -Wl,-z,relro -L../libcwiid -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocai

Bug#1008689: getfem++: FTBFS with Python 3.10

Source: getfem++ Version: 5.3+dfsg1-4 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org getfem++ FTBFS: checking for the distutils Python package... no configure: error: cannot import Python module "distutils". Please check your Python inst

Processed: biabam: diff for NMU version 0.9.7-7.3

Processing control commands: > tags 965435 + patch Bug #965435 [src:biabam] biabam: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965435 + pending Bug #965435 [src:biabam] biabam: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending.

Bug#965435: biabam: diff for NMU version 0.9.7-7.3

Control: tags 965435 + patch Control: tags 965435 + pending Dear maintainer, I've prepared an NMU for biabam (versioned as 0.9.7-7.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru biabam-0.9.7/debian/changelog biabam-0.9.7/debian/chang

Bug#1008433: marked as done (golang-honnef-go-tools: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 honnef.co/go/tools/analysis/code honnef.co/go/tools/analysis/edit honnef.co/go/to

Your message dated Wed, 30 Mar 2022 18:04:20 + with message-id and subject line Bug#1008433: fixed in golang-honnef-go-tools 2022.1-1 has caused the Debian Bug report #1008433, regarding golang-honnef-go-tools: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 honnef.co/go/too

Bug#1008686: Puddletag: name 'operatorPrecedence' is not defined

Package:puddletag Version:2.0.1-3 Severity: critical Hello, Running Debian sid, it is not possible to launch puddletag Debian Forums has a possible fix: https://forums.debian.net/viewtopic.php?f=6&t=151493 sudo sed -i 's/operatorPrecedence/infixNotation/g' /usr/lib/python3/dist-packages/puddlest

Processed: tagging 953530

Processing commands for cont...@bugs.debian.org: > tags 953530 + pending Bug #953530 [samba-common-bin] samba-common-bin: post-install fails with "lock directory /run/samba does not exist" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 9535

Processed: Re: ruby2.7: ftbfs with autoconf 2.70

Processing control commands: > tags -1 moreinfo Bug #978900 [src:ruby2.7] ruby2.7: ftbfs with autoconf 2.70 Added tag(s) moreinfo. > severity -1 normal Bug #978900 [src:ruby2.7] ruby2.7: ftbfs with autoconf 2.70 Severity set to 'normal' from 'serious' -- 978900: https://bugs.debian.org/cgi-bin/b

Bug#978900: ruby2.7: ftbfs with autoconf 2.70

Control: tags -1 moreinfo Control: severity -1 normal On Thu, 31 Dec 2020 14:28:58 + Matthias Klose wrote: ./configure: line 3496: syntax error near unexpected token `fi' ./configure: line 3496: `fi ;; #(' make[1]: *** [debian/rules:75: override_dh_auto_configure] Error 2 make[1]: Leaving d

Processed: fixed 995115 in 2.7.4-1+b1

Processing commands for cont...@bugs.debian.org: > fixed 995115 2.7.4-1+b1 Bug #995115 [libruby2.7] /usr/bin/ruby: symbol lookup error: /lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash Marked as fixed in versions ruby2.7/2.7.4-1. > thanks Stopping processing here. Please

Bug#1008680: scipy: FTBFS with Python 3.10 as default

Source: scipy Version: 1.7.3-2 Severity: serious Tags: ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer As can be seen on reproducible builds [1], scipy FTBFS with Python 3.10 as the default version. I've copied what I hope is the relevant part of the log below

Bug#1008665: marked as done (node-react-popper: Package unusable due to missing build)

Your message dated Wed, 30 Mar 2022 14:56:10 + with message-id and subject line Bug#1008665: fixed in node-react-popper 2.2.5-5 has caused the Debian Bug report #1008665, regarding node-react-popper: Package unusable due to missing build to be marked as done. This means that you claim that th

Bug#1008666: marked as done (node-popper2: Package unusable due to missing build)

Your message dated Wed, 30 Mar 2022 13:53:51 + with message-id and subject line Bug#1008666: fixed in node-popper2 2.11.2-2 has caused the Debian Bug report #1008666, regarding node-popper2: Package unusable due to missing build to be marked as done. This means that you claim that the problem

Bug#1008666: marked as pending in node-popper2

Control: tag -1 pending Hello, Bug #1008666 in node-popper2 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-popper2/-/commit/130262715d243845edec75

Processed: Bug#1008666 marked as pending in node-popper2

Processing control commands: > tag -1 pending Bug #1008666 [node-popper2] node-popper2: Package unusable due to missing build Added tag(s) pending. -- 1008666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008670: [Pkg-rust-maintainers] Bug#1008670: librust-structopt+lints-dev uninstallable due to change in clap 2.34

Le 30/03/2022 à 13:04, peter green a écrit : Package: librust-structopt+lints-dev Version: 0.3.26-1 Severity: serious clap 2.34 dropped the "lints" feature, this has left librust-structopt+lints-dev uninstallable in unstable and is blocking the migration to testing of the new versions of clap an

Bug#1008380: marked as done (macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared)

Your message dated Wed, 30 Mar 2022 12:03:57 + with message-id and subject line Bug#1008380: fixed in macromoleculebuilder 3.5+dfsg-5 has caused the Debian Bug report #1008380, regarding macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared to be

Processed: Bug#1008400 marked as pending in golang-github-prometheus-common

Processing control commands: > tag -1 pending Bug #1008400 [src:golang-github-prometheus-common] golang-github-prometheus-common: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/prometheus/common/config github.com/prometheus/common/expfmt github.com/p

Bug#1008400: marked as pending in golang-github-prometheus-common

Control: tag -1 pending Hello, Bug #1008400 in golang-github-prometheus-common 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/go-team/packages/golang-github-p

Processed: affects 1008666

Processing commands for cont...@bugs.debian.org: > affects 1008666 node-react-popper Bug #1008666 [node-popper2] node-popper2: Package unusable due to missing build Added indication that 1008666 affects node-react-popper > thanks Stopping processing here. Please contact me if you need assistance.

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

Your message dated Wed, 30 Mar 2022 11:38:31 + with message-id and subject line Bug#999125: fixed in yale 5.0.95-3 has caused the Debian Bug report #999125, regarding yale: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim tha

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

Your message dated Wed, 30 Mar 2022 11:34:13 + with message-id and subject line Bug#999146: fixed in gliese 3.0.95-3 has caused the Debian Bug report #999146, regarding gliese: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

Your message dated Wed, 30 Mar 2022 11:37:51 + with message-id and subject line Bug#1002884: fixed in titantools 4.0.11+notdfsg1-7 has caused the Debian Bug report #1002884, regarding titantools: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that yo

Bug#1008550: marked as done (gnome-shell-extension-hide-activities: does not declare compatibility with GNOME Shell 42)

Your message dated Wed, 30 Mar 2022 11:19:19 + with message-id and subject line Bug#1008550: fixed in gnome-shell-extension-hide-activities 42-1 has caused the Debian Bug report #1008550, regarding gnome-shell-extension-hide-activities: does not declare compatibility with GNOME Shell 42 to b

Bug#1008357: marked as done (squeekboard: FTBFS: ninja: build stopped: subcommand failed.)

Your message dated Wed, 30 Mar 2022 11:07:21 + with message-id and subject line Bug#1008357: fixed in squeekboard 1.17.0-2 has caused the Debian Bug report #1008357, regarding squeekboard: FTBFS: ninja: build stopped: subcommand failed. to be marked as done. This means that you claim that the

Bug#1008554: marked as done (gnome-shell-extension-pixelsaver: does not declare compatibility with GNOME Shell 42)

Your message dated Wed, 30 Mar 2022 11:04:10 + with message-id and subject line Bug#1008554: fixed in gnome-shell-extension-pixelsaver 1.28-2 has caused the Debian Bug report #1008554, regarding gnome-shell-extension-pixelsaver: does not declare compatibility with GNOME Shell 42 to be marked

Bug#1008670: librust-structopt+lints-dev uninstallable due to change in clap 2.34

Package: librust-structopt+lints-dev Version: 0.3.26-1 Severity: serious clap 2.34 dropped the "lints" feature, this has left librust-structopt+lints-dev uninstallable in unstable and is blocking the migration to testing of the new versions of clap and textwrap. Since rust-structopt+lints-dev ha

Bug#1008669: libsbml FTBFS with Python 3.10

Source: libsbml Version: 5.19.0+dfsg-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=libsbml ... [ 99%] Swig Python source Traceback (most recent call last): File "/<>/src/bindings/python/doc-converter/rewrite_pydoc.py", line 121, in from format

Bug#1008665: marked as pending in node-react-popper

Control: tag -1 pending Hello, Bug #1008665 in node-react-popper 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-react-popper/-/commit/acfcc683f390

Processed: Bug#1008665 marked as pending in node-react-popper

Processing control commands: > tag -1 pending Bug #1008665 [node-react-popper] node-react-popper: Package unusable due to missing build Added tag(s) pending. -- 1008665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008665 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1008666: node-popper2: Package unusable due to missing build

Package: node-popper2 Version: 2.11.2-1 Severity: grave Justification: renders package unusable Another package pushed without building needed files... $ dpkg -L node-popper2 /. /usr /usr/share /usr/share/doc /usr/share/doc/node-popper2 /usr/share/doc/node-popper2/README.md.gz /usr/share/doc/node

Bug#1008357: marked as pending in squeekboard

Control: tag -1 pending Hello, Bug #1008357 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/d9e012264761

Processed: Bug#1008357 marked as pending in squeekboard

Processing control commands: > tag -1 pending Bug #1008357 [src:squeekboard] squeekboard: FTBFS: ninja: build stopped: subcommand failed. Added tag(s) pending. -- 1008357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008357 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 1007234 test suite fails on all but amd64 arches Bug #1007234 [src:netpbm-free] netpbm-free: FTBFS almost everywhere Changed Bug title to 'test suite fails on all but amd64 arches' from 'netpbm-free: FTBFS almost everywhere'. > severity 1

Bug#1008665: node-react-popper: Package unusable due to missing build

Package: node-react-popper Severity: grave Justification: renders package unusable This package was pushed without any care. Needed files aren't build which render package unusable (as reported by autopkgtest!)

Bug#1008536: marked as done (gnome-shell-extension-arc-menu: does not declare compatibility with GNOME Shell 42)

Your message dated Wed, 30 Mar 2022 10:19:37 + with message-id and subject line Bug#1008536: fixed in gnome-shell-extension-arc-menu 49+forkv29-1 has caused the Debian Bug report #1008536, regarding gnome-shell-extension-arc-menu: does not declare compatibility with GNOME Shell 42 to be mark

Bug#965434: barada-pam: diff for NMU version 0.5-3.2

Control: tags 965434 + patch Control: tags 965434 + pending Dear maintainer, I've prepared an NMU for barada-pam (versioned as 0.5-3.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru barada-pam-0.5/debian/changelog barada-pam-0.5/debian

Processed: barada-pam: diff for NMU version 0.5-3.2

Processing control commands: > tags 965434 + patch Bug #965434 [src:barada-pam] barada-pam: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965434 + pending Bug #965434 [src:barada-pam] barada-pam: Removal of obsolete debhelper compat 5 and 6 in bookworm Added

Bug#1008654: nvidia-modprobe version in bullseye-backports behind the stable update version

Package: nvidia-modprobe Version: 470.94-1~bpo11+1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Using bullyeye-backports - the version of the package 470.94-1~bpo11+1 is behind the version of the table update reposi

Bug#1005636: marked as done (python-tooz: FTBFS: TypeError: retry..() got an unexpected keyword argument 'retry_state')

Your message dated Wed, 30 Mar 2022 09:13:34 +0200 with message-id <001f6af1-779b-6918-bab9-c5cca7bfd...@debian.org> and subject line This is fixed has caused the Debian Bug report #1005636, regarding python-tooz: FTBFS: TypeError: retry..() got an unexpected keyword argument 'retry_state' to be m

Processed: severity of 1008497 is important

Processing commands for cont...@bugs.debian.org: > severity 1008497 important Bug #1008497 [src:linux] linux-image-5.10.0-13-arm64: 5.10.0-13-arm64 gets stuck after loading ramdisk on VMWareFusion under M1. 5.10.0-12-arm64 works. Severity set to 'important' from 'critical' > thanks Stopping proce

Processed: fixed 1005636 2.10.1-1

Processing commands for cont...@bugs.debian.org: > fixed 1005636 2.10.1-1 Bug #1005636 [src:python-tooz] python-tooz: FTBFS: TypeError: retry..() got an unexpected keyword argument 'retry_state' Marked as fixed in versions python-tooz/2.10.1-1. > End of message, stopping processing here. Please

Bug#1008650: python3-unbound: Cannot install because of Python dependencies

Package: python3-unbound Version: 1.13.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, % sudo apt install python3-unbound Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may me