action needed
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
-
This package is part of the ongoing testing transition known as auto-upperlimit-ruby-retriable.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
-
excuses:
- Migration status for ruby-retriable (4.2.0-1 to 5.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ migrating ruby-retriable/5.0.1-1/amd64 to testing makes ruby-google-apis-core/1.2.3-1/amd64 uninstallable
- ∙ ∙ migrating ruby-retriable/5.0.1-1/arm64 to testing makes ruby-google-apis-core/1.2.3-1/arm64 uninstallable
- ∙ ∙ Autopkgtest for ruby-google-api-client/0.53.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for ruby-google-apis-core/1.2.3-1: amd64: Test deferred, arm64: Test deferred, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for ruby-retriable/5.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-retriable.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 7 days old (needed 5 days)
- Not considered