Testing: Excuse for networking-bagpipe
- Migration status for networking-bagpipe (- to 20.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- autopkgtest for networking-bagpipe/20.0.1-2: amd64: Pass, arm64: Pass, i386: Regression or new test ♻, ppc64el: Pass, s390x: Pass
- Build-Depends-Indep: networking-bagpipe networking-bgpvpn (not considered)
- Build-Depends-Indep: networking-bagpipe networking-sfc (not considered)
- Build-Depends-Indep: networking-bagpipe sphinxcontrib-nwdiag
- Depends: networking-bagpipe networking-bgpvpn (not considered)
- Depends: networking-bagpipe networking-sfc (not considered)
- Additional info:
- Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bagpipe.html
- Reproducible on amd64 - info ♻
- Reproducible on arm64 - info ♻
- Waiting for reproducibility test results on armhf - info ♻
- Waiting for reproducibility test results on i386 - info ♻
- 9 days old (needed 5 days)
- Depends: networking-bagpipe networking-bgpvpn
- Depends: networking-bagpipe networking-sfc
- Depends: networking-bagpipe sphinxcontrib-nwdiag
Excuses generated on: Sat Apr 27 09:05:34 2024 UTC
Maintainer page Package tracker
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).