Your message dated Wed, 13 Jul 2022 20:44:33 +0200
with message-id
<CAEGjuv8REDu6RUEp2dyJFnkQiVU81uBqfV12C0pv9=s6vaw...@mail.gmail.com>
and subject line Re: Bug#1013930: src:iperf3: fails to migrate to testing for
too long: piuparts regression, changes conffile
has caused the Debian Bug report #1013930,
regarding src:iperf3: fails to migrate to testing for too long: piuparts
regression, changes conffile
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1013930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013930
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: iperf3
Version: 3.9-1
Severity: serious
Tags: sid bookworm
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:iperf3 has been trying to migrate for 61
days [2]. Hence, I am filing this bug. The migration is blocked because
piuparts reports a regression. A quick glance (piuparts log and your
changelog) suggests you are now changing a conffile (not to be confused
with a normal configuration file), see [3].
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Paul
[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=iperf3
[3]
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
iperf3 was migrated to testing today, closing this bug.
Regards,
--
Roberto Lumbreras
Debian developer
--- End Message ---
