Testing: Excuse for python-dbus-next
- Migration status for python-dbus-next (0.2.3-5 to 0.2.3-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Piuparts check waiting for test results - https://piuparts.debian.org/sid/source/p/python-dbus-next.html
- Autopkgtest for playerctl: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- Autopkgtest for python-dbus-next: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- Autopkgtest for qtile: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- Lintian check waiting for test results on all - info
- Too young, only 0 of 5 days old
- Additional info (not blocking):
- Reproducibility check waiting for results on amd64
- Reproducibility check waiting for results on arm64
- Reproducibility check waiting for results on armhf
- Reproducibility check waiting for results on i386
- Reproducibility check waiting for results on ppc64el
Excuses generated on: Thu Feb 5 09:14:22 2026 UTC
Maintainer page Package tracker
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).
