Source: jellyfish
Version: 2.3.0-13
Severity: serious
Control: close -1 2.3.0-14
Tags: sid bookworm
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1017261

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:jellyfish has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Although your package built on all official architectures by now, it's reported to FTBFS in bug #1017261 and also reproducible-builds.org shows your package FTBFS in both unstable and bookworm.

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 bookworm, 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=jellyfish

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to