Bug#1017623: nautilus-filename-repairer: Fails to build with Nautilus 43

I reviewed the code for a while but it needs a significant change to migrate. Adopting new APIs was relatively easy, but this repairer extension works by launching several modal synchronous dialogs, which are obsolete in GTK4, in sequence. This impacts the whole flow of this program in GTK4 migrat

Processed: tagging 1019594, bug 1019594 is forwarded to https://dev.deluge-torrent.org/ticket/3459 ...

Processing commands for cont...@bugs.debian.org: > tags 1019594 + upstream Bug #1019594 [src:deluge] deluge: CVE-2021-3427 Added tag(s) upstream. > forwarded 1019594 https://dev.deluge-torrent.org/ticket/3459 Bug #1019594 [src:deluge] deluge: CVE-2021-3427 Set Bug forwarded-to-address to 'https://

Bug#1019623: ruby-fog-core: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-fog-core Version: 2.1.0-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-fog-core with ruby3.1 enabled, the build failed.

Bug#1019620: ruby-enumerize: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-enumerize Version: 2.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-enumerize with ruby3.1 enabled, the build failed.

Bug#1019619: ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-did-you-mean Version: 1.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-did-you-mean with ruby3.1 enabled, the build f

Bug#1019622: ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "undefined method 'static_attributes_are_gone' in 'broken' factory\nDid you mean? 's

Source: ruby-factory-bot Version: 6.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-factory-bot with ruby3.1 enabled, the build fai

Bug#1019621: ruby-excon: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-excon Version: 0.88.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-excon with ruby3.1 enabled, the build failed. Relev

Bug#1019616: ruby-dalli: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory

Source: ruby-dalli Version: 3.0.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-dalli with ruby3.1 enabled, the build failed. Releva

Bug#1019618: ruby-delayed-job: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-delayed-job Version: 4.1.9-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-delayed-job with ruby3.1 enabled, the build fai

Bug#1019617: ruby-delayed-job-active-record: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-delayed-job-active-record Version: 4.1.6-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-delayed-job-active-record with ru

Bug#1019615: ruby-crack: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-crack Version: 0.4.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-crack with ruby3.1 enabled, the build failed. Releva

Bug#1019613: ruby-capybara: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: raise LoadError, 'Capybara is unable to load `puma` for its server, please add `puma` to your project or sp

Source: ruby-capybara Version: 3.36.0+ds-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-capybara with ruby3.1 enabled, the build faile

Bug#1019614: ruby-celluloid: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected Timeout::Error, got #

Source: ruby-celluloid Version: 0.17.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-celluloid with ruby3.1 enabled, the build failed

Bug#1019611: ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}

Source: ruby-asset-sync Version: 2.11.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-asset-sync with ruby3.1 enabled, the build fail

Processed: severity of 1016541 is serious

Processing commands for cont...@bugs.debian.org: > severity 1016541 serious Bug #1016541 [src:ruby-aruba] ruby-aruba: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assist

Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

Source: ruby-ahoy-email Version: 1.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-ahoy-email with ruby3.1 enabled, the build faile

Bug#1019609: ruby-activerecord-import: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-activerecord-import Version: 1.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-activerecord-import with ruby3.1 enable

Bug#1019607: redmine: FTBFS with ruby3.1: Could not find gem 'rails (~> 6.1.4.6)' in cached gems or installed locally.

Source: redmine Version: 5.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild redmine with ruby3.1 enabled, the build failed. Relevant par

Bug#1019608: rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq('')

Source: rubocop Version: 0.89.1+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild rubocop with ruby3.1 enabled, the build failed. Releva

Bug#1019606: roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: YAML.load_file config_file

Source: roodi Version: 5.0.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild roodi with ruby3.1 enabled, the build failed. Relevant part of

Bug#1019605: feed2imap: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: feed2imap Version: 1.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild feed2imap with ruby3.1 enabled, the build failed. Relevant

Bug#1019604: bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: bsfilter Version: 1:1.0.19-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild bsfilter with ruby3.1 enabled, the build failed. Relevan

Bug#1019603: asciidoctor: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: asciidoctor Version: 2.0.16-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild asciidoctor with ruby3.1 enabled, the build failed. Rel

Bug#1004782: marked as done (pytorch: FTBFS with ffmpeg 5.0)

Your message dated Mon, 12 Sep 2022 21:44:26 + with message-id and subject line Bug#1004782: fixed in pytorch 1.12.0-1 has caused the Debian Bug report #1004782, regarding pytorch: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1009200: marked as done (pytorch: (autopkgtest) needs update for python3.10: 'float' object cannot be interpreted as an integer)

Your message dated Mon, 12 Sep 2022 21:44:26 + with message-id and subject line Bug#1009200: fixed in pytorch 1.12.0-1 has caused the Debian Bug report #1009200, regarding pytorch: (autopkgtest) needs update for python3.10: 'float' object cannot be interpreted as an integer to be marked as do

Processed: loggerhead: autopkgtest regression: No module named 'loggerhead.tests'

Processing commands for cont...@bugs.debian.org: > reopen 1016452 Bug #1016452 {Done: Jelmer Vernooij } [src:loggerhead] loggerhead: autopkgtest regression: No module named 'loggerhead.tests' 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleare

Bug#1017210: marked as done (python-pyfakefs: FTBFS: AssertionError: FileNotFoundError not raised)

Your message dated Mon, 12 Sep 2022 20:41:10 + with message-id and subject line Bug#1017210: fixed in python-pyfakefs 4.6.3-1 has caused the Debian Bug report #1017210, regarding python-pyfakefs: FTBFS: AssertionError: FileNotFoundError not raised to be marked as done. This means that you cla

Bug#1019600: swfmill: CVE-2022-36139 CVE-2022-36144

Source: swfmill X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for swfmill. CVE-2022-36139[0]: | SWFMill commit 53d7690 was discovered to contain a heap-buffer | overflow via SWF::Writer::writeByte(unsigned char). https://g

Bug#997462: marked as done (dogecoin: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 12 Sep 2022 19:04:16 + with message-id and subject line Bug#997462: fixed in dogecoin 1.14.6-1 has caused the Debian Bug report #997462, regarding dogecoin: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below t

Processed: tagging 1019589, found 1019589 in 21.11-5, tagging 1019590, found 1019590 in 2:9.0.0242-1 ...

Processing commands for cont...@bugs.debian.org: > tags 1019589 + upstream Bug #1019589 [src:dpdk] dpdk: CVE-2022-28199 CVE-2022-2132 Ignoring request to alter tags of bug #1019589 to the same tags previously set > found 1019589 21.11-5 Bug #1019589 [src:dpdk] dpdk: CVE-2022-28199 CVE-2022-2132 Ig

Processed: tagging 1019589, found 1019589 in 21.11-5

Processing commands for cont...@bugs.debian.org: > tags 1019589 + upstream Bug #1019589 [src:dpdk] dpdk: CVE-2022-28199 CVE-2022-2132 Added tag(s) upstream. > found 1019589 21.11-5 Bug #1019589 [src:dpdk] dpdk: CVE-2022-28199 CVE-2022-2132 Marked as found in versions dpdk/21.11-5. > thanks Stoppin

Processed: Re: node-jquery breaks r-cran-pkgdown autopkgtest: replacement has 11 rows, data has 10

Processing control commands: > reassign -1 r-cran-jquerylib 0.1.4+dfsg-3 Bug #1019513 [src:node-jquery, src:r-cran-pkgdown] node-jquery breaks r-cran-pkgdown autopkgtest: replacement has 11 rows, data has 10 Bug reassigned from package 'src:node-jquery, src:r-cran-pkgdown' to 'r-cran-jquerylib'.

Bug#1019513: node-jquery breaks r-cran-pkgdown autopkgtest: replacement has 11 rows, data has 10

Control: reassign -1 r-cran-jquerylib 0.1.4+dfsg-3 Control: reassign 1019514 r-cran-jquerylib 0.1.4+dfsg-3 Control: close -1 Control: close 1019514 Both this and #1019514 are due to jquerylib build pointing to old symlinks of jquery. I have re-uploaded a new changelog revision with this updated an

Bug#1019589: dpdk: CVE-2022-28199 CVE-2022-2132

Source: dpdk X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities are fixed in DSA 5222, but filing a bug to track the fix in unstable: CVE-2022-28199[0]: | NVIDIA’s distribution of the Data Plane Development Kit | (MLNX_DPDK) contains a v

Processed: Starting ruby3.1 transition: important bugs now marked as serious

Processing commands for cont...@bugs.debian.org: > severity 1015305 serious Bug #1015305 [src:puma] puma: FTBFS: ERROR: Test "ruby3.1" failed. Severity set to 'serious' from 'important' > severity 1015309 serious Bug #1015309 [src:ruby-bson] ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure

Bug#1015327: Starting ruby3.1 transition: important bugs now marked as serious

severity 1015305 serious severity 1015309 serious severity 1015310 serious severity 1015322 serious severity 1015327 serious severity 1015328 serious severity 1015329 serious severity 1015334 serious thanks Hi, We are about to start the ruby3.1 transition. I will coordinate this with the release

Bug#1000927: fixed in unstable

On Thu, 8 Sep 2022 15:20:23 +0200 Matthias Klose wrote: > fixed in unstable, now built using LLVM 13. When this bug was closed, it was titled "creduce: Please upgrade to llvm-toolchain-14", so i don't believe this is fixed, which is suboptimal because creduce is the only blocker for me to be able

Processed: Re: Bug#1019586: gnome-shell-extension-weather: Extension not compatible with libsoup3

Processing commands for cont...@bugs.debian.org: > severity 1019586 serious Bug #1019586 [gnome-shell-extension-weather] gnome-shell-extension-weather: Extension not compatible with libsoup3 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me

Processed: Restoring patch tag

Processing commands for cont...@bugs.debian.org: > tags 1017944 patch Bug #1017944 [grub-xen-host] grub-xen-host: 2.06-3 crashes PV guests in early boot Ignoring request to alter tags of bug #1017944 to the same tags previously set > severity 1017944 grave Bug #1017944 [grub-xen-host] grub-xen-ho

Processed: [bts-link] source package src:frr

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:frr > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Bug#1019512: marked as done (r-cran-jquerylib: autopkgtest needs update for new version of node-jquery: Mismatch between compiled version 3.6.0 and current version 3.6.1)

Your message dated Mon, 12 Sep 2022 17:19:19 + with message-id and subject line Bug#1019512: fixed in r-cran-jquerylib 0.1.4+dfsg-4 has caused the Debian Bug report #1019512, regarding r-cran-jquerylib: autopkgtest needs update for new version of node-jquery: Mismatch between compiled version

Processed: Bug#1019512 marked as pending in r-cran-jquerylib

Processing control commands: > tag -1 pending Bug #1019512 [src:r-cran-jquerylib] r-cran-jquerylib: autopkgtest needs update for new version of node-jquery: Mismatch between compiled version 3.6.0 and current version 3.6.1 Added tag(s) pending. -- 1019512: https://bugs.debian.org/cgi-bin/bugre

Bug#1019512: marked as pending in r-cran-jquerylib

Control: tag -1 pending Hello, Bug #1019512 in r-cran-jquerylib 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/r-pkg-team/r-cran-jquerylib/-/commit/e54bad7631f

Bug#1019131: marked as done (r-bioc-dada2: autopkgtest regression in testing)

Your message dated Mon, 12 Sep 2022 22:28:15 +0530 with message-id <20220912165815.pzu5b2fxcnbbz...@nileshpatra.info> and subject line Re: r-bioc-dada2: autopkgtest regression in testing has caused the Debian Bug report #1019131, regarding r-bioc-dada2: autopkgtest regression in testing to be marke

Bug#1017391: kpmcore: FTBFS on armel

Hi Jonathan/Aurelien, Looks like armel needs some more symbols in symbols file for kpmcore. (I did not dig deep, but maybe this package should provide different symbol files per-architecture?) In any case, this RC bug is stalling migration of kpmcore and consequently calamares for over a month.

Bug#1019551: marked as done (node-jake: autopkgtest failure on armel: Timeout of 7000ms exceeded.)

Your message dated Mon, 12 Sep 2022 15:23:02 + with message-id and subject line Bug#1019551: fixed in node-jake 10.8.5+~1.0.4-2 has caused the Debian Bug report #1019551, regarding node-jake: autopkgtest failure on armel: Timeout of 7000ms exceeded. to be marked as done. This means that you c

Bug#1009112: marked as done (python-eventlet: (autopkgtest) needs update for python3.10: tests.patcher_test.test_patcher_existing_locks_locked)

Your message dated Mon, 12 Sep 2022 15:23:38 + with message-id and subject line Bug#1009112: fixed in python-eventlet 0.33.1-1 has caused the Debian Bug report #1009112, regarding python-eventlet: (autopkgtest) needs update for python3.10: tests.patcher_test.test_patcher_existing_locks_locked

Bug#1019579: raku-json-unmarshal: trying to overwrite '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package rak

Package: raku-json-unmarshal Version: 0.10-1 Severity: serious Tags: ftbfs Control: affects -1 raku-json-marshal src:raku-json-class https://buildd.debian.org/status/logs.php?pkg=raku-json-class&ver=0.0.18-1 ... Unpacking raku-json-unmarshal (0.10-1) ... dpkg: error processing archive /tmp/apt-d

Processed: raku-json-unmarshal: trying to overwrite '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-

Processing control commands: > affects -1 raku-json-marshal src:raku-json-class Bug #1019579 [raku-json-unmarshal] raku-json-unmarshal: trying to overwrite '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in packa

Bug#1019050: marked as done (postrm template: failed to remove)

Your message dated Mon, 12 Sep 2022 13:56:17 + with message-id and subject line Bug#1019050: fixed in dh-fortran-mod 0.27 has caused the Debian Bug report #1019050, regarding postrm template: failed to remove to be marked as done. This means that you claim that the problem has been dealt with

Bug#1009112: marked as pending in python-eventlet

Control: tag -1 pending Hello, Bug #1009112 in python-eventlet 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/python-eventlet/-/commit/495

Processed: Bug#1009112 marked as pending in python-eventlet

Processing control commands: > tag -1 pending Bug #1009112 [src:python-eventlet] python-eventlet: (autopkgtest) needs update for python3.10: tests.patcher_test.test_patcher_existing_locks_locked Added tag(s) pending. -- 1009112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009112 Debian B

Bug#1019222: marked as done (cdo: autopkgtest regression: cdo --help fails)

Your message dated Mon, 12 Sep 2022 13:18:54 + with message-id and subject line Bug#1019222: fixed in cdo 2.0.6-2 has caused the Debian Bug report #1019222, regarding cdo: autopkgtest regression: cdo --help fails to be marked as done. This means that you claim that the problem has been dealt

Bug#997178: Build tested and ready as PR

> Hello, just to make sure we are aligned on this bug resolution, thanks for > fixing! > > However, I would like to make sure that this isn't a "silly warning" and that Thanks for pushing it further, the file name is this way due to being auto-created from the upstream commit title.

Bug#997178: Build tested and ready as PR

On Thu, 25 Nov 2021 14:28:08 +0100 Christian Ehrhardt wrote: Hi, I have opened PR [1] which fixes this (without the full bump to the new ABI) [1]: https://salsa.debian.org/debian-gps-team/pkg-gpsd/-/merge_requests/11 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd Hello,

Bug#1017806: marked as done (python3-fluids FTBFS: all tests deselected)

Your message dated Mon, 12 Sep 2022 11:51:14 + with message-id and subject line Bug#1017806: fixed in python-fluids 1.0.22-1 has caused the Debian Bug report #1017806, regarding python3-fluids FTBFS: all tests deselected to be marked as done. This means that you claim that the problem has bee

Bug#1008451: marked as done (python-fluids: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils'))

Your message dated Mon, 12 Sep 2022 11:51:14 + with message-id and subject line Bug#1008451: fixed in python-fluids 1.0.22-1 has caused the Debian Bug report #1008451, regarding python-fluids: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils') to be mar

Bug#1004875: marked as done (python-fluids: autopkgtest regression on arm64, i386 and ppc64el:)

Your message dated Mon, 12 Sep 2022 11:51:14 + with message-id and subject line Bug#1004875: fixed in python-fluids 1.0.22-1 has caused the Debian Bug report #1004875, regarding python-fluids: autopkgtest regression on arm64, i386 and ppc64el: to be marked as done. This means that you claim t

Bug#1005719: mumble: diff for NMU version 1.3.4-1.1

Date: Mon, 12 Sep 2022 08:00:43 +0700 X-NMUDIFF-Version: 2.22.2 Control: tags 1005719 + pending Dear maintainer, I've prepared an NMU for mumble (versioned as 1.3.4-1.1) and it was uploaded to DELAYED/3. Please feel free to tell me if it should be delayed longer. Regards.diff -Nru mumble-1.3.4

Bug#1019556: marked as done (sse3-support: version 14 fails to install where version 13 installs fine due to different binary capitalization: test-sse3 vs test-SSE3)

Your message dated Mon, 12 Sep 2022 11:04:41 + with message-id and subject line Bug#1019556: fixed in isa-support 15 has caused the Debian Bug report #1019556, regarding sse3-support: version 14 fails to install where version 13 installs fine due to different binary capitalization: test-sse3

Bug#1019572: marked as done (FTBFS: node-nock requires network during tests)

Your message dated Mon, 12 Sep 2022 10:50:38 + with message-id and subject line Bug#1019572: fixed in node-nock 13.2.9-2 has caused the Debian Bug report #1019572, regarding FTBFS: node-nock requires network during tests to be marked as done. This means that you claim that the problem has bee

Processed: Bug#1019572 marked as pending in node-nock

Processing control commands: > tag -1 pending Bug #1019572 [node-nock] FTBFS: node-nock requires network during tests Added tag(s) pending. -- 1019572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1019572: marked as pending in node-nock

Control: tag -1 pending Hello, Bug #1019572 in node-nock 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-nock/-/commit/c5025fd1e8051ab7414ba149ac7e

Processed: set severity properly

Processing commands for cont...@bugs.debian.org: > severity 1019572 serious Bug #1019572 [node-nock] FTBFS: node-nock requires network during tests Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1019572: https://bugs.debian

Processed: severity of 1017944 is grave

Processing commands for cont...@bugs.debian.org: > severity 1017944 grave Bug #1017944 [grub-xen-host] grub-xen-host: 2.06-3 crashes PV guests in early boot Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017944: https://bu

Bug#1019571: paramcoq: autopkgtest failure

Source: paramcoq Version: 1.1.3+coq8.16-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/p/paramcoq/25968228/log.gz autopkgtest [22:17:33]: test upstreamtestsuite: [--- /tmp/autopkgtest-lxc.7qclpa4k/downtmp/build.ZbD/src/debian/tests/upstreamtestsuite:

Bug#1017944: grub-xen-host: 2.06-3 crashes PV guests in early boot

Control: seveerity -1 grave On Tue, Sep 06, 2022 at 03:55:39PM +0200, Valentin Kleibel wrote: >found 1017944 grub2/2.06-3~deb11u1 >severity 1017944 serious >tags 1017944 patch > >Dear Maintainers, > >We can confirm that this bug affects all pv and pvh domUs that use pvgrub. >The commit responsible

Bug#1017944: grub-xen-host: 2.06-3 crashes PV guests in early boot

On Tue, 6 Sep 2022 15:55:39 +0200 Valentin Kleibel wrote: found 1017944 grub2/2.06-3~deb11u1 severity 1017944 serious tags 1017944 patch Dear Maintainers, We can confirm that this bug affects all pv and pvh domUs that use pvgrub. The commit responsible is 20239c28 "Bump debhelper from old 10 t

Processed: fixed 1002341 in 2.4.2+ds-1, closing 1002341

Processing commands for cont...@bugs.debian.org: > fixed 1002341 2.4.2+ds-1 Bug #1002341 [src:cmd2] cmd2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" --system=custom "--test-args=PYTHONPATH={build_dir} {interpreter} -m pytest -k 'not test_vers

Bug#1017155: marked as done (fuzzylite: FTBFS: catch.hpp:6378:33: error: size of array ‘altStackMem’ is not an integral constant-expression)

Your message dated Mon, 12 Sep 2022 08:37:40 + with message-id and subject line Bug#1017155: fixed in fuzzylite 6.0+dfsg-5 has caused the Debian Bug report #1017155, regarding fuzzylite: FTBFS: catch.hpp:6378:33: error: size of array ‘altStackMem’ is not an integral constant-expression to be

Processed: forcibly merging 1017316 1017157

Processing commands for cont...@bugs.debian.org: > forcemerge 1017316 1017157 Bug #1017316 [src:gatling] gatling: FTBFS: cdefs.h:297:60: error: macro "__has_attribute" requires an identifier Bug #1017157 [src:gatling] gatling: FTBFS: cdefs.h:297:60: error: macro "__has_attribute" requires an ide

Bug#1019556:

Confirming same thing on an Intel Xeon running sid and the sse3-support:13 package. CPU info: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Xeon(R) CPU E3-1245 v6 @ 3.70GHz stepping: 9 microcode : 0x84 cpu MHz

Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

Control: severity -1 important On Sat, 23 Jul 2022 18:04:43 +0200 Jan Kiszka wrote: Upstream patch proposal sent: https://sourceforge.net/p/gnu-efi/mailman/message/37684742/ Thanks for that, Jan. Seems your patch was rejected unfortunately. I couldn't quite follow the reasoning of the rej

Processed: Re: Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

Processing control commands: > severity -1 important Bug #1013341 [gnu-efi] /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack Severity set to 'important' from 'serious' -- 1013341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101

Processed: forcibly merging 1017323 1017150

Processing commands for cont...@bugs.debian.org: > forcemerge 1017323 1017150 Bug #1017323 [src:adcli] adcli: FTBFS: ld: test_ldap-addisco.o: undefined reference to symbol 'ns_get32@@GLIBC_2.9' Bug #1017150 [src:adcli] adcli: FTBFS: ld: test_ldap-addisco.o: undefined reference to symbol 'ns_get3

Processed: notfixed 1017320 in gadap/2.0-15

Processing commands for cont...@bugs.debian.org: > notfixed 1017320 gadap/2.0-15 Bug #1017320 {Done: Alastair McKinstry } [src:grads] grads: FTBFS: (.text+0xc8): undefined reference to `libdap::DDS::var_begin()' No longer marked as fixed in versions gadap/2.0-15. > thanks Stopping processing here

Processed: forcibly merging 1017317 1017179

Processing commands for cont...@bugs.debian.org: > forcemerge 1017317 1017179 Bug #1017317 [src:webcamoid] webcamoid: FTBFS: abstractstream.h:60:21: error: ‘AVCodecContext’ does not name a type; did you mean ‘AVIODirContext’? Bug #1017179 [src:webcamoid] webcamoid: FTBFS: abstractstream.h:60:21:

Processed: 2.000beta3 builds

Processing commands for cont...@bugs.debian.org: > tags 1017282 fixed-upstream Bug #1017282 [src:fonts-elstob] fonts-elstob: FTBFS: fontmake: Error: In 'sources/Elstob.glyphs' -> 'master_ufo/Elstob.designspace' -> 'master_ufo/instance_ufo/Elstob-Regular.ufo': Compiling UFO failed: master_ufo/in

Processed: Move where it was fixed

Processing commands for cont...@bugs.debian.org: > reassign 1017264 libattean-perl 0.031-1 Bug #1017264 [src:libtest-fitesque-rdf-perl] libtest-fitesque-rdf-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Bug reassigned from package 'src:libtest-fitesque-rdf-pe

Bug#1001262: monado: diff for NMU version 21.0.0~dfsg1-2.1

Control: tags 1001262 + pending Dear maintainer, I've prepared an NMU for monado (versioned as 21.0.0~dfsg1-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru monado-21.0.0~dfsg1/debian/changelog monado-21.0.0~dfsg1/debian/changelog ---

Processed: monado: diff for NMU version 21.0.0~dfsg1-2.1

Processing control commands: > tags 1001262 + pending Bug #1001262 [src:monado] monado: FTBFS with glibc 2.34 Bug #1017251 [src:monado] monado: FTBFS: catch.hpp:10794:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’ Added tag(s) pending. Added tag(s) pending. -- 1001262: http

Bug#1017944: Included in Debian 11.5

Hello, This bug is included in the Debian 11.5 released and the faultly package is now use as an update on many systems that will be useless. I vote for critical too: > critical >makes unrelated software on the system (or the whole system) break, or >causes serious data loss, or introduc

Bug#1013064: marked as done (vmatch: ftbfs with GCC-12)

Your message dated Mon, 12 Sep 2022 12:43:29 +0530 with message-id <20220912071329.3omiccwul4xgd...@nileshpatra.info> and subject line Re: [Debian-med-packaging] Bug#1013064: vmatch: ftbfs with GCC-12 has caused the Debian Bug report #1013064, regarding vmatch: ftbfs with GCC-12 to be marked as do

Bug#1017944: Doesn't affect buster

Guess we're finding out where everyone's update windows are. Some though may report before resolving the issue or somewhat after. Or people may not have noticed yet if they haven't rebooted or attempted to start a new guest. It doesn't affect buster hosts. bullseye is impacted.