Source: python-av Version: 16.1.0+ds-3 Severity: serious Control: close -1 17.0.1+ds-1 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:python-av 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 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-av Current text from [2]: Migration status for python-av (16.1.0+ds-3 to 17.0.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ python3-av/amd64 has unsatisfiable dependency ∙ ∙ python3-av/arm64 has unsatisfiable dependency ∙ ∙ python3-av/armhf has unsatisfiable dependency ∙ ∙ python3-av/i386 has unsatisfiable dependency ∙ ∙ python3-av/ppc64el has unsatisfiable dependency ∙ ∙ python3-av/riscv64 has unsatisfiable dependency ∙ ∙ python3-av/s390x has unsatisfiable dependency ∙ ∙ Updating python-av would introduce bugs in testing: #1135954 ∙ ∙ Piuparts regression - https://piuparts.debian.org/sid/source/p/python-av.html ∙ ∙ migrating python3-av/17.0.1+ds-1/amd64 to testing makes Build-Depends of src:pims uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/amd64 to testing makes Build-Depends of src:pyinstaller-hooks-contrib uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/amd64 to testing makes Build-Depends of src:python-aiortc uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/amd64 to testing makes python3-aiortc/1.14.0-1/amd64 uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/arm64 to testing makes python3-aiortc/1.14.0-1/arm64 uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/armhf to testing makes python3-aiortc/1.14.0-1/armhf uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/i386 to testing makes python3-aiortc/1.14.0-1/i386 uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/ppc64el to testing makes python3-aiortc/1.14.0-1/ppc64el uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/riscv64 to testing makes python3-aiortc/1.14.0-1/riscv64 uninstallable ∙ ∙ migrating python3-av/17.0.1+ds-1/s390x to testing makes python3-aiortc/1.14.0-1/s390x uninstallable Additional info (not blocking): ∙ ∙ Updating python-av will fix bugs in testing: #1131746 ∙ ∙ Autopkgtest skipped on amd64: not installable ∙ ∙ Autopkgtest skipped on arm64: not installable ∙ ∙ Autopkgtest skipped on i386: not installable ∙ ∙ Autopkgtest skipped on ppc64el: not installable ∙ ∙ Autopkgtest skipped on riscv64: not installable ∙ ∙ Autopkgtest skipped on s390x: not installable ∙ ∙ Reproduced on amd64 - info ∙ ∙ Reproduced on arm64 - info ∙ ∙ Reproduced on armhf - info ∙ ∙ Reproduced on i386 - info ∙ ∙ 21 days old (needed 5 days)
