Source: borgbackup2 Version: 2.0.0b20-2 Severity: serious Control: close -1 2.0.0b20-4 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:borgbackup2 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. 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. Blocked packages can have impact on other packages, which makes preparing for the release more difficult. The situation that caused this bug report might even be the result of such an issue. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. If your package in this situation do to another package, consider helping out. 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. 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=borgbackup2 Current text from [2]: Migration status for borgbackup2 (2.0.0b20-2 to 2.0.0b20-4): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Updating borgbackup2 would introduce bugs in testing: #1127849 Additional info (not blocking): ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/b/borgbackup2.html ∙ ∙ Autopkgtest for borgbackup2/2.0.0b20-4: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ∙ ∙ Reproduced on amd64 ∙ ∙ Reproduced on arm64 ∙ ∙ Reproduced on armhf ∙ ∙ Reproduced on i386 ∙ ∙ Reproduced on ppc64el ∙ ∙ 31 days old (needed 5 days)
