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
-
excuses:
- Migrates after: rust-aes, rust-ctr, rust-ghash
- Migration status for rust-aes-gcm (0.10.3-2 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for rust-aes-gcm/0.11.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for rust-hpke/0.13.0+ds-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ Build-Depends(-Arch): rust-aes-gcm rust-aes (not considered)
- ∙ ∙ Build-Depends(-Arch): rust-aes-gcm rust-ctr (not considered)
- ∙ ∙ Build-Depends(-Arch): rust-aes-gcm rust-ghash
- ∙ ∙ Depends: rust-aes-gcm rust-aes (not considered)
- ∙ ∙ Depends: rust-aes-gcm rust-ctr (not considered)
- ∙ ∙ Depends: rust-aes-gcm rust-ghash
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aes-gcm.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 16 days old (needed 5 days)
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/r/rust-aes-gcm.png){kind=link}