Bug#1056852: python-cassandra-driver: ftbfs with cython 3.0.x

2024-01-26 Thread Andreas Tille
Control: tags -1 help Control: tags -1 moreinfo Hi, I tried building the current status in Git and realised that the suggested patch is not sufficient. I decided to relax the versioned dependency from cython[1] which at least let the configure and build step pass. Unfortunately the

Processed: Re: python-cassandra-driver: ftbfs with cython 3.0.x

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Added tag(s) help. > tags -1 moreinfo Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Added tag(s) moreinfo. --

Bug#1060143: gnss-sdr ftbfs in unstable

2024-01-26 Thread Gianfranco Costamagna
control: fixed -1 0.0.19-1 control: close -1 thanks On Sat, 6 Jan 2024 12:19:35 +0100 Matthias Klose wrote: Package: src:gnss-sdr Version: 0.0.18-2 Severity: serious Tags: sid trixie ftbfs gnss-sdr ftbfs in unstable: [...] In file included from /usr/include/gnuradio/basic_block.h:15,

Processed: Re: gnss-sdr ftbfs in unstable

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.0.19-1 Bug #1060143 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr ftbfs in unstable Ignoring request to alter fixed versions of bug #1060143 to the same values previously set > close -1 Bug #1060143 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr ftbfs in

Bug#1042250: marked as done (bup: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jan 2024 05:34:11 + with message-id and subject line Bug#1042250: fixed in bup 0.33.3-1 has caused the Debian Bug report #1042250, regarding bup: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked as

Bug#1054644: marked as done (xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jan 2024 05:54:08 +0100 with message-id and subject line xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices has caused the Debian Bug report #1054644, regarding xfsprogs-udeb: causes D-I to fail, reporting errors about missing

Bug#1059424: marked as done (xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jan 2024 05:54:08 +0100 with message-id and subject line xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices has caused the Debian Bug report #1059424, regarding xfsprogs-udeb: causes D-I to fail, reporting errors about missing

Bug#1060961: clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25

2024-01-26 Thread Johannes Schauer Marin Rodrigues
Hi, On Tue, 16 Jan 2024 20:43:11 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. thank you for your bug! > Couldn't find include 'GObject-2.0.gir' (search path: '['/usr/share/gir-1.0', > '/usr/lib/x86_64-linux-gnu/gir-1.0', >

Bug#1060032: marked as done (libcircle-fe-term-perl: test failures with libtickit-widgets-perl 0.39-1)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Sat, 27 Jan 2024 03:27:34 + with message-id and subject line Bug#1060032: fixed in libcircle-fe-term-perl 0.240250-1 has caused the Debian Bug report #1060032, regarding libcircle-fe-term-perl: test failures with libtickit-widgets-perl 0.39-1 to be marked as done. This

Bug#1061591: rhsrvany: tests can fail on ci.debian.net due to wine32 installation

2024-01-26 Thread Michael Gilbert
package: src:rhsrvany version: 1.1-2 severity: serious tag: patch runsrvany64 and runpnpwait64 autopkgtests can fail on amd64 on ci.debian.net because of foreign arch wine32 installability issues [0]. This currently prevents wine from migrating to testing [1]. The attached patch solves the

Bug#1061567: marked as done (gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 23:34:19 + with message-id and subject line Bug#1061567: fixed in gnome-builder 45.0-2 has caused the Debian Bug report #1061567, regarding gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage to be marked as done. This means that you claim

Processed: set forwarded on 1061318

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1061318 https://github.com/dgibson/dtc/issues/123 Bug #1061318 [src:device-tree-compiler] device-tree-compiler ftbfs with Python 3.12 as default Set Bug forwarded-to-address to 'https://github.com/dgibson/dtc/issues/123'. > thanks

Processed: Bug#1061567 marked as pending in gnome-builder

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061567 [src:gnome-builder] gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage Ignoring request to alter tags of bug #1061567 to the same tags previously set -- 1061567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061567

Bug#1061567: marked as pending in gnome-builder

2024-01-26 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1061567 in gnome-builder 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#1061567: gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1061567 https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2156 Bug #1061567 [src:gnome-builder] gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage Changed Bug forwarded-to-address to

Bug#1060173: ruby-hiredis FTBFS with hiredis 1.2.0-6

2024-01-26 Thread Dan Bungert
I examined this bug a bit. In test/reader_test.rb, test_nil / test_null_multi_bulk are both failing. If these tests are commented out, the package build will complete. Doesn't sound like a great idea though as it's not clear to me why these tests regressed. -Dan

Bug#1061546: srcpd: installs file into aliased location

2024-01-26 Thread Preuße
On 26.01.2024 09:35, Chris Hofstaedtler wrote: Hi, Please move /lib/udev/rules.d/10-liusb.rules into /usr/lib before srcpd reaches testing. hille42@hz:~/devel/srcpd$ dpkg-deb -c srcpd_2.1.6-2_amd64.deb|grep usb -rw-r--r-- root/root 151 2024-01-26 21:45

Processed: severity of 1061577 is grave

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1061577 grave Bug #1061577 [src:rust-rio] rust-rio: use-after-free buffer access when a future is leaked Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061577:

Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-26 Thread Paul Gevers
Hi zeha, On 26-01-2024 10:21, Chris Hofstaedtler wrote: I see this "works", but now the tests fail after one try on the problematic worker and then are never retried. Can this please be fixed? What do you have in mind? I think you need to wait until issue 166 [1] is fixed, which I guess

Processed: Bug#1061272 marked as pending in sudo

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061272 {Done: Marc Haber } [src:sudo] sudo: Does not build from prefered source Added tag(s) pending. -- 1061272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1061272: marked as pending in sudo

2024-01-26 Thread Marc Haber
Control: tag -1 pending Hello, Bug #1061272 in sudo 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#1061272: marked as done (sudo: Does not build from prefered source)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 20:45:19 + with message-id and subject line Bug#1061272: fixed in sudo 1.9.15p5-3 has caused the Debian Bug report #1061272, regarding sudo: Does not build from prefered source to be marked as done. This means that you claim that the problem has been dealt

Bug#1061009: marked as done (winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2)

2024-01-26 Thread Abou Al Montacir
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part

Processed: Re: marked as done (winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2)

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 lazarus Bug #1061009 {Done: Abou Al Montacir } [src:winff] winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2 Bug reassigned from package 'src:winff' to 'lazarus'. No longer marked as found in versions winff/1.6.2+dfsg-2.

Processed: Re: marked as done (ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2)

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 lazarus Bug #1060995 {Done: Abou Al Montacir } [src:ddrescueview] ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 Bug reassigned from package 'src:ddrescueview' to 'lazarus'. No longer marked as found in versions

Processed: Re: marked as done (doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2)

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 lazarus Bug #1060932 {Done: Abou Al Montacir } [src:doublecmd] doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2 Bug reassigned from package 'src:doublecmd' to 'lazarus'. No longer marked as found in versions

Bug#1060995: marked as done (ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2)

2024-01-26 Thread Abou Al Montacir
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part

Bug#1060932: marked as done (doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2)

2024-01-26 Thread Abou Al Montacir
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part

Processed: found 1060898 in 0.3.7-1

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1060898 0.3.7-1 Bug #1060898 {Done: Gürkan Myczko } [apfs-dkms] apfs-dkms: fails to build module: super.c:17:10: fatal error: version.h: No such file or directory Marked as found in versions linux-apfs-rw/0.3.7-1; no longer marked as

Bug#947510: marked as done (Asterisk won't response for a while after run the TTS for the first time.)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 18:49:04 + with message-id and subject line Bug#947510: fixed in asterisk-espeak 5.0~1-4 has caused the Debian Bug report #947510, regarding Asterisk won't response for a while after run the TTS for the first time. to be marked as done. This means that

Bug#1035547: marked as done (asterisk-espeak: depends on misspelled asterisk abi hash)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 18:49:04 + with message-id and subject line Bug#1035547: fixed in asterisk-espeak 5.0~1-4 has caused the Debian Bug report #1035547, regarding asterisk-espeak: depends on misspelled asterisk abi hash to be marked as done. This means that you claim that the

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

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 19:22:28 +0100 with message-id and subject line Re: numpydoc's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056431, regarding numpydoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

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

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 19:22:28 +0100 with message-id and subject line Re: numpydoc's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056431, regarding numpydoc's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Processed: closing 1060143

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060143 0.0.19-1 Bug #1060143 [src:gnss-sdr] gnss-sdr ftbfs in unstable Marked as fixed in versions gnss-sdr/0.0.19-1. Bug #1060143 [src:gnss-sdr] gnss-sdr ftbfs in unstable Marked Bug as done > thanks Stopping processing here. Please

Bug#1061567: gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage

2024-01-26 Thread Adrian Bunk
Source: gnome-builder Version: 45.0-1 Severity: serious Tags: ftbfs patch Forwarded: https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/7aaaecefc2ea8a37eaeae8b4d726d119d4eb8fa3 https://buildd.debian.org/status/fetch.php?pkg=gnome-builder=riscv64=45.0-1%2Bb2=1706281444=0

Bug#1061392: uploaded NMU to DELAYED/5

2024-01-26 Thread Matthias Klose
uploaded NMU 4.2.0-0.1 to DELAYED/5

Bug#1061466: marked as done (nautilus FTBFS with nocheck profile: ../test/automated/displayless/meson.build:1:19: ERROR: Dependency "tracker-testutils-3.0" not found, tried pkgconfig)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 16:05:28 + with message-id and subject line Bug#1061466: fixed in nautilus 45.2.1-4 has caused the Debian Bug report #1061466, regarding nautilus FTBFS with nocheck profile: ../test/automated/displayless/meson.build:1:19: ERROR: Dependency

Bug#1061470: marked as done (vasttrafik-cli: API is offline)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 15:50:23 + with message-id and subject line Bug#1061470: fixed in vasttrafik-cli 1.9-1 has caused the Debian Bug report #1061470, regarding vasttrafik-cli: API is offline to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#1060964 marked as pending in python-pure-sasl

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060964 [src:python-pure-sasl] python-pure-sasl: FTBFS: tests failed Added tag(s) pending. -- 1060964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060964: marked as pending in python-pure-sasl

2024-01-26 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1060964 in python-pure-sasl 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#1058259: marked as done (python-ncclient: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 15:07:49 + with message-id and subject line Bug#1058259: fixed in python-ncclient 0.6.15-0.1 has caused the Debian Bug report #1058259, regarding python-ncclient: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you

Bug#1061345: marked as done (lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 13:49:15 + with message-id and subject line Bug#1061345: fixed in gcc-14 14-20240126-1 has caused the Debian Bug report #1061345, regarding lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict to be marked

Processed: Re: Bug#1061560: Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1061560 [debian-edu-config] Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade Severity set to 'serious' from 'normal' -- 1061560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061560 Debian Bug Tracking System

Bug#1042612: marked as done (pydicom: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 12:34:25 + with message-id and subject line Bug#1042612: fixed in pydicom 2.4.3-1 has caused the Debian Bug report #1042612, regarding pydicom: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting to be

Bug#1061319: proposed package update

2024-01-26 Thread Matthias Klose
Control: tags -1 + patch https://launchpad.net/ubuntu/+source/cadabra2/2.4.5.4-0ubuntu1

Processed: proposed package update

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1061319 [src:cadabra2] cadabra2 ftbfs with Python 3.12 as default Added tag(s) patch. -- 1061319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1054688: proposed package update

2024-01-26 Thread Matthias Klose
Here is what we came up with. Note that there's still one test hanging, which is disabled for now. https://launchpad.net/ubuntu/+source/gringo/5.6.2-0ubuntu1

Bug#1056854: marked as done (python-djvulibre: ftbfs with cython 3.0.x)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 12:20:55 + with message-id and subject line Bug#1056854: fixed in python-djvulibre 0.9.0-1 has caused the Debian Bug report #1056854, regarding python-djvulibre: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has

Bug#1042661: marked as done (python-djvulibre: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 12:20:55 + with message-id and subject line Bug#1042661: fixed in python-djvulibre 0.9.0-1 has caused the Debian Bug report #1042661, regarding python-djvulibre: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as

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

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 12:20:55 + with message-id and subject line Bug#1056468: fixed in python-djvulibre 0.9.0-1 has caused the Debian Bug report #1056468, regarding python-djvulibre's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Processed (with 2 errors): fixed and closed

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1058109 0.10.1-4 Bug #1058109 [src:sphinx-gallery] sphinx-gallery: FTBFS: NameError: name 'iae' is not defined The source 'sphinx-gallery' and version '0.10.1-4' do not appear to match any binary packages Marked as fixed in versions

Processed: Re: ERROR: Unable to connect to servers to test latency.

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1024830 [speedtest-cli] ERROR: Unable to connect to servers to test latency. Severity set to 'serious' from 'important' -- 1024830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024830 Debian Bug Tracking System Contact

Processed: severity of 1061554 is normal, affects 1061554, affects 1061554

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1061554 normal Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable Severity set to 'normal' from 'serious' > affects 1061554 src:pdns Bug

Processed: Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1059995 -1 Bug #1059995 {Done: Chris Hofstaedtler } [src:pdns] pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable Bug 1059995 cloned as bug 1061554 > reopen -1 Bug

Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-26 Thread Chris Hofstaedtler
clone 1059995 -1 reopen -1 reassign -1 systemd found -1 systemd/254.3-1 forwarded -1 https://github.com/systemd/systemd/issues/31037 thanks Dear systemd Packagers, Paul Gevers noted that src:pdns's autopkgtests fail every so often on a large amd64 debci worker and on s390x workers. Apparently a

Bug#1060848: marked as done (rust-isahc: Autopkgtest failures)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 10:06:23 + with message-id and subject line Bug#1060848: fixed in rust-isahc 1.7.2+ds-25 has caused the Debian Bug report #1060848, regarding rust-isahc: Autopkgtest failures to be marked as done. This means that you claim that the problem has been dealt

Bug#1061551: sndfile-tools: Please disable autopkgtest on armhf

2024-01-26 Thread Emanuele Rocca
Source: sndfile-tools Version: 1.5-2 Severity: serious User: debian-...@lists.debian.org Usertags: 32bit-stackclash Tags: patch Hi, the autopkgtest "upstream-tests" is currently failing on armhf due to valgrind bug https://bugs.debian.org/1061496. tests/test-wrapper.sh: line 15: 2957099

Bug#1056431: numpydoc's autopkg tests fail with Python 3.12

2024-01-26 Thread s3v
Control: reopen -1 Dear Maintainer, autopkg tests still fail [1] with this error:  49s = test session starts ==  49s platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0  49s rootdir:

Processed: Re: numpydoc's autopkg tests fail with Python 3.12

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1056431 {Done: Chiara Marmo } [src:numpydoc] numpydoc's autopkg tests fail with Python 3.12 Bug #1058407 {Done: Chiara Marmo } [src:numpydoc] numpydoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Processed: Re: Bug#1061546: srcpd: installs file into aliased location

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1061546 [src:srcpd] srcpd: installs file into aliased location Severity set to 'serious' from 'important' -- 1061546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061546 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1061344: emboss-lib: identified for time_t transition but no ABI in shlibs

2024-01-26 Thread Andreas Tille
Hi Charles, I wonder how we can properly solve this bug. In the early stage of Emboss packaging obviously the packages libajax6, libajax6-dev, libnucleus6, libnucleus6-dev existed (thus the remaining Conflicts/Replaces on emboss-lib which can

Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

2024-01-26 Thread Chris Hofstaedtler
Hi Paul, * Paul Gevers [240104 18:14]: > Can you figure out decent numbers for these? Below I printed the output of > lsipc and AFAICT SHMMAX is already pretty big ;) (and the same on all our > hosts, which is also true for MSGMAX). > > On the other hand, $(ipcs -a) doesn't show anything on the

Processed: Just adding a blocker for a new upload as upstream tag

2024-01-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1056813 [src:macs] macs: ftbfs with cython 3.0.x Added tag(s) upstream. > forwarded -1 https://github.com/macs3-project/MACS/issues/615 Bug #1056813 [src:macs] macs: ftbfs with cython 3.0.x Set Bug forwarded-to-address to

Bug#1056813: Just adding a blocker for a new upload as upstream tag

2024-01-26 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/macs3-project/MACS/issues/615 This is no issue about the topic of this bug report (cython) but rather an issue opened upstream to solve the problem which prevents us uploading latest macs3. Kind regards Andreas. --

Bug#1059256: marked as done (falcosecurity-libs: CVE-2023-49287)

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 08:34:48 + with message-id and subject line Bug#1059256: fixed in falcosecurity-libs 0.14.1-1 has caused the Debian Bug report #1059256, regarding falcosecurity-libs: CVE-2023-49287 to be marked as done. This means that you claim that the problem has been

Bug#1057449: marked as done (falcosecurity-scap-dkms: module build fails for Linux 6.6: ppm_fillers.c:1438:63: error: 'struct inode' has no member named 'i_ctime')

2024-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2024 08:34:48 + with message-id and subject line Bug#1057449: fixed in falcosecurity-libs 0.14.1-1 has caused the Debian Bug report #1057449, regarding falcosecurity-scap-dkms: module build fails for Linux 6.6: ppm_fillers.c:1438:63: error: 'struct inode' has