[Debian-med-packaging] Bug#968436: cluster3: fails to migrate to testing for too long

[Graham Inggs]

Source: cluster3
Version: 2.4.1-1
Severity: serious
Control: close -1 2.4.1-2
Tags: sid bullseye
User: release.debian.org at packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: elbrus at debian.org

Hi Maintainer

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:bppsuite in its current version in unstable has been trying to
migrate for 63 days [2]. Hence, I am filing this bug.

In this case, cluster 3 is non-free, and binaries are not autobuilt on
the buildds so a source-only upload does not work.  You can still
build the package locally and upload the binary packages for 2.4.1-2,
without having to bump the version.

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
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.

Regards
Graham

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=cluster3