Bug#1069526: libevdevplus: FTBFS on armhf: InputEvent.hpp:23:39: error: ‘struct input_event’ has no member named ‘time’

Followup-For: Bug #1069526 Control: tag -1 patch pending Hi, I've uploaded the attached patch as a NMU to DELAYED/2, it fixes the issue at hand and does some more minor cleanup. Please let me know if I should delay it longer. Andreas diff --git a/debian/changelog b/debian/changelog index

Processed: Re: libevdevplus: FTBFS on armhf: InputEvent.hpp:23:39: error: ‘struct input_event’ has no member named ‘time’

Processing control commands: > tag -1 patch pending Bug #1069526 [src:libevdevplus] libevdevplus: FTBFS on armhf: InputEvent.hpp:23:39: error: ‘struct input_event’ has no member named ‘time’ Added tag(s) patch and pending. -- 1069526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069526

Bug#1065993: xwiimote: FTBFS on arm{el,hf}:

Followup-For: Bug #1065993 Control: tag -1 pending Hi, I've uploaded this fix along with some more minor cleanup (can be found in the git repository) as a NMU to DELAYED/2. Please let me know if I should delay it longer. Andreas

Processed: Re: xwiimote: FTBFS on arm{el,hf}:

Processing control commands: > tag -1 pending Bug #1065993 [src:xwiimote] xwiimote: FTBFS on arm{el,hf}: Ignoring request to alter tags of bug #1065993 to the same tags previously set -- 1065993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065993 Debian Bug Tracking System Contact

Bug#1069796: rust-abscissa-derive - (build-)depends unsatisfiable.

Thanks for the report. abscissa_derive is a dependency of abscissa_core but I have been waiting with the upload of that since tracing-subscriber have some features disabled and it's non-trivial to reenable them (due to the regex situation iirc). abscissa_core is a dependency of cargo-audit, and

Bug#1069923: util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel

Package: util-linux-extra Version: 2.40-7 Severity: serious Tags: patch Control: affects -1 + util-linux User: helm...@debian.org Usertags: dep17p1 Hi Chris, in my last patch, I trusted your earlier changes too much and failed to notice that it didn't cover ctrlaltdel. I'm attaching a patch to

Processed: util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel

Processing control commands: > affects -1 + util-linux Bug #1069923 [util-linux-extra] util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel Added indication that 1069923 affects util-linux -- 1069923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069923 Debian Bug Tracking

Bug#1069520: sbcl: FTBFS on armhf: make[1]: *** [debian/rules:53: override_dh_auto_build] Error 1

Hello, Thanks Peter. Looks like upstream might be able to commit a fix. -- Sean Whitton signature.asc Description: PGP signature

Processed: bug 1069520 is forwarded to https://bugs.launchpad.net/sbcl/+bug/2063340

Processing commands for cont...@bugs.debian.org: > forwarded 1069520 https://bugs.launchpad.net/sbcl/+bug/2063340 Bug #1069520 [src:sbcl] sbcl: FTBFS on armhf: make[1]: *** [debian/rules:53: override_dh_auto_build] Error 1 Set Bug forwarded-to-address to

Bug#1066587: marked as done (gramofile: FTBFS: gramofile.c:42:3: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

Your message dated Sat, 27 Apr 2024 08:38:24 + with message-id and subject line Bug#1066587: fixed in gramofile 1.6-13 has caused the Debian Bug report #1066587, regarding gramofile: FTBFS: gramofile.c:42:3: error: implicit declaration of function ‘exit’

Processed: Re: libkqueue: fails to build on most my boxes

Processing control commands: > severity -1 serious Bug #955260 [src:libkqueue] libkqueue: fails to build on most my boxes Severity set to 'serious' from 'important' > found -1 2.3.1-1 Bug #955260 [src:libkqueue] libkqueue: fails to build on most my boxes Marked as found in versions

Bug#1066346: marked as done (sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’? [-Werror=implicit-function-declaration])

Your message dated Sat, 27 Apr 2024 11:06:18 + with message-id and subject line Bug#1066346: fixed in sc 7.16-4.2 has caused the Debian Bug report #1066346, regarding sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’?

Bug#1069945: rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io'

Package: rapiddisk-dkms Version: 9.1.0-2 Severity: serious Control: found -1 9.0.0-1 DKMS make.log for rapiddisk-dkms-9.1.0 for kernel 6.7.12-amd64 (x86_64) Fri Apr 26 21:35:41 UTC 2024 make: Entering directory '/usr/src/linux-headers-6.7.12-amd64' CC [M]

Processed: rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io'

Processing control commands: > found -1 9.0.0-1 Bug #1069945 [rapiddisk-dkms] rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io' Marked as found in versions rapiddisk/9.0.0-1. -- 1069945:

Bug#1058433: marked as done (kexec-tools: FTBFS: purgatory/arch/i386/entry32-16.S:23: Error: 64bit mode not supported on `i386'.)

Your message dated Sat, 27 Apr 2024 13:34:54 + with message-id and subject line Bug#1058433: fixed in kexec-tools 1:2.0.27-1.1 has caused the Debian Bug report #1058433, regarding kexec-tools: FTBFS: purgatory/arch/i386/entry32-16.S:23: Error: 64bit mode not supported on `i386'. to be marked

Bug#1069953: libgstreamer-plugins-bad1.0-dev: not installable on i386

Package: libgstreamer-plugins-bad1.0-dev Version: 1.24.2-3 Severity: grave X-Debbugs-Cc: sramac...@debian.org $ apt install --no-install-recommends libgstreamer-plugins-bad1.0-dev Some packages could not be installed. This may mean that you have requested an impossible situation or if you are

Bug#1061435: lintian-brush ftbfs with updated pyo3 version

relaxing that in Cargo.toml to >= 0.19 lets the build succeed (and build with python3-defaults from experimental). I was doing a test build of lintian brush to test I could build it with the version of rust-distro-info I was preparing (now uploaded) and ran into a couple of other issues.

Bug#1031512: marked as done (docbook-defguide: non-free GFDL-licensed files)

Your message dated Sat, 27 Apr 2024 16:25:31 +0200 with message-id and subject line Re: docbook-defguide: non-free GFDL-licensed files has caused the Debian Bug report #1031512, regarding docbook-defguide: non-free GFDL-licensed files to be marked as done. This means that you claim that the

Bug#1031512: docbook-defguide: non-free GFDL-licensed files

[Bastian Germann 2023-02-17] > Some files in the package are licensed under the non-free variant of the GFDL > with explicit Invariant Section. > Please repack to remove them. I had a look to try to locate the files, but failed to find them. Which files did you have in mind? As the package is

Bug#1069935: lyskom-elisp-client: missing Build-Depends: emacs

Source: lyskom-elisp-client Version: 0.48+git.20231226.364902c3-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, lyskom-elisp-client fails to build for arch:all due to missing emacs:

Bug#1069261: marked as done (cwlformat: fails with newer ruamel.yaml)

Your message dated Sat, 27 Apr 2024 10:49:07 + with message-id and subject line Bug#1069261: fixed in cwlformat 2022.02.18-3 has caused the Debian Bug report #1069261, regarding cwlformat: fails with newer ruamel.yaml to be marked as done. This means that you claim that the problem has been

Bug#955260: libkqueue: fails to build on most my boxes

On Sat, 27 Apr 2024 12:32:58 +0200 Andreas Beckmann wrote: [...] > This is now happening on the buildds as well and I can also reproduce it > locally on amd64. You must try with the latest source 2.6.1 https://github.com/mheily/libkqueue/releases Christian

Processed: cloning 1069222, reassign -1 to src:purple-xmpp-http-upload ...

Processing commands for cont...@bugs.debian.org: > clone 1069222 -1 Bug #1069222 [purple-xmpp-carbons] purple-xmpp-carbons: debian/shlibs.local hardcodes dependency on libpurple0 Bug 1069222 cloned as bug 1069944 > reassign -1 src:purple-xmpp-http-upload 0.2.4-2 Bug #1069944

Processed: Re: dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

Processing control commands: > tags -1 + help unreproducible Bug #1069400 [src:dqlite] dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) help and unreproducible. > severity -1 important Bug #1069400 [src:dqlite]

Bug#1069400: dqlite: FTBFS on arm64: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

Control: tags -1 + help unreproducible Control: severity -1 important Lowering bug severity to important since I can't reproduce this issue on any of my systems. Additionally, looking at the various reproducible builds shows the most recent arm64 build passed, while the amd64 one failed.

Processed: tagging 1015689, tagging 1015558, tagging 1015466, tagging 1015450, tagging 1015448, tagging 1015441 ...

Processing commands for cont...@bugs.debian.org: > tags 1015689 + experimental Bug #1015689 {Done: Patrick Franz } [src:threadweaver] threadweaver: ftbfs with LTO (link time optimization) enabled Added tag(s) experimental. > tags 1015558 + experimental Bug #1015558 {Done: Patrick Franz }

Bug#1069946: rust-webpki-roots: hardcoded root certs are unfit for stable Debian

Source: rust-webpki-roots Version: 0.26.1-1 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The purpose of WebPKI-Roots is to hardcode a static set of PKI certificates into compiled code. This functionality is unfit for a

Bug#1066695: marked as done (lmemory: FTBFS: mmain.c:29:7: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

Your message dated Sat, 27 Apr 2024 12:31:32 + with message-id and subject line Bug#1066695: fixed in lmemory 0.6c-12 has caused the Debian Bug report #1066695, regarding lmemory: FTBFS: mmain.c:29:7: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’?

Processed: Bug#1069923 marked as pending in util-linux

Processing control commands: > tag -1 pending Bug #1069923 [util-linux-extra] util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel Added tag(s) pending. -- 1069923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069923 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1069923: marked as pending in util-linux

Control: tag -1 pending Hello, Bug #1069923 in util-linux 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#1058433: kexec-tools: diff for NMU version 1:2.0.27-1.1

Control: tags 1058433 + patch Dear maintainer, I've prepared an NMU for kexec-tools (versioned as 1:2.0.27-1.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru kexec-tools-2.0.27/debian/changelog kexec-tools-2.0.27/debian/changelog ---

Processed: kexec-tools: diff for NMU version 1:2.0.27-1.1

Processing control commands: > tags 1058433 + patch Bug #1058433 [src:kexec-tools] kexec-tools: FTBFS: purgatory/arch/i386/entry32-16.S:23: Error: 64bit mode not supported on `i386'. Added tag(s) patch. -- 1058433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058433 Debian Bug Tracking

Processed: Re: dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’

Processing control commands: > tag -1 + bookworm Bug #1069878 [dm-writeboost-dkms] dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’ Added tag(s) bookworm. -- 1069878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069878 Debian

Bug#1069878: dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’

Followup-For: Bug #1069878 Control: tag -1 + bookworm DKMS make.log for dm-writeboost-2.2.16 for kernel 6.1.0-20-cloud-amd64 (x86_64) Sat Apr 27 11:45:49 UTC 2024 make -C /lib/modules/6.1.0-20-cloud-amd64/build M=/var/lib/dkms/dm-writeboost/2.2.16/build modules make[1]: Entering directory

Bug#1052772: isoquery: diff for NMU version 3.3.3-1.1

Control: tags 1052772 + patch Dear maintainer, I've prepared an NMU for isoquery (versioned as 3.3.3-1.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru isoquery-3.3.3/debian/changelog isoquery-3.3.3/debian/changelog --- isoquery-3.3.3/debian/changelog

Processed: isoquery: diff for NMU version 3.3.3-1.1

Processing control commands: > tags 1052772 + patch Bug #1052772 [src:isoquery] isoquery: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) patch. -- 1052772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052772 Debian

Processed: bug 1069945 is forwarded to https://github.com/pkoutoupis/rapiddisk/commit/3d7944363e83389d56a82de931e4801d82d99b5f ...

Processing commands for cont...@bugs.debian.org: > forwarded 1069945 > https://github.com/pkoutoupis/rapiddisk/commit/3d7944363e83389d56a82de931e4801d82d99b5f Bug #1069945 [rapiddisk-dkms] rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few

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

Your message dated Sat, 27 Apr 2024 12:21:32 + with message-id and subject line Bug#1052772: fixed in isoquery 3.3.3-1.1 has caused the Debian Bug report #1052772, regarding isoquery: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to

Bug#1069948: python3-pydevd: cannot be installed on Debian testing, unsatisfied dependency on gdb

Package: python3-pydevd Version: 2.10.0+ds-10 Severity: grave Justification: renders package unusable Dear Maintainer, On an up-to-date Debian testing, python3-pydevd cannot be installed because of an unsatisfied dependency on gdb. Best, Amr -- System Information: Debian Release: trixie/sid

Bug#1069923: marked as done (util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel)

Your message dated Sat, 27 Apr 2024 13:26:58 + with message-id and subject line Bug#1069923: fixed in util-linux 2.40-8 has caused the Debian Bug report #1069923, regarding util-linux-extra: /usr-move mitigation fails to cover ctrlaltdel to be marked as done. This means that you claim that

Processed: severity of 1067117 is important

Processing commands for cont...@bugs.debian.org: > severity 1067117 important Bug #1067117 [src:budgie-desktop] budgie-desktop: Fails to build with mutter >= 45 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067117:

Bug#1069935: marked as done (lyskom-elisp-client: missing Build-Depends: emacs)

Your message dated Sat, 27 Apr 2024 13:26:02 + with message-id and subject line Bug#1069935: fixed in lyskom-elisp-client 0.48+git.20231226.364902c3-2 has caused the Debian Bug report #1069935, regarding lyskom-elisp-client: missing Build-Depends: emacs to be marked as done. This means that

Bug#1068598: spice-gtk: diff for NMU version 0.42-2.1

Control: tags 1068598 + patch Dear maintainer, I've prepared an NMU for spice-gtk (versioned as 0.42-2.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru spice-gtk-0.42/debian/changelog spice-gtk-0.42/debian/changelog --- spice-gtk-0.42/debian/changelog

Processed: spice-gtk: diff for NMU version 0.42-2.1

Processing control commands: > tags 1068598 + patch Bug #1068598 [spice-client-gtk] spice-client-gtk - still depends on old libusbredir packages after binnmu Added tag(s) patch. -- 1068598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068598 Debian Bug Tracking System Contact

Bug#1052772: isoquery: diff for NMU version 3.3.3-1.1

Am 27.04.24 um 14:08 schrieb Sebastian Ramacher: Control: tags 1052772 + patch Dear maintainer, I've prepared an NMU for isoquery (versioned as 3.3.3-1.1). The diff is attached to this message. Regards. Hi Sebastian, thanks a lot for your NMU. Unfortunately, the fix from Steve is not

Bug#1064675: marked as pending in adonthell

Control: tag -1 pending Hello, Bug #1064675 in adonthell 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: Bug#1064675 marked as pending in adonthell

Processing control commands: > tag -1 pending Bug #1064675 [src:adonthell] adonthell: FTBFS: mv: cannot stat './adonthell.py': No such file or directory Added tag(s) pending. -- 1064675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064675 Debian Bug Tracking System Contact

Bug#1068598: marked as done (spice-client-gtk - still depends on old libusbredir packages after binnmu)

Your message dated Sat, 27 Apr 2024 16:23:17 + with message-id and subject line Bug#1068598: fixed in spice-gtk 0.42-2.1 has caused the Debian Bug report #1068598, regarding spice-client-gtk - still depends on old libusbredir packages after binnmu to be marked as done. This means that you

Processed: Reassign #1069821

Processing commands for cont...@bugs.debian.org: > reassign 1069821 src:dask Bug #1069821 [src:satpy] satpy: FTBFS: tests failed Bug reassigned from package 'src:satpy' to 'src:dask'. No longer marked as found in versions satpy/0.47.0-2. Ignoring request to alter fixed versions of bug #1069821 to

Bug#1068422: possibly caused by python 3.12.3 Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

On Sun, 21 Apr 2024 13:07:41 +0100 "Rebecca N. Palmer" wrote: This bug is not *obviously* known to dask upstream, but their CI is failing and I haven't checked why. It happens only in Python 3.12, not 3.11: https://ci.debian.net/packages/d/dask/unstable/amd64/45013666/ and still doesn't

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

Your message dated Sat, 27 Apr 2024 16:54:01 + with message-id and subject line Bug#1052772: fixed in isoquery 3.3.4-1 has caused the Debian Bug report #1052772, regarding isoquery: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be

Bug#1066721: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]

Followup-For: Bug #1066721 Control: tag -1 patch I've committed a fix to the git repository. Will followup with a NMU in a few days. I've also enabled the salsa-ci pipeline for the package. Andreas

Processed: Re: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]

Processing control commands: > tag -1 patch Bug #1066721 [src:netcat] netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066721 Debian Bug

Bug#1064675: marked as done (adonthell: FTBFS: mv: cannot stat './adonthell.py': No such file or directory)

Your message dated Sat, 27 Apr 2024 18:34:48 + with message-id and subject line Bug#1064675: fixed in adonthell 0.3.8-3 has caused the Debian Bug report #1064675, regarding adonthell: FTBFS: mv: cannot stat './adonthell.py': No such file or directory to be marked as done. This means that

Bug#1069963: python-nbxmpp: Build-depends on NBS package libglib2.0-0

Source: python-nbxmpp Version: 4.5.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source This package has a hard coded build-depends on libglib2.0-0, which is NBS and the package will FTBFS once it is decrufted. It was renamed libglib2.0-0t64 as part of the 64 bit time

Bug#1069405: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met

Followup-For: Bug #1069405 Control: retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Control: block -1 with 1069408 This happens on all architectures and is probably caused by the missing libxcb-dri3-dev dependency

Processed: Re: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met

Processing control commands: > retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb > xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Bug #1069405 [src:x11-apps] x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes

Bug#1068934: marked as done (perl: autopkgtest failure due to the t64 package rename)

Your message dated Sat, 27 Apr 2024 18:54:19 + with message-id and subject line Bug#1068934: fixed in perl 5.38.2-4 has caused the Debian Bug report #1068934, regarding perl: autopkgtest failure due to the t64 package rename to be marked as done. This means that you claim that the problem

Bug#1034993: software-properties-qt: missing Conflicts+Replaces for software-properties-kde when upgrading from bullseye

Followup-For: Bug #1034993 Control: tag -1 patch pending I'v just uploaded a NMU with the attached changes to DELAYED/14. My intention is to rebuild this for bookworm-pu to get this fixed in a point release. Please let me know if I should delay it longer. Andreas diff --git a/debian/changelog

Processed: Re: software-properties-qt: missing Conflicts+Replaces for software-properties-kde when upgrading from bullseye

Processing control commands: > tag -1 patch pending Bug #1034993 [software-properties-qt] software-properties-qt: missing Conflicts+Replaces for software-properties-kde when upgrading from bullseye Added tag(s) patch and pending. -- 1034993:

Processed: ruby3.1: CVE-2024-27280: Buffer overread vulnerability in StringIO

Processing control commands: > found -1 3.1.2-7 Bug #1069966 [src:ruby3.1] ruby3.1: CVE-2024-27280: Buffer overread vulnerability in StringIO Marked as found in versions ruby3.1/3.1.2-7. -- 1069966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069966 Debian Bug Tracking System Contact

Bug#1069966: ruby3.1: CVE-2024-27280: Buffer overread vulnerability in StringIO

Source: ruby3.1 Version: 3.1.2-8 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.1.2-7 Hi, The following vulnerability was published for ruby3.1. CVE-2024-27280[0]: | Buffer overread

Processed (with 1 error): ruby3.2: CVE-2024-27282

Processing control commands: > clone -1 -2 Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282 Bug 1069968 cloned as bug 1069969 > reassign -2 src;ruby3.1 3.1.2-8 Unknown command or malformed arguments to command. > retitle -2 ruby3.1: CVE-2024-27282 Bug #1069969 [src:ruby3.2] ruby3.2:

Bug#1069968: ruby3.2: CVE-2024-27282

Source: ruby3.2 Version: 3.2.3-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: reassign -2 src;ruby3.1 3.1.2-8 Control: retitle -2 ruby3.1: CVE-2024-27282 Control: found -2 3.1.2-7 Hi,

Processed: reassign 1069969 to src:ruby3.1, found 1069969 in 3.1.2-7

Processing commands for cont...@bugs.debian.org: > reassign 1069969 src:ruby3.1 3.1.2-8 Bug #1069969 [src:ruby3.2] ruby3.1: CVE-2024-27282 Bug reassigned from package 'src:ruby3.2' to 'src:ruby3.1'. No longer marked as found in versions ruby3.2/3.1.2-7 and ruby3.2/3.2.3-1. Ignoring request to

Bug#1067623: marked as done (FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’})

Your message dated Sat, 27 Apr 2024 20:35:02 + with message-id and subject line Bug#1067623: fixed in acm 6.0+20200416-1.2 has caused the Debian Bug report #1067623, regarding FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long

Processed: Re: Bug#1036369: ruby-rest-client: network-dependent tests fail

Processing control commands: > severity -1 serious Bug #1036369 [ruby-rest-client] ruby-rest-client: network-dependent tests fail Severity set to 'serious' from 'normal' -- 1036369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036369 Debian Bug Tracking System Contact

Bug#1069983: dwarf-fortress: Manual build-depends on NBS package libgtk2.0-0

Source: dwarf-fortress Version: 0.47.04+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source The package has a manual build-depends on libgtk2.0-0, which has been replaced by libgtk2.0-0t64. Once it has been decrufted, the package will no longer build. Scott K

Bug#1069963: marked as done (python-nbxmpp: Build-depends on NBS package libglib2.0-0)

Your message dated Sat, 27 Apr 2024 23:47:50 + with message-id and subject line Bug#1069963: fixed in python-nbxmpp 4.5.4-2 has caused the Debian Bug report #1069963, regarding python-nbxmpp: Build-depends on NBS package libglib2.0-0 to be marked as done. This means that you claim that the

Bug#1066743: backblaze-b2: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.12 3.11" returned exit code 13

update is blocked by this https://github.com/TvoroG/pytest-lazy-fixture/issues/65 many duplicates: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=python-pytest-lazy-fixture

Bug#1069985: python-cobra: Manual build-depends on NBS package libsbml5

Source: python-cobra Version: 0.26.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The package build-depends on the NBS package libsbml5. It has been renamed libsbml5t64. Once the package is decrufted, this one will FTBFS. Please

Bug#1069986: dublin-traceroute: Manual build-depends on NBS package libtins4.0

Source: dublin-traceroute Version: 0.4.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The package has a manual build-depends on libtins4.0, which is NBS. It has been renamed libtins4.5. Once it is decrufted, this package will

Bug#1066860: marked as done (libprelude ftbfs on time_t64 archs)

Your message dated Sat, 27 Apr 2024 23:41:56 + with message-id and subject line Bug#1066860: fixed in libprelude 5.2.0-5.5 has caused the Debian Bug report #1066860, regarding libprelude ftbfs on time_t64 archs to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#1060772: python3-jupyterlab: Using node-corepack downloads yarnpkg from Internet

Processing control commands: > severity -1 serious Bug #1060772 [python3-jupyterlab] python3-jupyterlab: Using node-corepack downloads yarnpkg from Internet Severity set to 'serious' from 'important' -- 1060772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060772 Debian Bug Tracking

Bug#1069980: haskell-futhark FTBFS: Missing build dependency on alex

Source: haskell-futhark Version: 0.25.15-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=haskell-futhark=0.25.15-1 ... CallStack (from HasCallStack): withMetadata, called at libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in

Bug#1069982: theli: Manual build-depends on NBS package libcurl4

Source: theli Version: 3.1.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Once libcurl4 is decrufted, the package will no longer build. The libcurl4 package has been replaced by libcurl4t64. Scott K

Bug#1069984: alire: Build-depends on NBS package libgnatcoll21-dev

Source: alire Version: 1.2.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The package libgnatcoll21-dev has been renamed to libgnatcoll-dev. Once libgnatcoll21-dev is decfufted, it will FTBFS. Please update your build depends.