Processed: src:iwd: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.22-1 Bug #1082961 [src:iwd] src:iwd: fails to migrate to testing for too long Marked as fixed in versions iwd/2.22-1. Bug #1082961 [src:iwd] src:iwd: fails to migrate to testing for too long Marked Bug as done -- 1082961: https://bugs.debian.org/cgi-bin/

Bug#1082962: src:ell: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: ell Version: 0.67-1 Severity: serious Control: close -1 0.69-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a

Bug#1082961: src:iwd: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: iwd Version: 2.19-1 Severity: serious Control: close -1 2.22-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a

Processed: src:ell: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.69-2 Bug #1082962 [src:ell] src:ell: fails to migrate to testing for too long Marked as fixed in versions ell/0.69-2. Bug #1082962 [src:ell] src:ell: fails to migrate to testing for too long Marked Bug as done -- 1082962: https://bugs.debian.org/cgi-bin/

Bug#1082956: apt: autoremove --purge changed behavior; immediately removes packages

2024-09-28 Thread Andres Salomon
Package: apt Version: 2.9.8 Severity: serious Justification: breaks entire system X-Debbugs-Cc: dilin...@queued.net On bookworm, running 'apt [auto]remove --purge ' will provide a list of packages to be removed, and prompt the user before actually removing those packages. It has been this way (pre

Bug#1082747: cod-tools: FTBFS (only) on riscv64

2024-09-28 Thread Santiago Vila
tools/help2man scripts/utf8-to-cif --bugs-email cod-b...@ibt.lt > doc/man/utf8-to-cif.1 make[1]: *** No rule to make target 'doc/man/cif_list_tags.1', needed by 'man'. Stop. make[1]: Leaving directory '/<>' Hi. For the record: I get a similar failure on amd64 when using "make --shuffle". I

Processed: Re: Bug#1082612: lintian: Argument "v0.902.0" isn't numeric in numeric lt (<) at /usr/share/lintian/lib/Lintian/Check/Debian/Upstream/Metadata.pm line 106

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1082612 [lintian] lintian: Argument "v0.902.0" isn't numeric in numeric lt (<) at /usr/share/lintian/lib/Lintian/Check/Debian/Upstream/Metadata.pm line 106 Bug #1082760 [lintian] lintian: stumbles over new $YAML::XS::VERSION: "v0.902.0" is

Bug#1082747: cod-tools: FTBFS (only) on riscv64

2024-09-28 Thread Bernhard Übelacker
On Fri, 27 Sep 2024 19:25:10 +0200 Aurelien Jarno wrote: TIL disorderfs. I have also been able to reproduce it with disorderfs. In addition knowing the root of the issue, I have been able to reproduce the issue on a riscv64 machine using tmpfs as a build directory, just like on the build daemon

Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues

2024-09-28 Thread gregor herrmann
On Sun, 29 Sep 2024 00:49:29 +0200, gregor herrmann wrote: > Now we have libxml2 2.9 back in testing > (2.12.7+dfsg+really2.9.14-0.1), and a libxml-libxml-perl which > depends on this version and has been built against it, but the > autopkgtest failures are still there: > https://tracker.debian.or

Bug#1082782: marked as done (libcupsfilters2-common is uninstallable.)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 23:09:33 + (UTC) with message-id and subject line Re: libcupsfilters2-common is uninstallable has caused the Debian Bug report #1082782, regarding libcupsfilters2-common is uninstallable. to be marked as done. This means that you claim that the problem has

Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues

2024-09-28 Thread gregor herrmann
On Thu, 18 Jul 2024 08:46:00 +0200, Paul Gevers wrote: > On 17-07-2024 11:20 p.m., gregor herrmann wrote: > > So I guess I'd just wait (the new libxml-libxslt-perl version also > > has no groundbreaking changes); but I might miss something which > > others may add. > I think that's acceptable if o

Processed: bug 1082952 is forwarded to https://github.com/DCIT/perl-CryptX/issues/111

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1082952 https://github.com/DCIT/perl-CryptX/issues/111 Bug #1082952 [src:libcryptx-perl] libcryptx-perl: t/sshkey.t fails on some architectures Set Bug forwarded-to-address to 'https://github.com/DCIT/perl-CryptX/issues/111'. > thanks

Bug#1082952: libcryptx-perl: t/sshkey.t fails on some architectures

2024-09-28 Thread gregor herrmann
Source: libcryptx-perl Version: 0.081-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.081-1 has test failures on some architectures (s390x, ppc64, sparc64, x32): https://build

Bug#1082944: marked as done (FTBFS because of new jmagick version)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 21:49:59 + with message-id and subject line Bug#1082944: fixed in libtwelvemonkeys-java 3.11.0+dfsg-1 has caused the Debian Bug report #1082944, regarding FTBFS because of new jmagick version to be marked as done. This means that you claim that the problem

Bug#1075329: marked as done (ocaml-lo: ftbfs with GCC-14)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 21:36:12 + with message-id and subject line Bug#1075329: fixed in ocaml-lo 0.2.0.git20240724.0b43bdf-1 has caused the Debian Bug report #1075329, regarding ocaml-lo: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been

Bug#975120: marked as done (spdx-licenses: upstream source is not true source)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 20:38:20 + with message-id and subject line Bug#975120: fixed in spdx-licenses 3.21-1 has caused the Debian Bug report #975120, regarding spdx-licenses: upstream source is not true source to be marked as done. This means that you claim that the problem has

Bug#1082810: gscan2pdf: deadlock in tests

2024-09-28 Thread Jeff
On 28/09/2024 16:41, наб wrote: retitle 1082815 analizo: FTBFS (tests fail) on sid if building as root retitle 1082810 gscan2pdf: deadlock in tests if building as root # 1082804 is already ledgersmb: FTBFS (test failure) if building as root thanks On Sat, Sep 28, 2024 at 01:10:48PM +0200, Santia

Processed: closing 1075330

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1075330 1:0.90-pa9-19 Bug #1075330 [src:omega-rpg] omega-rpg: ftbfs with GCC-14 The source 'omega-rpg' and version '1:0.90-pa9-19' do not appear to match any binary packages Marked as fixed in versions omega-rpg/1:0.90-pa9-19. Bug #1075330

Bug#1073249: marked as done (booth: CVE-2024-3049)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 18:49:06 + with message-id and subject line Bug#1073249: fixed in booth 1.2-1 has caused the Debian Bug report #1073249, regarding booth: CVE-2024-3049 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1082944: FTBFS because of new jmagick version

2024-09-28 Thread Pierre Gruet
Source: libtwelvemonkeys-java Version: 3.9.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, The package FTBFS in unstable because of ABI-braking changes in jmagick: [ERROR] Failed to execute goal org.apache.maven.pl

Bug#1070983: supertuxkart/shaderc: symbol lookup error: undefined symbol -- closing ?

2024-09-28 Thread Philippe SWARTVAGHER
Hello, I think we can now close this bug? I guess, as it has been already pointed out, this bug was fixed in the same time as fixing #1029939 (https://bugs.debian.org/1029939). Moreover, the corrected version migrated in testing 3 months ago. In current sid, supertuxkart works well, there is no

Processed: Re: Bug#1082698: qt5-ukui-platformtheme: FTBFS: /bin/sh: 2: Syntax error: "(" unexpected

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1082698 + patch Bug #1082698 [src:qt5-ukui-platformtheme] qt5-ukui-platformtheme: FTBFS: /bin/sh: 2: Syntax error: "(" unexpected Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1082698:

Bug#1082698: qt5-ukui-platformtheme: FTBFS: /bin/sh: 2: Syntax error: "(" unexpected

2024-09-28 Thread Santiago Vila
tags 1082698 + patch thanks Hello. Maybe you just need to use quotes, as in the attached patch. (I'm actually surprised that it worked at all in the buildds) While we are at it, you had *two* identical blocks for override_dh_gencontrol, the patch removes one of them. Also: Please keep the sals

Bug#1074828: atril: ftbfs with GCC-14

2024-09-28 Thread Andreas Rönnquist
On Mon, 12 Aug 2024 08:35:10 -0700 Philip Chung wrote: > On Wed, 03 Jul 2024 12:22:26 + Matthias Klose wrote: > > This is fixed upstream in version 1.27.1, first in a GitHub pull request > [1] and later in a separate commit [2]. (The second instance of the > error is fixed using a different

Bug#1081560: marked as done (ruby-saml: CVE-2024-45409)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 16:47:12 + with message-id and subject line Bug#1081560: fixed in ruby-saml 1.13.0-1+deb12u1 has caused the Debian Bug report #1081560, regarding ruby-saml: CVE-2024-45409 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1073249: marked as done (booth: CVE-2024-3049)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 16:47:08 + with message-id and subject line Bug#1073249: fixed in booth 1.0-283-g9d4029a-2+deb12u1 has caused the Debian Bug report #1073249, regarding booth: CVE-2024-3049 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1082938: rust-coreutils - FTBFS on 32-bit.

2024-09-28 Thread Peter Green
Package: rust-coreutils Version: 0.0.26-3 Severity: serious rust-coreutils fails to build on 32-bit architectures. I first noticed this after uploading 0.0.26-4 to fix the build with the new version of rust-half, but according to reproducible builds it also seems to affect 0.0.26-3 > make[1]: En

Processed: 1082933 affects pygeofilter

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1082933 +pygeofilter Bug #1082933 [src:geoalchemy2] geoalchemy2: build failure on s390x Added indication that 1082933 affects pygeofilter > thanks Stopping processing here. Please contact me if you need assistance. -- 1082933: https://bu

Bug#1082933: geoalchemy2: build failure on s390x

2024-09-28 Thread Antonio Valentino
Source: geoalchemy2 Version: 0.15.1-1 Severity: serious Tags: ftbfs Justification: geoalchemy2 fails to build from source on s390x X-Debbugs-Cc: antonio.valent...@tiscali.it Dear Maintainer, the package is unable to migrate to testing due to a regression. It is unable to build on s390x. Looking

Bug#1079730: marked as done (devscripts: bts does not work with mail-submit.debian.org:587 in bookworm)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 15:32:31 + with message-id and subject line Bug#1079730: fixed in devscripts 2.23.4+deb12u2 has caused the Debian Bug report #1079730, regarding devscripts: bts does not work with mail-submit.debian.org:587 in bookworm to be marked as done. This means that

Processed: Re: Bug#1082810: gscan2pdf: deadlock in tests

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1082815 analizo: FTBFS (tests fail) on sid if building as root Bug #1082815 [src:analizo] analizo: FTBFS (tests fail) on sid Changed Bug title to 'analizo: FTBFS (tests fail) on sid if building as root' from 'analizo: FTBFS (tests fail) o

Bug#1082810: gscan2pdf: deadlock in tests

2024-09-28 Thread наб
retitle 1082815 analizo: FTBFS (tests fail) on sid if building as root retitle 1082810 gscan2pdf: deadlock in tests if building as root # 1082804 is already ledgersmb: FTBFS (test failure) if building as root thanks On Sat, Sep 28, 2024 at 01:10:48PM +0200, Santiago Vila wrote: > El 28/9/24 a las

Bug#1052917: marked as done (scala-mode-el: FTBFS: make[1]: *** [Makefile:55: clean] Error 2)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 14:36:27 + with message-id and subject line Bug#1052917: fixed in scala-mode-el 1:1.1.0+git20240729.bd0638c-1 has caused the Debian Bug report #1052917, regarding scala-mode-el: FTBFS: make[1]: *** [Makefile:55: clean] Error 2 to be marked as done. This me

Bug#1082892: magpie FTBFS: ERROR: Dependency "udev" not found, tried pkgconfig

2024-09-28 Thread David Mohammed
Many thanks for the report. I've prepared a package update that resolves this issue. I prefer though to wait until gnome-settings-daemon is uplifted in unstable from 47~beta to v47.1 since this is the version I have tested with. David On Fri, 27 Sept 2024 at 20:39, Adrian Bunk wrote: > > Sourc

Bug#1082893: marked as done (libxs-parse-sublike-perl: Compiler warnings on 32bit architecures cause autopkgtest failures)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 13:34:22 + with message-id and subject line Bug#1082893: fixed in libxs-parse-sublike-perl 0.27-2 has caused the Debian Bug report #1082893, regarding libxs-parse-sublike-perl: Compiler warnings on 32bit architecures cause autopkgtest failures to be marked

Bug#1081631: marked as done (pyzoltan: FTBFS error: ‘MPI_Session’ does not name a type)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 13:34:30 + with message-id and subject line Bug#1081631: fixed in pyzoltan 1.0.1-10 has caused the Debian Bug report #1081631, regarding pyzoltan: FTBFS error: ‘MPI_Session’ does not name a type to be marked as done. This means that you claim that the probl

Bug#1082927: flatpak [LTS]: CVE-2024-42472: sandbox escape for apps with --persist=DIR permission

2024-09-28 Thread Simon McVittie
Source: flatpak Version: 1.10.8-0+deb11u2 Severity: grave Justification: user security hole Tags: bullseye security X-Debbugs-Cc: debian-...@lists.debian.org Control: found -1 1.2.5-0+deb10u4 Control: fixed -1 1.14.10-1~deb12u1 Control: fixed -1 1.14.10-1 Control: fixed -1 1.15.10-1 Advisory: http

Processed: flatpak [LTS]: CVE-2024-42472: sandbox escape for apps with --persist=DIR permission

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.2.5-0+deb10u4 Bug #1082927 [src:flatpak] flatpak [LTS]: CVE-2024-42472: sandbox escape for apps with --persist=DIR permission Marked as found in versions flatpak/1.2.5-0+deb10u4. > fixed -1 1.14.10-1~deb12u1 Bug #1082927 [src:flatpak] flatpak [LTS]: CVE-2

Bug#1081716: libdrumstick: FTBFS: dh_install: warning: libdrumstick-plugins missing files: usr/lib/*/qt6/plugins/designer/libdrumstick-vpiano-plugin.so

2024-09-28 Thread Pedro Lopez-Cabanillas
The build log says that the plugin was correctly built: [ 97%] Linking CXX shared module ../../lib/designer/libdrumstick-vpiano-plugin.so cd /<>/obj-aarch64-linux-gnu/library/vpiano-plugin && /usr/bin/cmake -E cmake_link_script CMakeFiles/drumstick-vpiano-plugin.dir/link.txt --verbose=1 /usr/b

Bug#1082728: openssh: Passive SSH Key Compromise via Lattices (RSA host keys)

2024-09-28 Thread Beat Bolli
Source: openssh Followup-For: Bug #1082728 Dear Maintainer, Since this paper has nothing to do with this specific OpenSSH release (9.9), I propose to downgrade the severity of this bug. Lots of us want to try the new Refuse settings on testing, and I don't think that Debian (or upstream, for tha

Bug#1082810: gscan2pdf: deadlock in tests

2024-09-28 Thread Santiago Vila
El 28/9/24 a las 12:31, Jeff escribió: I can't reproduce this. The tests pass elsewhere in chroots: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gscan2pdf.html What is different about your setup? Most probably, the fact that he's building the package as root. This is fro

Bug#1082922: Removal notice: obsolete

2024-09-28 Thread Ilias Tsitsimpis
Source: haskell-x509-util Version: 1.6.6-1 Severity: serious I intend to remove this package: * It has no rev dependencies * It is unmaintained; Upstream abandoned this package * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close thi

Bug#1079848: Proceeding with removal of spdx-licenses

2024-09-28 Thread Helmut Grohne
Control: severity 1079848 normal Control: retitle 1079848 RM: spdx-licenses -- RoQA; rc-buggy Control: reassign 1079848 ftp.debian.org Control: affects 1079848 + src:spdx-licenses Dear spdx-licenses maintainer and ftp team, a month has passed since filing a suggestion to remove spdx-licenses from

Processed: Proceeding with removal of spdx-licenses

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079848 normal Bug #1079848 [src:spdx-licenses] Should spdx-licenses be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079848 RM: spdx-licenses -- RoQA; rc-buggy Bug #1079848 [src:spdx-licenses] Should spdx-licenses be removed from

Bug#1079846: Proceeding with removal of chibi-scheme

2024-09-28 Thread Helmut Grohne
Control: severity 1079846 normal Control: retitle 1079846 RM: chibi-scheme -- RoQA; rc-buggy Control: reassign 1079846 ftp.debian.org Control: affects 1079846 + src:chibi-scheme Dear chibi-scheme maintainer and ftp team, a month has passed since filing a suggestion to remove chibi-scheme from Deb

Processed: Proceeding with removal of jsunit

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079849 normal Bug #1079849 [src:jsunit] Should jsunit be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079849 RM: jsunit -- RoQA; rc-buggy Bug #1079849 [src:jsunit] Should jsunit be removed from unstable? Changed Bug title to 'RM

Bug#1079849: Proceeding with removal of jsunit

2024-09-28 Thread Helmut Grohne
Control: severity 1079849 normal Control: retitle 1079849 RM: jsunit -- RoQA; rc-buggy Control: reassign 1079849 ftp.debian.org Control: affects 1079849 + src:jsunit Dear jsunit maintainer and ftp team, a month has passed since filing a suggestion to remove jsunit from Debian. It was suggested fo

Processed: Proceeding with removal of chibi-scheme

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079846 normal Bug #1079846 [src:chibi-scheme] Should chibi-scheme be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079846 RM: chibi-scheme -- RoQA; rc-buggy Bug #1079846 [src:chibi-scheme] Should chibi-scheme be removed from unst

Processed: Proceeding with removal of pluginhook

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079844 normal Bug #1079844 [src:pluginhook] Should pluginhook be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079844 RM: pluginhook -- RoQA; rc-buggy Bug #1079844 [src:pluginhook] Should pluginhook be removed from unstable? Chan

Bug#1079844: Proceeding with removal of pluginhook

2024-09-28 Thread Helmut Grohne
Control: severity 1079844 normal Control: retitle 1079844 RM: pluginhook -- RoQA; rc-buggy Control: reassign 1079844 ftp.debian.org Control: affects 1079844 + src:pluginhook Dear pluginhook maintainer and ftp team, a month has passed since filing a suggestion to remove pluginhook from Debian. It

Processed: Proceeding with removal of elektra

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079779 normal Bug #1079779 [src:elektra] Should elektra be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079779 RM: elektra -- RoQA; rc-buggy Bug #1079779 [src:elektra] Should elektra be removed from unstable? Changed Bug title t

Processed: Proceeding with removal of vncterm

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079778 normal Bug #1079778 [src:vncterm] Should vncterm be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079778 RM: vncterm -- RoQA; rc-buggy Bug #1079778 [src:vncterm] Should vncterm be removed from unstable? Changed Bug title t

Bug#1079779: Proceeding with removal of elektra

2024-09-28 Thread Helmut Grohne
Control: severity 1079779 normal Control: retitle 1079779 RM: elektra -- RoQA; rc-buggy Control: reassign 1079779 ftp.debian.org Control: affects 1079779 + src:elektra Dear elektra maintainer and ftp team, a month has passed since filing a suggestion to remove elektra from Debian. It was suggeste

Bug#1079778: Proceeding with removal of vncterm

2024-09-28 Thread Helmut Grohne
Control: severity 1079778 normal Control: retitle 1079778 RM: vncterm -- RoQA; rc-buggy Control: reassign 1079778 ftp.debian.org Control: affects 1079778 + src:vncterm Dear vncterm maintainer and ftp team, a month has passed since filing a suggestion to remove vncterm from Debian. It was suggeste

Processed: Proceeding with removal of libpthread-workqueue

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079775 normal Bug #1079775 [src:libpthread-workqueue] Should libpthread-workqueue be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079775 RM: libpthread-workqueue -- RoQA; rc-buggy Bug #1079775 [src:libpthread-workqueue] Should

Processed: Proceeding with removal of golang-github-minio-cli

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079774 normal Bug #1079774 [src:golang-github-minio-cli] Should golang-github-minio-cli be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079774 RM: golang-github-minio-cli -- RoQA; rc-buggy Bug #1079774 [src:golang-github-minio-

Bug#1079775: Proceeding with removal of libpthread-workqueue

2024-09-28 Thread Helmut Grohne
Control: severity 1079775 normal Control: retitle 1079775 RM: libpthread-workqueue -- RoQA; rc-buggy Control: reassign 1079775 ftp.debian.org Control: affects 1079775 + src:libpthread-workqueue Dear libpthread-workqueue maintainer and ftp team, a month has passed since filing a suggestion to remo

Bug#1079774: Proceeding with removal of golang-github-minio-cli

2024-09-28 Thread Helmut Grohne
Control: severity 1079774 normal Control: retitle 1079774 RM: golang-github-minio-cli -- RoQA; rc-buggy Control: reassign 1079774 ftp.debian.org Control: affects 1079774 + src:golang-github-minio-cli Dear golang-github-minio-cli maintainer and ftp team, a month has passed since filing a suggestio

Processed: Proceeding with removal of socket-activate

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > severity 1079771 normal Bug #1079771 [src:socket-activate] Should socket-activate be removed from unstable? Severity set to 'normal' from 'serious' > retitle 1079771 RM: socket-activate -- RoQA; rc-buggy Bug #1079771 [src:socket-activate] Should socket-activate be r

Bug#1079771: Proceeding with removal of socket-activate

2024-09-28 Thread Helmut Grohne
Control: severity 1079771 normal Control: retitle 1079771 RM: socket-activate -- RoQA; rc-buggy Control: reassign 1079771 ftp.debian.org Control: affects 1079771 + src:socket-activate Dear socket-activate maintainer and ftp team, a month has passed since filing a suggestion to remove socket-activ

Bug#1082810: gscan2pdf: deadlock in tests

2024-09-28 Thread Jeff
I can't reproduce this. The tests pass elsewhere in chroots: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gscan2pdf.html What is different about your setup? OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1082898: marked as done (dhcpcd - Runs as service)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 13:21:27 +0300 with message-id and subject line Re: Bug#1082898: dhcpcd - Runs as service has caused the Debian Bug report #1082898, regarding dhcpcd - Runs as service to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1081866: marked as done (gnupg2: FTBFS: You need libassuan to build this program.)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 10:07:19 + with message-id and subject line Bug#1081866: fixed in gnupg2 2.2.44-1 has caused the Debian Bug report #1081866, regarding gnupg2: FTBFS: You need libassuan to build this program. to be marked as done. This means that you claim that the problem

Processed: bug 1075472 is forwarded to https://github.com/rtomayko/posix-spawn/issues/92

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1075472 https://github.com/rtomayko/posix-spawn/issues/92 Bug #1075472 [src:ruby-posix-spawn] ruby-posix-spawn: ftbfs with GCC-14 Set Bug forwarded-to-address to 'https://github.com/rtomayko/posix-spawn/issues/92'. > thanks Stopping pro

Bug#1080048: marked as done (Should mlucas be removed from unstable?)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 08:35:20 + with message-id and subject line Bug#1080048: fixed in mlucas 20.1.1-1.1 has caused the Debian Bug report #1080048, regarding Should mlucas be removed from unstable? to be marked as done. This means that you claim that the problem has been dealt

Bug#1027776: marked as done (mlucas: FTBFS on arm64: fermat-number feature known broken on arm64)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 08:35:20 + with message-id and subject line Bug#1027776: fixed in mlucas 20.1.1-1.1 has caused the Debian Bug report #1027776, regarding mlucas: FTBFS on arm64: fermat-number feature known broken on arm64 to be marked as done. This means that you claim that

Bug#1014547: marked as done (mlucas: FTBFS on arm* because of wrong fopen())

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 08:35:20 + with message-id and subject line Bug#1014547: fixed in mlucas 20.1.1-1.1 has caused the Debian Bug report #1014547, regarding mlucas: FTBFS on arm* because of wrong fopen() to be marked as done. This means that you claim that the problem has been

Bug#1013910: marked as done (src:mlucas: invalid maintainer address)

2024-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2024 08:35:20 + with message-id and subject line Bug#1013910: fixed in mlucas 20.1.1-1.1 has caused the Debian Bug report #1013910, regarding src:mlucas: invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt w

Processed (with 1 error): reassign 1073296 to src:poppler, tagging 1067342, tagging 1064004, tagging 1067972, tagging 1075547 ...

2024-09-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1073296 src:poppler 24.02.0-4 Bug #1073296 [libpoppler134] libpoppler134: Cannot upgrade libpoppler134 Warning: Unknown package 'libpoppler134' Bug reassigned from package 'libpoppler134' to 'src:poppler'. No longer marked as found in ver

Bug#1082913: src:debian-hamradio: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: debian-hamradio Version: 0.8 Severity: serious Control: close -1 0.9 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as hav

Processed: src:dogtail: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.0-3 Bug #1082909 [src:dogtail] src:dogtail: fails to migrate to testing for too long Marked as fixed in versions dogtail/1.0.0-3. Bug #1082909 [src:dogtail] src:dogtail: fails to migrate to testing for too long Marked Bug as done -- 1082909: https://bu

Processed: src:uronode: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.15-4 Bug #1082910 [src:uronode] src:uronode: fails to migrate to testing for too long Marked as fixed in versions uronode/2.15-4. Bug #1082910 [src:uronode] src:uronode: fails to migrate to testing for too long Marked Bug as done -- 1082910: https://bugs

Bug#1082910: src:uronode: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: uronode Version: 2.15-3 Severity: serious Control: close -1 2.15-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as havin

Bug#1082909: src:dogtail: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: dogtail Version: 0.9.11-13 Severity: serious Control: close -1 1.0.0-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as h

Processed: src:python-quantities: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.16.0-1 Bug #1082911 [src:python-quantities] src:python-quantities: fails to migrate to testing for too long Marked as fixed in versions python-quantities/0.16.0-1. Bug #1082911 [src:python-quantities] src:python-quantities: fails to migrate to testing fo

Processed: src:debian-hamradio: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.9 Bug #1082913 [src:debian-hamradio] src:debian-hamradio: fails to migrate to testing for too long Marked as fixed in versions debian-hamradio/0.9. Bug #1082913 [src:debian-hamradio] src:debian-hamradio: fails to migrate to testing for too long Marked Bu

Bug#1082912: src:python-pefile: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: python-pefile Version: 2023.2.7-3 Severity: serious Control: close -1 2024.8.26-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 3

Bug#1082911: src:python-quantities: fails to migrate to testing for too long

2024-09-28 Thread Paul Gevers
Source: python-quantities Version: 0.15.0-2 Severity: serious Control: close -1 0.16.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Processed: src:python-pefile: fails to migrate to testing for too long

2024-09-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2024.8.26-1 Bug #1082912 [src:python-pefile] src:python-pefile: fails to migrate to testing for too long The source 'python-pefile' and version '2024.8.26-1' do not appear to match any binary packages Marked as fixed in versions python-pefile/2024.8.26-1.