Bug#1018448: marked as done (pynn: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Tue, 18 Feb 2025 07:50:53 + with message-id and subject line Bug#1018448: fixed in pynn 0.10.1-4 has caused the Debian Bug report #1018448, regarding pynn: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that the prob

Bug#1096209: marked as done (ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory)

Your message dated Tue, 18 Feb 2025 06:06:40 +0100 with message-id <0810c995-7550-4f34-b5cc-296849878...@sprickerhof.de> and subject line Close has caused the Debian Bug report #1096209, regarding ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory to be marked as d

Bug#1069410: efitools: FTBFS on arm64: make[1]: *** [Make.rules:130: HelloWorld-signed.efi] Error 1

Source: efitools Followup-For: Bug #1069410 Hi Gianfranco, > Hello, I found a patch in Ubuntu archive, unfortunately the patch is > really huge, and I'm not confident to just upload it because > it also drops some support. > > I'm attaching the diff file. Thanks for the patch. I have checked th

Bug#1097128: halide: FTBFS on i386: clang++-19: error: unable to execute command: Aborted

On Mon, Feb 17, 2025 at 8:31 PM Lucas Nussbaum wrote: > > Source: halide > Version: 19.0.0-5 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-2025-02-15 ftbfs-trixie > > Hi, Hi. > During a rebuild of all packages in sid, this package f

Bug#1096207: libcap2-bin: File conflict upgrading from to 1:2.73-2

Thanks Christian for fixing this quickly! This may help to prevent similar issues in the future: https://salsa.debian.org/debian/libcap2/-/merge_requests/2

Bug#1096240: marked as done (deepin-movie-reborn: FTBFS: playlist_model.cpp:202:21: error: ‘DGuiApplicationHelper’ has not been declared)

Your message dated Tue, 18 Feb 2025 00:20:24 + with message-id and subject line Bug#1096240: fixed in deepin-movie-reborn 5.15.10-1 has caused the Debian Bug report #1096240, regarding deepin-movie-reborn: FTBFS: playlist_model.cpp:202:21: error: ‘DGuiApplicationHelper’ has not been declared

Processed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987009

Processing commands for cont...@bugs.debian.org: > severity 987009 normal Bug #987009 [courier-authlib] courier-authlib: the purported fix for #984810 breaks maildrop "delivery mode" Severity set to 'normal' from 'critical' > -- Stopping processing here. Please contact me if you need assistance.

Bug#987009: courier-authlib: the purported fix for #984810 breaks maildrop "delivery mode"

Control: serverity -1 normal Flavio, I have just taken over maintenance of the courier-authlib and maildrop packages. I am in the process of wrapping my mind around all the open bug reports and the best way to deal with them. I am not yet sure how I want to deal with this bug, but first I wa

Processed: affects 1095286

Processing commands for cont...@bugs.debian.org: > affects 1095286 src:pcre2 Bug #1095286 [src:mariadb] mariadb: FTBFS with pcre2 10.45 due to incorrect case-insensitive regex test Added indication that 1095286 affects src:pcre2 > thanks Stopping processing here. Please contact me if you need as

Bug#1086097: marked as done (Replace obsolete Build-Depends: libidn11-dev with libidn-dev)

Your message dated Mon, 17 Feb 2025 23:19:31 + with message-id and subject line Bug#1086097: fixed in courier-authlib 0.72.3-1 has caused the Debian Bug report #1086097, regarding Replace obsolete Build-Depends: libidn11-dev with libidn-dev to be marked as done. This means that you claim that

Processed: block 1060427 with 1095915

Processing commands for cont...@bugs.debian.org: > block 1060427 with 1095915 Bug #1060427 [python3-appdirs] python3-appdirs: Do not release with trixie 1060427 was blocked by: 1063816 1067962 1067963 1067964 1067965 1067967 1067968 1067969 1067970 1067971 1067972 1067973 1067974 1067975 1067976

Processed: Bug#1095286 marked as pending in mariadb

Processing control commands: > tag -1 pending Bug #1095286 [src:mariadb] mariadb: FTBFS with pcre2 10.45 due to incorrect case-insensitive regex test Ignoring request to alter tags of bug #1095286 to the same tags previously set -- 1095286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095

Bug#1018312: marked as done (bcbio: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Mon, 17 Feb 2025 22:49:55 + with message-id and subject line Bug#1018312: fixed in bcbio 1.2.9-3 has caused the Debian Bug report #1018312, regarding bcbio: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that the pro

Bug#1095286: marked as pending in mariadb

Control: tag -1 pending Hello, Bug #1095286 in mariadb 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/mariadb-team/mariadb-server/-/commit/661664bffdee368f4d05

Processed: bug 1097513 is forwarded to https://github.com/urcu/userspace-rcu/commit/19ae4fc7cb4ac65025778a71352ebe69478ee2ea ...

Processing commands for cont...@bugs.debian.org: > forwarded 1097513 > https://github.com/urcu/userspace-rcu/commit/19ae4fc7cb4ac65025778a71352ebe69478ee2ea Bug #1097513 [liburcu-dev] urcu/uatomic/generic.h:422:24: error: implicit declaration of function ‘abort’ Changed Bug forwarded-to-address

Bug#1061185: apt-verify: unsupportable

On Mon, Feb 17, 2025 at 5:24 PM Simon Josefsson wrote: > I don't understand this -- why is it a RC bug if the apt maintainers > declare a Conflicts with a package? Where in the debian policies do you > find support for that view? apt is Priority: required. It is impossible to install apt-verify

Bug#1061185: apt-verify: unsupportable

Jeremy Bícha writes: > Control: severity -1 serious > > On Mon, Feb 17, 2025 at 5:10 PM Simon Josefsson wrote: >> >> severity 1061185 important >> thanks >> >> I'm downgrading this due to lack of explanation what is the 'serious' >> severity level problem. >> >> /Simon >> >> Simon Josefsson wri

Bug#1094034: marked as done (todoist-api-python: FTBFS: rm: cannot remove 'debian/*/usr/lib/*/*/LICENSE': No such file or directory)

Your message dated Mon, 17 Feb 2025 22:21:44 + with message-id and subject line Bug#1094034: fixed in todoist-api-python 2.1.7-2 has caused the Debian Bug report #1094034, regarding todoist-api-python: FTBFS: rm: cannot remove 'debian/*/usr/lib/*/*/LICENSE': No such file or directory to be ma

Processed: Re: apt-verify: unsupportable

Processing control commands: > severity -1 serious Bug #1061185 [src:apt-verify] apt-verify: unsupportable Severity set to 'serious' from 'important' -- 1061185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1061185: apt-verify: unsupportable

severity 1061185 important thanks I'm downgrading this due to lack of explanation what is the 'serious' severity level problem. /Simon Simon Josefsson writes: > Hi! You re-opened this ITP bug and changed the title to 'apt-verify: > unsupportable' and made it a RC bug. It is not clear to me w

Processed: Re: apt-verify: unsupportable

Processing commands for cont...@bugs.debian.org: > severity 1061185 important Bug #1061185 [src:apt-verify] apt-verify: unsupportable Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061185: https://bugs.debian.org/cgi-bi

Bug#1096235: marked as done (deepin-terminal: FTBFS: tabbar.cpp:631:31: error: invalid use of incomplete type ‘class QMimeData’)

Your message dated Mon, 17 Feb 2025 22:06:41 + with message-id and subject line Bug#1096235: fixed in deepin-terminal 5.9.51+dfsg-1 has caused the Debian Bug report #1096235, regarding deepin-terminal: FTBFS: tabbar.cpp:631:31: error: invalid use of incomplete type ‘class QMimeData’ to be mar

Processed: Re: bcbio: Workflows not ready for non-developers to depend on.

Processing control commands: > severity -1 serious Bug #928076 [src:bcbio] bcbio: Workflows not ready for non-developers to depend on. Severity set to 'serious' from 'important' -- 928076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928076 Debian Bug Tracking System Contact ow...@bugs.deb

Processed: Reopen

Processing control commands: > reopen -1 Bug #1096209 {Done: Christian Kastner } [src:ros-opencv-apps] ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Bug#1096209: Reopen

Control: reopen -1 Apologies, I had a typo in my bug number. Best, Christian

Bug#1090984: opensm: fails to build for arch:all

On Mon, 17 Feb 2025 19:50:22 +0100 Michael Biebl wrote: [...] > I'm not the maintainer of opensm, but I've made an NMU to DELAYED/14 > with the attached patch which fixes this issue. [...] Thank you so much! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! .

Processed: fixed 1063530 in 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4

Processing commands for cont...@bugs.debian.org: > fixed 1063530 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4 Bug #1063530 [src:node-undici] node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1 Marked as fixed in versions node-undici/5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4. > thanks Stopping processing here.

Bug#1096209: marked as done (ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory)

Your message dated Mon, 17 Feb 2025 21:37:03 + with message-id and subject line Bug#1096209: fixed in libcap2 1:2.73-3 has caused the Debian Bug report #1096209, regarding ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory to be marked as done. This means tha

Bug#1096255: marked as done (deepin-image-viewer: FTBFS: main.cpp:41:24: error: ‘QDir’ has not been declared)

Your message dated Mon, 17 Feb 2025 21:35:37 + with message-id and subject line Bug#1096255: fixed in deepin-image-viewer 5.8.2-4 has caused the Debian Bug report #1096255, regarding deepin-image-viewer: FTBFS: main.cpp:41:24: error: ‘QDir’ has not been declared to be marked as done. This me

Bug#1096207: marked as done (libcap2-bin: File conflict upgrading from 1:2.66-5+b1 to 1:2.73-2)

Your message dated Mon, 17 Feb 2025 21:37:03 + with message-id and subject line Bug#1096207: fixed in libcap2 1:2.73-3 has caused the Debian Bug report #1096207, regarding libcap2-bin: File conflict upgrading from 1:2.66-5+b1 to 1:2.73-2 to be marked as done. This means that you claim that th

Bug#1098217: singularity: doesn't work with Numpy 2

Package: singularity Version: 1.0.0-1 Severity: grave On systems with Numpy 2 installed, singularity crashes with the following exception:     AttributeError: `np.cast` was removed in the NumPy 2.0 release. Use `np.asarray(arr, dtype=dtype)` instead. Apparently, it relies on `np.cast', whic

Bug#1096247: marked as done (amberol: FTBFS: build-dependency not installable: librust-ashpd-0.9+gtk4-dev)

Your message dated Mon, 17 Feb 2025 16:19:30 -0500 with message-id and subject line Re: amberol: FTBFS: build-dependency not installable: librust-ashpd-0.9+gtk4-dev has caused the Debian Bug report #1096247, regarding amberol: FTBFS: build-dependency not installable: librust-ashpd-0.9+gtk4-dev

Bug#1092441: FTBFS with Python 3.13: error: ‘PyEval_CallObject’ was not declared in this scope

Any chance we can cherry-pick the fix for this? https://github.com/zeroc-ice/ice/pull/2910/files While the upstream issue report is tied to the milestone for the next release, there's no indication when that might be, and the previous release was quite awhile ago. I'm inquiring as this is blo

Bug#1096248: marked as done (deepin-album: FTBFS: application.cpp:160:14: error: ‘QProcessEnvironment’ has not been declared)

Your message dated Mon, 17 Feb 2025 21:19:31 + with message-id and subject line Bug#1096248: fixed in deepin-album 5.9.1+dfsg-3 has caused the Debian Bug report #1096248, regarding deepin-album: FTBFS: application.cpp:160:14: error: ‘QProcessEnvironment’ has not been declared to be marked as

Processed: severity of 1096207 is serious

Processing commands for cont...@bugs.debian.org: > severity 1096207 serious Bug #1096207 [libcap2-bin] libcap2-bin: File conflict upgrading from 1:2.66-5+b1 to 1:2.73-2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 109

Processed: closing 1096233

Processing commands for cont...@bugs.debian.org: > close 1096233 Bug #1096233 [src:mrpt] mrpt: FTBFS: /usr/bin/ld: cannot find -lopencv_barcode: No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1096233: https://bugs.deb

Bug#1096233: closing 1096233

close 1096233 thanks Invalid due to the opencv transition (see #1096209)

Processed: bug 1096245 is forwarded to https://github.com/radiator-software/p5-net-ssleay/issues/513

Processing commands for cont...@bugs.debian.org: > forwarded 1096245 > https://github.com/radiator-software/p5-net-ssleay/issues/513 Bug #1096245 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Set Bug forwarded-to-addres

Processed: bug 1096245 is not forwarded

Processing commands for cont...@bugs.debian.org: > notforwarded 1096245 Bug #1096245 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if y

Processed: tagging 1096245

Processing commands for cont...@bugs.debian.org: > tags 1096245 + upstream Bug #1096245 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Ignoring request to alter tags of bug #1096245 to the same tags previously set > thank

Processed: tagging 1096245 ...

Processing commands for cont...@bugs.debian.org: > tags 1096245 + confirmed upstream Bug #1096245 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) upstream and confirmed. > forwarded 1096245 > https://github.c

Bug#1096242: golang-k8s-kube-openapi: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 k8s.io/kube-openapi/cmd/openapi-gen [...] k8s.io/kube-openapi/test/integration/testutil returned

Source: golang-k8s-kube-openapi Version: 0.0~git20231214.ab13479-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefu

Bug#1095286: marked as pending in mariadb

Control: tag -1 pending Hello, Bug #1095286 in mariadb 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/mariadb-team/mariadb-server/-/commit/661664bffdee368f4d05

Processed: Bug#1095286 marked as pending in mariadb

Processing control commands: > tag -1 pending Bug #1095286 [src:mariadb] mariadb: FTBFS with pcre2 10.45 due to incorrect case-insensitive regex test Ignoring request to alter tags of bug #1095286 to the same tags previously set -- 1095286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095

Bug#1096259: gnumach: FTBFS: configure: error: failed to patch using `config.status.dep.patch'.

Source: gnumach Version: 2:1.8+git20241227-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > yes > checking

Processed: bug 1078617 is forwarded to https://github.com/fsouza/go-dockerclient/issues/1112

Processing commands for cont...@bugs.debian.org: > forwarded 1078617 https://github.com/fsouza/go-dockerclient/issues/1112 Bug #1078617 [src:golang-github-fsouza-go-dockerclient] golang-github-fsouza-go-dockerclient: will FTBFS during trixie support period Set Bug forwarded-to-address to 'https:

Bug#1095356: marked as done (mdp: FTBFS: E AttributeError: `np.longfloat` was removed in the NumPy 2.0 release.)

Your message dated Mon, 17 Feb 2025 18:52:44 + with message-id and subject line Bug#1095356: fixed in mdp 3.6-10 has caused the Debian Bug report #1095356, regarding mdp: FTBFS: E AttributeError: `np.longfloat` was removed in the NumPy 2.0 release. to be marked as done. This means that you

Bug#1095026: marked as done (mdp: autopkgtests fail with numpy 2.x)

Your message dated Mon, 17 Feb 2025 18:52:44 + with message-id and subject line Bug#1095026: fixed in mdp 3.6-10 has caused the Debian Bug report #1095026, regarding mdp: autopkgtests fail with numpy 2.x to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1090984: opensm: fails to build for arch:all

Am 17.02.25 um 15:08 schrieb Francesco Poli: On Sun, 19 Jan 2025 12:41:05 +0100 Francesco Poli wrote: On Sat, 21 Dec 2024 17:37:24 +0100 Francesco Poli (wintermute) wrote: Dear Debian HPC Team, I am worried by the long absence of package 'opensm' from Debian testing. [...] Please fix the is

Bug#1095685: Weekly Build now working again.

This problem appears to be fixed in Debian GNU/Linux testing "Trixie" - Official Snapshot amd64 NETINST with firmware 20250217-04:57 Thank you. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

Processed: bug 1097513 is forwarded to https://bugs.lttng.org/issues/1420

Processing commands for cont...@bugs.debian.org: > forwarded 1097513 https://bugs.lttng.org/issues/1420 Bug #1097513 [liburcu-dev] urcu/uatomic/generic.h:422:24: error: implicit declaration of function ‘abort’ Set Bug forwarded-to-address to 'https://bugs.lttng.org/issues/1420'. > thanks Stopping

Bug#1097324: yadifa: FTBFS on i386: src/file_mtime_set.c:103:15: error: 'ptr_treemap_node_t' {aka 'struct ptr_treemap_node_s'} has no member named 'value_s64'; did you mean 'value_s32'?

Source: yadifa Version: 3.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so t

Bug#1093353: marked as done (python-mne: FTBFS: NumPy 2.0 AttributeError and other issues)

Your message dated Mon, 17 Feb 2025 18:06:59 + with message-id and subject line Bug#1093353: fixed in python-mne 1.9.0-1 has caused the Debian Bug report #1093353, regarding python-mne: FTBFS: NumPy 2.0 AttributeError and other issues to be marked as done. This means that you claim that the p

Bug#1078617: marked as done (golang-github-fsouza-go-dockerclient: will FTBFS during trixie support period)

Your message dated Mon, 17 Feb 2025 18:34:29 + with message-id and subject line Bug#1078617: fixed in golang-github-fsouza-go-dockerclient 1.12.0-2 has caused the Debian Bug report #1078617, regarding golang-github-fsouza-go-dockerclient: will FTBFS during trixie support period to be marked

Bug#1097325: marked as done (supermin: FTBFS on i386: build-dependency not installable: linux-image-686-pae)

Your message dated Mon, 17 Feb 2025 19:25:08 +0100 with message-id <878qq4l98b@msgid.hilluzination.de> and subject line Re: Bug#1097325: supermin: FTBFS on i386: build-dependency not installable: linux-image-686-pae has caused the Debian Bug report #1097325, regarding supermin: FTBFS on i386:

Bug#1093489: Useless in Debian

Hi David, I appreciate your attempt to clean up the set of PHP packages. I just wonder in this specific case whether the new version released less than one year ago: Current Release 1.1.4 (stable) was released on 2024-03-10 by ashnazg qualifies as '“This package is not maintained” [upstream

Processed: Re: Bug#1097513: urcu/uatomic/generic.h:422:24: error: implicit declaration of function ‘abort’

Processing control commands: > severity -1 serious Bug #1097513 [liburcu-dev] urcu/uatomic/generic.h:422:24: error: implicit declaration of function ‘abort’ Severity set to 'serious' from 'important' -- 1097513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097513 Debian Bug Tracking Syste

Bug#1095760: marked as done (ruby-state-machines-activerecord: uninitialized constant Minitest::Reporters::BaseReporter::MiniTest (NameError))

Your message dated Mon, 17 Feb 2025 14:43:52 + with message-id and subject line Bug#1095760: fixed in ruby-state-machines-activerecord 0.9.0-1 has caused the Debian Bug report #1095760, regarding ruby-state-machines-activerecord: uninitialized constant Minitest::Reporters::BaseReporter::MiniT

Bug#965067: googler: "No results"

Package: googler Version: 4.3.13-1 Followup-For: Bug #965067 This issue has returned and it doesn't look like googler works at all in trixie right now. wondering if there are any alternatives out there. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (

Bug#1097326: pocl: FTBFS on i386: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: pocl Version: 6.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so this

Bug#1097325: supermin: FTBFS on i386: build-dependency not installable: linux-image-686-pae

Source: supermin Version: 5.2.2-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so

Bug#1097134: meep: FTBFS on i386: make[5]: *** [Makefile:1090: test-suite.log] Error 1

Source: meep Version: 1.25.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so th

Bug#1097135: cssc: FTBFS on i386: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Source: cssc Version: 1.4.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so thi

Bug#1097132: crun: FTBFS on i386: build-dependency not installable: libcriu-dev

Source: crun Version: 1.19.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, so th

Bug#1097133: haskell-language-python: FTBFS on i386: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:170: build-haddock-stamp] Error 251

Source: haskell-language-python Version: 0.5.8-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packa

Bug#1097129: haskell-copilot-c99: FTBFS on i386: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25

Source: haskell-copilot-c99 Version: 4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on

Bug#1097131: gocryptfs: FTBFS on i386: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/rfjakob/gocryptfs [...]

Source: gocryptfs Version: 2.5.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386, s

Bug#1097127: cppgir: FTBFS on i386: dh_auto_test: error: cd obj-i686-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

Source: cppgir Version: 2.0+git20240928.c8bb1c6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary pack

Bug#1097125: ibm-3270: FTBFS on i386: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Source: ibm-3270 Version: 4.3ga10-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-2025-02-15 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages on i386,

Bug#1096236: marked as done (warp: FTBFS: unsatisfiable build-dependencies: librust-ashpd-0.9+default-dev (>= 0.9.0-~~), librust-ashpd-0.9+gtk4-dev (>= 0.9.0-~~), librust-gvdb-0.7+default-dev, librust

Your message dated Mon, 17 Feb 2025 18:25:31 +0100 with message-id and subject line Re: Bug#1096236: warp: FTBFS: unsatisfiable build-dependencies: librust-ashpd-0.9+default-dev (>= 0.9.0-~~), librust-ashpd-0.9+gtk4-dev (>= 0.9.0-~~), librust-gvdb-0.7+default-dev, librust-gvdb-0.7+gresource-dev

Bug#1095286: marked as pending in mariadb

Control: tag -1 pending Hello, Bug #1095286 in mariadb 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/mariadb-team/mariadb-server/-/commit/661664bffdee368f4d05

Processed: Bug#1095286 marked as pending in mariadb

Processing control commands: > tag -1 pending Bug #1095286 [src:mariadb] mariadb: FTBFS with pcre2 10.45 due to incorrect case-insensitive regex test Added tag(s) pending. -- 1095286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095286 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1096260: golang-honnef-go-tools: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 honnef.co/go/tools/analysis/callcheck [...] honnef.co/go/tools/unused returned exit code 1

Source: golang-honnef-go-tools Version: 2024.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: E

Bug#1096222: marked as done (xdg-desktop-portal-gnome: FTBFS: ../src/notification.c:72:3: error: too few arguments to function ‘xdp_impl_notification_complete_add_notification’)

Your message dated Mon, 17 Feb 2025 17:04:09 + with message-id and subject line Re: Bug#1096222: xdg-desktop-portal-gnome: FTBFS: ../src/notification.c:72:3: error: too few arguments to function ‘xdp_impl_notification_complete_add_notification’ has caused the Debian Bug report #1096222, rega

Bug#1096248: deepin-album: FTBFS: application.cpp:160:14: error: ‘QProcessEnvironment’ has not been declared

Source: deepin-album Version: 5.9.1+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reprod

Bug#1096240: deepin-movie-reborn: FTBFS: playlist_model.cpp:202:21: error: ‘DGuiApplicationHelper’ has not been declared

Source: deepin-movie-reborn Version: 5.10.8-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd > /build/

Bug#1096233: mrpt: FTBFS: /usr/bin/ld: cannot find -lopencv_barcode: No such file or directory

Source: mrpt Version: 1:2.14.7+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reproducible-

Processed: tagging 1096259

Processing commands for cont...@bugs.debian.org: > tags 1096259 + pending Bug #1096259 [src:gnumach] gnumach: FTBFS: configure: error: failed to patch using `config.status.dep.patch'. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1096259:

Bug#1096232: invidtui: FTBFS: make: *** [debian/rules:14: binary] Error 25

Source: invidtui Version: 0.4.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh

Bug#1096254: r-cran-spatstat.random: FTBFS: build-dependency not installable: r-cran-spatstat.geom (>= 3.3-0)

Source: r-cran-spatstat.random Version: 3.3-2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--

Bug#1096239: rust-gdk4-wayland: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

Source: rust-gdk4-wayland Version: 0.9.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Running `CA

Bug#1096227: kooha: FTBFS: error[E0599]: the method `peek_fds` exists for enum `Option`, but its trait bounds were not satisfied

Source: kooha Version: 2.3.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > error[E0599]: the method `pe

Bug#1096257: haskell-gtk-traymanager: FTBFS: unsatisfiable build-dependencies: libghc-pango-dev-0.13.11.0-8acaf, libghc-pango-prof-0.13.11.0-8acaf

Source: haskell-gtk-traymanager Version: 1.0.1-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +-

Bug#1096230: rust-rebuildctl: FTBFS: make[1]: *** [debian/rules:6: execute_before_dh_install] Error 101

Source: rust-rebuildctl Version: 0.21.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering

Bug#1096243: postgresql-17: FTBFS: make[2]: *** [Makefile:32: check] Error 1

Source: postgresql-17 Version: 17.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering dir

Bug#1096237: blupimania: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 2

Source: blupimania Version: 1.6.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direc

Bug#1096228: rust-rebuilderd-common: FTBFS: 80 | Error::Utf8(ref err) => error::Error::description(err),

Source: rust-rebuilderd-common Version: 0.21.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > running 13

Bug#1096226: receptor: FTBFS: dh_auto_test: error

Source: receptor Version: 1.5.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > === RUN TestCreateCertR

Bug#1096215: etcd: FTBFS: make[1]: *** [debian/rules:35: build] Error 255

Source: etcd Version: 3.5.16-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory

Bug#1096212: dbus: FTBFS: ../../bus/selinux.c:928:49: error: ‘struct security_id’ has no member named ‘refcnt’

Source: dbus Version: 1.16.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Ibus/libdbus-daemon-inte

Bug#1096217: rust-gtk4: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

Source: rust-gtk4 Version: 0.9.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Running `CARGO=/usr

Bug#1096218: r-cran-spatstat.geom: FTBFS: build-dependency not installable: r-cran-spatstat.univar

Source: r-cran-spatstat.geom Version: 3.3-5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +

Bug#1096238: marked as done (ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory)

Your message dated Mon, 17 Feb 2025 17:49:09 +0100 with message-id and subject line Re: Bug#1096238: ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory has caused the Debian Bug report #1096238, regarding ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barc

Bug#1096209: marked as done (ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory)

Your message dated Mon, 17 Feb 2025 17:48:00 +0100 with message-id and subject line Re: Bug#1096209: ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory has caused the Debian Bug report #1096209, regarding ros-opencv-apps: FTBFS: ld: cannot find -lopencv_barcode: N

Bug#1096216: libatomic-queue: FTBFS: collect2: fatal error: cannot find ‘ld’

Source: libatomic-queue Version: 1.6.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -o > /build/r

Bug#1096258: golang-github-mendersoftware-mender-artifact: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/mendersoftware/mender-artifact github.com/menderso

Source: golang-github-mendersoftware-mender-artifact Version: 3.9.0+ds1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#1096256: asyncpg: FTBFS: ValueError: Invalid IPv6 URL

Source: asyncpg Version: 0.30.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh

Bug#1096253: starship: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 101

Source: starship Version: 1.22.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direct

Bug#1096255: deepin-image-viewer: FTBFS: main.cpp:41:24: error: ‘QDir’ has not been declared

Source: deepin-image-viewer Version: 5.8.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd > /build/r

Bug#1096250: llvm-toolchain-18: FTBFS: make[1]: *** [debian/rules:748: stamps/configure] Error 1

Source: llvm-toolchain-18 Version: 1:18.1.8-16 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250215 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Ent

  1   2   >