Your message dated Wed, 1 Apr 2020 22:09:29 +0200
with message-id <9fd18286-a935-e7de-5654-a4b2cc195...@debian.org>
and subject line Re: src:fuzzywuzzy: fails to migrate to testing for too long
has caused the Debian Bug report #953347,
regarding src:fuzzywuzzy: 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.)
--
953347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fuzzywuzzy
Version: 0.17.0-1
Severity: serious
Control: fixed -1 0.17.0-2
Tags: sid bullseye pending
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:fuzzywuzzy in
its current version in unstable has been trying to migrate for 190 days.
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.
Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.
Paul
[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.18.0-1
On Sun, 8 Mar 2020 10:31:54 +0100 Paul Gevers <elb...@debian.org> wrote:
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
> shortly do a no-changes source-only upload to DELAYED/15, closing this
> bug. Please let me know if I should delay or cancel that upload.
A regular upload beat my binNMU, thank you. Closing this bug.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
