Processed: bug 1032104 is forwarded to https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u https://lore.kernel.org/regressions/480932026.4

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1032104 > https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u > >

Bug#1055729: marked as done (FTBFS: faad2 fails to build on i386, blocking DSA fix transition)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Nov 2023 07:49:07 + with message-id and subject line Bug#1055729: fixed in faad2 2.11.1-1 has caused the Debian Bug report #1055729, regarding FTBFS: faad2 fails to build on i386, blocking DSA fix transition to be marked as done. This means that you claim that the

Bug#1032104: Status update

2023-11-13 Thread Timothy Pearson
I have traced this bug to a missing memory barrier in the powerpc IPI handling code. io_uring uses task_work_add() to schedule I/O worker creation, which in turn issues an IPI, and when precise timing conditions are met the inconsistent state between the two CPU cores can lead to corruption of

Processed: your mail

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1032104 ! > https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read Changed Bug forwarded-to-address to '!

Bug#1055895: marked as done (rust-self-cell: RUSTSEC-2023-0070)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Nov 2023 04:04:15 + with message-id and subject line Bug#1055895: fixed in rust-self-cell 1.0.2-1 has caused the Debian Bug report #1055895, regarding rust-self-cell: RUSTSEC-2023-0070 to be marked as done. This means that you claim that the problem has been dealt

Bug#1055895: [Pkg-rust-maintainers] Bug#1055895: rust-self-cell: RUSTSEC-2023-0070

2023-11-13 Thread Peter Green
Please see https://rustsec.org/advisories/RUSTSEC-2023-0070.html I have read the upstream advisory and the linked bug report and while I don't fully understand the nitty gritty details my understanding of the issue is. * It was discovered that code (which was not marked as unsafe) could

Bug#1055540: marked as done (obs-time-source: FTBFS on several archs: linker input file not found)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 23:04:09 + with message-id and subject line Bug#1055540: fixed in obs-time-source 0.2-2 has caused the Debian Bug report #1055540, regarding obs-time-source: FTBFS on several archs: linker input file not found to be marked as done. This means that you

Bug#1055540: obs-time-source: FTBFS on several archs: linker input file not found

2023-11-13 Thread Eriberto Mota
Some tests were made over Debian, Alpine and Fedora and the issue causing the FTBFS is present only on Debian. The Meson finds the libobs, but fails to build using it. Maybe it can be something related to #998853. The upstream doesn't have a solution because he uses Alpine and the build is

Bug#1055901: [Pkg-raspi-maintainers] Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

2023-11-13 Thread Hilmar Preuße
On 11/13/23 23:20, Cyril Brulebois wrote: Hilmar Preusse (2023-11-13): Hi, the package fails to install on my system. I simply assumes that /boot/firmware is a mount point and fails if this is not the case. If /boot/firmware is expected to be a mount point the installer should have

Bug#1055901: [Pkg-raspi-maintainers] Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

2023-11-13 Thread Cyril Brulebois
Hi, Hilmar Preusse (2023-11-13): > Package: raspi-firmware > Version: 1:1.20231024+ds-1+rpt1 > Severity: serious > Justification: Policy 6.4 > > Hello, > > the package fails to install on my system. I simply assumes that > /boot/firmware is a > mount point and fails if this is not the case.

Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)

2023-11-13 Thread Hilmar Preuße
On 11/13/23 23:03, Debian Bug Tracking System wrote: Hi, Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1055901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055901. Here is the error message I get: hille@rasppi1:~ $ sudo apt -f install

Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

2023-11-13 Thread Hilmar Preusse
Package: raspi-firmware Version: 1:1.20231024+ds-1+rpt1 Severity: serious Justification: Policy 6.4 Hello, the package fails to install on my system. I simply assumes that /boot/firmware is a mount point and fails if this is not the case. If /boot/firmware is expected to be a mount point the

Processed: Fixed 1054750

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1054750 reuse/2.1.0-1 Bug #1054750 [src:reuse] reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1 Marked as fixed in versions reuse/2.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054750:

Bug#1055896: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?

2023-11-13 Thread Sebastian Ramacher
Source: cod-tools Version: 3.7.0+dfsg-1 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cod-tools=s390x=3.7.0%2Bdfsg-1%2Bb4=1699906136=0

Processed: severity of 1055895 is grave

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1055895 grave Bug #1055895 [src:rust-self-cell] rust-self-cell: RUSTSEC-2023-0070 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1055895:

Processed: severity of 1055880 is serious, tagging 1055880

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1055880 serious Bug #1055880 [kaidan] kaidan missing two dependencies Severity set to 'serious' from 'grave' > tags 1055880 + pending Bug #1055880 [kaidan] kaidan missing two dependencies Added tag(s) pending. > thanks Stopping

Bug#1055670: marked as done (fwknop-server: must Depends: apparmor-profiles-extra)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 19:19:24 + with message-id and subject line Bug#1055670: fixed in fwknop 2.6.10-19 has caused the Debian Bug report #1055670, regarding fwknop-server: must Depends: apparmor-profiles-extra to be marked as done. This means that you claim that the problem

Bug#1055783: marked as done (glib: FTBFS on armhf: test failure)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 18:35:15 + with message-id and subject line Bug#1055783: fixed in glib2.0 2.78.1-4 has caused the Debian Bug report #1055783, regarding glib: FTBFS on armhf: test failure to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1055892: sunpy: FTBFS in bookworm: leap-second file is expired.

2023-11-13 Thread Santiago Vila
Package: src:sunpy Version: 4.1.2-1 Severity: serious Tags: ftbfs bookworm upstream Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build. The error I got is the same in reproducible-builds:

Processed: transition: gdal

2023-11-13 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:gdal Bug #1055891 [release.debian.org] transition: gdal Added indication that 1055891 affects src:gdal > forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Bug #1055891 [release.debian.org] transition: gdal Set Bug

Processed: your mail

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1053004 5.1+ds-4+deb10u1 Bug #1053004 [src:phppgadmin] phppgadmin: CVE-2023-40619 The source 'phppgadmin' and version '5.1+ds-4+deb10u1' do not appear to match any binary packages Marked as fixed in versions phppgadmin/5.1+ds-4+deb10u1. >

Bug#1055154: marked as done (ugrep: FTBFS on mipse64el)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 14:38:15 + with message-id and subject line Bug#1055154: fixed in ugrep 4.3.2+dfsg-2 has caused the Debian Bug report #1055154, regarding ugrep: FTBFS on mipse64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1050854: Please push your changes to python-xarray

2023-11-13 Thread Alastair McKinstry
Hi Apologies I am swamped on this. Please go ahead and apply. Thanks Alastair On 13/11/2023 12:51, Andreas Tille wrote: Ping? I'd love to apply the patch from the bug report and push everything properly. If I do not hear from you I might consider mass-commiting all the releases you made

Bug#1054933: marked as done (yi: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 14:55:48 +0100 with message-id <169988374859.32117.508216297783495278.reportbug@localhost> and subject line yi: bug no longer found has caused the Debian Bug report #1054933, regarding yi: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa,

Processed: found 1055679 in 2.12-1, found 1055679 in 2.5-1, tagging 1055679, reassign 1036268 to src:mutter ...

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1055679 2.12-1 Bug #1055679 {Done: Jakub Ružička } [nvchecker,python3-nvchecker] nvchecker and python3-nvchecker have an undeclared file conflict on 56 files There is no source info for the package 'nvchecker' at version '2.12-1' with

Bug#1042609: sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError')

2023-11-13 Thread Dmitry Shachnev
Hi Faidon! On Mon, Nov 13, 2023 at 10:52:58AM +0200, Faidon Liambotis wrote: > Upstream commit 6f8de39¹, the only commit since 0.9.2, replaces > sphinx.util.SphinxParallelError by sphinx.util.DownloadFiles. > > I've verified that backporting this commit makes the package build > successfully in

Bug#1050854: Please push your changes to python-xarray

2023-11-13 Thread Andreas Tille
Ping? I'd love to apply the patch from the bug report and push everything properly. If I do not hear from you I might consider mass-commiting all the releases you made without pushing to the repository in one single commit and add what I'd like to commit. Kind regards Andreas. Am Tue, Nov

Bug#1055880: kaidan missing two dependencies

2023-11-13 Thread Pirate Praveen
Package: kaidan version: 0.9.1-1 severity: grave justification: fails to start Though fix is easy, missing dependencies are qml-module-org-kde-kquickimageeditor and qml-module-org-kde-kirigami-addons-labs-mobileform After installing these manually, kaidan starts as expected.

Bug#1055877: ndcube: FTBFS in bookworm: leap-second file is expired

2023-11-13 Thread Santiago Vila
A more simple approach would be to modify debian/rules so that (all) the tests are skipped after a certain date, as in the attached patch. Thanks.--- a/debian/rules +++ b/debian/rules @@ -7,6 +7,9 @@ export PYBUILD_TEST_ARGS=../../../ndcube export http_proxy=127.0.0.1:9 export HOME=$(shell

Bug#1055877: ndcube: FTBFS in bookworm: leap-second file is expired

2023-11-13 Thread Santiago Vila
Package: src:ndcube Version: 2.0.3-1 Severity: serious Tags: ftbfs bookworm patch upstream Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build with the following error: --- files =

Bug#1042356: marked as done (rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 12:04:08 + with message-id and subject line Bug#1042356: fixed in rapid-photo-downloader 0.9.34+repack-1 has caused the Debian Bug report #1042356, regarding rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25 to be marked as done.

Bug#1054684: marked as done (spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such file or directory)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 11:00:10 + with message-id and subject line Bug#1054684: fixed in spdlog 1:1.12.0+ds-1~exp has caused the Debian Bug report #1054684, regarding spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such file or directory to be marked as done.

Bug#1053774: marked as done (spdlog: need new upstream release 1.12 for catch2 v3)

2023-11-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Nov 2023 11:00:10 + with message-id and subject line Bug#1053774: fixed in spdlog 1:1.12.0+ds-1~exp has caused the Debian Bug report #1053774, regarding spdlog: need new upstream release 1.12 for catch2 v3 to be marked as done. This means that you claim that the

Processed: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed.

2023-11-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.15136.3-1 Bug #1055874 [src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed. Marked as fixed in versions

Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed.

2023-11-13 Thread Santiago Vila
Package: src:intel-graphics-compiler Version: 1.0.12504.6-1 Severity: serious Tags: ftbfs bookworm Control: close -1 1.0.15136.3-1 Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build with the following error: cd /<>/build/IGC/VectorCompiler/lib/BiF &&

Processed: 1053774 and 1054684 are pending

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1053774 + pending Bug #1053774 [src:spdlog] spdlog: need new upstream release 1.12 for catch2 v3 Added tag(s) pending. > tag 1054684 + pending Bug #1054684 [src:spdlog] spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such

Bug#1024079: uvloop FTBFS on IPV6-only buildds

2023-11-13 Thread dale
It looks like the test_aiohttp.py test is using hardcoded IPv4 addresses, causing the test to fail on hosts where no IPv4 interfaces are available. The attached patch should make the test agnostic to IP version. Best regards, Dale Richards aiohttp-test-IPv6-fix.patch Description: Binary data

Bug#1042609: sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError')

2023-11-13 Thread Faidon Liambotis
Hi, This is now RC, which means sphinxcontrib-mermaid has been marked for autoremoval, including its reverse dependencies (one of which I maintain). On Sun, Jul 30, 2023 at 08:30:07PM +0200, Lucas Nussbaum wrote: > sphinxcontrib-mermaid fails to build with Sphinx 7.1 and docutils 0.20, both >

Processed: unarchive

2023-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 993014 Bug #993014 {Done: Michael Tokarev } [src:cifs-utils] cifs-utils non-parallel FTBFS Unarchived Bug 993014 > tags 993014 + bullseye Bug #993014 {Done: Michael Tokarev } [src:cifs-utils] cifs-utils non-parallel FTBFS Added tag(s)