Testing: Excuse for pyrate-limiter
- Migration status for pyrate-limiter (3.9.0-1 to 3.9.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- autopkgtest for pyrate-limiter/3.9.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered (will not be considered a regression) ♻ (reference ♻)
- autopkgtest for python-roborock/2.60.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- Waiting for lintian test results on all - info
- Too young, only 0 of 5 days old
- Built-Using: pyrate-limiter sphinx (not considered)
- Additional info:
- Updating pyrate-limiter will fix bugs in testing: #1115767
- Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrate-limiter.html
- Waiting for reproducibility test results on amd64 - info ♻
- Waiting for reproducibility test results on arm64 - info ♻
- Depends: pyrate-limiter sphinx
Excuses generated on: Wed Oct 22 18:05:03 2025 UTC
Maintainer page Package tracker
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).