Bug#1096037: mutter: 48's autopkgtests are failing

I have a strong suspicion the issue is https://gitlab.gnome.org/GNOME/mutter/-/issues/3875 and started with https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4022 which was introduced in 48.beta.

Bug#1098793: fixed in refpolicy

severity 1098793 normal thanks This is fixed in refpolicy 2.20250213-1 by depending on the right versions of everything. I'll leave it open for the moment while things are still getting through to testing but I've lowered the priority. -- My Main Blog http://etbe.coker.com.au/ My Docu

Processed: fixed in refpolicy

Processing commands for cont...@bugs.debian.org: > severity 1098793 normal Bug #1098793 [semodule-utils] semodule-utils 3.8-1 breaks selinux-policy-default all: Re-declaration of role unconfined_r Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you

Bug#1098852: notmuch: autopkgtest fails with Emacs 30.1

Source: notmuch Version: 0.38.3-3 Severity: serious Dear maintainer, The notmuch autopkgtest fails with Emacs 30.1, blocking the latter's migration to testing: . Could you take a look? Thanks. -- Sean Whitton signature.asc De

Bug#1098811: couriergrey: Should couriergrey be removed from unstable?

hi all, Am Dienstag, dem 25.02.2025 um 06:35 +0100 schrieb Andreas Tille: > Am Mon, Feb 24, 2025 at 02:38:43PM -0700 schrieb Soren Stoutner: > > I am the maintainer of courier-mta.  couriergrey is abandoned > > upstream and is no longer > > suggested by the upstream courier project.  As such, I h

Bug#1098314: marked as done (Fix DEP8 failure in packages-and-report test case)

Your message dated Tue, 25 Feb 2025 06:04:21 + with message-id and subject line Bug#1098314: fixed in logwatch 7.12-3 has caused the Debian Bug report #1098314, regarding Fix DEP8 failure in packages-and-report test case to be marked as done. This means that you claim that the problem has bee

Processed: fixed upstream

Processing commands for cont...@bugs.debian.org: > close 1091109 Bug #1091109 {Done: Sebastian Ramacher } [src:libsemanage] libsemanage: FTBFS: semanageswig_wrap.c:4209:17: error: too few arguments to function ‘SWIG_Python_AppendOutput’ Bug 1091109 is already marked as done; not doing anything.

Bug#1091109: fixed upstream

close 1091109 thanks The 3.8 upstream release incorporated a fix for this. Sorry for dropping the NMU changelog entry. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1098811: couriergrey: Should couriergrey be removed from unstable?

Hi Soren, Am Mon, Feb 24, 2025 at 02:38:43PM -0700 schrieb Soren Stoutner: > > I am the maintainer of courier-mta. couriergrey is abandoned upstream and is > no longer > suggested by the upstream courier project. As such, I have just uploaded > courier 1.3.13-8, > which removes couriergrey

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

Hello Kevin 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

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

Your message dated Tue, 25 Feb 2025 05:06:08 + with message-id and subject line Bug#1073406: fixed in python-cattrs 24.1.2-1 has caused the Debian Bug report #1073406, regarding python-cattrs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1098846: marked as done (dh-elpa: Incompatibility with Emacs 30+)

Your message dated Tue, 25 Feb 2025 04:34:02 + with message-id and subject line Bug#1098846: fixed in dh-elpa 2.1.6 has caused the Debian Bug report #1098846, regarding dh-elpa: Incompatibility with Emacs 30+ to be marked as done. This means that you claim that the problem has been dealt with

Bug#1098847: meli :FTBFS:build failed (error[E0063]: missing field `modifiers`)

Source: meli Version: 0.8.10+dfsg-2 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear meli maintainer, The package meli build failed on riscv64.The crucial buildd log below: ``` error[E0063]: missing field

Bug#1098846: dh-elpa: Incompatibility with Emacs 30+

Package: dh-elpa Version: 2.1.5 Severity: grave Dear Maintainer, Upstream has removed the internal function `package--prepare-dependencies' since 30.0.90. This causes all addons that have a `Package-Requires:' in the header to causing an error: , | Error: void-function (package--prepare-dep

Bug#1075698: Patch to ygl package (fixing gcc-14 bug)

Hi There, On 24/02/2025 20:01, Pablo Lucas Silva Santos wrote: Hi Chris, Ty to see the patch, On 24/02/2025 19:31, Chris Hofstaedtler wrote: Duplicating these in fortran.c seems to make little sense. Ygl.h defines them, if the preconditions are correctly met. To me this seems to mean there i

Bug#1094947: marked as done (inxi: not installable due to missing dnsutils)

Your message dated Tue, 25 Feb 2025 00:06:41 + with message-id and subject line Bug#1094947: fixed in inxi 3.3.37-1-1.1 has caused the Debian Bug report #1094947, regarding inxi: not installable due to missing dnsutils to be marked as done. This means that you claim that the problem has been

Bug#1094947: marked as done (inxi: not installable due to missing dnsutils)

Your message dated Tue, 25 Feb 2025 00:06:49 + with message-id and subject line Bug#1094947: fixed in inxi 3.3.37-1-2 has caused the Debian Bug report #1094947, regarding inxi: not installable due to missing dnsutils to be marked as done. This means that you claim that the problem has been de

Bug#1098840: virtualbox-dkms: Doesn't build with kernel 6.12.16

Package: virtualbox-dkms Version: 7.0.20-dfsg-1.2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 Dear Maintainer, * What led up to the s

Bug#1084827: marked as done (speech-dispatcher: systemd .service file using Alias= and not symlink)

Your message dated Mon, 24 Feb 2025 20:40:04 + with message-id and subject line Bug#1084827: fixed in speech-dispatcher 0.12.0-2 has caused the Debian Bug report #1084827, regarding speech-dispatcher: systemd .service file using Alias= and not symlink to be marked as done. This means that you

Bug#1075698: Patch to ygl package (fixing gcc-14 bug)

Hi Chris, Ty to see the patch, On 24/02/2025 19:31, Chris Hofstaedtler wrote: On Mon, Feb 24, 2025 at 07:09:01PM -0300, Pablo Lucas Silva Santos wrote: --- ygl-4.2e.orig/fortran.c +++ ygl-4.2e/fortran.c @@ -8,6 +8,12 @@ static const char vcid[] = "$Id: fortran #include "header.h" /* for C

Bug#1089497: gost-crypto-dkms: module fails to build for Linux 6.12: asm/unaligned.h moved to linux/unaligned.h

Followup-For: Bug #1089497 While you fix this, please also set BUILD_EXCLUSIVE_KERNEL_MIN in dkms.conf to document the oldest supported kernel version. See the attached patch for this. Thanks Andreas >From d35e0b78ceb0ea42ad0652a1b53814b308815e59 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann

Bug#1075698: Patch to ygl package (fixing gcc-14 bug)

On Mon, Feb 24, 2025 at 07:09:01PM -0300, Pablo Lucas Silva Santos wrote: > --- ygl-4.2e.orig/fortran.c > +++ ygl-4.2e/fortran.c > @@ -8,6 +8,12 @@ static const char vcid[] = "$Id: fortran > > #include "header.h" /* for COVERSLEEP & string.h */ > > +extern Display *getXdpy ( void ); > +ex

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

On Tue, 18 Feb 2025 13:19:42 +0900 Nobuhiro Iwamatsu wrote: > 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 suppor

Processed: tags 1075698 + patch

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

Bug#1075698: Patch to ygl package (fixing gcc-14 bug)

Hi there, I have worked on this Bug and learning about gcc-14 changes, I saw that the new version of gcc needs to declare implicit functions that was unnecessary on older version of gcc [1]. I'm attaching a patch with the solution and I'll add a tag for Bug, let me see if I help with something

Bug#1098661: linux: fails to boot on VisionFive 2: Unhandled exception: Store/AMO access fault

On 2025-02-24 22:32, Bastian Blank wrote: > On Sat, Feb 22, 2025 at 11:59:38AM +0100, Aurelien Jarno wrote: > > | Loading Linux 6.13-riscv64 ... > > | Loading initial ramdisk ... > > | EFI stub: Decompressing Linux Kernel... > > | Unhandled exception: Store/AMO access fault > > | EPC: fb64a

Bug#1098811: couriergrey: Should couriergrey be removed from unstable?

On Monday, February 24, 2025 9:40:23 AM MST Andreas Tille wrote: > Source: couriergrey > Version: 0.3.2-5 > Severity: serious > Justification: grab attention of maintainer > X-Debbugs-Cc: Marco Balmer , Package Salvaging Team > , Soren Stoutner > > Dear maintainer, > > I suggest removing courier

Bug#1098661: linux: fails to boot on VisionFive 2: Unhandled exception: Store/AMO access fault

On Sat, Feb 22, 2025 at 11:59:38AM +0100, Aurelien Jarno wrote: > | Loading Linux 6.13-riscv64 ... > | Loading initial ramdisk ... > | EFI stub: Decompressing Linux Kernel... > | Unhandled exception: Store/AMO access fault > | EPC: fb64a6ea RA: fb64a6da TVAL: 40020020 > | EP

Bug#1094947: inxi: not installable due to missing dnsutils

* Eriberto Mota [250224 20:56]: > On Mon, 24 Feb 2025 20:11:29 +0100 > Chris Hofstaedtler wrote: > > > * Eriberto Mota [250224 18:10]: > > > > Package: inxi > > > > Version: 3.3.37-1-1 > > > > Severity: serious > > > > > > > > Your package depends on "dnsutils", which is not available anymore.

Bug#1094138: udptunnel: flaky autopkgtest on s390x: UDPTunnel communication failed

Hi there! On Sat, Feb 22, 2025 at 08:16:08PM +0100, Paul Gevers wrote: [...] > To align a time, it easiest to do that on IRC in #debci on oftc. Does that > work for you? > > (Either I or terceiro needs to be on-line while you do this). > > Paul Thanks Paul, terceiro provided access to a testbed

Bug#1092441: marked as done (FTBFS with Python 3.13: error: ‘PyEval_CallObject’ was not declared in this scope)

Your message dated Mon, 24 Feb 2025 20:41:08 + with message-id and subject line Bug#1092441: fixed in zeroc-ice 3.7.10-3.1 has caused the Debian Bug report #1092441, regarding FTBFS with Python 3.13: error: ‘PyEval_CallObject’ was not declared in this scope to be marked as done. This means t

Bug#1084827: [Tts-project] Bug#1084827: speech-dispatcher: systemd .service file using Alias= and not symlink

Hello, Laurent Bigonville, le lun. 24 févr. 2025 14:22:27 +0100, a ecrit: > On Wed, 09 Oct 2024 10:44:59 +0200 Laurent Bigonville > wrote: > > The systemd .service file using Alias= and not symlink but as service is > > not enabled, the symlink is not created. > > > > That means that the LSB scri

Processed: found 1084827 in 0.12.0-1

Processing commands for cont...@bugs.debian.org: > found 1084827 0.12.0-1 Bug #1084827 [speech-dispatcher] speech-dispatcher: systemd .service file using Alias= and not symlink Ignoring request to alter found versions of bug #1084827 to the same values previously set > thanks Stopping processing

Bug#1094947: inxi: not installable due to missing dnsutils

On Mon, 24 Feb 2025 20:11:29 +0100 Chris Hofstaedtler wrote: > * Eriberto Mota [250224 18:10]: > > > Package: inxi > > > Version: 3.3.37-1-1 > > > Severity: serious > > > > > > Your package depends on "dnsutils", which is not available anymore. > > > Please switch to "bind9-dnsutils". > > > > >

Bug#1098800: marked as done (rust-imap-client - debian and cargo depedencies inconsistent.)

Your message dated Mon, 24 Feb 2025 19:51:42 + with message-id and subject line Bug#1098800: fixed in rust-imap-client 0.2.3-3 has caused the Debian Bug report #1098800, regarding rust-imap-client - debian and cargo depedencies inconsistent. to be marked as done. This means that you claim tha

Bug#1093661: marked as done (mumble-server files in mumble client package conflict with mumble-server)

Your message dated Mon, 24 Feb 2025 19:05:07 + with message-id and subject line Bug#1093661: fixed in mumble 1.5.735-3 has caused the Debian Bug report #1093661, regarding mumble-server files in mumble client package conflict with mumble-server to be marked as done. This means that you claim

Bug#1098661: linux: fails to boot on VisionFive 2: Unhandled exception: Store/AMO access fault

On Sun, Feb 23, 2025 at 10:41:44PM +0100, Aurelien Jarno wrote: > > As I currently try to assemble a list of all the interfaces the kernel > > fullfils: How would you define this? Running this in u-boot is not > > (U)EFI, but something more strict, or there is a bug in the kernel > > decompressor

Bug#1092364: [Debian-med-packaging] Bug#1092364: cluster3: needs rebuild for Python 3.13 as default

Hi, cluster3 removal request is open at #1098772 for reference. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/0, please excuse my verbosity `- signature.asc Description: PGP signature

Bug#1094947: inxi: not installable due to missing dnsutils

* Eriberto Mota [250224 18:10]: > > Package: inxi > > Version: 3.3.37-1-1 > > Severity: serious > > > > Your package depends on "dnsutils", which is not available anymore. > > Please switch to "bind9-dnsutils". > > > > Chris > > Hi Chris, > > The inxi only recommends the dnsutils, not depending

Bug#1089817: marked as pending in kaidan

Control: tag -1 pending Hello, Bug #1089817 in kaidan 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/qt-kde-team/extras/kaidan/-/commit/0f61a8d18bd33a1533b32dc

Processed (with 15 errors): unarchiving 1098322, fixed 1098322 in 2.9.1+dfsg1-5+deb8u18, fixed 1098322 in 2.9.4+dfsg1-2.2+deb9u12 ...

Processing commands for cont...@bugs.debian.org: > unarchive 1098322 > fixed 1098322 2.9.1+dfsg1-5+deb8u18 Bug #1098322 [src:libxml2] libxml2: CVE-2025-27113: Null-deref in xmlPatMatch The source 'libxml2' and version '2.9.1+dfsg1-5+deb8u18' do not appear to match any binary packages Marked as fi

Bug#1094238: Accepted libxml2 2.9.10+dfsg-6.7+deb11u6 (source) into oldstable-security

Control: fixed -1 2.9.10+dfsg-6.7+deb11u6 - Forwarded message from Debian FTP Masters - Date: Sat, 22 Feb 2025 11:00:20 + From: Debian FTP Masters To: debian-lts-chan...@lists.debian.org, dispa...@tracker.debian.org Subject: Accepted libxml2 2.9.10+dfsg-6.7+deb11u6 (source) into

Processed: Accepted libxml2 2.9.10+dfsg-6.7+deb11u6 (source) into oldstable-security

Processing control commands: > fixed -1 2.9.10+dfsg-6.7+deb11u6 Bug #1094238 [src:libxml2] libxml2: CVE-2022-49043 The source 'libxml2' and version '2.9.10+dfsg-6.7+deb11u6' do not appear to match any binary packages Marked as fixed in versions libxml2/2.9.10+dfsg-6.7+deb11u6. -- 1094238: https

Bug#1098811: couriergrey: Should couriergrey be removed from unstable?

Source: couriergrey Version: 0.3.2-5 Severity: serious Justification: grab attention of maintainer X-Debbugs-Cc: Marco Balmer , Package Salvaging Team , Soren Stoutner Dear maintainer, I suggest removing couriergrey from Debian for the following reasons: * Bug "#849523 couriergrey needs to be

Bug#1098661: linux: fails to boot on VisionFive 2: Unhandled exception: Store/AMO access fault

Hi, Let me summarize the situation for external reviewers. The kernel for riscv64 used to rely on CONFIG_EFI_STUB=y, enabling the kernel to be used either as an EFI executable or as conventional ELF file. Unlike x86, this requires the kernel to be uncompressed, which is why it was shipped as vmli

Processed: Re: acpi-call-dkms: dkms kernel module fails to build

Processing control commands: > tags -1 ftbfs Bug #1098805 [acpi-call-dkms] acpi-call-dkms: dkms kernel module fails to build Ignoring request to alter tags of bug #1098805 to the same tags previously set > severity -1 normal Bug #1098805 [acpi-call-dkms] acpi-call-dkms: dkms kernel module fails to

Bug#1098805: acpi-call-dkms: dkms kernel module fails to build

Package: acpi-call-dkms Followup-For: Bug #1098805 X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 Control: tags -1 ftbfs Control: severity -1 normal I was confused by the last update date of acpi-call-dkms (22 Feb) and thought my issue was triggered

Processed: Re: python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets'

Processing control commands: > tag -1 +patch Bug #1098606 [src:python-pysmi-lextudio] python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets' Ignoring request to alter tags of bug #1098606 to the same tags previously set -- 1098606: https://bugs.debian.org/

Processed: forcibly merging 1098706 1098814

Processing commands for cont...@bugs.debian.org: > forcemerge 1098706 1098814 Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: not found Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole Bug #1098739 [src:linux] vhba-dkms fails to build

Bug#1090237: marked as done (kaidan: FTBFS: Could not find a configuration file for package "Qt5Core")

Your message dated Mon, 24 Feb 2025 17:38:52 + with message-id and subject line Bug#1090237: fixed in kaidan 0.11.0-1 has caused the Debian Bug report #1090237, regarding kaidan: FTBFS: Could not find a configuration file for package "Qt5Core" to be marked as done. This means that you claim

Bug#1089817: marked as done (kaidan needs a Qt6 port with the KQuickImageEditor transition to Qt6)

Your message dated Mon, 24 Feb 2025 17:38:52 + with message-id and subject line Bug#1089817: fixed in kaidan 0.11.0-1 has caused the Debian Bug report #1089817, regarding kaidan needs a Qt6 port with the KQuickImageEditor transition to Qt6 to be marked as done. This means that you claim that

Processed: [bts-link] source package smifb2

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package smifb2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Bug#1098578: marked as done (mypy: FTBFS: testI64BasicOps fails)

Your message dated Mon, 24 Feb 2025 17:20:41 + with message-id and subject line Bug#1098578: fixed in mypy 1.15.0-4 has caused the Debian Bug report #1098578, regarding mypy: FTBFS: testI64BasicOps fails to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#1089817 marked as pending in kaidan

Processing control commands: > tag -1 pending Bug #1089817 [kaidan] kaidan needs a Qt6 port with the KQuickImageEditor transition to Qt6 Added tag(s) pending. -- 1089817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089817 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1085992: marked as done (gtklock: fails to run "Your compositor doesn't support wlr-input-inhibitor")

Your message dated Mon, 24 Feb 2025 12:12:08 -0500 with message-id and subject line Re: Please provide new upstream version 4.0.0 has caused the Debian Bug report #1085992, regarding gtklock: fails to run "Your compositor doesn't support wlr-input-inhibitor" to be marked as done. This means tha

Bug#1094947: inxi: not installable due to missing dnsutils

> Package: inxi > Version: 3.3.37-1-1 > Severity: serious > > Your package depends on "dnsutils", which is not available anymore. > Please switch to "bind9-dnsutils". > > Chris Hi Chris, The inxi only recommends the dnsutils, not depending on it. What do you think about lowering the severity to

Processed: Bug#1098729 marked as pending in prometheus-pgbouncer-exporter

Processing control commands: > tag -1 pending Bug #1098729 [prometheus-pgbouncer-exporter] prometheus-pgbouncer-exporter has an undeclared file conflict on /usr/bin/pgbouncer_exporter Added tag(s) pending. -- 1098729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098729 Debian Bug Tracking

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

Your message dated Mon, 24 Feb 2025 16:57:26 + with message-id and subject line Bug#1096239: fixed in rust-gdk4-wayland 0.9.6-1 has caused the Debian Bug report #1096239, regarding rust-gdk4-wayland: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be mar

Bug#1098729: marked as pending in prometheus-pgbouncer-exporter

Control: tag -1 pending Hello, Bug #1098729 in prometheus-pgbouncer-exporter 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/go-team/packages/prometheus-pgboun

Bug#1098787: marked as done (rust-gping: Placeholder in Section: field for source)

Your message dated Mon, 24 Feb 2025 16:57:34 + with message-id and subject line Bug#1098787: fixed in rust-gping 1.19.0-2 has caused the Debian Bug report #1098787, regarding rust-gping: Placeholder in Section: field for source to be marked as done. This means that you claim that the problem

Processed: Bug#1098578 marked as pending in mypy

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

Bug#1098578: marked as pending in mypy

Control: tag -1 pending Hello, Bug #1098578 in mypy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/mypy/-/commit/43e5553ca320c5681fbfae8aa

Bug#1098810: pytrainer: FTBFS: ERROR: Could not find a version that satisfies the requirement numpy<2,>=1.21 (from matplotlib) (from versions: none)

Package: src:pytrainer Version: 2.2.1-5 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] adding 'pytrainer-2.2.1.dist-info/t

Processed: unmerging 1098805, reassign 1098805 to acpi-call-dkms

Processing commands for cont...@bugs.debian.org: > unmerge 1098805 Bug #1098805 [src:linux] acpi-call-dkms: dkms kernel module fails to build Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: not found Bug #1098737 [src:linux] virtualbox-dmks: possible missing depend

Bug#1095723: marked as done (bmtk: FTBFS with numpy 2.x)

Your message dated Mon, 24 Feb 2025 16:19:25 + with message-id and subject line Bug#1095723: fixed in bmtk 1.1.1+ds-4 has caused the Debian Bug report #1095723, regarding bmtk: FTBFS with numpy 2.x to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: reassign 1098805 to src:linux, forcibly merging 1098706 1098805, affects 1098706

Processing commands for cont...@bugs.debian.org: > reassign 1098805 src:linux Bug #1098805 [acpi-call-dkms] acpi-call-dkms: dkms kernel module fails to build Bug reassigned from package 'acpi-call-dkms' to 'src:linux'. No longer marked as found in versions acpi-call/1.2.2-2.1. Ignoring request to

Processed: metadata

Processing commands for cont...@bugs.debian.org: > affects 1098592 - src:ironic src:pysmi src:python-pysmi-lextudio > src:python-scciclient src:python-proliantutils Bug #1098592 {Done: Alexandre Detiste } [src:pysmi] pysmi: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' Remov

Processed: python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets'

Processing commands for cont...@bugs.debian.org: > reopen 1098606 Bug #1098606 {Done: Alexandre Detiste } [src:python-pysmi-lextudio] python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets' 'reopen' may be inappropriate when a bug has been closed with a vers

Bug#1098736: ibus 1.5.32~beta2-2 breaks + on US intl layout

Also funnily enough, `apt purge ibus` (and related packages) then `rm -r ~/.config/ibus ~/.cache/ibus` solves the issue as well, I guess in that case GNOME falls back to some internal IM handler? Honestly inscrutable to me what the physics of the whole thing is, but removing ibus altogether gives m

Bug#1098736: ibus 1.5.32~beta2-2 breaks + on US intl layout

On Mon, Feb 24, 2025 at 04:12:43PM +0100, наб wrote: > So the breakage was intentional upstream. > I don't believe this to be acceptable and I'll try to conjure up a patch for > this. After a careful examination of the source code, I do not belive it's possible to add "include %L" if upgrading (t

Processed: affects 1094947

Processing commands for cont...@bugs.debian.org: > affects 1094947 forensics-extra Bug #1094947 [inxi] inxi: not installable due to missing dnsutils Added indication that 1094947 affects forensics-extra > thanks Stopping processing here. Please contact me if you need assistance. -- 1094947: http

Bug#1098602: marked as done (python-persistent: FTBFS: error: 'cPersistentObject' has no member named 'ob_refcnt')

Your message dated Mon, 24 Feb 2025 15:51:26 + with message-id and subject line Bug#1098602: fixed in python-persistent 6.1-2 has caused the Debian Bug report #1098602, regarding python-persistent: FTBFS: error: 'cPersistentObject' has no member named 'ob_refcnt' to be marked as done. This m

Processed: bug 1098578 is forwarded to https://github.com/python/mypy/issues/18610

Processing commands for cont...@bugs.debian.org: > forwarded 1098578 https://github.com/python/mypy/issues/18610 Bug #1098578 [src:mypy] mypy: FTBFS: testI64BasicOps fails Set Bug forwarded-to-address to 'https://github.com/python/mypy/issues/18610'. > thanks Stopping processing here. Please cont

Processed: Bug#1098602 marked as pending in python-persistent

Processing control commands: > tag -1 pending Bug #1098602 [src:python-persistent] python-persistent: FTBFS: error: 'cPersistentObject' has no member named 'ob_refcnt' Added tag(s) pending. -- 1098602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098602 Debian Bug Tracking System Contact

Bug#1098602: marked as pending in python-persistent

Control: tag -1 pending Hello, Bug #1098602 in python-persistent reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-persistent/-/commit

Processed: Re: Bug#1098736: ibus 1.5.32~beta2-2 breaks + on US intl layout

Processing control commands: > forcemerge -1 1098792 Bug #1098736 [ibus] ibus 1.5.32~beta2-2 breaks + on US intl layout Bug #1098792 [ibus] ibus: Dead keys on french keyboard no longer accept spaces Set Bug forwarded-to-address to 'https://github.com/ibus/ibus/issues/2727'. Severity set to 'gra

Bug#1098736: ibus 1.5.32~beta2-2 breaks + on US intl layout

Control: forcemerge -1 1098792 In discussion under forwarded, we can see that > But if user does not have the compose file, IBus won't touch it. > I thought this case and it's now timeout. And naturally the release notes https://github.com/ibus/ibus/releases/tag/1.5.32-beta2 say > Your compose

Processed: version

Processing commands for cont...@bugs.debian.org: > notfound 1083075 openshot-qt/3.1.1+dfsg1-1 Bug #1083075 {Done: Bastian Germann } [openshot-qt] openshot-qt: fails to start: AttributeError: module 'eventlet.green.select' has no attribute 'epoll' No longer marked as found in versions openshot-qt

Bug#1098805: acpi-call-dkms: dkms kernel module fails to build

Package: acpi-call-dkms Version: 1.2.2-2.1 Severity: serious Tags: ftbfs Justification: FTBFS Upgrading to 1.2.2-2.1, acpi-call-dkms is failing to build kernel modules, complaining about existing source: Setting up acpi-call-dkms (1.2.2-2.1) ... Removing old acpi-call/1.2.2 DKMS files... Loading

Bug#1083075: marked as done (openshot-qt: fails to start: AttributeError: module 'eventlet.green.select' has no attribute 'epoll')

Your message dated Mon, 24 Feb 2025 15:35:37 +0100 with message-id <106f61c5-32d9-46ff-abc9-9daacbfb1...@debian.org> and subject line Re: openshot-qt: fails to start: AttributeError: module 'eventlet.green.select' has no attribute 'epoll' has caused the Debian Bug report #1083075, regarding opensh

Bug#1085045: Fix for this bug

Hello ! Please apply this attached patch to fix this bug. From f4fc2c19361a91798bfa6be87312be3863bc3f84 Mon Sep 17 00:00:00 2001 From: "nicolas.maillet-contoz" Date: Mon, 24 Feb 2025 15:07:01 +0100 Subject: [PATCH] Add breaks + replaces libcfitsio-dev (<< 4.5.0-5~) (Closes: #1085045). --- debi

Processed: metadata

Processing commands for cont...@bugs.debian.org: > # Increasing severity because it breaks other package(s). > severity 1098389 important Bug #1098389 [golang-1.24] golang-1.24: Please install (again) wasm_exec.js Severity set to 'important' from 'normal' > # Restoring serious severity for golang-

Bug#1098246: sympy: autopkgtest failures

Emilio wrote: > This is blocking the numpy transition. I triggered the autopkgtests of sympy/1.13.3-1 in testing with numpy from unstable, and they passed on armel [1] and ppc64el [2]. I don't think the numpy transition is blocked by this, only sympy itself by its test failures introduced by the

Processed: Re: r-cran-git2r: FTBFS: git2r_deprecated.h:54:30: error: implicit declaration of, function ‘git_error_set_str’

Processing commands for cont...@bugs.debian.org: > fixed 1084352 0.35.0-1 Bug #1084352 {Done: "Michael R. Crusoe" } [src:r-cran-git2r] r-cran-git2r: FTBFS: git2r_deprecated.h:54:30: error: implicit declaration of function ‘git_error_set_str’; did you mean ‘giterr_set_str’? [-Wimplicit-function-

Processed: severity of 1096251 is important

Processing commands for cont...@bugs.debian.org: > severity 1096251 important Bug #1096251 [src:golang-github-evanw-esbuild] golang-github-evanw-esbuild: FTBFS: make[1]: *** [debian/rules:36: execute_after_dh_auto_build-arch] Error 1 Severity set to 'important' from 'serious' > thanks Stopping pr

Processed: found 1084827 in 0.12.0-1

Processing commands for cont...@bugs.debian.org: > found 1084827 0.12.0-1 Bug #1084827 {Done: Michael Biebl } [speech-dispatcher] speech-dispatcher: systemd .service file using Alias= and not symlink Marked as found in versions speech-dispatcher/0.12.0-1 and reopened. > thanks Stopping processing

Bug#1084827: speech-dispatcher: systemd .service file using Alias= and not symlink

On Wed, 09 Oct 2024 10:44:59 +0200 Laurent Bigonville wrote: [...] > > Hello, > > The systemd .service file using Alias= and not symlink but as service is > not enabled, the symlink is not created. > > That means that the LSB script and the systemd service are not linked > together. > > This cou

Bug#1098800: rust-imap-client - debian and cargo depedencies inconsistent.

Package: rust-imap-client Version: 0.1.5 Severity: serious I recently introduced a semver-suffix package rust-tokio-rustls-0.24, and updated the main rust-tokio-rustls package to 0.26. Unfortunately rust-imap-client's debian dependency is inconsistent with it's cargo dependency. The Debian dep

Bug#1098525: marked as done (dh-fortran-mod: Several packages having dh-fortran-mod in their build-depends currently FTBFS)

Your message dated Mon, 24 Feb 2025 12:18:59 + with message-id and subject line Bug#1098525: fixed in dh-fortran-mod 0.43 has caused the Debian Bug report #1098525, regarding dh-fortran-mod: Several packages having dh-fortran-mod in their build-depends currently FTBFS to be marked as done. T

Bug#1064921: marked as done (src:r-cran-estimatr: fails to migrate to testing for too long: autopkgtest regression on i386)

Your message dated Mon, 24 Feb 2025 11:37:01 + with message-id and subject line Bug#1064921: fixed in r-cran-estimatr 1.0.4-2 has caused the Debian Bug report #1064921, regarding src:r-cran-estimatr: fails to migrate to testing for too long: autopkgtest regression on i386 to be marked as done

Bug#1084352: marked as done (r-cran-git2r: FTBFS: git2r_deprecated.h:54:30: error: implicit declaration of function ‘git_error_set_str’; did you mean ‘giterr_set_str’? [-Wimplicit-function-declaration

Your message dated Mon, 24 Feb 2025 12:37:09 +0100 with message-id and subject line Re: r-cran-git2r: FTBFS: git2r_deprecated.h:54:30: error: implicit declaration of function ‘git_error_set_str’; did you mean ‘giterr_set_str’? [-Wimplicit-function-declaration] has caused the Debian Bug report #1

Bug#1064921: marked as pending in r-cran-estimatr

Control: tag -1 pending Hello, Bug #1064921 in r-cran-estimatr 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/r-pkg-team/r-cran-estimatr/-/commit/e98571dcafc82

Processed: reassign 1098794 to src:linux, forcibly merging 1098706 1098794, affects 1098706

Processing commands for cont...@bugs.debian.org: > reassign 1098794 src:linux Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing? Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: not found Bug #1098737 [src:linux] virtualbox-dmks: possible missing de

Processed: Bug#1064921 marked as pending in r-cran-estimatr

Processing control commands: > tag -1 pending Bug #1064921 [src:r-cran-estimatr] src:r-cran-estimatr: fails to migrate to testing for too long: autopkgtest regression on i386 Added tag(s) pending. -- 1064921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064921 Debian Bug Tracking System C

Processed: another dkms pahole bug

Processing commands for cont...@bugs.debian.org: > reassign 1098794 src:linux Bug #1098794 [v4l2loopback-dkms] FTBFS: pahole Build-Deps might be missing? Bug reassigned from package 'v4l2loopback-dkms' to 'src:linux'. No longer marked as found in versions v4l2loopback/0.13.2-1. Ignoring request to

Bug#1098794: FTBFS: pahole Build-Deps might be missing?

Package: v4l2loopback-dkms Version: 0.13.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is my failure log: /var/lib/dkms/v4l2loopback/0.13.2/build/make.log DKMS (dkms-3.1.5) mak

Processed: block 1082237 with 1098247 1098246

Processing commands for cont...@bugs.debian.org: > block 1082237 with 1098247 1098246 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 1088823 1091809 1091938 1092781 1094109 1094332 1094369 1094370 1094371 1094372 1094373 1094374 1094375 1094376 1094377 1094477 10944

Processed: unblock 1095723 with 1098247 1098246

Processing commands for cont...@bugs.debian.org: > unblock 1095723 with 1098247 1098246 Bug #1095723 [src:bmtk] bmtk: FTBFS with numpy 2.x 1095723 was blocked by: 1098246 1098247 1095723 was not blocking any bugs. Removed blocking bug(s) of 1095723: 1098247 and 1098246 > thanks Stopping processing

Processed: unblock 1082237 with 1063599 1066316 1067335 1071807 1086577 1086578 1088707 1090292 1092083 1094757 1094928 1094984 1095085 1095090 1095091 1095092 1095723 ...

Processing commands for cont...@bugs.debian.org: > unblock 1082237 with 1063599 1066316 1067335 1071807 1086577 1086578 1088707 > 1090292 1092083 1094757 1094928 1094984 1095085 1095090 1095091 1095092 > 1095723 Bug #1082237 [release.debian.org] transition: numpy 2 1082237 was blocked by: 106359

Bug#1094704: marked as done (r-cran-fastcluster: FTBFS with numpy 2.x: tests failed)

Your message dated Mon, 24 Feb 2025 10:35:32 + with message-id and subject line Bug#1094704: fixed in r-cran-fastcluster 1.2.6-2 has caused the Debian Bug report #1094704, regarding r-cran-fastcluster: FTBFS with numpy 2.x: tests failed to be marked as done. This means that you claim that the

  1   2   >