Source: python-django Version: 3:4.2.30-1 Severity: serious Control: close -1 3:5.2.14-2 Tags: sid forky User: [email protected] Usertags: out-of-sync Control: block -1 by 1135698
Dear maintainer(s),[ This bug is just filed for tracking purposes, text below is from my template. ].
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:python-django has been trying to migrate for 32 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 due 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=python-django Current text from [2]:Migration status for python-django (3:4.2.30-1 to 3:5.2.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:∙ ∙ migrating python3-django/3:5.2.14-2/amd64 to testing makes python3-django-postorius/1.3.13-1+deb13u1/amd64 uninstallable ∙ ∙ migrating python3-django/3:5.2.14-2/arm64 to testing makes python3-django-postorius/1.3.13-1+deb13u1/arm64 uninstallable ∙ ∙ Autopkgtest for debusine/0.14.7: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Ignored failure ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻) ∙ ∙ Autopkgtest for horizon/3:25.7.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass ∙ ∙ Autopkgtest for hyperkitty/1.3.12-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻) ∙ ∙ Autopkgtest for postorius/1.3.13-1+deb13u1: amd64: Test deferred, arm64: Test deferred, i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻) ∙ ∙ Autopkgtest for python-django/3:5.2.14-2: amd64: Ignored failure ♻ (reference ♻), arm64: Pass, i386: Pass, ppc64el: Ignored failure ♻ (reference ♻), riscv64: Pass, s390x: Ignored failure ♻ (reference ♻) ∙ ∙ Autopkgtest for python-hypothesis/6.152.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
Additional info (not blocking):∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
∙ ∙ Reproduced on amd64 - info ∙ ∙ Reproduced on arm64 - info ∙ ∙ Reproduced on armhf - info ∙ ∙ Reproduced on i386 - info ∙ ∙ 17 days old (needed 2 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
