Testing: Excuse for rust-libseccomp
- Migration status for rust-libseccomp (0.3.0-11 to 0.4.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on riscv64
- arch:riscv64 not built yet, autopkgtest delayed there
- autopkgtest for rust-glycin/2.1.1-1: amd64: Test triggered, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- autopkgtest for rust-glycin-utils/3.0.1-1: amd64: Test triggered, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- autopkgtest for rust-libseccomp/0.4.0-3: amd64: Test triggered, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- Waiting for lintian test results on riscv64 - info
- Too young, only 0 of 5 days old
- Build-Depends(-Arch): rust-libseccomp rust-libseccomp-sys
- Depends: rust-libseccomp rust-libseccomp-sys
- Additional info:
- Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libseccomp.html
- Waiting for reproducibility test results on amd64 - info ♻
- Waiting for reproducibility test results on arm64 - info ♻
- Depends: rust-libseccomp rust-libseccomp-sys
Excuses generated on: Sun Sep 7 08:05:28 2025 UTC
Maintainer page Package tracker Experimental manual migration pseudo-excuses for rust-libseccomp
Testing migration hints, key packages, autoremovals (YAML), excuses (YAML), log, cruft, documentation.
Experimental manual migration pseudo-excuses (YAML).