Bug#1082200: marked as pending in python-bytecode

Control: tag -1 pending Hello, Bug #1082200 in python-bytecode 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-bytecode/-/commit/d73

Processed: unarchiving 1077521, reopening 1077521, notfixed 1077521 in 3.1.0+ds-2+rm, tagging 1077521

Processing commands for cont...@bugs.debian.org: > unarchive 1077521 Bug #1077521 {Done: Debian FTP Masters } [src:pydevd] pydevd: FTBFS: make[1]: *** [debian/rules:24: _pydevd_bundle/pydevd_runpy.py] Error 1 Unarchived Bug 1077521 > reopen 1077521 Bug #1077521 {Done: Debian FTP Masters } [src:

Processed: Bug#1082200 marked as pending in python-bytecode

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

Processed (with 1 error): unarchiving 1082200, reopening 1082200, notfixed 1082200 in 0.15.1-3+rm, tagging 1082200

Processing commands for cont...@bugs.debian.org: > unarchive 1082200 > reopen 1082200 Bug #1082200 {Done: Debian FTP Masters } [src:python-bytecode] python-bytecode FTBFS with Python 3.13 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Bug#1098930: xref-el: Proposed removal of this separate package

Source: xref-el Version: 1.7.0-2 Severity: serious Tags: trixie sid Hello, I propose to remove this package. This bug is to ensure we don't ship it with trixie. See . eglot should be able to just drop its dependency on this package

Bug#1098929: seq-el: Keep out of testing pending removal, won't be in trixie

Source: seq-el Version: 2.24-2 Severity: serious Tags: trixie sid Upstream have decided that seq.el is stable enough that new versions won't be distributed separately from Emacs: ;; Note regarding the `seq' package on GNU ELPA: ;; ;; It was decided not to bother upgrading seq beyond 2.24 on GNU E

Bug#1098931: project-el: Proposed removal of this separate package

Source: project-el Version: 1.7.0-2 Severity: serious Tags: trixie sid Hello, I propose to remove this package. This bug is to ensure we don't ship it with trixie. See . eglot should be able to just drop its dependency on this packa

Processed: Re: Bug#1098913 closed by Rene Engelhard (Re: Bug#1098913: 113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry)

Processing control commands: > reopen -1 Bug #1098913 {Done: Rene Engelhard } [libreoffice-l10n-ug,libreoffice-impress,libreoffice-l10n-ast,libreoffice-l10n-nb,libreoffice-report-builder,libreoffice-l10n-gu,libreoffice-l10n-ml,libreoffice-l10n-gd,libreoffice-l10n-zh-tw,libreoffice-l10n-bg,libreof

Bug#1098913: closed by Rene Engelhard (Re: Bug#1098913: 113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry)

Control: reopen -1 On Tue, Feb 25, 2025 at 10:30:02PM +, Debian Bug Tracking System wrote: > > The file /usr/lib/libreoffice/share/registry is contained in the > > packages > > * libreoffice-base/4:25.2.1~rc2-1 as present in experimental > > * libreoffice-base-nogui/4:25.2.1~rc2-1 as prese

Bug#1098923: marked as done (ipxe: Build-Depends uninstallable on arch:all)

Your message dated Wed, 26 Feb 2025 06:19:28 + with message-id and subject line Bug#1098923: fixed in ipxe 1.21.1+git20250224.12ea8c40+dfsg-1 has caused the Debian Bug report #1098923, regarding ipxe: Build-Depends uninstallable on arch:all to be marked as done. This means that you claim that

Bug#1098923: ipxe: Build-Depends uninstallable on arch:all

Source: ipxe Version: 1.21.1+git20250207.bd90abf4+dfsg-1 Severity: serious Tags: ftbfs The arch:all buildd cannot build ipxe, because: Dependency installability problem for ipxe on all: ipxe build-depends on: - qemu-system-x86:amd64 qemu-system-x86 depends on missing: - ipxe-qemu:amd64

Bug#1098905: elpa-key-chord: incompatibility with Gnu Emacs 30

Hi Thorsten, Key-chord.el has been orphaned in Debian and needs a new maintainer. https://bugs.debian.org/1007866 Regards, Nicholas signature.asc Description: PGP signature

Bug#1098255: Backporting in progress

Hello, I'm now in the middle of backporting the fixes for these two CVES to bookworm, generously funded by the Freexian LTS project. bullseye to follow. -- Sean Whitton signature.asc Description: PGP signature

Bug#1075709: marked as done (zziplib: ftbfs with GCC-14)

Your message dated Tue, 25 Feb 2025 23:51:29 + with message-id and subject line Bug#1075709: fixed in zziplib 0.13.78+dfsg.1-0.1 has caused the Debian Bug report #1075709, regarding zziplib: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with

Processed: retitle 1088400 to libept: do not ship in trixie [ftbfs + RoM]

Processing commands for cont...@bugs.debian.org: > retitle 1088400 libept: do not ship in trixie [ftbfs + RoM] Bug #1088400 [src:libept] libept: FTBFS: error: expected constructor, destructor, or type conversion before ‘;’ token Changed Bug title to 'libept: do not ship in trixie [ftbfs + RoM]' f

Bug#1098902: marked as done (marble: Workaround for the build on armhf)

Your message dated Tue, 25 Feb 2025 23:07:35 + with message-id and subject line Bug#1098902: fixed in marble 4:24.12.2-3 has caused the Debian Bug report #1098902, regarding marble: Workaround for the build on armhf to be marked as done. This means that you claim that the problem has been dea

Bug#1096216: marked as done (libatomic-queue: FTBFS: collect2: fatal error: cannot find ‘ld’)

Your message dated Tue, 25 Feb 2025 22:49:13 + with message-id and subject line Bug#1096216: fixed in libatomic-queue 1.6.5-2 has caused the Debian Bug report #1096216, regarding libatomic-queue: FTBFS: collect2: fatal error: cannot find ‘ld’ to be marked as done. This means that you claim th

Bug#1098910: modsecurity: CVE-2025-27110

Hi Salvatore, On Tue, Feb 25, 2025 at 10:29:40PM +0100, Salvatore Bonaccorso wrote: > Source: modsecurity > Version: 3.0.13-1 > Severity: grave > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerability was published for modsecu

Bug#1098548: marked as done (gnustep-gui: FTBFS: make[1]: *** [debian/rules:76: override_dh_auto_test] Error 1)

Your message dated Wed, 26 Feb 2025 00:21:44 +0200 with message-id <87frk1mzrb.GNU's_not_UNIX!-ya...@gnu.org> and subject line Re: Bug#1098548: gnustep-gui: FTBFS: make[1]: *** [debian/rules:76: override_dh_auto_test] Error 1 has caused the Debian Bug report #1098548, regarding gnustep-gui: FTBFS:

Bug#1098913: marked as done (113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry)

Your message dated Tue, 25 Feb 2025 23:28:09 +0100 with message-id <2fd0351a-c61b-4037-b2d9-43d445a67...@debian.org> and subject line Re: Bug#1098913: 113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry has caused the Debian Bug report #1098913, re

Bug#1098549: marked as done (gnustep-base: FTBFS: make[1]: *** [debian/rules:117: override_dh_auto_test] Error 1)

Your message dated Wed, 26 Feb 2025 00:19:27 +0200 with message-id <87h64hmzv4.GNU's_not_UNIX!-ya...@gnu.org> and subject line Re: Bug#1098549: gnustep-base: FTBFS: make[1]: *** [debian/rules:117: override_dh_auto_test] Error 1 has caused the Debian Bug report #1098549, regarding gnustep-base: FTB

Processed: 113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry

Processing control commands: > affects -1 + libreoffice-common Bug #1098913 [libreoffice-l10n-ug,libreoffice-impress,libreoffice-l10n-ast,libreoffice-l10n-nb,libreoffice-report-builder,libreoffice-l10n-gu,libreoffice-l10n-ml,libreoffice-l10n-gd,libreoffice-l10n-zh-tw,libreoffice-l10n-bg,libreoffi

Processed: Re: Bug#1091864: tech-ctte: Avahi vs systemd-resolved vote concluded

Processing control commands: > clone -1 -2 Bug #1091864 [tech-ctte] tech-ctte: Avahi and systemd-resolved cannot a run mDNS responder at the same time Bug 1091864 cloned as bug 1098914 1077937 was blocked by: 1091864 1077937 was not blocking any bugs. Added blocking bug(s) of 1077937: 1098914 > r

Bug#1098913: 113 packages from libreoffice have an undeclared file conflict on /usr/lib/libreoffice/share/registry

Package: libreoffice-l10n-ug,libreoffice-impress,libreoffice-l10n-ast,libreoffice-l10n-nb,libreoffice-report-builder,libreoffice-l10n-gu,libreoffice-l10n-ml,libreoffice-l10n-gd,libreoffice-l10n-zh-tw,libreoffice-l10n-bg,libreoffice-l10n-br,libreoffice-math,libreoffice-l10n-ru,libreoffice-l10n-hr,l

Bug#1098910: modsecurity: CVE-2025-27110

Source: modsecurity Version: 3.0.13-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for modsecurity. CVE-2025-27110[0]: | Libmodsecurity is one component of the ModSecurity v3 project. The | library co

Bug#1098852: marked as done (notmuch: FTBFS: 3 tests fail against Emacs 30.1)

Your message dated Tue, 25 Feb 2025 21:20:29 + with message-id and subject line Bug#1098852: fixed in notmuch 0.38.3-4 has caused the Debian Bug report #1098852, regarding notmuch: FTBFS: 3 tests fail against Emacs 30.1 to be marked as done. This means that you claim that the problem has been

Bug#1087809: Bug#1086028: I've reproduced the bug in QEMU

Hi Salvatore, On Tue, Feb 25, 2025, 19:36 Salvatore Bonaccorso wrote: > Hi Sergei, > > Can you test the two patched attached instead please? > > I'm on it. Cheers! -- Sergei Golovan

Bug#1098852: marked as done (notmuch: FTBFS: 3 tests fail against Emacs 30.1)

Your message dated Tue, 25 Feb 2025 21:06:37 + with message-id and subject line Bug#1098852: fixed in notmuch 0.39~rc1-1 has caused the Debian Bug report #1098852, regarding notmuch: FTBFS: 3 tests fail against Emacs 30.1 to be marked as done. This means that you claim that the problem has be

Bug#1098909: passenger: CVE-2025-26803

Source: passenger Version: 6.0.24+ds-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for passenger. CVE-2025-26803[0]: | The http parser in Phusion Passenger 6.0.21 th

Bug#1098906: xorg-server: CVE-2025-26594 CVE-2025-26595 CVE-2025-26596 CVE-2025-26597 CVE-2025-26598 CVE-2025-26599 CVE-2025-26600 CVE-2025-26601

Source: xorg-server Version: 2:21.1.15-3 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2:21.1.7-3 Control: fixed -1 2:21.1.7-3+deb12u9 Hi, The following vulnerabilities were published for xorg-server. CVE-2025-26594[0]: | A use-a

Processed: xorg-server: CVE-2025-26594 CVE-2025-26595 CVE-2025-26596 CVE-2025-26597 CVE-2025-26598 CVE-2025-26599 CVE-2025-26600 CVE-2025-26601

Processing control commands: > found -1 2:21.1.7-3 Bug #1098906 [src:xorg-server] xorg-server: CVE-2025-26594 CVE-2025-26595 CVE-2025-26596 CVE-2025-26597 CVE-2025-26598 CVE-2025-26599 CVE-2025-26600 CVE-2025-26601 Marked as found in versions xorg-server/2:21.1.7-3. > fixed -1 2:21.1.7-3+deb12u9

Bug#1092509: marked as done (nml: FTBFS: make[3]: *** [Makefile:24: 001_action8] Error 1)

Your message dated Tue, 25 Feb 2025 20:37:23 + with message-id and subject line Bug#1092509: fixed in nml 0.7.6-1 has caused the Debian Bug report #1092509, regarding nml: FTBFS: make[3]: *** [Makefile:24: 001_action8] Error 1 to be marked as done. This means that you claim that the problem h

Bug#1098905: elpa-key-chord: incompatibility with Gnu Emacs 30

Package: elpa-key-chord Version: 0.6-7 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@not-in-kansas-anymore.org Dear Maintainer, key-chord.el is using the obsolete calling convention of 'sit-for' on line 340. As of GNU Emacs 30, the function 'sit-for' has two arguments

Bug#1098852: [PATCH] test/emacs: add workaround for Emacs 30 pp changes

Tomi Ollila writes: > On Tue, Feb 25 2025, David Bremner wrote: > >> This relies on the fact that setting pp-default-function has no effect >> for Emacs <30. > > I think this close to a release (and maybe for a while later) this is LGTM. > > Tomi Applied to release and master. Someone suggested

Bug#1094811:

This does not reproduce for me on recent trixie. Neither 2.25.1 nor 2.25.2 nor latest 2.25.5. Also building seems to work in the Debian build-infrastructure according to https://tracker.debian.org/pkg/devscripts Your output looks like building is done in parallel, are there some additional option

Bug#1098902: marble: Workaround for the build on armhf

Source: marble Version: 4:24.12.2-2 Severity: serious Tags: ftbfs patch X-Debbugs-Cc: 1098741-d...@bugs.debian.org Below is a patch workarounding the FTBFS on armhf. diff -Nru marble-24.12.2/debian/control marble-24.12.2/debian/control --- marble-24.12.2/debian/control 2025-02-19 13:55:25.

Bug#1074850: [PATCH] Fix implicit int type errors in lex.c for GCC 14 compatibility

Hi There, I am submitting a patch to address the implicit int type errors in the `lex.c` file, which occur when compiling with GCC 14. The errors were due to missing type declarations for function parameters, which are no longer implicitly assumed in GCC 14 [1] The patch includes the followi

Processed: tags 1074850 + patch

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

Bug#1098507: python-click: Please revert the upload of the unreleased 8.2 version to unstable

On Mon, Feb 24, 2025 at 12:58:16AM +, Colin Watson wrote: > On Fri, Feb 21, 2025 at 02:34:12PM -0700, Soren Stoutner wrote: > > Just to add a bit of additional information, 8.2.0 has been tagged but not > > released, which > > was probably the confusion that caused it to be uploaded to unstab

Bug#1098898: satdump: Build dependency libomp-dev no longer available on i386

Source: satdump Version: 1.2.0-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian OpenCL team The build dependency libomp-dev is no longer available on i386. While not strictly part of this bug, a question to the Debian OpenCL team is whether intel-graphics-compiler2 and intel-compute-runtime

Bug#1098897: librust-tonic-dev: Uninstallable in unstable: Depends: librust-axum-0.6-dev but it is not installable

Package: librust-tonic-dev Version: 0.10.2+dfsg-12 Severity: serious Justification: Breaks compilation of depending packages When trying to use librust-tonic-dev as a build dependencies, it fails to install with: Install main build dependencies (apt-based resolver) ---

Bug#1098896: xtables-addons: dkms and module-assistant updates

Source: xtables-addons Version: 3.27-3 Severity: serious Tags: patch Justification: -source is currently unable to build modules Hi, I have a few updates for the dkms and module-assistant support of this package. The -source package currently fails to build module packages. This is fixed and an a

Processed: closing 1081100

Processing commands for cont...@bugs.debian.org: > close 1081100 24.35.30872.14-1 Bug #1081100 [intel-compute-runtime] satdump: FTBFS: unsatisfiable build-depends There is no source info for the package 'intel-compute-runtime' at version '24.35.30872.14-1' with architecture '' Unable to make a so

Processed: severity

Processing commands for cont...@bugs.debian.org: > severity 1087970 normal Bug #1087970 [ftp.debian.org] RM: pep8 -- ROM; was renamed pycodestyle many years ago Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 10879

Processed: tagging 1086028

Processing commands for cont...@bugs.debian.org: > tags 1086028 - unreproducible Bug #1086028 [src:linux] loupe: FTBFS on mips64el: failed to acquire jobserver token: Bad address (os error 14) Bug #1087809 [src:linux] cargo: [mipsel64] failed to acquire jobserver token/Bad address (os error 14)

Bug#1086028: I've reproduced the bug in QEMU

Hi Sergei, On Thu, Feb 13, 2025 at 01:35:13PM +0300, Sergei Golovan wrote: > tag 1086028 + patch > tag 1087809 + patch > tag 1093200 + patch > thanks > > Hi! > > I've finally managed to reproduce this EFAULT in QEMU (using an > Erlang-based script which is shipped in the wings3d source package):

Bug#1098852: [PATCH] test/emacs: add workaround for Emacs 30 pp changes

On Tue, Feb 25 2025, David Bremner wrote: > This relies on the fact that setting pp-default-function has no effect > for Emacs <30. I think this close to a release (and maybe for a while later) this is LGTM. Tomi > --- > test/test-lib.el | 3 +++ > 1 file changed, 3 insertions(+) > > diff --gi

Bug#1093200: mips64el in trixie: [was: Bug#1093200: Some packages consistently FTBFS with EFAULT (Bad address) on most mips64el buildds]

On Sun, Feb 16, 2025 at 09:14:24PM +0100, Paul Gevers wrote: >... > I also like to hear your view on the topic of the Debian hosts, like it was > raised in bug 1050872. I understand that there are difficulties upgrading > existing hardware to bookworm (and later) kernels. Some hosts apparently are

Bug#1098886: gbemol: Should gbemol be removed from unstable?

Source: gbemol Version: 0.3.2-2 Severity: serious Justification: grab attention of maintainer X-Debbugs-Cc: Andrea Colangelo , Andrea Colangelo , 967...@bugs.debian.org, 469...@bugs.debian.org, Package Salvaging Team Dear maintainer, I suggest removing gbemol from Debian for the following reas

Bug#1095391: marked as done (smartmontools: FTBFS: GNU Automake 1.10 (up to 1.16) is required to bootstrap smartmontools from SVN.)

Your message dated Tue, 25 Feb 2025 12:35:06 + with message-id and subject line Bug#1095391: fixed in smartmontools 7.4-3 has caused the Debian Bug report #1095391, regarding smartmontools: FTBFS: GNU Automake 1.10 (up to 1.16) is required to bootstrap smartmontools from SVN. to be marked as

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

Your message dated Tue, 25 Feb 2025 12:21:13 + with message-id and subject line Bug#1098847: fixed in meli 0.8.10+dfsg-3 has caused the Debian Bug report #1098847, regarding meli :FTBFS:build failed (error[E0063]: missing field `modifiers`) to be marked as done. This means that you claim that

Bug#1098877: autopkgtest failure on riscv64, preventing testing migration

Package: bdebstrap Version: 0.7.0-2 Severity: serious AIUI bdebstrap's autopkgtests are attempting to deploy a bullseye system, using deb.debian.org as its source. riscv64 was not an official port for bullseye and there is no such suite in the archive for this architecture. This results in this t

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

On Mon, Feb 24, 2025 at 10:50:58PM +0100, Aurelien Jarno wrote: > It works fine when the kernel is directly started from U-Boot with > bootefi. It only fails when U-Boot launches Grub and Grub launches the > EFI file. Okay, so exactly the one use case "hardware -> u-boot -> grub -> kernel" does no

Bug#1098875: python-ml-collections: autopkgtests fail: cp: cannot create regular file 'ml_collections/config_dict/tests/BUILD': No such file or directory

Source: python-ml-collections Version: 1.0.0-1 Severity: serious https://ci.debian.net/packages/p/python-ml-collections/testing/amd64/58124703/ and can be reproduced locally. autopkgtest [17:00:47]: test run-unit-test: [--- cp: cannot create regular file 'ml_collections/config

Bug#1098852: [PATCH] test/emacs: add workaround for Emacs 30 pp changes

This relies on the fact that setting pp-default-function has no effect for Emacs <30. --- test/test-lib.el | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/test-lib.el b/test/test-lib.el index 4cfb8ef1..bf1fab66 100644 --- a/test/test-lib.el +++ b/test/test-lib.el @@ -33,6 +33,9 @@ (

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

Processing control commands: > tag -1 pending Bug #1098847 [src:meli] meli :FTBFS:build failed (error[E0063]: missing field `modifiers`) Added tag(s) pending. -- 1098847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098847 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

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

Control: tag -1 pending Quoting Manos Pitsidianakis (2025-02-25 10:40:28) > On Tue, 25 Feb 2025 04:20, Yue Gui wrote: > >The full buildd log is here: > >https://buildd.debian.org/status/fetch.php?pkg=meli&arch=riscv64&ver=0.8.10%2Bdfsg-2%2Bb1&stamp=1740301953&raw=0 > >My solution to this issue: >

Bug#1098852: notmuch: autopkgtest fails with Emacs 30.1

control: retitle -1 notmuch: FTBFS: 3 tests fail against Emacs 30.1 This is actually an FTBFS. -- Sean Whitton signature.asc Description: PGP signature

Processed: Re: notmuch: autopkgtest fails with Emacs 30.1

Processing control commands: > retitle -1 notmuch: FTBFS: 3 tests fail against Emacs 30.1 Bug #1098852 [src:notmuch] notmuch: autopkgtest fails with Emacs 30.1 Changed Bug title to 'notmuch: FTBFS: 3 tests fail against Emacs 30.1' from 'notmuch: autopkgtest fails with Emacs 30.1'. -- 1098852: h

Bug#1091496: dns-root-data: will FTBFS during trixie support period

severity 1091496 normal reopen 1091496 thanks El 22/2/25 a las 18:20, Marco d'Itri escribió: On Dec 27, Santiago Vila wrote: During a rebuild of all packages in unstable in the year 2028, your package failed to build: This is expected, due to its specific nature. If it will be needed to reb

Processed: Re: Bug#1091496: dns-root-data: will FTBFS during trixie support period

Processing commands for cont...@bugs.debian.org: > severity 1091496 normal Bug #1091496 {Done: Marco d'Itri } [src:dns-root-data] dns-root-data: will FTBFS during trixie support period Severity set to 'normal' from 'serious' > reopen 1091496 Bug #1091496 {Done: Marco d'Itri } [src:dns-root-data]

Bug#1098862: marked as done (asahi-audio: unable to migrate because of unsatisfiable dependency)

Your message dated Tue, 25 Feb 2025 10:48:57 + with message-id and subject line Bug#1098862: fixed in asahi-audio 3.0-3 has caused the Debian Bug report #1098862, regarding asahi-audio: unable to migrate because of unsatisfiable dependency to be marked as done. This means that you claim that

Bug#1098862: asahi-audio: unable to migrate because of unsatisfiable dependency

Hello Jeremy, On Tue, Feb 25, 2025 at 04:01:41AM -0500, Jeremy Bícha wrote: > Source: asahi-audio > Version: 3.0-2 > Severity: serious > X-Debbugs-CC: m...@tobhe.de > > asahi-audio is unable to migrate to Testing because it has an > unsatisfiable dependency. > > https://qa.debian.org/excuses.php?p

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

I just tried again and it seems that purging the package ibus and the config/cache did work after a reboot... On 2/25/25 11:22, Emmanuel Fleury wrote: Hi all, I would like to confirm this bug on my system. I am using a Compose key (US keyboard and writing in French most of the time). But, sin

Processed: Bug#1098811: couriergrey -- RoM; unmaintained upstream, most probably not working

Processing control commands: > severity -1 normal Bug #1098811 [src:couriergrey] couriergrey: Should couriergrey be removed from unstable? Severity set to 'normal' from 'serious' > retitle -1 RM: couriergrey -- RoM; unmaintained upstream, most probably not > working Bug #1098811 [src:couriergrey

Bug#1098811: couriergrey -- RoM; unmaintained upstream, most probably not working

Control: severity -1 normal Control: retitle -1 RM: couriergrey -- RoM; unmaintained upstream, most probably not working Control: reassign -1 ftp.debian.org Control: affects -1 + src:couriergrey Thanks As a consequence of this bug log where the maintainer confirmed that a removal is good I hereby

Bug#1075416: marked as done (python-librtmp: ftbfs with GCC-14)

Your message dated Tue, 25 Feb 2025 10:22:54 + with message-id and subject line Bug#1075416: fixed in python-librtmp 0.3.0-2 has caused the Debian Bug report #1075416, regarding python-librtmp: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1069410: NMU fix actually removed files from the package

On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote: > On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote: > > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote: > > Would you be able to provide a patch that fixes them? > > Unfortunately no, but I only discovered the

Bug#1069410: NMU fix actually removed files from the package

On Tue, Feb 25, 2025 at 11:26:58AM +0100, Yves-Alexis Perez wrote: > On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote: > > On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote: > > > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote: > > > Would you be able to provide

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

Hi all, I would like to confirm this bug on my system. I am using a Compose key (US keyboard and writing in French most of the time). But, since the update of the ibus to 1.5.32~beta2-2, I noticed that my Compose key was not working anymore on some application (mostly Emacs and Discord/VSCode

Bug#1069410: NMU fix actually removed files from the package

On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote: > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote: > > > > Hi, > > > > it seems that the efitools NMU actually broke the package (at least for > > my use case). > > > > efitools 1.9.2-3 contains multiple .efi binaries in /u/l/*/e

Bug#1069410: NMU fix actually removed files from the package

On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote: > > Hi, > > it seems that the efitools NMU actually broke the package (at least for > my use case). > > efitools 1.9.2-3 contains multiple .efi binaries in /u/l/*/efitools, for > example on amd64 > (https://packages.debian.org/bookworm/amd64/e

Bug#1069410: NMU fix actually removed files from the package

Hi, it seems that the efitools NMU actually broke the package (at least for my use case). efitools 1.9.2-3 contains multiple .efi binaries in /u/l/*/efitools, for example on amd64 (https://packages.debian.org/bookworm/amd64/efitools/filelist): /usr/lib/efitools/x86_64-linux-gnu/HashTool.efi /usr

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

On Tue, 25 Feb 2025 04:20, Yue Gui wrote: >The full buildd log is here: >https://buildd.debian.org/status/fetch.php?pkg=meli&arch=riscv64&ver=0.8.10%2Bdfsg-2%2Bb1&stamp=1740301953&raw=0 >My solution to this issue: >The error is caused by the modifiers field in the structure being a >required field

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

Processing commands for cont...@bugs.debian.org: > reassign 1098840 src:linux Bug #1098840 [virtualbox-dkms] virtualbox-dkms: Doesn't build with kernel 6.12.16 Bug reassigned from package 'virtualbox-dkms' to 'src:linux'. No longer marked as found in versions virtualbox/7.0.20-dfsg-1.2. Ignoring

Bug#1098862: asahi-audio: unable to migrate because of unsatisfiable dependency

Source: asahi-audio Version: 3.0-2 Severity: serious X-Debbugs-CC: m...@tobhe.de asahi-audio is unable to migrate to Testing because it has an unsatisfiable dependency. https://qa.debian.org/excuses.php?package=asahi-audio Piuparts reveals: dependency triforce-lv2 is does-not-exist https://piupa

Bug#1093700: pyacoustid: test failures on s390x

> any objections to just disabling the test on s390x ? With the freeze > approaching, as maintainer of eartag I would like to see it in testing. Matthias, I encourage you to proceed with an NMU. Thank you, Jeremy Bícha