Source: grub Version: 0.97-83 Severity: serious Control: close -1 0.97-84 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:grub has been trying to migrate for 31 days [2], hence this bug report. The current output of the migration software for this package is copied to the bottom of this report and should list the reason why the package is blocked.... well it doesn't. It seems that grub-legacy Breaks/Replaces the version of grub-pc that is currently in unstable/testing while at the same time it Depends on it. That means the package can't be installed:
The following packages have unmet dependencies: grub-legacy : Depends: grub-pc (>= 2.12-4) but it is not installable E: Unable to correct problems, you have held broken packages.E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. grub-pc:amd64=2.12-5 is not selected for install because:
1. grub-legacy:amd64=0.97-84 is selected for install
2. grub-legacy:amd64 Breaks grub-pc (< 2.12-6)
2. grub-pc:amd64 is selected for install because:
1. grub-legacy:amd64=0.97-84 is selected for install as above
2. grub-legacy:amd64 Depends grub-pc (>= 2.12-4)
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.
This bug submission immediately closes the bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. This bug is also tagged 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.
This bug report has been automatically generated and has only been sent manually. If you have any comments with regards to the content or the process, please reach out to me.
Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html [2] https://qa.debian.org/excuses.php?package=grub Current text from [2]:Migration status for grub (0.97-83 to 0.97-84): Will attempt migration (Any information below is purely informational)
Additional info:∙ ∙ Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/grub.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
