Source: gst-plugins-bad1.0
Version: 1.18.0-2
Severity: serious
Control: close -1 1.18.2-1
Tags: sid bullseye
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 976288

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:gst-plugins-bad1.0 in unstable has been trying to migrate for 61
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.

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.
In this case, I think it may be wise to upload to
testing-proposed-updates and ask for an unblock. Otherwise your two bug
fix releases may not make it to bullseye.

Paul

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


Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to