Testing: Excuse for ruby-power-assert
- Migration status for ruby-power-assert (2.0.5-1 to 3.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Autopkgtest for jruby/9.4.8.0+ds-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: Test triggered
- Autopkgtest for ruby-minitest-power-assert/0.3.1-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- Autopkgtest for ruby-power-assert/3.0.1-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- Autopkgtest for ruby-test-unit/3.6.2-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- Lintian check waiting for test results - info
- Too young, only 0 of 5 days old
- Additional info (not blocking):
- Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-power-assert.html
- Reproducible on amd64
- Reproducible on arm64
- Reproducible on armhf
- Reproducible on i386
- Reproducible on ppc64el
Excuses generated on: Mon Feb 9 00:14:52 2026 UTC
Maintainer page Package tracker
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).