Processed: Re: Bug#1084228: FTBFS: Test failure: test_array_inference[data7-expected7]: AssertionError: DatetimeArray._ndarray are different

Processing control commands: > tags -1 pending Bug #1084228 [src:pandas] FTBFS: Test failure: test_array_inference[data7-expected7]: AssertionError: DatetimeArray._ndarray are different Added tag(s) pending. -- 1084228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084228 Debian Bug Track

Bug#1084228: FTBFS: Test failure: test_array_inference[data7-expected7]: AssertionError: DatetimeArray._ndarray are different

Control: tags -1 pending This particular bug is already known (as #1084190, though that covers several packages so not actually merging them) and fixed in Salsa. Thank you for reporting it, and please do continue to report any other bugs you find.

Bug#1084146: ausweisapp2: FTBFS against Qt 6.7.2

Hello Patrick, On Sat, 2024-10-05 at 18:56 +0200, Patrick Franz wrote: > your package fails to build against Qt 6.7.2 which has been uploaded > to unstable. The reason is that it uses obsolete package names for > its Qt 6 build-dependencies. > > All Qt 6 dev-packages are now called qt6-$MODULE-de

Processed: reassign 1083262 to linux-image-amd64, reassign 1084162 to libqt6core6t64, tagging 1083254

Processing commands for cont...@bugs.debian.org: > reassign 1083262 linux-image-amd64 Bug #1083262 [linux-image-amd64 (or initramfs-tools)] Bug Report - Built-in Keyboard Issue on Microsoft Surface in Install Environment and LUKS Decryption Warning: Unknown package 'or' Bug reassigned from packag

Processed: fixed 1077840 in 0.18.1-1, found 1084054 in 4.0.13-1

Processing commands for cont...@bugs.debian.org: > fixed 1077840 0.18.1-1 Bug #1077840 {Done: Dima Kogan } [falcosecurity-scap-dkms] falcosecurity-scap-dkms: module fails to build for Linux 6.10: error: implicit declaration of function 'fd_is_open' Marked as fixed in versions falcosecurity-libs/

Processed: metadata

Processing commands for cont...@bugs.debian.org: > # The libxml2 downgrade has made these failures not to happen anymore > # Downgrading and not closing because the changes are still desired > severity 1073309 important Bug #1073309 [src:cegui-mk2] cegui-mk2: FTBFS: XMLParser.cpp:102:40: error: i

Bug#1077840: marked as done (falcosecurity-scap-dkms: module fails to build for Linux 6.10: error: implicit declaration of function 'fd_is_open')

Your message dated Sun, 06 Oct 2024 16:51:34 -0700 with message-id <8734l8x01l@secretsauce.net> and subject line Fixed in 0.18.1-1 has caused the Debian Bug report #1077840, regarding falcosecurity-scap-dkms: module fails to build for Linux 6.10: error: implicit declaration of function 'fd_is_

Processed: metadata

Processing commands for cont...@bugs.debian.org: > # this one qualifies as a ftbfs when using the unshare backend > tags 1068197 ftbfs Bug #1068197 [src:debian-installer] debian-installer: accesses the internet during build Added tag(s) ftbfs. > # these ones actually ftbfs (in addition to being o

Bug#1068731: marked as done (falcosecurity-libs: FTBFS on riscv64 and ppc64el)

Your message dated Sun, 06 Oct 2024 16:00:19 -0700 with message-id <87cykcx2f0@secretsauce.net> and subject line Fixed in 0.18.1-1 has caused the Debian Bug report #1068731, regarding falcosecurity-libs: FTBFS on riscv64 and ppc64el to be marked as done. This means that you claim that the prob

Bug#1067619: Update

In the latest release (0.18.1) the i386 tests don't crash anymore, but some of them do fail: https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-libs&arch=i386&ver=0.18.1-1&stamp=1727846180&raw=0 Upstream is aware: https://github.com/falcosecurity/libs/issues/1203#issuecomment-2387

Processed: tags

Processing commands for cont...@bugs.debian.org: > tags 1081373 ftbfs Bug #1081373 [src:haskell-argon2] Removal notice: obsolete Added tag(s) ftbfs. > tags 1081936 ftbfs Bug #1081936 [src:haskell-configfile] Removal notice: obsolete Added tag(s) ftbfs. > tags 1082009 ftbfs Bug #1082009 [src:haskel

Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable

On Sat, 05 Oct 2024 at 14:19:50 +0100, Simon McVittie wrote: > The error message suggests that there might be a problem with the > chroot/container, or possibly with the host /tmp being shared with it: > > > Bail out! libmutter-FATAL-ERROR: Failed to start X Wayland: Directory > > "/tmp/.X11-unix

Bug#1084228: FTBFS: Test failure: test_array_inference[data7-expected7]: AssertionError: DatetimeArray._ndarray are different

Source: pandas Version: 2.2.3+dfsg-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, pandas failed to rebuild. --- [...] = test session starts ==

Bug#1084223: python-pygit2: fails to build from source on all, armel, armhf, mips64el and riscv64

Source: python-pygit2 Version: 1.15.1-3 Severity: serious Tags: ftbfs Justification: ftbfs Dear maintainers, The version of python-pygit2 in unstable fails to build on several architectures including all. I copied a piece from the arch:all below. Paul test/test_credentials.py::test_callback

Bug#1084214: libgit-raw-perl: FTBFS with libgit2 1.8.2~rc1: t/17-filter.t fails

Source: libgit-raw-perl Version: 0.90+ds-2 Severity: serious Tags: ftbfs trixie sid Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: libg...@packages.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libgit2 was updated to 1.8.2~rc1+ds-2 in uns

Bug#1084213: FTBFS: :: Fatal: GES: Skipping foreign identifier 'GstFrameCompositionApi' from namespace GstPbutils

Source: gstreamer-editing-services1.0 Version: 1.24.8-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, gstreamer-editing-services1.0 failed to rebuild. --- [...] [191/217] env

Bug#862378: check-all-the-things: not suitable for Debian stable at this time

Hi Paul, On Fri, May 12, 2017 at 08:51:32AM +0800, Paul Wise wrote: > check-all-the-things is not suitable for Debian stable at this time. > It is still evolving a bit and doesn't have any sandboxing of tools. > There are also a lot of bugs in stretch fixed in the git repository. Is there progres

Bug#1084190: breakage due to tzdata System V name removal

I now have dateparser and pandas building (but only have the right to actually upload pandas). https://salsa.debian.org/rnpalmer-guest/dateparser And yes, that glib test failure looks like another instance of this. Changing g_time_zone_get_abbreviation (tz, 0) to g_time_zone_get_abbreviation (

Bug#1084056: marked as done (libgsf: CVE-2024-36474 CVE-2024-42415)

Your message dated Sun, 06 Oct 2024 16:32:49 + with message-id and subject line Bug#1084056: fixed in libgsf 1.14.50-1+deb12u1 has caused the Debian Bug report #1084056, regarding libgsf: CVE-2024-36474 CVE-2024-42415 to be marked as done. This means that you claim that the problem has been d

Bug#1083067: marked as done (cups: CVE-2024-47176 reports severe vulnerability in CUPS)

Your message dated Sun, 06 Oct 2024 16:32:38 + with message-id and subject line Bug#1082820: fixed in cups-filters 1.28.17-3+deb12u1 has caused the Debian Bug report #1082820, regarding cups: CVE-2024-47176 reports severe vulnerability in CUPS to be marked as done. This means that you claim t

Bug#1082820: marked as done (cups-filters: CVE-2024-47176)

Your message dated Sun, 06 Oct 2024 16:32:38 + with message-id and subject line Bug#1082820: fixed in cups-filters 1.28.17-3+deb12u1 has caused the Debian Bug report #1082820, regarding cups-filters: CVE-2024-47176 to be marked as done. This means that you claim that the problem has been deal

Processed: RE: Bug#1083286: libxnnpack0: rmoved symbols (xnn_setup_convolution2d_nhwc_qc8 xnn_create_convolution2d_nhwc_qc8) cause third party packages to fail

Processing control commands: > block 1084103 by -1 Bug #1084103 {Done: Paul Gevers } [src:xnnpack] src:xnnpack: fails to migrate to testing for too long 1084103 was not blocked by any bugs. 1084103 was not blocking any bugs. Added blocking bug(s) of 1084103: 1083286 > block -1 by 1080510 Bug #108

Bug#1083286: libxnnpack0: rmoved symbols (xnn_setup_convolution2d_nhwc_qc8 xnn_create_convolution2d_nhwc_qc8) cause third party packages to fail

control: block 1084103 by -1 control: block -1 by 1080510 control: block 1081664 by 1080510 > Such ABI changes require an updated SONAME to avoid breaking programs in > Debian, for example with a rename from libxnnpack0 to libxnnpack1. Certainly true. But let me explain the situation more: xnnpac

Bug#1075590: tuxpaint: ftbfs with GCC-14

On Sun, Oct 06, 2024 at 06:04:49PM +0200, Florian Ernst wrote: > [...] > So, not only is "-lm" missing, but now there is a bunch of additional > libraries (Gnome?) present that wasn't there before, for whatever > reason. H. In May 2023 upstream already decided to not rely on receiving all requ

Bug#1075590: tuxpaint: ftbfs with GCC-14

On Sun, Oct 06, 2024 at 02:31:48PM +0200, Chris Hofstaedtler wrote: > On Sun, Aug 11, 2024 at 01:35:34PM +0200, Florian Ernst wrote: > > With the attached minimized patch this tuxpaint version compiles again > > with gcc-14. It seems this was first fixed upstream in 0.9.29, cf. > >

Bug#1084122: marked as done (haskell-unixutils: FTBFS: Couldn't match expected type)

Your message dated Sun, 06 Oct 2024 15:22:39 + with message-id and subject line Bug#1084122: fixed in haskell-unixutils 1.54.3-1 has caused the Debian Bug report #1084122, regarding haskell-unixutils: FTBFS: Couldn't match expected type to be marked as done. This means that you claim that the

Bug#1084126: marked as done (askell-cassava: FTBFS: Encountered missing or private dependencies)

Your message dated Sun, 06 Oct 2024 15:21:20 + with message-id and subject line Bug#1084126: fixed in haskell-cassava 0.5.3.2-1 has caused the Debian Bug report #1084126, regarding askell-cassava: FTBFS: Encountered missing or private dependencies to be marked as done. This means that you cla

Bug#1081864: git-delta: FTBFS: assertion `left == right` failed: on line 3 of input

The new version of rust-unicode-width fixes the assertion failure. However a libgit2 transition has started, which brought with it a new version of rust-git2. After bumping the dependencies I was able to succesfully build git-delta, debdiff is attatched. diff -Nru git-delta-0.18.2/debian/changel

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

Your message dated Sun, 06 Oct 2024 15:08:56 + with message-id and subject line Bug#1061029: fixed in lookatme 2.5.4-3 has caused the Debian Bug report #1061029, regarding lookatme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to be

Bug#1075434: marked as done (randtype: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 15:10:17 + with message-id and subject line Bug#1075434: fixed in randtype 1.13-11.2 has caused the Debian Bug report #1075434, regarding randtype: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Processed (with 3 errors): RM: libtar -- RoQA; Abandoned upstream

Processing control commands: > clone -1 -2 Bug #1072586 [src:libtar] RM: libtar -- RoQA; Abandoned upstream Bug 1072586 cloned as bug 1084204 No valid blocking bug(s) given; not doing anything Failed to clone 1072586: Unknown/archived blocking bug(s):1072585. > severity -2 normal Failed to set se

Bug#1072586: RM: libtar -- RoQA; Abandoned upstream

Control: clone -1 -2 Control: severity -2 normal Control: reassign -2 ftp.debian.org Bastian Germann wrote: > Upstream last touched libtar more than a decade ago. Given the rdep is gone, lets also remove libtar then. Chris

Bug#1075538: marked as done (ssmtp: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 14:47:44 + with message-id and subject line Bug#1075538: fixed in ssmtp 2.64-12 has caused the Debian Bug report #1075538, regarding ssmtp: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1084154: marked as done (libdatetime-format-flexible-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63 - Olson DB 2024b)

Your message dated Sun, 06 Oct 2024 14:42:48 + with message-id and subject line Bug#1084154: fixed in libdatetime-format-flexible-perl 0.35-1 has caused the Debian Bug report #1084154, regarding libdatetime-format-flexible-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / Da

Bug#1084155: marked as done (libdatetimex-easy-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.63 - Olson DB 2024b)

Your message dated Sun, 06 Oct 2024 14:43:04 + with message-id and subject line Bug#1084155: fixed in libdatetimex-easy-perl 0.091-2 has caused the Debian Bug report #1084155, regarding libdatetimex-easy-perl: Test failures with libdatetime-timezone-perl 1:2.63-1+2024b / DateTime::TimeZone 2.

Bug#1074954: marked as done (ffproxy: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 14:39:09 + with message-id and subject line Bug#1074954: fixed in ffproxy 1.6-12.1 has caused the Debian Bug report #1074954, regarding ffproxy: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Re: Bug#1068503: mlterm: Please consider dropping Canna (and perhaps freewnn)

Processing commands for cont...@bugs.debian.org: > # On 2024-04-06 Andreas Metzler wrote: > # [...] > # > However I can see that freewnn and canna are both very much dead > # > upstream and have been orphaned for a very long time. > # [...] > # > # freewnn is now marked for removal #1084196, clon

Processed: Re: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincomp

Processing control commands: > block 1081740 by 1084087 Bug #1081740 [release.debian.org] transition: gmsh 1081740 was not blocked by any bugs. 1081740 was not blocking any bugs. Added blocking bug(s) of 1081740: 1084087 -- 1081740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081740 10840

Bug#1084087: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincompat

Source: gmsh Followup-For: Bug #1084087 X-Debbugs-Cc: francesco.balla...@unicatt.it Control: block 1081740 by 1084087

Processed: Re: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincomp

Processing control commands: > forwarded 1084087 https://gitlab.onelab.info/gmsh/gmsh/-/issues/2915 Bug #1084087 [src:gmsh] gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincom

Bug#1084087: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincompat

Source: gmsh Followup-For: Bug #1084087 X-Debbugs-Cc: francesco.balla...@unicatt.it Control: forwarded 1084087 https://gitlab.onelab.info/gmsh/gmsh/-/issues/2915

Bug#1084193: pyside6: FTBFS against Qt 6.7.2

Source: pyside6 Version: 6.6.2-5 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package fails to build against Qt 6.7.2 as part of the Qt 6.7.2 transition. The relevant part of the log is: FAILED: PySide6/QtCore/CMakeFiles/QtCore.dir/PySide6/Q

Bug#1084087: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincompat

Source: gmsh Followup-For: Bug #1084087 X-Debbugs-Cc: francesco.balla...@unicatt.it, sramac...@debian.org Control: tags -1 ftbfs Hi Sebastian, thanks for the message. I asked upstream for an update about this error, see https://gitlab.onelab.info/gmsh/gmsh/-/issues/2915 which was already reported

Processed: Re: gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincomp

Processing control commands: > tags -1 ftbfs Bug #1084087 [src:gmsh] gmsh: FTBFS on 32 bit architectures: /<>/contrib/hxt/tetMesh/src/hxt_tetRefine.c:346:32: error: passing argument 1 of ‘scanbsearch’ from incompatible pointer type [-Wincompatible-pointer-types] Ignoring request to alter tags o

Processed: tagging 1075538

Processing commands for cont...@bugs.debian.org: > tags 1075538 + pending Bug #1075538 [src:ssmtp] ssmtp: ftbfs with GCC-14 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075538 Deb

Bug#1084190: breakage due to tzdata System V name removal

Control: tags -1 ftbfs Control: affects -1 src:glib2.0 On Sun, Oct 06, 2024 at 01:41:50PM +0100, Rebecca N. Palmer wrote: > Package: tzdata > Version: 2024b-2 > Severity: serious > Justification: fails multiple autopkgtests > > tadata 2024b changes the meaning of short names such as 'EST' from 'a

Processed: Re: Bug#1084190: breakage due to tzdata System V name removal

Processing control commands: > tags -1 ftbfs Bug #1084190 [tzdata] breakage due to tzdata System V name removal Added tag(s) ftbfs. > affects -1 src:glib2.0 Bug #1084190 [tzdata] breakage due to tzdata System V name removal Added indication that 1084190 affects src:glib2.0 -- 1084190: https://bu

Bug#1084190: breakage due to tzdata System V name removal

Package: tzdata Version: 2024b-2 Severity: serious Justification: fails multiple autopkgtests tadata 2024b changes the meaning of short names such as 'EST' from 'always this offset' to 'alias for a place that currently uses this offset'. This causes several autopkgtest failures: - pandas and

Bug#1075594: marked as done (ucblogo: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 12:41:30 + with message-id and subject line Bug#1075594: fixed in ucblogo 6.2.4-1.1 has caused the Debian Bug report #1075594, regarding ucblogo: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1069556: marked as done (rovclock: FTBFS on armel: rovclock.c:27:10: fatal error: sys/io.h: No such file or directory)

Your message dated Sun, 06 Oct 2024 12:40:08 + with message-id and subject line Bug#1069556: fixed in rovclock 0.6e-7.1 has caused the Debian Bug report #1069556, regarding rovclock: FTBFS on armel: rovclock.c:27:10: fatal error: sys/io.h: No such file or directory to be marked as done. This

Bug#1084121: marked as done (haskell-mueval: FTBFS: Module ‘Control.Monad.Writer’ does not export ‘Any(..)’)

Your message dated Sun, 06 Oct 2024 12:36:48 + with message-id and subject line Bug#1084121: fixed in haskell-mueval 0.9.4-1 has caused the Debian Bug report #1084121, regarding haskell-mueval: FTBFS: Module ‘Control.Monad.Writer’ does not export ‘Any(..)’ to be marked as done. This means th

Bug#1075590: tuxpaint: ftbfs with GCC-14

On Sun, Aug 11, 2024 at 01:35:34PM +0200, Florian Ernst wrote: > > With the attached minimized patch this tuxpaint version compiles again > with gcc-14. It seems this was first fixed upstream in 0.9.29, cf. >

Bug#1077914: marked as done (surf: flaky autopkgtest on some architectures: Alarm clock)

Your message dated Sun, 06 Oct 2024 12:13:43 + with message-id and subject line Bug#1077914: fixed in surf 2.1+git20240324-1 has caused the Debian Bug report #1077914, regarding surf: flaky autopkgtest on some architectures: Alarm clock to be marked as done. This means that you claim that the

Bug#1077666: marked as done (Build-Depends: libllvmlibc--dev is missing)

Your message dated Sun, 6 Oct 2024 12:39:58 +0200 with message-id <3d78f052-24f8-4637-9054-07c96a989...@debian.org> and subject line has caused the Debian Bug report #1077666, regarding Build-Depends: libllvmlibc--dev is missing to be marked as done. This means that you claim that the problem has

Bug#1077666: (no subject)

it was an intermittent issue with llvm,nothing to do with iwyu Cheers S

Processed: Re: arcp: FTBFS: FAIL: test_parse_ni_uri (tests.test_parse.TestParse.test_parse_ni_uri)

Processing control commands: > forwarded -1 https://github.com/stain/arcp-py/issues/3 Bug #1081857 [src:arcp] arcp: FTBFS: FAIL: test_parse_ni_uri (tests.test_parse.TestParse.test_parse_ni_uri) Set Bug forwarded-to-address to 'https://github.com/stain/arcp-py/issues/3'. -- 1081857: https://bugs

Bug#1081857: arcp: FTBFS: FAIL: test_parse_ni_uri (tests.test_parse.TestParse.test_parse_ni_uri)

Control: forwarded -1 https://github.com/stain/arcp-py/issues/3 I've notified upstream. My guess is that https://github.com/python/cpython/issues/67693 which became https://github.com/python/cpython/commit/387ff96e95b9f8a8cc7e646523ba3175b1350669 in Python 3.12.4 is to blame OpenPGP_signatur

Bug#1083058: marked as done (src:rust-coreutils: unsatisfied build dependency in testing: librust-half-1+default-dev)

Your message dated Sun, 06 Oct 2024 09:38:51 + with message-id and subject line Bug#1083058: fixed in rust-coreutils 0.0.26-5 has caused the Debian Bug report #1083058, regarding src:rust-coreutils: unsatisfied build dependency in testing: librust-half-1+default-dev to be marked as done. Thi

Bug#1082938: marked as done (rust-coreutils - FTBFS on 32-bit.)

Your message dated Sun, 06 Oct 2024 09:38:51 + with message-id and subject line Bug#1082938: fixed in rust-coreutils 0.0.26-5 has caused the Debian Bug report #1082938, regarding rust-coreutils - FTBFS on 32-bit. to be marked as done. This means that you claim that the problem has been dealt

Bug#1084125: marked as done (haskell-hookup: FTBFS: Encountered missing or private dependencies)

Your message dated Sun, 06 Oct 2024 09:08:21 + with message-id and subject line Bug#1084125: fixed in haskell-hookup 0.8-1 has caused the Debian Bug report #1084125, regarding haskell-hookup: FTBFS: Encountered missing or private dependencies to be marked as done. This means that you claim th

Bug#1084123: marked as done (haskell-libmpd: FTBFS: Variable not in scope)

Your message dated Sun, 06 Oct 2024 09:10:17 + with message-id and subject line Bug#1084123: fixed in haskell-libmpd 0.10.0.1-1 has caused the Debian Bug report #1084123, regarding haskell-libmpd: FTBFS: Variable not in scope to be marked as done. This means that you claim that the problem ha

Bug#1075282: marked as done (moarvm: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 08:42:19 + with message-id and subject line Bug#1077392: fixed in moarvm 2024.09+dfsg-1 has caused the Debian Bug report #1077392, regarding moarvm: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1077392: marked as done (moarvm: FTBFS: src/6model/containers.c:117:5: error: initialization of ‘void (*)(MVMThreadContext *, MVMObject *, MVMuint64)’ {aka ‘void (*)(MVMThreadContext *, MVMObject

Your message dated Sun, 06 Oct 2024 08:42:19 + with message-id and subject line Bug#1077392: fixed in moarvm 2024.09+dfsg-1 has caused the Debian Bug report #1077392, regarding moarvm: FTBFS: src/6model/containers.c:117:5: error: initialization of ‘void (*)(MVMThreadContext *, MVMObject *, MV

Processed: Re: Bug#1084174: sbuild: shell hook '%s' broken (cannot open /dev/tty: no such device)

Processing control commands: > severity -1 serious Bug #1084174 [sbuild] sbuild: shell hook '%s' broken (cannot open /dev/tty: no such device) Severity set to 'serious' from 'normal' -- 1084174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084174 Debian Bug Tracking System Contact ow...@b

Bug#1075302: marked as done (nam: ftbfs with GCC-14)

Your message dated Sun, 06 Oct 2024 07:51:27 + with message-id and subject line Bug#1075302: fixed in nam 1.15-8 has caused the Debian Bug report #1075302, regarding nam: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1083024: teg: new upstream release fixes frequent segfault

Control: tags -1 upstream Control: fixed -1 0.13.0-1 Control: forwarded -1 https://github.com/wfx/teg/issues/53 (Tagging as fixed in unstable already, the mentioned commit is in 0.13.0) Patch: https://github.com/wfx/teg/commit/d16e8c31be5aeea52c71490c5f68e4e07155cc68 -- tobi On Mon, Sep 30, 2

Processed: Re: Bug#1083024: teg: new upstream release fixes frequent segfault

Processing control commands: > tags -1 upstream Bug #1083024 {Done: Alexandre Detiste } [teg] teg: new upstream release fixes frequent segfault Added tag(s) upstream. > fixed -1 0.13.0-1 Bug #1083024 {Done: Alexandre Detiste } [teg] teg: new upstream release fixes frequent segfault Ignoring requ