Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64

I tried to reproduce this in my sid chroot on a machine running Debian Stable, but here it built just fine for amd64. Was this a problem in some other package which have since been fixed? When I try the same build in a testing/trixy chroot on a different machine, running testing, the build fail l

Bug#1103641: RM: coz-profiler -- RoQA; RC-buggy, orphaned, blocks removal of libelfin

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: coz-profi...@packages.debian.org Control: affects -1 + src:coz-profiler User: ftp.debian@packages.debian.org Usertags: remove Please remove coz-profiler. It's RC-buggy for over a year, the last maintainer upload was in 2020 and it blocks t

Bug#1103642: RM: libelfin -- RoQA; open security issues, no reverse dependencies, orphaned

Package: ftp.debian.org Severity: normal Tags: security X-Debbugs-Cc: libel...@packages.debian.org, Debian Security Team Control: affects -1 + src:libelfin User: ftp.debian@packages.debian.org Usertags: remove Please remove libelfin, upstream is mostly dormant (there's plenty of unfixed secu

gnunet-gtk is marked for autoremoval from testing

gnunet-gtk 0.20.0-5 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/11026

gnunet-fuse is marked for autoremoval from testing

gnunet-fuse 0.20.0-5 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102

doodle is marked for autoremoval from testing

doodle 0.7.3-1 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102653

rpmlint is marked for autoremoval from testing

rpmlint 2.7.0-2 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102653

epm is marked for autoremoval from testing

epm 4.2-12 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102653 For

alien is marked for autoremoval from testing

alien 8.95.8 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102653 F

gnunet is marked for autoremoval from testing

gnunet 0.20.0-7 is marked for autoremoval from testing on 2025-05-25 It (build-)depends on packages with these RC bugs: 1102653: rust-rpm-sequoia: rust-rpm-sequoia FTBFS with the nocheck build profile: ValueError: non-existent registry: /usr/share/cargo/registry https://bugs.debian.org/1102653

6tunnel_0.13-4_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Apr 2025 14:57:10 +0200 Source: 6tunnel Architecture: source Version: 1:0.13-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandr

Processing of 6tunnel_0.13-4_source.changes

6tunnel_0.13-4_source.changes uploaded successfully to localhost along with the files: 6tunnel_0.13-4.dsc 6tunnel_0.13-4.debian.tar.xz 6tunnel_0.13-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1103572: storebackup: Please keep up-to-date this package

Package: storebackup Version: 3.2.1-2 Severity: wishlist Dear Maintainer, please keep the storebackup program in the APT repository. I use the Perl based storebackup since about 20 years! Sadly, https://www.storebackup.org is down currently! I also can't find a offical GitHub.com page for store

Bug#1102703: libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml

I suspect the appropriate fix is to only provide this file from libam7xxx0.1-bin and drop it from libam7xxx0.1. -- Happy hacking Petter Reinholdtsen

Bug#1103192: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

Control: reassign -1 dssi-dev Control: found -1 1.1.1~dfsg0-6 Control: affects -1 src:naspro-bridges Issue #1103192 is also reported as issue #1103187, and need to be fixed in dssi-dev. -- Happy hacking Petter Reinholdtsen

Processed: Re: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

Processing control commands: > reassign -1 dssi-dev Bug #1103192 [src:naspro-bridges] naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp] Bug reassigned from package 'src:naspro-bridges' to 'dssi-dev'. No longer

libam7xxx_0.1.7-5_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 19 Apr 2025 17:45:57 +0200 Source: libam7xxx Architecture: source Version: 0.1.7-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter

Bug#1102703: marked as done (libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml)

Your message dated Sat, 19 Apr 2025 16:04:55 + with message-id and subject line Bug#1102703: fixed in libam7xxx 0.1.7-5 has caused the Debian Bug report #1102703, regarding libam7xxx0.1-bin has an undeclared file conflict on /usr/share/metainfo/it.ao2.libam7xxx.metainfo.xml to be marked as do

Processing of libam7xxx_0.1.7-5_source.changes

libam7xxx_0.1.7-5_source.changes uploaded successfully to localhost along with the files: libam7xxx_0.1.7-5.dsc libam7xxx_0.1.7-5.debian.tar.xz libam7xxx_0.1.7-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)