Bug#1056821: marked as done (music: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Dec 2023 01:50:32 + with message-id and subject line Bug#1056821: fixed in music 1.2.1-0.1 has caused the Debian Bug report #1056821, regarding music: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1054801: marked as done (music: FTBFS: dh_install: error: missing files, aborting)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Dec 2023 01:50:32 + with message-id and subject line Bug#1054801: fixed in music 1.2.1-0.1 has caused the Debian Bug report #1054801, regarding music: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem

Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-27 Thread Drew Parsons
Hi Alistair, given the complexity around hacking openmpi to accommodate placing the mod files under /usr/include, I'm starting to wonder whether it's the best way of resolving Bug#1058526 in the first place. I did it bit of background reading on the fortran mod files. There's a fair bit of

Bug#1058245: marked as done (libportal: FTBFS: dh_auto_test regression with python3-dbusmock (>= 0.30.0-2))

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 21:20:29 + with message-id and subject line Bug#1058245: fixed in libportal 0.7.1-4 has caused the Debian Bug report #1058245, regarding libportal: FTBFS: dh_auto_test regression with python3-dbusmock (>= 0.30.0-2) to be marked as done. This means that

Bug#1059484: rasdaemon: autopkgtest failure: cannot access '/var/lib/rasdaemon/ras-mc_event.db'

2023-12-27 Thread Taihsiang Ho (tai271828)
Hi Paul, Thanks for reporting the issue. I will take a look. -tai On Tue, Dec 26, 2023 at 7:09 PM Paul Gevers wrote: > > Source: rasdaemon > Version: 0.8.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainer(s), > > You recently added an

Bug#1053825: Screensaver with only blank does not work after suspend

2023-12-27 Thread Klaus Ethgen
Hi Salvatore, Am Mi den 27. Dez 2023 um 21:24 schrieb Salvatore Bonaccorso: > I do realize, but given we have nobody else reporting similar > behaviour we need to rely on you bisecting the breaking change so it > might be reported upstream. But that said, in meanwhile we have > 6.6.8-1 uploaded

Bug#1053825: Screensaver with only blank does not work after suspend

2023-12-27 Thread Salvatore Bonaccorso
Hi Klaus, On Sat, Oct 21, 2023 at 08:34:55AM +0100, Klaus Ethgen wrote: > Hi, > > Am Do den 19. Okt 2023 um 20:46 schrieb Salvatore Bonaccorso: > > On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > > > Package: src:linux > > > Version: 6.5.6-1 > > > Severity: critical > > > Tags:

Bug#1056081: marked as done (fife: FTBFS: boost1.83 transition)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 19:50:03 + with message-id and subject line Bug#1056081: fixed in fife 0.4.2-6 has caused the Debian Bug report #1056081, regarding fife: FTBFS: boost1.83 transition to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1059334: marked as done (python-bytecode fails it's autopkg tests)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 19:21:14 + with message-id and subject line Bug#1059334: fixed in python-bytecode 0.15.1-3 has caused the Debian Bug report #1059334, regarding python-bytecode fails it's autopkg tests to be marked as done. This means that you claim that the problem has

Bug#1059334: marked as pending in python-bytecode

2023-12-27 Thread Julian Gilbey
Control: tag -1 pending Hello, Bug #1059334 in python-bytecode 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#1059334 marked as pending in python-bytecode

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

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

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 18:49:39 + with message-id and subject line Bug#1056542: fixed in xlsxwriter 3.1.9-1 has caused the Debian Bug report #1056542, regarding xlsxwriter's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

Processed: Bug#1056542 marked as pending in xlsxwriter

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

Bug#1056542: marked as pending in xlsxwriter

2023-12-27 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #1056542 in xlsxwriter 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#997224: marked as done (btag: FTBFS: InteractiveTagger.cpp:201:34: error: ‘bool TagLib::String::isNull() const’ is deprecated [-Werror=deprecated-declarations])

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 17:34:45 + with message-id and subject line Bug#997224: fixed in btag 1.4.1-0.1 has caused the Debian Bug report #997224, regarding btag: FTBFS: InteractiveTagger.cpp:201:34: error: ‘bool TagLib::String::isNull() const’ is deprecated

Bug#1057446: marked as done (evdi-dkms: module build fails for Linux 6.6: evdi_fb.c:421:23: error: 'FBINFO_DEFAULT' undeclared)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 17:34:53 + with message-id and subject line Bug#1057446: fixed in evdi 1.14.0+dfsg-3 has caused the Debian Bug report #1057446, regarding evdi-dkms: module build fails for Linux 6.6: evdi_fb.c:421:23: error: 'FBINFO_DEFAULT' undeclared to be marked as

Bug#1056805: marked as done (healpy: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 17:35:23 + with message-id and subject line Bug#1056805: fixed in healpy 1.16.6-1 has caused the Debian Bug report #1056805, regarding healpy: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1056843: marked as done (pymssql: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 17:20:05 + with message-id and subject line Bug#1056843: fixed in pymssql 2.2.11-1 has caused the Debian Bug report #1056843, regarding pymssql: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1059525: linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD

2023-12-27 Thread .
Package: src:linux Version: 6.1.67-1 Severity: serious X-Debbugs-Cc: yelcnce01w76dbotr...@gmail.com Dear Maintainer, * What led up to the situation? I started Debian 12 on an Intel NUC with Crucial P5 Plus NVME and noticed that Secure Boot is not active, only if an NVME is installed. When the

Bug#1056792: marked as done (bitshuffle: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 13:51:51 +0100 (CET) with message-id <2028135726.10247290.1703681511851.javamail.zim...@synchrotron-soleil.fr> and subject line bitshuffle: ftbfs with cython 3.0.x has caused the Debian Bug report #1056792, regarding bitshuffle: ftbfs with cython 3.0.x to be

Bug#1056082: marked as done (field3d: FTBFS: boost1.83 transition)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 12:49:45 + with message-id and subject line Bug#1056082: fixed in field3d 1.7.3-4 has caused the Debian Bug report #1056082, regarding field3d: FTBFS: boost1.83 transition to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 1058132, bug 1058132 is forwarded to https://github.com/mitogen-hq/mitogen/issues/1033

2023-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058132 + upstream Bug #1058132 [src:python-mitogen] python-mitogen: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) upstream. > forwarded 1058132 https://github.com/mitogen-hq/mitogen/issues/1033 Bug #1058132

Bug#1056862: marked as done (python-line-profiler: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 11:05:24 + with message-id and subject line Bug#1056862: fixed in python-line-profiler 4.1.2-1 has caused the Debian Bug report #1056862, regarding python-line-profiler: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the

Bug#1055715: marked as done (python-line-profiler ftbfs with Python 3.12)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 11:05:24 + with message-id and subject line Bug#1055715: fixed in python-line-profiler 4.1.2-1 has caused the Debian Bug report #1055715, regarding python-line-profiler ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem

Bug#1056043: marked as done (yt ftbfs with Python 3.12 (and cython 3.0.5))

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 10:50:34 + with message-id and subject line Bug#1056043: fixed in yt 4.3.0-1 has caused the Debian Bug report #1056043, regarding yt ftbfs with Python 3.12 (and cython 3.0.5) to be marked as done. This means that you claim that the problem has been dealt

Bug#1057864: marked as done (yt ftbfs with Python 3.11/3.12)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 10:50:34 + with message-id and subject line Bug#1057864: fixed in yt 4.3.0-1 has caused the Debian Bug report #1057864, regarding yt ftbfs with Python 3.11/3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1056896: marked as done (yt: ftbfs with cython 3.0.x)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 10:50:34 + with message-id and subject line Bug#1056896: fixed in yt 4.3.0-1 has caused the Debian Bug report #1056896, regarding yt: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1057451: marked as done (rust-ahash: autopkgtests failing)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 09:19:24 + with message-id and subject line Bug#1057451: fixed in rust-ahash 0.8.5-4 has caused the Debian Bug report #1057451, regarding rust-ahash: autopkgtests failing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-27 Thread Drew Parsons
On 2023-12-27 09:51, Alastair McKinstry wrote: On 27/12/2023 08:45, Drew Parsons wrote: ... I guess the problem must be the common files from openmpi-common in /usr/share/openmpi/. They're not actually arch-independent.  Do mpif90.openmpi and the other components actively read them at

Bug#1058337: marked as done (dirty-equals: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

2023-12-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Dec 2023 09:04:00 + with message-id and subject line Bug#1058337: fixed in dirty-equals 0.7.0-2 has caused the Debian Bug report #1058337, regarding dirty-equals: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 to

Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-27 Thread Alastair McKinstry
On 27/12/2023 08:45, Drew Parsons wrote: On 2023-12-26 12:45, Drew Parsons wrote: I can manually reproduce the error trivially on an arm64 chroot (amdahl.debian.org).  Copying hello.f90 from openmpi's debian/tests and manually running   mpif90 -o hello hello.f90 reproduces the error

Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)

2023-12-27 Thread Drew Parsons
On 2023-12-26 12:45, Drew Parsons wrote: I can manually reproduce the error trivially on an arm64 chroot (amdahl.debian.org). Copying hello.f90 from openmpi's debian/tests and manually running mpif90 -o hello hello.f90 reproduces the error reference to the x86_64 include path on the arm64