Bug#1060929: marked as done (r-bioc-savr: FTBFS: make: *** [debian/rules:4: binary] Error 255)

Your message dated Thu, 25 Jan 2024 07:50:53 + with message-id and subject line Bug#1060929: fixed in r-bioc-savr 1.37.0-2 has caused the Debian Bug report #1060929, regarding r-bioc-savr: FTBFS: make: *** [debian/rules:4: binary] Error 255 to be marked as done. This means that you claim

Processed: Reduce severity since it is not reproducible

Processing control commands: > severity -1 important Bug #1060973 [src:python-pbcore] python-pbcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Severity set to 'important' from 'serious' -- 1060973:

Bug#1060973: Reduce severity since it is not reproducible

Control: severity -1 important

Processed (with 1 error): Re: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

Processing control commands: > retitle -1: Upgrade to 23.3.* breaks video rendering Unknown command or malformed arguments to command. > severity -1 serious Bug #1059782 [mesa-vdpau-drivers] mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter Severity set to 'serious' from

Bug#1061462: marked as done (revolt: Stop depending on webkit2gtk 4.0)

Your message dated Thu, 25 Jan 2024 04:21:17 + with message-id and subject line Bug#1061462: fixed in revolt 0.0+git20211216.7f6f762-2 has caused the Debian Bug report #1061462, regarding revolt: Stop depending on webkit2gtk 4.0 to be marked as done. This means that you claim that the

Processed: bug 1061339 is forwarded to https://github.com/numpy/numpy/issues/25681

Processing commands for cont...@bugs.debian.org: > forwarded 1061339 https://github.com/numpy/numpy/issues/25681 Bug #1061339 [src:numpy] numpy_1.26.3-1_s390x-buildd.changes REJECTED Set Bug forwarded-to-address to 'https://github.com/numpy/numpy/issues/25681'. > thanks Stopping processing here.

Bug#1055999: marked as pending in python-asyncssh

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

Processing control commands: > tag -1 pending Bug #1055999 [src:python-asyncssh] python-asyncssh: CVE-2023-46446 Added tag(s) pending. -- 1055999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060052: Status?

Can we please get a new release of a stable kernel? This keeps crashing our machines, and it is a pain manually updating to the 6.5 kernel on all of them. Med venlig hilsen Dennis Haney d...@voxmeter.dk Catglobe Direktør Mobil +84 907 42 46 52 Voxmeter A/S

Bug#1061470: vasttrafik-cli: API is offline

Package: vasttrafik-cli Version: 1.5-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: ltw...@debian.org Dear myself. The public API has completely changed. There is no way to register new accounts and obtain tokens for the new API. Until that is solved,

Bug#887139: d-i daily 2018-01-14 amd64 damages UEFI setup on Fujitsu Lifebook AH532

On Sun, 14 Jan 2018 13:38:11 +0100 Karsten Merker wrote: Machine: Fujitsu Lifebook AH532, first version (with BIOS version 1.09) [...] How can one bring the NVRAM back into a sane state that allows getting into the setup and booting from external devices? I personally had luck with doing a

Bug#1061466: nautilus FTBFS with nocheck profile: ../test/automated/displayless/meson.build:1:19: ERROR: Dependency "tracker-testutils-3.0" not found, tried pkgconfig

Source: nautilus Version: 45.2.1-3 Severity: serious Tags: patch ftbfs trixie sid nautilus fails to build from source when built with the nocheck profile. Since trixie such a build failure is considered release-critical. The build system does not automatically disable tests when test dependencies

Processed: tagging 1060934

Processing commands for cont...@bugs.debian.org: > tags 1060934 - trixie Bug #1060934 [src:pycountry] pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 Removed tag(s) trixie. > thanks Stopping processing here. Please contact me if you

Bug#1061457: marked as done (src:box64: fails to migrate to testing for too long: FTBFS on ppc64el)

Your message dated Wed, 24 Jan 2024 22:05:59 + with message-id and subject line Bug#1061457: fixed in box64 0.2.6+dfsg-3 has caused the Debian Bug report #1061457, regarding src:box64: fails to migrate to testing for too long: FTBFS on ppc64el to be marked as done. This means that you claim

Processed: tagging 1060934

Processing commands for cont...@bugs.debian.org: > tags 1060934 + patch Bug #1060934 [src:pycountry] pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need

Bug#1058172: marked as done (unattended-upgrades: FTBFS: AssertionError: 1 != 0)

Your message dated Wed, 24 Jan 2024 21:57:48 + with message-id and subject line Bug#1058172: fixed in unattended-upgrades 2.9.1+nmu4 has caused the Debian Bug report #1058172, regarding unattended-upgrades: FTBFS: AssertionError: 1 != 0 to be marked as done. This means that you claim that

Bug#1060934: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13

On Tue, 16 Jan 2024 20:41:58 +0100 Lucas Nussbaum wrote: > Source: pycountry > Version: 23.12.11+ds1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your

Bug#1051091: marked as done (giara: FTBFS: error: Expected string or translated string)

Your message dated Wed, 24 Jan 2024 21:52:25 + with message-id and subject line Bug#1051091: fixed in giara 1.1.0-0.1 has caused the Debian Bug report #1051091, regarding giara: FTBFS: error: Expected string or translated string to be marked as done. This means that you claim that the

Bug#1061464: tracker FTBFS with nocheck profile: ../meson.build:99:26: ERROR: python3 is missing modules: gi

Source: tracker Version: 3.4.2-3 Severity: serious Tags: patch trixie sid tracker fails to build from source when built with the nocheck build profile. This is considered release-critical since the trixie release, but not earlier. The failure is: ../meson.build:99:26: ERROR: python3 is

Bug#1061462: revolt: Stop depending on webkit2gtk 4.0

Source: revolt Version: 0.0+git20211216.7f6f762-1 Severity: serious Tags: patch trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 Forwarded: https://salsa.debian.org/matrix-team/revolt/-/merge_requests/1 The webkit2gtk maintainers intend to stop building the 4.0

Processed: src:pmacct: fails to migrate to testing for too long: Build-Depends not available on s390x

Processing control commands: > close -1 1.7.8-1 Bug #1061456 [src:pmacct] src:pmacct: fails to migrate to testing for too long: Build-Depends not available on s390x Marked as fixed in versions pmacct/1.7.8-1. Bug #1061456 [src:pmacct] src:pmacct: fails to migrate to testing for too long:

Processed: src:box64: fails to migrate to testing for too long: FTBFS on ppc64el

Processing control commands: > close -1 0.2.6+dfsg-2 Bug #1061457 [src:box64] src:box64: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions box64/0.2.6+dfsg-2. Bug #1061457 [src:box64] src:box64: fails to migrate to testing for too long: FTBFS on ppc64el

Bug#1061457: src:box64: fails to migrate to testing for too long: FTBFS on ppc64el

Source: box64 Version: 0.2.4+dfsg-1 Severity: serious Control: close -1 0.2.6+dfsg-2 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

Bug#1061456: src:pmacct: fails to migrate to testing for too long: Build-Depends not available on s390x

Source: pmacct Version: 1.7.7-1 Severity: serious Control: close -1 1.7.8-1 X-Debbugs-CC: Boyuan Yang 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

Bug#1028634: marked as done (libbtas-dev requires blaspp)

Your message dated Wed, 24 Jan 2024 14:59:30 -0500 with message-id <87frymijtp@sergiodj.net> and subject line Re: Bug#1028634: tiledarray: FTBFS: Could not find a package configuration file provided by "blaspp" has caused the Debian Bug report #1028634, regarding libbtas-dev requires blaspp

Processed: src:r-cran-ggally: fails to migrate to testing for too long: autopkgtest failure

Processing control commands: > close -1 2.2.0-1 Bug #1061455 [src:r-cran-ggally] src:r-cran-ggally: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions r-cran-ggally/2.2.0-1. Bug #1061455 [src:r-cran-ggally] src:r-cran-ggally: fails to migrate to testing

Bug#1061455: src:r-cran-ggally: fails to migrate to testing for too long: autopkgtest failure

Source: r-cran-ggally Version: 2.1.2-2 Severity: serious Control: close -1 2.2.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1059385 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1058101: marked as done (taurus-pyqtgraph: FTBFS: RuntimeError: wrapped C/C++ object of type Y2ViewBox has been deleted)

Your message dated Wed, 24 Jan 2024 14:29:12 -0500 with message-id <87mssuil87@sergiodj.net> and subject line Re: Bug#1058101: taurus-pyqtgraph: FTBFS: RuntimeError: wrapped C/C++ object of type Y2ViewBox has been deleted has caused the Debian Bug report #1058101, regarding taurus-pyqtgraph:

Processed: bug 1061451 is forwarded to https://github.com/renpy/renpy/issues/5303

Processing commands for cont...@bugs.debian.org: > forwarded 1061451 https://github.com/renpy/renpy/issues/5303 Bug #1061451 [renpy] renpy: remove dependency on python3-future Set Bug forwarded-to-address to 'https://github.com/renpy/renpy/issues/5303'. > thanks Stopping processing here. Please

Processed: block 1059934 with 1061451

Processing commands for cont...@bugs.debian.org: > block 1059934 with 1061451 Bug #1059934 [src:python-future] python-future: RM python3-future / tracker 1059934 was blocked by: 1058995 1059109 1059098 1059108 1058861 1059944 1059948 1059949 1058987 1060025 1058952 1058997 1059946 1058644

Bug#1061451: renpy: remove dependency on python3-future

Package: renpy Version: 8.0.3+dfsg-1 Severity: serious pitfall n°1: there's no version 8.2.0: it's a daily snapshot, we need to wait for a proper release pitfall n°2: removing python3-future from RenPy seems not so complicated but that _may_ or not break games if they

Bug#999990: marked as done (poco: depends on obsolete pcre3 library)

Your message dated Wed, 24 Jan 2024 19:10:32 + with message-id and subject line Bug#89: fixed in poco 1.13.0-1 has caused the Debian Bug report #89, regarding poco: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with.

Bug#999989: marked as done (poco: depends on obsolete pcre3 library)

Your message dated Wed, 24 Jan 2024 19:10:32 + with message-id and subject line Bug#89: fixed in poco 1.13.0-1 has caused the Debian Bug report #89, regarding poco: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1061320: marked as done (dblatex: FTBFS with Python 3.12 as default)

Your message dated Wed, 24 Jan 2024 18:19:52 + with message-id and subject line Bug#1061320: fixed in dblatex 0.3.12py3-3 has caused the Debian Bug report #1061320, regarding dblatex: FTBFS with Python 3.12 as default to be marked as done. This means that you claim that the problem has been

Processed: severity of 926900 is serious

Processing commands for cont...@bugs.debian.org: > severity 926900 serious Bug #926900 [reportbug] sslv3 alert illegal parameter Bug #988415 [reportbug] sslv3 alert illegal parameter Bug #988416 [reportbug] sslv3 alert illegal parameter Severity set to 'serious' from 'normal' Severity set to

Bug#1061301: test failures are caused by python3.12

looks like the tests pass with python 3.11, but fail with 3.12. Not related to any network lookups. Is there a reason that the tests are not run for all supported Python versions?

Bug#1061441: python-glanceclient: autopkgtest failure with Python 3.12

Source: python-glanceclient Version: 1:4.4.0-2 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-glanceclient's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1061440: azure-cosmos-table-python: autopkgtest failure with Python 3.12

Source: azure-cosmos-table-python Version: 1.0.5+git20191025-6 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer azure-cosmos-table-python's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log

Processed: closing 1060968

Processing commands for cont...@bugs.debian.org: > # igor2 is now available in Debian > close 1060968 Bug #1060968 [src:navarp] navarp: FTBFS: build-dependency not installable: python3-igor2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1061438: tpm2-tss: can't upgrade the tpm2-tss packages to 4.0.1-6; missing Conflicts?

Source: tpm2-tss Version: 4.0.1-6 Severity: serious It is not possible to upgrade the tpm2-tss packages to 4.0.1-6 with "apt upgrade" or with aptitude (command line or its TUI, without a *manual* dependency resolution): root@disset:~# apt upgrade Reading package lists... Done Building dependency

Bug#1061437: firefox-esr: Fails to build with Python 3.12 as default

Source: firefox-esr Version: 115.6.0esr-1 Severity: serious Tags: ftbfs patch sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 mozjs115 115.7.0 failed to build on Ubuntu 24.04 LTS which is one step ahead of Debian on the Python 3.12 transition. I didn't check the firefox-esr

Processed: Bug#1058182 marked as pending in mistral

Processing control commands: > tag -1 pending Bug #1058182 [src:mistral] mistral: FTBFS: AssertionError: Failed to wait for expected result: Execution f2a97f87-7b08-4171-819a-47e30a0a1840 must have reached state SUCCESS state but it is in RUNNING Added tag(s) pending. -- 1058182:

Bug#1058182: marked as pending in mistral

Control: tag -1 pending Hello, Bug #1058182 in mistral 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#1061435: lintian-brush ftbfs with updated pyo3 version

Package: src:lintian-brush Version: 2.0.5-2 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 the package ftbfs, with: running build_rust cargo build --manifest-path debianize/Cargo.toml --message-format=json-render-diagnostics --release -v

Bug#1061434: python 3.12 extension not working

Package: python3-levenshtein Version: 0.12.2-2+b5 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 the python 3.12 extension is not working: $ python3.12 -c 'import Levenshtein' Traceback (most recent call last): File "", line 1, in File

Bug#1061426: opm-common ftbfs with Python 3.12 as the default

Package: src:opm-common Version: 2023.04+ds-5 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 ftbfs with python3-defaults from experimental the package builds, then fails in the tests. there is also a b-d on python3-distutils, which is gone in

Bug#1014862: marked as done (vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad")

Your message dated Wed, 24 Jan 2024 11:50:50 +0100 with message-id <07dc42d7-eb8c-425c-b8fd-f4e95eb25...@uni-mainz.de> and subject line Fwd: Bug#1014862 vdr-plugin-markad: FTBFS: Cannot find (any matches for) "command/markad" has caused the Debian Bug report #1014862, regarding vdr-plugin-markad:

Bug#1060449: marked as done (completely wrong version number reported)

Your message dated Wed, 24 Jan 2024 10:34:31 + with message-id and subject line Bug#1060449: fixed in imapfilter 1:2.8.2+1-0.1 has caused the Debian Bug report #1060449, regarding completely wrong version number reported to be marked as done. This means that you claim that the problem has

Processed: Re: python3-trio: AttributeError: module 'eventlet.green.select' has no attribute 'epoll'

Processing commands for cont...@bugs.debian.org: > severity 1061410 wishlist Bug #1061410 [python3-trio] python3-trio: AttributeError: module 'eventlet.green.select' has no attribute 'epoll' Severity set to 'wishlist' from 'grave' > thanks Stopping processing here. Please contact me if you need

Bug#1061410: python3-trio: AttributeError: module 'eventlet.green.select' has no attribute 'epoll'

severity 1061410 wishlist thanks This doesn't seem like a bug in python-trio to me. It's simply using select.epoll(). If that's being monkey patched by gevent in a way that breaks things then that seems like either a gevent problem or a fundamental incompatibility in trying to use Trio at the

Bug#1061385: marked as done (golang-github-google-go-pkcs11: tests fail on 32 bit architectures)

Your message dated Wed, 24 Jan 2024 10:20:04 + with message-id and subject line Bug#1061385: fixed in golang-github-google-go-pkcs11 0.3.0+dfsg-2 has caused the Debian Bug report #1061385, regarding golang-github-google-go-pkcs11: tests fail on 32 bit architectures to be marked as done.

Bug#1061421: Fails to start after an upgrade

Package: wlgreet Version: 0.4.1-3 Severity: grave After a semi-recent upgrade (I'm not sure which one, as I don't reboot or restart my session after each one) of testing wlgreet no longer starts. Here is what I get when trying to start it under a manually launched sway session:

Processed: Bug#1061385 marked as pending in golang-github-google-go-pkcs11

Processing control commands: > tag -1 pending Bug #1061385 [src:golang-github-google-go-pkcs11] golang-github-google-go-pkcs11: tests fail on 32 bit architectures Added tag(s) pending. -- 1061385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061385 Debian Bug Tracking System Contact

Bug#1061385: marked as pending in golang-github-google-go-pkcs11

Control: tag -1 pending Hello, Bug #1061385 in golang-github-google-go-pkcs11 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#1057576: mako: FTBFS: dh_sphinxdoc: error: debian/python-mako-doc/usr/share/doc/python-mako-doc/html/search.html top-level node does not have data-content_root attribute

Dear Maintainer, Your package builds fine locally in a sid chroot environment, but I'm able to reproduce the reported failure against zzzeeksphinx/1.4.0-1 from snapshot.debian.org [1]. Reported FTBFS log states:   Get:98 http://deb.debian.org/debian sid/main amd64 python3-zzzeeksphinx all

Bug#1061420: obs-studio won't migrate, missing build on ppc64el

Package: src:obs-studio Version: 30.0.2+dfsg-2 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 obs-studio won't migrate, missing build on ppc64el, because luajit isn't built anymore on ppc64el. This will block python3-defaults, when making 3.12 the

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

Dear Maintainer, This issue was fixed in cryptodrome [1] and I can build successfully your package in a sid chroot environment for amd64 architecture. I guess the failure still persists on armel and mips64el [2] (not verified).   ∙ ∙ missing build on armel   ∙ ∙ missing build on mips64el [1]