Testing: Excuse for ruby-get-process-mem
- Migration status for ruby-get-process-mem (0.2.5-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Autopkgtest for ruby-get-process-mem/1.0.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered
- Autopkgtest for ruby-puma-worker-killer/0.3.1-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Reference test triggered, but real test failed already ♻, riscv64: Regression ♻ (reference ♻), s390x: Test triggered
- Autopkgtest for ruby-rspec-profiling/0.0.9-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, 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-get-process-mem.html
- Waiting for reproducibility test results on amd64 - info ♻
- Reproducible on arm64 - info ♻
Excuses generated on: Thu Nov 13 06:04:21 2025 UTC
Maintainer page Package tracker
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).