action needed
A new upstream version is available: 6.11.1
high
A new upstream version 6.11.1 is available, you should consider packaging it.
The package has not entered testing even though the delay is over
normal
The package has not entered testing even though the 5-day delay is over.
Check why.
testing migrations
-
excuses:
- Migrates after: libodsstream, libpappsomspp, libxpertmass
- Migration status for qt6-5compat (6.10.2-2 to 6.10.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:ecflow uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:massxpert3 uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:metview uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:minexpert3 uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:mixxx uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:mlt uninstallable
- ∙ ∙ migrating qt6-5compat-dev/6.10.2-3/amd64 to testing makes Build-Depends of src:v4l-utils uninstallable
- ∙ ∙ Autopkgtest for ecflow/5.16.0-1: amd64: Test deferred, arm64: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Implicit dependency: qt6-5compat libodsstream
- ∙ ∙ Implicit dependency: qt6-5compat libpappsomspp (not considered)
- ∙ ∙ Implicit dependency: qt6-5compat libxpertmass (not considered)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6-5compat.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 12 days old (needed 5 days)
- Not considered