Your message dated Mon, 30 Mar 2020 20:53:58 +0200
with message-id <74ef34de-2a9f-408c-602d-4a5d8d18a...@debian.org>
and subject line Re: Bug#953780: src:zip4j: fails to migrate to testing for too
long
has caused the Debian Bug report #953780,
regarding src:zip4j: fails to migrate to testing for too long
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 ow...@bugs.debian.org
immediately.)
--
953780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zip4j
Version: 2.1.3-1
Severity: serious
Control: fixed -1 2.2.8-1
Tags: sid bullseye
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:zip4j in its
current version in unstable has been trying to migrate for 74 days [2].
Hence, I am filing this bug.
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 marked the version in unstable as fixing this bug, 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 bullseye, 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=zip4j
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi Andrius,
On 30-03-2020 12:32, mer...@debian.org wrote:
> I have uploaded a new version of zip4j, and this one has successfully
> migrated. However, the bug remains open - I assume it should have been
> closed automatically, or am I wrong? Should I close it manually?
That assumption is wrong. Closure is done by either a "Closes" in the
changelog or by manual sending a message to bug-done, like I've done
now. Probably someone doing QA on the BTS would have closed it in due
time as the bug impacts no release anymore, but it's unnecessary to wait
for that.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
