Bug#1058254: marked as pending in python-keystonemiddleware

Control: tag -1 pending Hello, Bug #1058254 in python-keystonemiddleware 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#1058254 marked as pending in python-keystonemiddleware

Processing control commands: > tag -1 pending Bug #1058254 [src:python-keystonemiddleware] python-keystonemiddleware: FTBFS: make[1]: pyversions: No such file or directory Added tag(s) pending. -- 1058254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058254 Debian Bug Tracking System

Bug#1058208: marked as done (pytorch-sparse: FTBFS: ImportError: Failed to load PyTorch C extensions:)

Your message dated Thu, 14 Dec 2023 07:35:10 + with message-id and subject line Bug#1058208: fixed in pytorch-sparse 0.6.18-2 has caused the Debian Bug report #1058208, regarding pytorch-sparse: FTBFS: ImportError: Failed to load PyTorch C extensions: to be marked as done. This means that

Processed (with 1 error): (No Subject)

Processing commands for cont...@bugs.debian.org: > tags 1056225 + fixed-upstream Bug #1056225 [src:aioquic] aioquic's autopkg tests fail with Python 3.12 Added tag(s) fixed-upstream. > merge 1056225 1058365 Bug #1056225 [src:aioquic] aioquic's autopkg tests fail with Python 3.12 Unable to merge

Bug#1058555: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)

Hi, Am 13.12.23 um 16:19 schrieb Andreas Tille: Control: tags -1 help Am Tue, Dec 12, 2023 at 09:52:48PM +0100 schrieb Lucas Nussbaum: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory This file is (re-)created via libreoffice --headless --convert-to pdf

Processed: (No Subject)

Processing commands for cont...@bugs.debian.org: > tags 1058365 + fixed-upstream Bug #1058365 [python-jedi] python-lsp-server: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) fixed-upstream. > thanks Stopping

Processed: Bug#1058536 marked as pending in ironic-inspector

Processing control commands: > tag -1 pending Bug #1058536 [src:ironic-inspector] ironic-inspector: FTBFS: AttributeError: 'called_once_with' is not a valid assertion. Use a spec for the mock if 'called_once_with' is meant to be an attribute.. Did you mean: 'assert_called_once_with'? Added

Bug#1058536: marked as pending in ironic-inspector

Control: tag -1 pending Hello, Bug #1058536 in ironic-inspector 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#1058657: python3-apt: undefined symbol: PyAptWarning

Package: python3-apt Version: 2.7.2 Severity: serious Dear Maintainer, This morning I see : , | dak@christian ~ % dak dominate | Traceback (most recent call last): | File "/usr/bin/dak", line 43, in | import daklib.utils | File "/usr/lib/python3/dist-packages/daklib/utils.py", line

Processed: Re: ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug"

Processing commands for cont...@bugs.debian.org: > severity 1054749 normal Bug #1054749 [src:ruby-android-key-attestation] ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug" Severity set to 'normal' from 'serious' > thanks Stopping processing

Bug#1054749: ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug"

severity 1054749 normal thanks I could reproduce this locally, I am lowering the severity of this bug to normal.

Bug#1036697: asterisk: CVE-2023-27585

Dear Jonas, On Mon, Aug 07, 2023 at 03:51:51PM +0300, Faidon Liambotis wrote: > Dear maintainer, security team, > > (See #1032092 for a similar bug with an almost equivalent response) I've seen that you've uploaded a couple new upstream releases of Asterisk in the time since my last response.

Bug#1058513: marked as done (node-signal-exit: FTBFS: SyntaxError: Cannot use import statement outside a module)

Your message dated Thu, 14 Dec 2023 09:42:55 +0400 with message-id <5e74ca61-1eb7-448d-aca5-3ca6f98eb...@debian.org> and subject line Fixed elsewhere has caused the Debian Bug report #1058513, regarding node-signal-exit: FTBFS: SyntaxError: Cannot use import statement outside a module to be

Bug#1058535: marked as done (libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25)

Your message dated Thu, 14 Dec 2023 05:35:04 + with message-id and subject line Bug#1058535: fixed in libhinawa 4.0.0-2 has caused the Debian Bug report #1058535, regarding libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25 to be marked as done. This means that you claim that the

Bug#1058273: marked as done (gpredict: FTBFS: dh_install: error: missing files, aborting)

Your message dated Thu, 14 Dec 2023 05:34:25 + with message-id and subject line Bug#1058273: fixed in gpredict 2.3-115-g0f3beb6-3 has caused the Debian Bug report #1058273, regarding gpredict: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim

Bug#1058540: marked as done (ditaa: FTBFS: xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory)

Your message dated Thu, 14 Dec 2023 06:12:50 +0100 with message-id and subject line FTBF has caused the Debian Bug report #1058540, regarding ditaa: FTBFS: xargs: /usr/lib/jvm/default-java/bin/javac: No such file or directory to be marked as done. This means that you claim that the problem has

Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting

On Tue, Dec 12, 2023 at 05:47:46PM -0700, Bdale Garbee wrote: > tony mancill writes: > > > So this is very possibly a bug in libreoffice-writer-nogui. > > Sure seems like it. My guess would be that what files go in what > libreoffice binary packages got refactored somehow? Not sure what the >

Bug#1058346: marked as done (libitext-java: FTBFS: [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88: error: cannot find symbol)

Your message dated Thu, 14 Dec 2023 03:49:45 + with message-id and subject line Bug#1057165: fixed in libitext-java 2.1.7-15 has caused the Debian Bug report #1057165, regarding libitext-java: FTBFS: [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88: error: cannot find symbol to be

Bug#1057165: marked as done (libitext-java: FTBFS with bouncycastle 1.77)

Your message dated Thu, 14 Dec 2023 03:49:45 + with message-id and subject line Bug#1057165: fixed in libitext-java 2.1.7-15 has caused the Debian Bug report #1057165, regarding libitext-java: FTBFS with bouncycastle 1.77 to be marked as done. This means that you claim that the problem has

Bug#1058237: python-boto: FTBFS: ModuleNotFoundError: No module named 'imp'

On Tue, Dec 12, 2023 at 08:14:41PM +0100, Andreas Tille wrote: > maybe we need to remove python-boto and fix all its rdepends. > > According to upstream[1]: > > This repo, boto was deprecated in 2020 and the last supported Python 3 > version was 3.4. It's unlikely this package will ever work

Bug#1056480: python-markdown2's autopkg tests fail with Python 3.12

The issue seems to have been fixed in upstream markdown2 v2.4.11 commit commit 0fde72b: Remove deprecated imp module Updating markdown2 to 2.4.11 may fix the issue.

Bug#1058171: marked as done (python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

Your message dated Wed, 13 Dec 2023 23:04:44 + with message-id and subject line Bug#1058171: fixed in python-logutils 0.3.5-3 has caused the Debian Bug report #1058171, regarding python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean:

Processed: Bug#1058171 marked as pending in python-logutils

Processing control commands: > tag -1 pending Bug #1058171 [src:python-logutils] python-logutils: FTBFS: AttributeError: 'ConfigDictTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? Added tag(s) pending. -- 1058171:

Bug#1058171: marked as pending in python-logutils

Control: tag -1 pending Hello, Bug #1058171 in python-logutils 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: reassign 1057926 to src:linux, reassign 1057694 to src:nodejs, tagging 1057850, tagging 1057356 ...

Processing commands for cont...@bugs.debian.org: > reassign 1057926 src:linux 6.1.64-1 Bug #1057926 {Done: Salvatore Bonaccorso } [linux-image-6.1.0-14-rt-amd64] 403 Access Denied on some packages on official Debian repo Warning: Unknown package 'linux-image-6.1.0-14-rt-amd64' Bug reassigned

Bug#1058348: marked as done (libapache-poi-java: FTBFS: [javac] /<>/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/facets/XAdESXLSignatureFacet.java:235: error: cannot find symbol)

Your message dated Wed, 13 Dec 2023 22:20:53 + with message-id and subject line Bug#1057167: fixed in libapache-poi-java 4.0.1-5 has caused the Debian Bug report #1057167, regarding libapache-poi-java: FTBFS: [javac]

Bug#1057167: marked as done (libapache-poi-java: FTBFS with bouncycastle 1.77)

Your message dated Wed, 13 Dec 2023 22:20:53 + with message-id and subject line Bug#1057167: fixed in libapache-poi-java 4.0.1-5 has caused the Debian Bug report #1057167, regarding libapache-poi-java: FTBFS with bouncycastle 1.77 to be marked as done. This means that you claim that the

Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

On Sun, Nov 26, 2023 at 09:01:12 +, Mate Kukri wrote: > The mechanism used to load the kernel has changed from GRUB 2.06 to > GRUB 2.12, it is possible that there are unfortunate bugs in either in > GRUB and/or your firmware that is stopping the new mechanism from > loading the kernel. Just

Bug#1058086: marked as done (python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd' object has no attribute 'assertRegexpMatches')

Your message dated Wed, 13 Dec 2023 22:07:05 + with message-id and subject line Bug#1058086: fixed in python-monasca-statsd 2.7.0-3 has caused the Debian Bug report #1058086, regarding python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd' object has no attribute

Processed: Bug#1058086 marked as pending in python-monasca-statsd

Processing control commands: > tag -1 pending Bug #1058086 [src:python-monasca-statsd] python-monasca-statsd: FTBFS: AttributeError: 'TestMonascaStatsd' object has no attribute 'assertRegexpMatches' Added tag(s) pending. -- 1058086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058086

Bug#1058086: marked as pending in python-monasca-statsd

Control: tag -1 pending Hello, Bug #1058086 in python-monasca-statsd 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 (with 1 error): merging 1057167 1057516

Processing commands for cont...@bugs.debian.org: > merge 1057167 1057516 Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac]

Processed: Re: aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Processing control commands: > tags -1 + fixed-upstream Bug #1058169 [src:aioquic] aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) fixed-upstream. -- 1058169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058169 Debian Bug Tracking System

Bug#1058169: aioquic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Control: tags -1 + fixed-upstream This has been fixed upstream in aioquic/0.9.22 - https://github.com/aiortc/aioquic/commit/b09747820e3539950123f85385c978d473ac5a61 Best regards, Dale Richards

Processed: Re: Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1

Processing control commands: > reassign -1 debputy Bug #1057934 [src:libjs-jquery-jstree] libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1 Bug reassigned from package 'src:libjs-jquery-jstree' to

Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1

Control: reassign -1 debputy Control: affects -1 src:libjs-jquery-jstree Hi Niels, I think this one is for you. Paul On 10-12-2023 20:18, Santiago Vila wrote: Package: src:libjs-jquery-jstree Version: 3.3.16+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all

Processed: Bug#1057167 marked as pending in libapache-poi-java

Processing control commands: > tag -1 pending Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac]

Bug#1057167: marked as pending in libapache-poi-java

Control: tag -1 pending Hello, Bug #1057167 in libapache-poi-java 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: (No Subject)

Processing commands for cont...@bugs.debian.org: > merge 1056224 1058209 Bug #1056224 [src:advocate] advocate's autopkg tests fail with Python 3.12 Bug #1056224 [src:advocate] advocate's autopkg tests fail with Python 3.12 Added tag(s) ftbfs. Bug #1058209 [src:advocate] advocate: FTBFS:

Bug#1058365: python-lsp-server: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

This is fixed upstream in jedi/0.19.1 - https://github.com/davidhalter/jedi/commit/c137eb69182f21771dbd1dce8ce9f6b3c4901777 Best regards, Dale Richards

Bug#1058640: src:lintian-brush: unsatisfied build dependency in testing: ognibuild (>= 0.0.18)

Source: lintian-brush Version: 0.152 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be

Bug#1051166: FTBFS with doxygen 1.9.8

This is discussed upstream here: https://github.com/breathe-doc/breathe/issues/935 It appears to be a regression in doxygen caused by: https://github.com/doxygen/doxygen/commit/a18e4c76ed6415893800c7d77a2f798614fb638b Best regards, Dale Richards

Processed: merging 1057167 1058348, owner 1057167

Processing commands for cont...@bugs.debian.org: > merge 1057167 1058348 Bug #1057167 [src:libapache-poi-java] libapache-poi-java: FTBFS with bouncycastle 1.77 Bug #1058348 [src:libapache-poi-java] libapache-poi-java: FTBFS: [javac]

Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake

Contol: tags -1 + fixed-upstream Control: found -1 6.1.66-1 Control: found -1 6.5.13-1 On Sun, Oct 29, 2023 at 02:16:57PM +0100, Aurelien Jarno wrote: > Source: linux > Version: 5.10.197-1 > Severity: grave > Tags: upstream patch > X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org > >

Processed: Re: Bug#1055021: linux: mips64el loongson3 kernel crashes when running cmake

Processing control commands: > found -1 6.1.66-1 Bug #1055021 [src:linux] linux: mips64el loongson3 kernel crashes when running cmake Marked as found in versions linux/6.1.66-1. > found -1 6.5.13-1 Bug #1055021 [src:linux] linux: mips64el loongson3 kernel crashes when running cmake Marked as

Processed: src:mes: fails to migrate to testing for too long: FTBFS on armhf

Processing control commands: > close -1 0.25-1 Bug #1058635 [src:mes] src:mes: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions mes/0.25-1. Bug #1058635 [src:mes] src:mes: fails to migrate to testing for too long: FTBFS on armhf Marked Bug as done --

Bug#1058635: src:mes: fails to migrate to testing for too long: FTBFS on armhf

Source: mes Version: 0.24.2-1 Severity: serious Control: close -1 0.25-1 Tags: sid trixie 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 30 days as

Processed: update found

Processing commands for cont...@bugs.debian.org: > found 1056427 2023.9.25-1 Bug #1056427 [src:monty] monty's autopkg tests fail with Python 3.12 Marked as found in versions monty/2023.9.25-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056427:

Processed: src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure

Processing control commands: > close -1 9.4-2 Bug #1058630 [src:coreutils] src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure Marked as fixed in versions coreutils/9.4-2. Bug #1058630 [src:coreutils] src:coreutils: fails to migrate to testing for too long:

Bug#1058630: src:coreutils: fails to migrate to testing for too long: triggers autopkgtest failure

Source: coreutils Version: 9.1-1 Severity: serious Control: close -1 9.4-2 Tags: sid trixie 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 30 days as

Processed: src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure

Processing control commands: > close -1 2.0+2023.10.31-1 Bug #1058629 [src:starjava-votable] src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure Marked as fixed in versions starjava-votable/2.0+2023.10.31-1. Bug #1058629 [src:starjava-votable]

Bug#1058629: src:starjava-votable: fails to migrate to testing for too long: triggers autopkgtest failure

Source: starjava-votable Version: 2.0+2023.04.14-1 Severity: serious Control: close -1 2.0+2023.10.31-1 Tags: sid trixie 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

Processed: src:r10k: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 4.0.0-1 Bug #1058628 [src:r10k] src:r10k: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r10k/4.0.0-1. Bug #1058628 [src:r10k] src:r10k: fails to migrate to testing for too long: autopkgtest regression Marked

Bug#1058628: src:r10k: fails to migrate to testing for too long: autopkgtest regression

Source: r10k Version: 3.15.4-1 Severity: serious Control: close -1 4.0.0-1 Tags: sid trixie 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 30 days as

Processed: src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 5.1-2 Bug #1058627 [src:zope.proxy] src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions zope.proxy/5.1-2. Bug #1058627 [src:zope.proxy] src:zope.proxy: fails to migrate to testing for too long:

Bug#1058627: src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression

Source: zope.proxy Version: 4.5.0-1 Severity: serious Control: close -1 5.1-2 Tags: sid trixie 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 30 days as

Processed: netcdf: Finalize HDF5 library at exit

Processing control commands: > block 1057590 by -1 Bug #1057590 [src:octave-netcdf] octave-netcdf: FTBFS: fatal: caught signal Segmentation fault -- stopping myself... Bug #1057589 [src:octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal Segmentation fault -- stopping myself... 1057590

Bug#1057802: marked as done (libgetdata ftbfs when building binary-indep packages only)

Your message dated Wed, 13 Dec 2023 16:37:57 + with message-id and subject line Bug#1057802: fixed in libgetdata 0.11.0-11 has caused the Debian Bug report #1057802, regarding libgetdata ftbfs when building binary-indep packages only to be marked as done. This means that you claim that the

Bug#1057872: marked as done (python3-pygetdata is empty)

Your message dated Wed, 13 Dec 2023 16:37:57 + with message-id and subject line Bug#1057872: fixed in libgetdata 0.11.0-11 has caused the Debian Bug report #1057872, regarding python3-pygetdata is empty to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1050086: marked as done (rust-ahash: Fails to build)

Your message dated Wed, 13 Dec 2023 11:00:02 -0500 with message-id and subject line Re: Bug#1050086: rust-ahash: Fails to build has caused the Debian Bug report #1050086, regarding rust-ahash: Fails to build to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

On 13/12/23 9:13 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:54 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. Proposed it to release team as #1058615

Processed: Re: Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned ex

Processing commands for cont...@bugs.debian.org: > tags 1058218 upstream Bug #1058218 [src:libei] libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 Added tag(s)

Bug#1058118: marked as done (python-apt: FTBFS: AssertionError: pyflakes failed with: 1)

Your message dated Wed, 13 Dec 2023 15:50:42 + with message-id and subject line Bug#1058118: fixed in python-apt 2.7.2 has caused the Debian Bug report #1058118, regarding python-apt: FTBFS: AssertionError: pyflakes failed with: 1 to be marked as done. This means that you claim that the

Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

On 13/12/23 8:54 pm, Praveen Arimbrathodiyil wrote: On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. Proposed it to release team as #1058615 OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP

Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1

The build is failing on ppc64el for Ubuntu so it might be more of a timing issue than architecture specific. I've reported it upstream to https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2046357

Processed: Bug#1058118 marked as pending in python-apt

Processing control commands: > tag -1 pending Bug #1058118 [src:python-apt] python-apt: FTBFS: AssertionError: pyflakes failed with: 1 Ignoring request to alter tags of bug #1058118 to the same tags previously set -- 1058118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058118 Debian Bug

Bug#1058118: marked as pending in python-apt

Control: tag -1 pending Hello, Bug #1058118 in python-apt 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#1042652: marked as done (pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

Your message dated Wed, 13 Dec 2023 15:34:48 + with message-id and subject line Bug#1042652: fixed in pyfuse3 3.3.0-0.1 has caused the Debian Bug report #1042652, regarding pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This means

Processed: Re: Fixed upstream

Processing control commands: > tags -1 pending Bug #1042652 [src:pyfuse3] pyfuse3: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. -- 1042652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042652 Debian Bug Tracking System Contact

Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

On 13/12/23 8:52 pm, Yadd wrote: since severity is grave, please prepare an update for stable also Yes, I'm backporting the updated patch. OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Bug#1058596: [Pkg-javascript-devel] Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

On 12/13/23 19:17, Praveen Arimbrathodiyil wrote: Control: fixed -1 1.22.19+~cs24.27.18-4 On Wed, 13 Dec 2023 20:39:39 +0530 Pirate Praveen wrote: We should backport the patches in unstable to bookworm as well. Updating the fixed info. Hi, since severity is grave, please prepare an

Bug#1058613: r-bioc-dss: Prevent migration to testing due to missing source

Source: r-bioc-dss Version: 2.48.0+dfsg-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: 1054...@bugs.debian.org As reported to upstream the source download for Bioconductor 3.18 of DSS is broken. To enable the Bioconductor 3.18 transition this package will be removed from

Bug#1058118: marked as pending in python-apt

Control: tag -1 pending Hello, Bug #1058118 in python-apt 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#1058118 marked as pending in python-apt

Processing control commands: > tag -1 pending Bug #1058118 [src:python-apt] python-apt: FTBFS: AssertionError: pyflakes failed with: 1 Added tag(s) pending. -- 1058118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058118 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1058247: marked as done (git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute 'assertRaisesRegexp')

Your message dated Wed, 13 Dec 2023 15:19:12 + with message-id and subject line Bug#1058247: fixed in git-review 2.3.1-2 has caused the Debian Bug report #1058247, regarding git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute

Processed: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)

Processing control commands: > tags -1 help Bug #1058555 [src:parallel] parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory Added tag(s) help. -- 1058555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058555 Debian Bug Tracking System

Bug#1058555: [Help] Missing proper Build-Depends from libreoffice (Wass: Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory)

Control: tags -1 help Am Tue, Dec 12, 2023 at 09:52:48PM +0100 schrieb Lucas Nussbaum: > > /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or > > directory This file is (re-)created via libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt Formerly this worked

Processed: Re: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

Processing control commands: > fixed -1 1.22.19+~cs24.27.18-4 Bug #1058596 [yarnpkg] yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function Marked as fixed in versions node-yarnpkg/1.22.19+~cs24.27.18-4. -- 1058596:

Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

Control: fixed -1 1.22.19+~cs24.27.18-4 On Wed, 13 Dec 2023 20:39:39 +0530 Pirate Praveen wrote: We should backport the patches in unstable to bookworm as well. Updating the fixed info. OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP

Bug#1058353: libadios2-mpi-c-dev: ships headers already shipped in libadios2-common-c-dev

Source: adios2 Followup-For: Bug #1058353 Damn, something went badly wrong in debian/rules. Sorry about that. I'll fix it as soon as possible, in the meantime use the version in testing. Drew

Bug#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

Package: yarnpkg Version: 1.22.19+~cs24.27.18-2 severity: grave justification: breaks any options passed to yarnpkg yarnpkg install also fails with similar errors due to incompatible node-commander We should backport the patches in unstable to bookworm as well. # cat

Bug#1058557: marked as done (msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package xcolor.)

Your message dated Wed, 13 Dec 2023 15:06:52 + with message-id and subject line Bug#1058557: fixed in msolve 0.6.1-2 has caused the Debian Bug report #1058557, regarding msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package xcolor. to be marked as done. This means that you

Bug#1058549: marked as done (plastex: FTBFS: make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2)

Your message dated Wed, 13 Dec 2023 15:07:03 + with message-id and subject line Bug#1058549: fixed in plastex 3.0-3 has caused the Debian Bug report #1058549, regarding plastex: FTBFS: make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 2 to be marked as done. This means that

Bug#1055817: marked as done (ghc-doc: piuparts regression)

Your message dated Wed, 13 Dec 2023 15:05:33 + with message-id and subject line Bug#1055817: fixed in ghc 9.4.7-2 has caused the Debian Bug report #1055817, regarding ghc-doc: piuparts regression to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Bug#1058247 marked as pending in git-review

Processing control commands: > tag -1 pending Bug #1058247 [src:git-review] git-review: FTBFS: AssertionError: Exception not expected: 'GitReviewConsole' object has no attribute 'assertRaisesRegexp' Added tag(s) pending. -- 1058247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058247

Bug#1058247: marked as pending in git-review

Control: tag -1 pending Hello, Bug #1058247 in git-review 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#1058462: marked as done (texlive-bibtex-extra: file conflict with liblatex-tounicode-perl on ltx2unitxt(1) manpage)

Your message dated Wed, 13 Dec 2023 14:49:36 + with message-id and subject line Bug#1058462: fixed in texlive-extra 2023.20231207-2 has caused the Debian Bug report #1058462, regarding texlive-bibtex-extra: file conflict with liblatex-tounicode-perl on ltx2unitxt(1) manpage to be marked as

Bug#1058152: marked as done (qt5reactor: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

Your message dated Wed, 13 Dec 2023 14:34:59 + with message-id and subject line Bug#1058152: fixed in qt5reactor 0.6.1-2 has caused the Debian Bug report #1058152, regarding qt5reactor: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean:

Processed: Bug#1058152 marked as pending in qt5reactor

Processing control commands: > tag -1 pending Bug #1058152 [src:qt5reactor] qt5reactor: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Added tag(s) pending. -- 1058152:

Bug#1058152: marked as pending in qt5reactor

Control: tag -1 pending Hello, Bug #1058152 in qt5reactor 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#1058384: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Control: forwarded -1 https://github.com/ionelmc/python-lazy-object-proxy/pull/78 Dear Maintainer, Root cause is that deprecations are treated as errors in pytest.ini [1] Kind regards [1] https://sources.debian.org/src/lazy-object-proxy/1.9.0-1/pytest.ini/#L35-L36

Processed: Re: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Processing control commands: > forwarded -1 https://github.com/ionelmc/python-lazy-object-proxy/pull/78 Bug #1058384 [src:lazy-object-proxy] lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Set Bug

Bug#1058166: marked as done (python-tubes: FTBFS: AttributeError: 'RouterTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

Your message dated Wed, 13 Dec 2023 13:49:40 + with message-id and subject line Bug#1058166: fixed in python-tubes 0.2.1-4 has caused the Debian Bug report #1058166, regarding python-tubes: FTBFS: AttributeError: 'RouterTests' object has no attribute 'assertEquals'. Did you mean:

Bug#1056509: marked as done (python-tube's autopkg tests fail with Python 3.12)

Your message dated Wed, 13 Dec 2023 13:49:40 + with message-id and subject line Bug#1056509: fixed in python-tubes 0.2.1-4 has caused the Debian Bug report #1056509, regarding python-tube's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem

Processed: tagging 1058031, bug 1058031 is forwarded to https://github.com/pygame/pygame/issues/4046

Processing commands for cont...@bugs.debian.org: > tags 1058031 + upstream Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Added tag(s) upstream. > forwarded 1058031 https://github.com/pygame/pygame/issues/4046 Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Set Bug

Bug#1058201: marked as done (pytorch-scatter: FTBFS: ImportError: Failed to load PyTorch C extensions:)

Your message dated Wed, 13 Dec 2023 13:04:29 + with message-id and subject line Bug#1058201: fixed in pytorch-scatter 2.1.2-1 has caused the Debian Bug report #1058201, regarding pytorch-scatter: FTBFS: ImportError: Failed to load PyTorch C extensions: to be marked as done. This means that

Bug#1058504: marked as done (lua-zlib: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)

Your message dated Wed, 13 Dec 2023 12:48:56 + with message-id and subject line Bug#1058504: fixed in lua-zlib 1.2-4 has caused the Debian Bug report #1058504, regarding lua-zlib: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test

Bug#1055553: marked as done (python-lzo ftbfs with Python 3.12)

Your message dated Wed, 13 Dec 2023 13:29:34 +0100 with message-id <5e5a0b0b-13ed-4c70-8af1-b26237afa...@debian.org> and subject line Fixed has caused the Debian Bug report #103, regarding python-lzo ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has

Bug#1058143: marked as done (python-pyutil: FTBFS: AttributeError: 'TestDecode' object has no attribute 'assert_'. Did you mean: 'assertIn'?)

Your message dated Wed, 13 Dec 2023 12:19:57 + with message-id and subject line Bug#1058143: fixed in python-pyutil 3.3.2-2 has caused the Debian Bug report #1058143, regarding python-pyutil: FTBFS: AttributeError: 'TestDecode' object has no attribute 'assert_'. Did you mean: 'assertIn'? to

Bug#1058519: marked as done (node-mdn-browser-compat-data: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)

Your message dated Wed, 13 Dec 2023 12:19:46 + with message-id and subject line Bug#1058519: fixed in node-mdn-browser-compat-data 5.2.20+~3.33.0-2 has caused the Debian Bug report #1058519, regarding node-mdn-browser-compat-data: FTBFS: make[1]: *** [debian/rules:11:

  1   2   >