action needed
A new upstream version is available: 2.0.5
high
A new upstream version 2.0.5 is available, you should consider packaging it.
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:
- Migration status for maven-resolver (1.6.3-1 to 1.9.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ autopkgtest for pomegranate-clojure/1.2.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
- ∙ ∙ autopkgtest for tools-deps-clojure/0.21.1460-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maven-resolver.html
- ∙ ∙ Reproducible on amd64 - info ♻
- ∙ ∙ Reproducible on arm64 - info ♻
- ∙ ∙ Reproducible on armhf - info ♻
- ∙ ∙ Reproducible on i386 - info ♻
- ∙ ∙ 13 days old (needed 5 days)
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/maven-resolver.png){kind=link}