Bug#1057171: marked as done (libitext5-java: FTBFS with bouncycastle 1.77)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Tue, 12 Dec 2023 07:19:57 + with message-id and subject line Bug#1057171: fixed in libitext5-java 5.5.13.3-3 has caused the Debian Bug report #1057171, regarding libitext5-java: FTBFS with bouncycastle 1.77 to be marked as done. This means that you claim that the problem

Bug#1057171: libitext5-java: FTBFS with bouncycastle 1.77

2023-12-11 Thread tony mancill
On Thu, Nov 30, 2023 at 11:06:56PM +0100, Markus Koschany wrote: > Source: libitext5-java > Version: 5.5.13.3-2 > Severity: serious > Tags: ftbfs sid > User: a...@debian.org > Usertags: bouncycastle-1.77 There are PDF signature and encryption test cases running as part of the build, and I did

Processed: Re: [Pkg-javascript-devel] Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1058078 [node-eslint-plugin-eslint-plugin] FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from Added tag(s) patch. -- 1058078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058078 Debian Bug Tracking System

Bug#1058078: [Pkg-javascript-devel] Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

2023-12-11 Thread Yadd
Control: tags -1 + patch On 12/12/23 09:59, Yadd wrote: Package: node-eslint-plugin-eslint-plugin Version: 2.3.0+~0.3.0-4 Severity: serious Tags: ftbfs Justification: ftbfs Hi, when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild fails. Below relevant logs: eslint --format

Bug#1055684: marked as done (beancount fails tests with Python 3.12)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Tue, 12 Dec 2023 06:04:17 + with message-id and subject line Bug#1055684: fixed in beancount 2.3.6-1 has caused the Debian Bug report #1055684, regarding beancount fails tests with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1058078: FTBFS: ESLint couldn't find the config "not-an-aardvark/node" to extend from

2023-12-11 Thread Yadd
Package: node-eslint-plugin-eslint-plugin Version: 2.3.0+~0.3.0-4 Severity: serious Tags: ftbfs Justification: ftbfs Hi, when trying to reproduce node-eslint-plugin-eslint-plugin build, sbuild fails. Below relevant logs: eslint --format tap Xcomposer TAP version 13 1..2 ok 1 -

Bug#1056534: marked as done (tkcalendar's autopkg tests fail with Python 3.12)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Tue, 12 Dec 2023 03:04:08 + with message-id and subject line Bug#1056534: fixed in tkcalendar 1.6.1-4 has caused the Debian Bug report #1056534, regarding tkcalendar's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Steve VanDevender
Salvatore Bonaccorso writes: > Control: tags -1 + moreinfo > > Hi Steve, > > On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote: > > Package: src:linux > > Version: 6.1.66-1 > > Severity: grave > > Tags: upstream > > Justification: renders package unusable > > > > I

Bug#1058074: rust-hyper-rustls - autopkgtest failure

2023-12-11 Thread Peter Green
Package: rust-hyper-rustls Version: 0.24.2-1 Severity: serious Tags: patch The autopkgtest for rust-hyper-rustls is failing, because the code in test_alpn_http2 requires a runtime, but the feature requirements for the test do not specify one. A debdiff fixing this is attatched.diff -Nru

Bug#1057579: marked as done (mplayer: FTBFS: error: 'INT_MAX' undeclared (first use in this function))

2023-12-11 Thread Debian Bug Tracking System
Your message dated Tue, 12 Dec 2023 00:35:01 + with message-id and subject line Bug#1057579: fixed in mplayer 2:1.5+svn38446-1 has caused the Debian Bug report #1057579, regarding mplayer: FTBFS: error: 'INT_MAX' undeclared (first use in this function) to be marked as done. This means that

Processed: reassign 1056461 to python3-future

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1056461 python3-future Bug #1056461 [src:python-canmatrix] python-canmatrix's autopkg tests fail with Python 3.12 Bug reassigned from package 'src:python-canmatrix' to 'python3-future'. No longer marked as found in versions

Bug#1042049: lintian: FTBFS: 3 tests failed

2023-12-11 Thread Richard Lewis
On Thu, 7 Dec 2023 22:05:29 +1300 Vladimir Petko wrote: > As of today there are more test failures: > Test Summary Report > --- > debian/test-out/eval/checks/documentation/manual/manpage-errors-from-man/generic.t >

Bug#1056461: python-canmatrix's autopkg tests fail with Python 3.12

2023-12-11 Thread IOhannes m zmoelnig
Source: python-canmatrix Followup-For: Bug #1056461 This seems to really be a bug in python3-future: ```sh $ python3-c "import past.builtins" $ python3.12 -c "import past.builtins" Traceback (most recent call last): File "", line 1, in File

Bug#1058038: texlive-extra: Blocker bug

2023-12-11 Thread Preuße
On 11.12.2023 21:30, Chris Hofstaedtler wrote: On Mon, Dec 11, 2023 at 02:57:35PM +, Hilmar Preusse wrote: Hi, Severity: normal This bug blocks the migration for now, I'll close it, once the other two packages tend to migrate. Pretty sure severity: normal does not block => raising.

Bug#1000112: kjs: depends on obsolete pcre3 library

2023-12-11 Thread Bastian Germann
okular and khelpcenter make kjs a key package via khtml. While it is optional in okular, khelpcenter requires khtml. This is changing with the 24.08.x versions, which will be part of Plasma 6. When khelpcenter upgrades to a khtml-free version, this should be followed-up.

Processed: pyopengl's autopkg tests fail with Python 3.12

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1058031 Bug #1056440 [src:pyopengl] pyopengl's autopkg tests fail with Python 3.12 1056440 was not blocked by any bugs. 1056440 was not blocking any bugs. Added blocking bug(s) of 1056440: 1058031 -- 1056440:

Bug#1056440: pyopengl's autopkg tests fail with Python 3.12

2023-12-11 Thread Sebastiaan Couwenberg
Control: block -1 by 1058031 This seems to be fixed upstream: https://github.com/mcfletch/pyopengl/issues/99 The pyopengl test suite fails because pygame FTBFS with Python 3.12 (#1058031) this likely also affects the autopkgtest. -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Breaking news: Am 11.12.23 um 19:14 schrieb Salvatore Bonaccorso: > I have put binary packages for amd64 built in > https://people.debian.org/~carnil/tmp/linux/1057967/ I confirm this test kernel is working fine for me, even with non-free broadcom-sta. (sent from " cat /proc/version Linux

Bug#1058062: marked as done (python-cloup accesses the network while building the docs)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 21:06:45 + with message-id and subject line Bug#1058062: fixed in python-cloup 3.0.3-2 has caused the Debian Bug report #1058062, regarding python-cloup accesses the network while building the docs to be marked as done. This means that you claim that the

Processed: Bug#1058062 marked as pending in python-cloup

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058062 [src:python-cloup] python-cloup accesses the network while building the docs Added tag(s) pending. -- 1058062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058062 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1058062: marked as pending in python-cloup

2023-12-11 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1058062 in python-cloup 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: Re: Bug#1058038: texlive-extra: Blocker bug

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1058038 [src:texlive-extra] texlive-extra: Blocker bug Severity set to 'serious' from 'normal' -- 1058038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Andreas Tille
Hi Alexandre, Am Mon, Dec 11, 2023 at 09:18:16PM +0100 schrieb Alexandre Detiste: > > https://github.com/lebigot/uncertainties/releases/tag/3.1.7 > > +1 OK. > > Also we should probably get rid of python-future at some point. > > I removed it from three games this week-end > and filled 6 more

Bug#1058062: python-cloup accesses the network while building the docs

2023-12-11 Thread Matthias Klose
Package: src:python-cloup Version: 3.0.3-1 Severity: serious Tags: sid trixie python-cloup accesses the network while building the docs: [...] [autosummary] generating autosummary for: index.rst, pages/aliases.rst, pages/arguments.rst, pages/changelog.rst, pages/constraints.rst,

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Alexandre Detiste
Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit : > I think the right thing here is to package the new uncertainties version > which drops the past import: > > https://github.com/lebigot/uncertainties/releases/tag/3.1.7 +1 > Also we should probably get rid of python-future at some

Processed: Re: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1058018 [libadios2-common-core-dev] libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake Severity set to 'important' from 'serious' -- 1058018:

Bug#1058018: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

2023-12-11 Thread Drew Parsons
Source: adios2 Followup-For: Bug #1058018 Control: severity -1 important Call it teething issues. This is a new package, so I'm trying to avoid making debian/control more verbose than it needs to be by not crowding the fields with the strict specifications needed to avoid this error. Once the

Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread Salvatore Bonaccorso
As there were some questions along in this thread let me summarize some points: The issue affects fs/ext4 code, so no other filesystems are affected (e.g. btrfs). The issue affects all kernels which have the commit 91562895f803 ("ext4: properly sync file size update after O_SYNC direct IO") from

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-11 Thread Julian Gilbey
On Mon, Dec 11, 2023 at 08:06:41PM +0100, Matthias Klose wrote: > > [...] > > Excellent - I didn't know about that. Are you OK for me to upload > > versions of cython and cython-legacy which depend on this to fix the > > Python 3.12 breakage? > > not for cython, which won't need that soonish for

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-11 Thread Matthias Klose
On 11.12.23 19:55, Julian Gilbey wrote: On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote: On 11.12.23 16:19, Julian Gilbey wrote: On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote: [...] You could package a non-conflicting cython-legacy, however that would require

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-11 Thread Julian Gilbey
On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote: > On 11.12.23 16:19, Julian Gilbey wrote: > > On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote: > > > [...] > > > You could package a non-conflicting cython-legacy, however that would > > > require more changes, also how

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Salvatore Bonaccorso
Hi, On Mon, Dec 11, 2023 at 01:27:07PM +0100, Kevin Price wrote: > Thank you Salvatore! > > Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso: > > It still would be helpfull if you can get to the logs of the previous > > boot. After booting back in the working kernel, do you have anything > >

Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4

2023-12-11 Thread Alexander Kjäll
Hi I'm sorry for the semver breakage, the last version was a bit stressed out due to the security problems with libgit2 not verifying server signatures (that has since been fixed). I think the best path forward might be to package the latest versions, I have started that but not finished yet due

Bug#1057843: Bug patching

2023-12-11 Thread Sergiu
Hi Any new information, when will this be patched? There are packages that can not be installed like nvidia-driver because while installing it updates the system and the process fails. Isn't possible to remove from the repo the corrupted kernel so that people can install other packages?

Bug#1058047: gammapy: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: gammapy Version: 1.1-3 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer gammapy FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread Dennis Grevenstein
On Mon, 11 Dec 2023 10:38:40 +0100 helios.sola...@gmx.ch wrote: > I have been running debian 12.3 with kernel 6.1.64-1 for a few hours, > how can I find out whether the file system has been corrupted? yes, I would also appreciate an explanation who could be affected, how to diagnose the problem,

Bug#1057614: marked as done (python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 16:52:56 + with message-id and subject line Bug#1057614: fixed in python-kaptan 0.6.0-1 has caused the Debian Bug report #1057614, regarding python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory to be marked as done.

Bug#1055597: marked as done (libmail-message-perl: off-by-one error wrt to newlines after a multipart separator)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 16:49:43 + with message-id and subject line Bug#1055597: fixed in libmail-message-perl 3.015-1 has caused the Debian Bug report #1055597, regarding libmail-message-perl: off-by-one error wrt to newlines after a multipart separator to be marked as done.

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 16:38:06 + with message-id and subject line Bug#1056493: fixed in python-pulp 2.7.0+dfsg-2 has caused the Debian Bug report #1056493, regarding python-pulp's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Processed: Re: gst-python1.0 ftbfs with Python 3.12

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1055575 > https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3170 Bug #1055575 [src:gst-python1.0] gst-python1.0 ftbfs with Python 3.12 Set Bug forwarded-to-address to

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 16:22:54 + with message-id and subject line Bug#1056487: fixed in python-multipletau 0.3.3+ds-5 has caused the Debian Bug report #1056487, regarding python-multipletau's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim

Processed: reassign 1055597 to libmail-message-perl, affects 1055597, tagging 1055597 ...

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1055597 libmail-message-perl 3.014-1 Bug #1055597 [src:libmail-box-perl] FTBFS: test failure with Mail-Message 3.014 Bug reassigned from package 'src:libmail-box-perl' to 'libmail-message-perl'. No longer marked as found in versions

Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64 Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Added indication that 1057967 affects src:broadcom-sta and linux-image-6.1.0-15-amd64 --

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Control: affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64 @other affected users: What wifi drivers are you using, and do they taint your kernel? Am 11.12.23 um 13:27 schrieb Kevin Price: > Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso: > Need any more logfiles or testing? Is it

Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Jochen Sprickerhof
Hi Andreas, * Andreas Tille [2023-12-11 16:42]: Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244.

Processed: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1042244 [src:python-future] python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) help. -- 1042244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042244 Debian

Processed: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1056419 [src:lmfit-py] lmfit-py's autopkg tests fail with Python 3.12 Added tag(s) help. -- 1056419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1042244: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-11 Thread Andreas Tille
Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244. Unfortunately this is not the case and now with

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-11 Thread Matthias Klose
On 11.12.23 16:19, Julian Gilbey wrote: On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote: [...] You could package a non-conflicting cython-legacy, however that would require more changes, also how to build it. Hi Matthias, Unfortunately, at least some of cython3-legacy doesn't

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 15:19:15 + with message-id and subject line Bug#1056506: fixed in python-stone 3.3.1-3 has caused the Debian Bug report #1056506, regarding python-stone's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-11 Thread Julian Gilbey
On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote: > [...] > You could package a non-conflicting cython-legacy, however that would > require more changes, also how to build it. Hi Matthias, Unfortunately, at least some of cython3-legacy doesn't currently work with Python 3.12, and

Bug#1058040: pymatgen: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: pymatgen Version: 2023.06.23+dfsg1-2 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pymatgen FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1058039: cctbx: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: cctbx Version: 2022.9+ds2+~3.11.2+ds1-6 Severity: serious Tags: ftbfs sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer cctbx FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below. Regards

Bug#1056493: python-pulp's autopkg tests fail with Python 3.12

2023-12-11 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/coin-or/pulp/issues/709 -- http://fam-tille.de

Processed: Re: python-pulp's autopkg tests fail with Python 3.12

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1056493 [src:python-pulp] python-pulp's autopkg tests fail with Python 3.12 Added tag(s) upstream. > forwarded -1 https://github.com/coin-or/pulp/issues/709 Bug #1056493 [src:python-pulp] python-pulp's autopkg tests fail with Python 3.12 Set

Processed: python-skbio ftbfs with Python 3.12 (and cython 3.0.5)

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1056047 [src:python-skbio] python-skbio ftbfs with Python 3.12 (and cython 3.0.5) Severity set to 'important' from 'serious' -- 1056047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056047 Debian Bug Tracking System Contact

Bug#1056047: python-skbio ftbfs with Python 3.12 (and cython 3.0.5)

2023-12-11 Thread Graham Inggs
Control: severity -1 important This was worked around in 0.5.8-4.1. Downgrading severity for now.

Bug#1057951: marked as done (promod3: FTBFS: No such file or directory: 'model.pdb')

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 14:51:36 + with message-id and subject line Bug#1057951: fixed in promod3 3.3.1+ds-2 has caused the Debian Bug report #1057951, regarding promod3: FTBFS: No such file or directory: 'model.pdb' to be marked as done. This means that you claim that the

Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

2023-12-11 Thread JP Pozzi
Hello, The script /etc/init.d/qemu-guest-agent was modified by me to look at the problem, it is not the original one. I use also a "home made" script to get clear informations through a dedicated logfile : #!/bin/bash METHOD='virtio-serial'

Bug#997720: marked as done (wims: FTBFS: configure.ac: error: required file 'config.sub' not found)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 14:39:04 + with message-id and subject line Bug#997720: fixed in wims 2:4.27a+dfsg1-1 has caused the Debian Bug report #997720, regarding wims: FTBFS: configure.ac: error: required file 'config.sub' not found to be marked as done. This means that you claim

Bug#1057032: marked as done (wims: An updated package of wims closing all bugs exists.)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 14:39:04 + with message-id and subject line Bug#1057032: fixed in wims 2:4.27a+dfsg1-1 has caused the Debian Bug report #1057032, regarding wims: An updated package of wims closing all bugs exists. to be marked as done. This means that you claim that the

Processed: yt ftbfs with Python 3.11/3.12

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1056043 + ftbfs Bug #1056043 [src:yt] yt ftbfs with Python 3.12 (and cython 3.0.5) Added tag(s) ftbfs. > tags 1057864 + ftbfs Bug #1057864 [src:yt] yt ftbfs with Python 3.11/3.12 Added tag(s) ftbfs. > thanks Stopping processing here. Please

Processed: Python 3.12 tagging

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1057860 + ftbfs Bug #1057860 [src:breezy] breezy ftbfs with Python 3.12: Added tag(s) ftbfs. > tags 1055733 + ftbfs Bug #1055733 [src:pytango] pytango ftbfs with Python 3.12 (test failures) Added tag(s) ftbfs. > tags 1057863 + ftbfs Bug

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > owner -1 ! Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 'model.pdb' Owner recorded as Andrius Merkys . -- 1057951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057951 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Andrius Merkys
Control: owner -1 ! Hi, On 2023-12-11 14:04, Santiago Vila wrote: # Also happens in bookworm found 1057951 3.2.1+ds-6 thanks El 11/12/23 a las 12:06, Andrius Merkys escribió: I can reproduce this in clean chroot on barriere.d.o. Interestingly, FTBFS happens only when building on two threads,

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 13:07:24 + with message-id and subject line Bug#1056501: fixed in python-qrcode 7.4.2-4 has caused the Debian Bug report #1056501, regarding python-qrcode's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Processed: Re: [Debichem-devel] Bug#1057556: elpa: FTBFS: not enough slots available

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1057556 normal Bug #1057556 [src:elpa] elpa: FTBFS: not enough slots available Severity set to 'normal' from 'serious' > retitle 1057556 elpa: FTBFS unless machine has more than one vcore Bug #1057556 [src:elpa] elpa: FTBFS: not enough

Bug#1057556: [Debichem-devel] Bug#1057556: elpa: FTBFS: not enough slots available

2023-12-11 Thread Michael Banck
severity 1057556 normal retitle 1057556 elpa: FTBFS unless machine has more than one vcore thanks Hi Santiago, On Tue, Dec 05, 2023 at 11:05:01PM +0100, Santiago Vila wrote: > Package: src:elpa > Version: 2022.11.001-2 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild

Bug#1057967: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Diederik de Haas
On Monday, 11 December 2023 12:29:01 CET Salvatore Bonaccorso wrote: > I cannot test for the regression explicitly myself, but 6.1.67 was > released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for > non-range use""). Would you be in the position of do a test build with > that commit

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello Up to now 6.1.67 is not available for my configuration apt list | grep linux-image-6.1* linux-image-6.1.0-11-686-dbg/stable-security 6.1.38-4 i386 linux-image-6.1.0-11-686-pae-dbg/stable-security 6.1.38-4 i386 linux-image-6.1.0-11-686-pae-unsigned/stable-security 6.1.38-4 i386

Bug#1056501: marked as pending in python-qrcode

2023-12-11 Thread Bastian Germann
Control: tag -1 pending Hello, Bug #1056501 in python-qrcode 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#1056501 marked as pending in python-qrcode

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056501 [src:python-qrcode] python-qrcode's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Thank you Salvatore! Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso: > It still would be helpfull if you can get to the logs of the previous > boot. After booting back in the working kernel, do you have anything > sensible logged in the previous boot log? If so can you share that > please?

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Diederik de Haas
On Monday, 11 December 2023 13:01:58 CET Grand T wrote: > Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few > days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range > use." That patch ended up regressing Linux wireless support with deadlocks > in the IWD

Bug#1058032: python-grpc-tools: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: python-grpc-tools Version: 1.14.1-6 Severity: serious Tags: ftbfs sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-grpc-tools FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below.

Bug#1057967:

2023-12-11 Thread Jason Zarin
I think it highly likely that it's that wifi reversion noted up thread. On my system, wifi hangs (broadcom-sta-dkms) and causes network manager to hit 100% according to top. Problem not present in kernels 6.1.0-13&14 and back port 6.5.

Bug#1058031: pygame: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: pygame Version: 2.5.2-1 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pygame FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1056132: marked as done (skimage: FTBFS in testing and unstable)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 12:20:11 + with message-id and subject line Bug#1056132: fixed in skimage 0.22.0-3 has caused the Debian Bug report #1056132, regarding skimage: FTBFS in testing and unstable to be marked as done. This means that you claim that the problem has been dealt

Bug#1058024: marked as done (skimage tries to access the net during the build)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 12:20:11 + with message-id and subject line Bug#1058024: fixed in skimage 0.22.0-3 has caused the Debian Bug report #1058024, regarding skimage tries to access the net during the build to be marked as done. This means that you claim that the problem has

Bug#1058030: pyferret: b-d on python3-all-dev, but not built for all supported Python3 versions

2023-12-11 Thread Graham Inggs
Source: pyferret Version: 7.6.5-4 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Stephan Verbücheln
Hello everybody Unfortunately, I can confirm the same problems for 2014 Macbook Pro (Intel CPU and graphics). At first I thought the network problem was due to the proprietary Broadcom WLAN driver because network connectivity was the most obvious problem. However, the problems persisted after

Bug#1056516: marked as done (qstylizer's autopkg tests fail with Python 3.12)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 12:04:31 + with message-id and subject line Bug#1056516: fixed in qstylizer 0.2.2-2 has caused the Debian Bug report #1056516, regarding qstylizer's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Also happens in bookworm > found 1057951 3.2.1+ds-6 Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 'model.pdb' Marked as found in versions promod3/3.2.1+ds-6. > thanks Stopping processing here. Please contact me if you

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Santiago Vila
# Also happens in bookworm found 1057951 3.2.1+ds-6 thanks El 11/12/23 a las 12:06, Andrius Merkys escribió: I can reproduce this in clean chroot on barriere.d.o. Interestingly, FTBFS happens only when building on two threads, four thread build succeeds. I have a feeling that the test

Processed: your mail

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1057967 src:linux Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Added indication that 1057967 affects src:linux > notfound 1057967 linux/6.1.64-1 Bug #1057967 [src:linux]

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello For my case: Is that a surprise if the problem is that one? wifi: cfg80211: fix CQM for non-range use https://www.phoronix.com/news/Linux-6.6.6-Released Linux 6.6.6 is out with just a sole change for dealing with another headache: WiFi regressions. Linux 6.6.6 is out and its only

Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

2023-12-11 Thread Y
Package: qemu-guest-agent Version: 1:8.1.2+ds-1~bpo12+1 Severity: serious Justification: 6 Dear Maintainer, The problem arose after upgrading from bullseye to bookworm. All was OK on bullseye, but on bookworm qemu-ga refuse to start with following messages : 1702295113.963828: debug: disabling

Bug#1056425: marked as done (microsoft-authentication-extensions-for-python's autopkg tests fail with Python 3.12)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 11:49:01 + with message-id and subject line Bug#1056425: fixed in microsoft-authentication-extensions-for-python 1.1.0-1 has caused the Debian Bug report #1056425, regarding microsoft-authentication-extensions-for-python's autopkg tests fail with Python

Bug#1056516: marked as pending in qstylizer

2023-12-11 Thread Julian Gilbey
Control: tag -1 pending Hello, Bug #1056516 in qstylizer 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#1056516 marked as pending in qstylizer

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056516 [src:qstylizer] qstylizer's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058027: pybj: FTBFS with Python 3.12

2023-12-11 Thread Graham Inggs
Source: pybj Version: 0.2.6-1 Severity: serious Tags: ftbfs sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pybj FTBFS [1] with Python 3.12 as a supported version. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1057899: marked as done (libc++abi-18-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 11:34:29 + with message-id and subject line Bug#1057899: fixed in llvm-toolchain-snapshot 1:18~++20231211102647+75193b192ad9-1~exp1 has caused the Debian Bug report #1057899, regarding libc++abi-18-dev has an undeclared file conflict on

Processed: reassign 1057967 to src:linux

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1057967 src:linux 6.1.66-1 Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Bug reassigned from package 'linux-image-6.1.0-15-amd64' to 'src:linux'. No

Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable Added tag(s) moreinfo. -- 1057967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967 Debian Bug Tracking

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo Hi Kevin, On Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price wrote: > Package: linux-image-6.1.0-15-amd64 > Version: 6.1.66-1 > Severity: critical > Control: -1 notfound 6.1.64-1 > > When booting 6.1.0-15, my physical amd64/bookworm/gnome computer > misbehaves in

Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo Hi Steve, On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote: > Package: src:linux > Version: 6.1.66-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > I would have tried to report this from the 6.1.66 kernel but once a

Processed: Re: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1057969 [src:linux] linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230 Added tag(s) moreinfo. -- 1057969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057969 Debian Bug Tracking System Contact

Processed: Re: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed Bug #1057951 [src:promod3] promod3: FTBFS: No such file or directory: 'model.pdb' Added tag(s) confirmed. -- 1057951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057951 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1057951: [Debichem-devel] Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

2023-12-11 Thread Andrius Merkys
Control: tags -1 + confirmed Hi, On 2023-12-10 22:51, Santiago Vila wrote: Package: src:promod3 Version: 3.3.1+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build:

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

2023-12-11 Thread Santiago Vila
El 10/12/23 a las 23:31, tony mancill escribió: I'm not able to reproduce this locally, and the only potentially relevant difference I see between the AWS testbed and my local environment is that I am running Intel and the AWS system is AMD. Well spotted! Yes, I believe that could explain the

  1   2   >