Testing: Excuse for gdcm
- Migration status for gdcm (3.0.22-2 to 3.0.22-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- autopkgtest for gdcm/3.0.22-2.1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
- missing build on armel
- missing build on armhf
- arch:armel not built yet, autopkgtest delayed there
- arch:armhf not built yet, autopkgtest delayed there
- Build-Depends(-Arch): gdcm castxml
- Build-Depends(-Arch): gdcm dpkg (not considered)
- Depends: gdcm openssl (not considered)
- Depends: gdcm poppler (not considered)
- Depends: gdcm vtk9 (not considered)
- Additional info:
- Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdcm.html
- Reproducibility regression on amd64 - info ♻
- Ignoring non-reproducibility on arm64 (not a regression) - info ♻
- Waiting for reproducibility test results on armhf - info ♻
- Reproducibility regression on i386 - info ♻
- 30 days old (needed 5 days)
- Depends: gdcm castxml
- Depends: gdcm dpkg
- Depends: gdcm openssl
- Depends: gdcm poppler
- Depends: gdcm vtk9
Excuses generated on: Thu Mar 28 19:06:05 2024 UTC
Maintainer page Package tracker Experimental manual migration pseudo-excuses for gdcm
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).