Processed: Bug#1071931 marked as pending in libaacs

Processing control commands: > tag -1 pending Bug #1071931 [src:libaacs] libaacs: FTBFS against libgcrypt 1.11 Added tag(s) pending. -- 1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071931: marked as pending in libaacs

Control: tag -1 pending Hello, Bug #1071931 in libaacs 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: https://salsa.debian.org/multimedia-team/libaacs/-/commit/87e3cd8aeaa165624d531b27

Bug#1071861: plakativ: prepare for next python3-fitz version

Quoting Bastian Germann (2024-06-26 19:36:05) > Control: retitle -1 plakativ: autopkgtest fails with python3-fitz 1.24.x > Control: severity -1 serious > > Now the pymupdf version has been updated. Thank you! Unfortunately, with the changes and the new version I now get a segmentation fault in t

Bug#1074399: marked as done (libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl)

Your message dated Fri, 28 Jun 2024 22:21:43 + with message-id and subject line Bug#1074399: fixed in libcgi-application-plugin-authentication-perl 0.24+~cs0.5-2 has caused the Debian Bug report #1074399, regarding libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi

Bug#1074271: closing 1074271

close 1074271 thanks Rebuilt and re-uploaded for amd64 in version 1.4.3-6

Bug#1074399: marked as pending in libcgi-application-plugin-authentication-perl

Control: tag -1 pending Hello, Bug #1074399 in libcgi-application-plugin-authentication-perl 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: https://salsa.debian.org/perl-team/modules/

Processed: Bug#1074399 marked as pending in libcgi-application-plugin-authentication-perl

Processing control commands: > tag -1 pending Bug #1074399 [libcgi-application-plugin-authentication-perl] libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl Added tag(s) pending. -- 1074399: https://bugs.debia

Processed: closing 1074271

Processing commands for cont...@bugs.debian.org: > close 1074271 Bug #1074271 [src:amgcl] amgcl: needs rebuild for Python 3.12 as default Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1074271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: bug 1074399 is forwarded to https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2

Processing commands for cont...@bugs.debian.org: > forwarded 1074399 > https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2 Bug #1074399 [libcgi-application-plugin-authentication-perl] libcgi-application-plugin-authentication-perl: autopkgtest regression: lib

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

On Sun, Apr 28, 2024 at 06:50:30PM +0100, Alberto Bertogli wrote: I'm still trying to find a reasonable workaround. I found a workaround to fix the compilation issue, by detecting and not building the 64-bit variants when there is asm aliasing for the relevant functions. However, it is now

Bug#1074451: librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so

Package: librecoll39-dev Version: 1.39.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + recollcmd librecoll39-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/librecoll.so is co

Processed: librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so

Processing control commands: > affects -1 + recollcmd Bug #1074451 [librecoll39-dev] librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so Added indication that 1074451 affects recollcmd -- 1074451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074451 De

Bug#1074379: marked as done (wireplumber: Bluetooth profile switch crashes wireplumber)

Your message dated Fri, 28 Jun 2024 19:57:55 + with message-id and subject line Bug#1074379: fixed in wireplumber 0.5.5-1 has caused the Debian Bug report #1074379, regarding wireplumber: Bluetooth profile switch crashes wireplumber to be marked as done. This means that you claim that the pro

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

Your message dated Fri, 28 Jun 2024 19:57:43 + with message-id and subject line Bug#1073432: fixed in unyt 3.0.2-2 has caused the Debian Bug report #1073432, regarding unyt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 to be

Processed: tagging 1074431, tagging 1074430, tagging 1074429, tagging 1074426 ..., tagging 1074425 ...

Processing commands for cont...@bugs.debian.org: > tags 1074431 + upstream Bug #1074431 [src:arm-trusted-firmware] arm-trusted-firmware: CVE-2024-6287 CVE-2024-6285 Added tag(s) upstream. > tags 1074430 + upstream Bug #1074430 [src:adminer] adminer: CVE-2023-45196 CVE-2023-45195 Added tag(s) upst

Processed: Bug#1073432 marked as pending in unyt

Processing control commands: > tag -1 pending Bug #1073432 [src:unyt] unyt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1073432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073432 Debian Bug Tra

Bug#1073432: marked as pending in unyt

Control: tag -1 pending Hello, Bug #1073432 in unyt 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: https://salsa.debian.org/python-team/packages/unyt/-/commit/18123880f1fd8098ace0d7210

Bug#1073128: marked as done (clamav: unaligned access on armhf architecture)

Your message dated Fri, 28 Jun 2024 18:50:10 + with message-id and subject line Bug#1073128: fixed in clamav 1.3.1+dfsg-4 has caused the Debian Bug report #1073128, regarding clamav: unaligned access on armhf architecture to be marked as done. This means that you claim that the problem has be

Bug#1074351: rust-curve25519-dalek: RUSTSEC-2024-0344

Hi Jonas, On Thu, Jun 27, 2024 at 10:52:47PM +0200, Jonas Smedegaard wrote: > Quoting Salvatore Bonaccorso (2024-06-27 08:03:39) > > There is RUSTSEC-2024-0344 provided for rust-curve25519-dalek, can you > > have a look for unstable? > > > > https://rustsec.org/advisories/RUSTSEC-2024-0344.html >

Bug#1074448: corrosion: fails to build with rustc >= 1.79

Source: corrosion Version: 0.4.7-1 Severity: serious Tags: ftbfs upstream patch Justification: fails to build from source (but built successfully in the past) hi! rustc in version 1.79 and later doesn't allow dashes in lib names anymore. corrosion's test cases executed as part of the build and la

Bug#1071338: marked as done (python-numpysane: FTBFS: test/testlib_pywrap_GENERATED.c:24:10: fatal error: numpy/arrayobject.h: No such file or directory)

Your message dated Fri, 28 Jun 2024 18:37:02 + with message-id and subject line Bug#1071338: fixed in python-numpysane 0.41-5 has caused the Debian Bug report #1071338, regarding python-numpysane: FTBFS: test/testlib_pywrap_GENERATED.c:24:10: fatal error: numpy/arrayobject.h: No such file or

Bug#1064495: marked as done (sitecopy FTBFS: incompatible neon version)

Your message dated Fri, 28 Jun 2024 18:37:51 + with message-id and subject line Bug#1064495: fixed in sitecopy 1:0.16.6-13 has caused the Debian Bug report #1064495, regarding sitecopy FTBFS: incompatible neon version to be marked as done. This means that you claim that the problem has been d

Processed: Re: sitecopy FTBFS: incompatible neon version

Processing control commands: > tags -1 + patch Bug #1064495 [src:sitecopy] sitecopy FTBFS: incompatible neon version Added tag(s) patch. -- 1064495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1064495: sitecopy FTBFS: incompatible neon version

Control: tags -1 + patch [Helmut Grohne] > Apparently, sitecopy is incompatible with neon >= 0.33. This quite > definitely needs a sourceful upload of sitecopy. This seem to be the fix, already applied several times for new versions already: diff --git a/debian/patches/31_Fix-various-issues.diff

Bug#1069403: marked as done (halide: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1069403: fixed in halide 17.0.2-1 has caused the Debian Bug report #1069403, regarding halide: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means

Bug#1068138: marked as done (halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed))

Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1068138: fixed in halide 17.0.2-1 has caused the Debian Bug report #1068138, regarding halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed) to be marked as done. This means that you claim that the

Bug#1066057: marked as done (libhalide17-1-dev has an undeclared file conflict)

Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1066057: fixed in halide 17.0.2-1 has caused the Debian Bug report #1066057, regarding libhalide17-1-dev has an undeclared file conflict to be marked as done. This means that you claim that the problem has bee

Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

Hi, this bug seems not to have been seen in the reproducible-builds [1] or in the buildd [2] projects. The FTBFS is related to a failing test 9: qt.qpa.xcb: could not connect to display :99 9: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. 9: This a

Bug#1074442: freecad: FTBFS with Python 3.12 as default

Source: freecad Version: 0.21.2+dfsg1-4 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 freecad FTBFS with Python 3.12 as the default version [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducibl

Processed: forcibly merging 1069433 1069512

Processing commands for cont...@bugs.debian.org: > forcemerge 1069433 1069512 Bug #1069433 {Done: Samuel Thibault } [src:openmpi] gtg-trace: FTBFS on armhf: tests fail Bug #1069512 {Done: Samuel Thibault } [src:openmpi] python-escript: FTBFS on armhf: tests fail Removed indication that 1069512 a

Bug#1042221: marked as done (xraylib: FTBFS: dh_install: error: missing files, aborting)

Your message dated Fri, 28 Jun 2024 20:14:14 +0300 with message-id and subject line Fixed in unstable has caused the Debian Bug report #1042221, regarding xraylib: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt wit

Processed: llvm/llvmlite/numba

Processing commands for cont...@bugs.debian.org: > block 1068961 by 1050069 Bug #1068961 [src:llvm-toolchain-18] llvm-toolchain-18: block migration to testing: to many llvm-toolchain versions in testing 1068961 was not blocked by any bugs. 1068961 was not blocking any bugs. Added blocking bug(s)

Bug#1073828: libuim-data update fails due to undefined symbol

Control: tags -1 patch On 2024-06-19 "Gustavo R. Montesino" wrote: > Package: libuim-data > Version: 1:1.8.8-9.4 > Severity: serious > Justification: Policy 8.6 > Hello, > Can't upate libuim-data due to undefined symbol in uim-module-manager: > Configurando libuim-data (1:1.8.8-9.4) ... > uim-

Processed: Re: Bug#1073828: libuim-data update fails due to undefined symbol

Processing control commands: > tags -1 patch Bug #1073828 [libuim-data] libuim-data update fails due to undefined symbol Added tag(s) patch. -- 1073828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 1069512 src:openmpi Bug #1069512 [src:python-escript] python-escript: FTBFS on armhf: tests fail Bug reassigned from package 'src:python-escript' to 'src:openmpi'. No longer marked as found in versions python-escript/5.6-7. Ignoring reque

Processed: Fixed in experimental, and no longer RC since old binaries were removed

Processing commands for cont...@bugs.debian.org: > close 1068684 22~git20240513132534.e278a05+ds3-1 Bug #1068684 [src:bornagain] bornagain: FTBFS on many architectures Marked as fixed in versions bornagain/22~git20240513132534.e278a05+ds3-1. Bug #1068684 [src:bornagain] bornagain: FTBFS on many ar

Processed: bump severity of python 3.12 ftbfs bugs

Processing commands for cont...@bugs.debian.org: > severity 1067507 serious Bug #1067507 [src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12 Severity set to 'serious' from 'important' > severity 1067598 serious Bug #1067598 [src:wfuzz] wfuzz: FTBFS with Python 3.12 as default Severity

Bug#1074435: yade: FTBFS with Python 3.12 as default

Source: yade Version: 2024.02a-1 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 yade FTBFS with Python 3.12 as the default version [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/f

Bug#1058165: marked as done (itango: FTBFS: ModuleNotFoundError: No module named 'tango._tango')

Your message dated Fri, 28 Jun 2024 13:19:16 + with message-id and subject line Bug#1058165: fixed in itango 0.1.9+ds-1 has caused the Debian Bug report #1058165, regarding itango: FTBFS: ModuleNotFoundError: No module named 'tango._tango' to be marked as done. This means that you claim that

Processed: Re: Bug#1071894: closing 1071894

Processing commands for cont...@bugs.debian.org: > # adding for completeness, as this was actually fixed yesterday > fixed 1071894 0.7.4-5 Bug #1071894 {Done: Roland Mas } [src:stackview] stackview: FTBFS: unsatisfiable build-dependencies Marked as fixed in versions stackview/0.7.4-5. > thanks St

Bug#1071894: closing 1071894

close 1071894 0.7.10-1 thanks

Processed: closing 1071894

Processing commands for cont...@bugs.debian.org: > close 1071894 0.7.10-1 Bug #1071894 [src:stackview] stackview: FTBFS: unsatisfiable build-dependencies The source 'stackview' and version '0.7.10-1' do not appear to match any binary packages Marked as fixed in versions stackview/0.7.10-1. Bug #1

Bug#1074430: adminer: CVE-2023-45196 CVE-2023-45195

Source: adminer X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for adminer. CVE-2023-45196[0]: | Adminer and AdminerEvo allow an unauthenticated remote attacker to | cause a denial of service by connecting to an attacker-con

Bug#1066629: marked as done (ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration])

Your message dated Fri, 28 Jun 2024 11:29:48 + with message-id and subject line Bug#1066629: fixed in ucspi-tcp 1:0.88-9 has caused the Debian Bug report #1066629, regarding ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-decla

Processed: tag 1074265 as pending

Processing commands for cont...@bugs.debian.org: > tag 1074265 pending Bug #1074265 [libcgal-qt6-dev] libcgal-qt6-dev: missing Breaks+Replaces: libcgal-qt5-dev (<< 6) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074265: https://bugs.debi

Processed: Re: closing 1063190

Processing control commands: > found -1 5.2.1.13040+dfsg-2 Bug #1063190 {Done: Pierre-Elliott Bécue } [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t transition Marked as found in versions owncloud-client/5.2.1.13040+dfsg-2 and reopened. -- 1063190: https://bugs.debian.org/cgi

Bug#1063190: closing 1063190

Control: found -1 5.2.1.13040+dfsg-2 On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin wrote: On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott Bécue wrote: > close 1063190 > thanks Hi, Pierre-Elliott owncloud-client seems still not in testing because of #1063190. Missing version i

Bug#1073991: marked as done (ezurio-qcacld-2.0-dkms: module fails to build for Linux 6.9: wlan_hdd_hostapd.c:1574:9: error: too many arguments to function 'cfg80211_ch_switch_notify')

Your message dated Fri, 28 Jun 2024 10:24:25 + with message-id and subject line Bug#1073991: fixed in ezurio-qcacld-2.0-dkms 0.0~git20230623.2cd31b6-3 has caused the Debian Bug report #1073991, regarding ezurio-qcacld-2.0-dkms: module fails to build for Linux 6.9: wlan_hdd_hostapd.c:1574:9:

Bug#1074412: rust-apr:FTBFS:build failure（arguments to this function are incorrect）

Source: rust-apr Version: 0.1.9-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear rust-apr Maintainer, The package rust-apr build failed on arch riscv64,arm64,ppc64el and s490x caused by incorrect arguments

Bug#1074321: marked as done (createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’)

Your message dated Fri, 28 Jun 2024 09:49:29 + with message-id and subject line Bug#1074321: fixed in createrepo-c 0.17.3-5 has caused the Debian Bug report #1074321, regarding createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’ to be marked as done. This means that yo

Bug#1069488: parsinsert: FTBFS on armhf: make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1

Some further results on parsinsert: after rebuilding on all release architectures, it turned out the other affected platform was armel, in addition to armhf. This suggests possibly a regression introduced by time_t migration to 64-bit size. Or this could be something else I have no clue of yet.

Bug#1069378: marked as done (picom: FTBFS: Package xcb-dri3 was not found in the pkg-config search path)

Your message dated Fri, 28 Jun 2024 10:30:06 +0200 with message-id <42fc6f57-2ce7-a0da-3832-39f3ea64a...@debian.org> and subject line Re: Bug#1069378: picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option' has caused the Debian Bug report #1069378, regarding

Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb

Control: tag -1 -patch On Friday, 28 June 2024 09:55:24 CEST Michel Dänzer wrote: > > This is fixed in upstream commit 5ca85d75c05de9df7c3170122dfdb04bc795b43a > > ("dri: Fix BGR format exclusion"), which I attached for your convenience. > > Beware that this commit caused a regression on little e

Processed: Re: Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb

Processing control commands: > tag -1 -patch Bug #1072971 [mesa] mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb Removed tag(s) patch. -- 1072971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072971 Debian Bug Tracking Syste

Processed: Re: Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

Processing control commands: > reassign -1 src:qt6-base Bug #1073480 [libzstd-dev] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Bug reassigned from package 'libzstd-dev' to 'src:qt6-base'. No longer marked as found in versions libzstd/1.5.6+dfsg-1.

Processed: Re: Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

Processing control commands: > reassign -1 src:qt6-base Bug #1073480 [src:qt6-base] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Ignoring request to reassign bug #1073480 to the same package -- 1073480: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

control: reassign -1 src:qt6-base On Thu, Jun 27, 2024 at 11:01:44AM +0900, yokota wrote: > Hello, > > I think this bug is not a libzstd's bug but qt6-base's bug. > > Please check this QTBUG. > > [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static > > https://bugreports.qt.io/browse/QT

Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb

On 2024-06-28 00:28, Diederik de Haas wrote: > Control: tag -1 upstream, fixed-upstream patch > Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360 > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837 > > On 14 Jun 2024 13:36:54 +0200 Emilio Pozuelo Monfort