Your message dated Fri, 08 May 2020 10:30:17 -0400
with message-id <cb9a501485d1b647bb3463d3323621db0d406e6c.ca...@debian.org>
and subject line Re: clips: fails to migrate to testing for too long
has caused the Debian Bug report #951620,
regarding clips: 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.)
--
951620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clips
Version: 6.24-3.2
Severity: serious
Control: fixed -1 6.30-4
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. Your package src:clips in its current
version in unstable has been trying to migrate for 834 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.
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
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 6.30-4.1
The new NMU has fixed this bug and entered Testing. Closing the bug now.
--
Regards,
Boyuan Yang
On Tue, 18 Feb 2020 22:54:44 +0100 Paul Gevers <elb...@debian.org> wrote:
> Source: clips
> Version: 6.24-3.2
> Severity: serious
> Control: fixed -1 6.30-4
> 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. Your package src:clips in its current
> version in unstable has been trying to migrate for 834 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.
>
> 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
>
>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
