Source: bluez Version: 5.84-1 Severity: serious Control: close -1 5.85-3 Tags: sid forky User: [email protected] 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:bluez has been trying to migrate for 33 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.
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 forky, 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=bluez Current text from [2]:Migration status for bluez (5.84-1 to 5.85-3): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration: ∙ ∙ Updating bluez would introduce bugs in testing: #1124744 Additional info (not blocking): ∙ ∙ Updating bluez will fix bugs in testing: #1123793 ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluez.html∙ ∙ Autopkgtest for bluez/5.85-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻ ∙ ∙ Autopkgtest for libreoffice/4:25.8.4-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass, s390x: Pass
∙ ∙ Not reproducible on amd64 (not a regression): bluez-source ∙ ∙ Not reproducible on arm64 (not a regression): bluez-source ∙ ∙ Not reproducible on armhf (not a regression): bluez-source ∙ ∙ Not reproducible on i386 (not a regression): bluez-source ∙ ∙ Not reproducible on ppc64el (not a regression): bluez-source ∙ ∙ 30 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
