Processed: Re: Bug#1109561: receptor: flaky autopkgtest: panic: Fail in goroutine after TestTCPProxyServiceOutbound has completed

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 receptor: flaky autopkgtest: panic: Fail in goroutine after > TestTCPProxyServiceOutbound has completed Bug #1109561 [src:receptor] receptor: flaky autopkgtest: no test files Changed Bug title to 'receptor: flaky autopkgtest: panic: Fail in goroutine aft

Bug#1109561: receptor: flaky autopkgtest: panic: Fail in goroutine after TestTCPProxyServiceOutbound has completed

2025-07-20 Thread Mathias Gibbens
control: retitle -1 receptor: flaky autopkgtest: panic: Fail in goroutine after TestTCPProxyServiceOutbound has completed The actual failure is: === RUN TestTCPProxyInboundCfgRun === RUN TestTCPProxyInboundCfgRun/Required_parameters_set_no_errors_raised panic: Fail in goroutine after TestT

Bug#1106105: dask.distributed flaky autopkgtest on ppc64el

2025-07-20 Thread Paul Gevers
Hi, On 21-07-2025 06:16, Diane Trout wrote: What do you think of this "solution" for the freeze for dask.distributed. Given that we announced the Full Freeze and the release dates and the fact that dask.distributed is a key package, I prefer to ignore this bug for trixie and avoid changes at

Bug#1106105: dask.distributed flaky autopkgtest on ppc64el

2025-07-20 Thread Diane Trout
Hello, What do you think of this "solution" for the freeze for dask.distributed. There's a section of get-test-exclusions which skips timing sensitive tests on riscv64 and s390x. What I did was add ppc64el to the list of skipped architectures and said this downgrades the severity of 1106105 I b

Processed: Autopkgtests fail with Python 3.13: Task was destroyed but it is pending!

2025-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1092793 https://github.com/muhrin/pytray/issues/4 Bug #1092793 [python3-pytray] Autopkgtests fail with Python 3.13: Task was destroyed but it is pending! Set Bug forwarded-to-address to 'https://github.com/muhrin/pytray/issues/4'. > tha

Processed: tagging 1109607

2025-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1109607 + patch Bug #1109607 [devscripts] devscripts: GPG part of tests starting to fail Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1109607: https://bugs.debian.org/cgi-bin/bugreport.

Bug#1109607: devscripts: GPG part of tests starting to fail

2025-07-20 Thread Yadd
On 7/21/25 02:20, Yadd wrote: On 7/20/25 20:47, Yadd wrote: Package: devscripts Version: 2.25.15 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: y...@debian.org Starting from today, test_mkorigtargz, test_debsign and some test_uscan* fail due to some gpg errors: - short keyid l

Bug#1109607: devscripts: GPG part of tests starting to fail

2025-07-20 Thread Yadd
On 7/20/25 20:47, Yadd wrote: Package: devscripts Version: 2.25.15 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: y...@debian.org Starting from today, test_mkorigtargz, test_debsign and some test_uscan* fail due to some gpg errors: - short keyid looks forbidden now - $GPGHOME s

Bug#1061241: marked as done (endless-sky: debian/copyright incomplete)

2025-07-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Jul 2025 23:34:46 + with message-id and subject line Bug#1061241: fixed in endless-sky 0.10.14-1 has caused the Debian Bug report #1061241, regarding endless-sky: debian/copyright incomplete to be marked as done. This means that you claim that the problem has been d

Processed: Re: Bug#1109612: cryptsetup-suspend: Stuck trying to suspend with certain processes running

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo unreproducible Bug #1109612 [cryptsetup-suspend] cryptsetup-suspend: Stuck trying to suspend with certain processes running Added tag(s) unreproducible and moreinfo. -- 1109612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109612 Debian Bug

Bug#1109612: cryptsetup-suspend: Stuck trying to suspend with certain processes running

2025-07-20 Thread Guilhem Moulin
Control: tag -1 + moreinfo unreproducible On Sun, 20 Jul 2025 at 20:37:53 +, Huey Chen wrote: > Alright, this still occurs without cryptsetup-suspend installed. > Instead, the system freezes. So how is that a problem with cryptsetup-suspend? -- Guilhem.

Bug#1109612: cryptsetup-suspend: Stuck trying to suspend with certain processes running

2025-07-20 Thread Huey Chen
Alright, this still occurs without cryptsetup-suspend installed. Instead, the system freezes. From: Huey Chen Sent: Sunday, July 20, 2025 8:27 PM To: Debian Bug Tracking System Subject: Bug#1109612: cryptsetup-suspend: Stuck trying to suspend with certain proces

Bug#1109612: cryptsetup-suspend: Stuck trying to suspend with certain processes running

2025-07-20 Thread Huey Chen
Package: cryptsetup-suspend Version: 2:2.8.0-1 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: hueyche...@outlook.com Dear Maintainer, Some processes, such as running timeshift, rsync, or another I/O intensive process, cause suspending with cryptsetup-suspend to be stuc

Bug#1109607: devscripts: GPG part of tests starting to fail

2025-07-20 Thread Yadd
Package: devscripts Version: 2.25.15 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: y...@debian.org Starting from today, test_mkorigtargz, test_debsign and some test_uscan* fail due to some gpg errors: - short keyid looks forbidden now - $GPGHOME should be chmod 700 - even after

Bug#1109561: receptor: flaky autopkgtest: no test files

2025-07-20 Thread Santiago Vila
tags 1109561 ftbfs thanks On Sun, Jul 20, 2025 at 07:44:11AM +0200, Paul Gevers wrote: > Don't hesitate to reach out if you need help and some more information > from our infrastructure. Hi. I had in fact this one pending to be reported (as a FTBFS bug). In my setup, this builds ok on systems w

Processed: Re: Bug#1109561: receptor: flaky autopkgtest: no test files

2025-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1109561 ftbfs Bug #1109561 [src:receptor] receptor: flaky autopkgtest: no test files Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1109561: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Processed: Debian bugs control

2025-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1109265 https://github.com/seveas/python-hpilo/pull/302 Bug #1109265 [python3-hpilo] python3-hpilo: does not work for Trixie with Python 3 Set Bug forwarded-to-address to 'https://github.com/seveas/python-hpilo/pull/302'. > thanks Stop

Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2025-07-20 at 12:25 +0200, Yves-Alexis Perez wrote: > In any case, help would be appreciated on how to interpret apt output and > how > to make it accept the removal of strongswan-charon for upgrading the > strongswan metapackage. > > Maybe

Bug#548024: marked as done (packages.debian.org: mirror doesn't close old databases)

2025-07-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Jul 2025 12:42:22 +0200 with message-id <26748.51214.246608.596...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #548024, regarding packages.debian.org: mirror doesn't close old databases to be marked as done. This means that you claim that t

Bug#1109499: bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Paul Gevers
Hi, On Sun, 20 Jul 2025 12:27:53 +0200 Niels Thykier wrote: Perharps debian-devel or other people that would be in similar situations can help. Concretely, I suspect the postgres/mariaDB maintainers would have been in a similar situation at some point (I think PostgreSQL has a yearly bump of

Bug#1109499: bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Niels Thykier
Sven Hartge: On 20.07.25 09:45, Niels Thykier wrote: @Bacula team: I have split this into two bugs for you.   - #1109499 remains RC and is about preinst defaulting to fail on a     non-interactive upgrade test. The problem here is that this question and the default to "no" is a very importa

Processed: Re: Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 help Bug #1109510 [strongswan] strongswan: fails to dist-upgrade from bookworm to trixie Added tag(s) help. -- 1109510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1109510: strongswan: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 help On Sat, 2025-07-19 at 20:25 +0200, Lucas Nussbaum wrote: > > > MWE: > > > PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y > > > install $PKG  && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && > > > a

Processed: Re: Bug#1109571: debian-installer: invalid configuration of dictionaries-common during KDE installation, GRUB cannot be installed

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1109571 [debian-installer] debian-installer: invalid configuration of dictionaries-common during KDE installation, GRUB cannot be installed Severity set to 'important' from 'grave' -- 1109571: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#1109571: debian-installer: invalid configuration of dictionaries-common during KDE installation, GRUB cannot be installed

2025-07-20 Thread Cyril Brulebois
Control: severity -1 important Björn Siebke (2025-07-20): > Package: debian-installer > Version: 20250701 > Severity: grave > Tags: d-i l10n > Justification: renders package unusable Not quite… > In GNOME boxes tried to install debian testing with KDE, using the > official testing amd64 netinst

Bug#1109568: vault: Installs files into usr-unmerged location

2025-07-20 Thread Chris Hofstädtler
Package: tinc Version: 1.1~pre18-1 Severity: serious lintian identifies your package as installing files into lib/systemd/system. These files must be installed into /usr instead. Please see the UsrMerge wiki page [1] for more information. Chris [1] https://wiki.debian.org/UsrMerge

Bug#1109570: munin: Installs files into usr-unmerged location

2025-07-20 Thread Chris Hofstaedtler
Source: munin Version: 2.999.16-1 Severity: serious lintian identifies your package(s) as installing files into /lib/systemd/system. These files must be installed into /usr instead. Please see the UsrMerge wiki page [1] for more information. Chris [1] https://wiki.debian.org/UsrMerge

Bug#1109569: janitor: Installs files into usr-unmerged location

2025-07-20 Thread Chris Hofstaedtler
Source: janitor Version: 0.1~git20220702-1 Severity: serious lintian identifies your package as installing files into /lib/systemd/system. These files must be installed into /usr instead. Please see the UsrMerge wiki page [1] for more information. Chris [1] https://wiki.debian.org/UsrMerge

Bug#1109567: vault: Installs files into usr-unmerged location

2025-07-20 Thread Chris Hofstädtler
Package: vault Version: 1.0.2+dfsg2-5 Severity: serious lintian identifies your package as installing a file /systemd/system/vault.service This file must be installed into /usr instead. Please see the UsrMerge wiki page [1] for more information. Chris [1] https://wiki.debian.org/UsrMerge

Bug#1109566: wmbusmeters: Installs into usr-unmerged location

2025-07-20 Thread Chris Hofstädtler
Package: wmbusmeters Version: 1.13.1-3 Severity: serious lintian identifies your package as installing a file lib/systemd/system/wmbusmeters.service. This file must be installed into /usr instead. Please see the UsrMerge wiki page [1] for more information. Chris [1] https://wiki.debian.org/UsrM

Processed: Re: Bug#1109499: bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1109499 -1 Bug #1109499 [bacula-director-sqlite3] bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie Bug 1109499 cloned as bug 1109564 > clone 1109499 -2 Bug #1109499 [bacula-director-sqlite3] bacula-director-sqlite3: fa

Bug#1109499: bacula-director-sqlite3: fails to dist-upgrade from bookworm to trixie

2025-07-20 Thread Niels Thykier
clone 1109499 -1 clone 1109499 -2 retitle 1109499 bacula-common: preinst intentionally breaks upgrade retitle -1 dpkg: Silent on invoking postinst abort-upgrade reassign -1 dpkg # Annoying to debug but not RC in itself severity -1 important retitle -2 bacula-common: Silent when aborting the upgrad

Bug#1108512: marked as done (kde-config-sddm: Writes to /usr/share upon applying theme)

2025-07-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Jul 2025 07:35:11 + with message-id and subject line Bug#1108512: fixed in sddm-kcm 4:6.3.4-4 has caused the Debian Bug report #1108512, regarding kde-config-sddm: Writes to /usr/share upon applying theme to be marked as done. This means that you claim that the prob

Bug#1108512: marked as pending in sddm-kcm

2025-07-20 Thread Aurélien COUDERC
Control: tag -1 pending Hello, Bug #1108512 in sddm-kcm 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/kde/sddm-kcm/-/commit/4ce5e836b003b3f920c970

Processed: Bug#1108512 marked as pending in sddm-kcm

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1108512 [kde-config-sddm] kde-config-sddm: Writes to /usr/share upon applying theme Added tag(s) pending. -- 1108512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108512 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble