Source: rocm-hipamd
Version: 5.7.1-3
Severity: serious
Control: close -1 5.7.1-4
Tags: sid trixie
User: release.debian....@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:rocm-hipamd has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The upload of the version in unstable included binaries built by the uploader for arch:all which we can't successfully binNMU on the infrastructure, while at the same time we don't allow binaries not build by the buildds. Normally I would upload a no-change-source-only NMU to DELAYED/15 together with filling the bug, but there's currently an RC bug open, so I'll refrain from doing that.

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 trixie, 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/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=rocm-hipamd

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to