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 will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
-
excuses:
- Migration status for libgit2 (1.9.2+ds-9 to 1.9.3+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for libgit2/1.9.3+ds-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for ruby-rugged/1.9.0+ds-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Reference test triggered, but real test failed already ♻
- ∙ ∙ Autopkgtest for rust-debcargo/2.8.2-2: i386: Pass ♻, riscv64: Pass ♻ (reference ♻), s390x: Pass ♻
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgit2.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 12 days old (needed 5 days)
- Not considered
-
all:
2
-
RC:
0
-
I&N:
2
-
M&W:
0
-
F&P:
0
-
patch:
0
![[bug history graph]](https://qa.debian.org/data/bts/graphs/libg/libgit2.png){kind=link}