[pkg-apparmor] Bug#1134203: src:apparmor: fails to migrate to testing for too long: FTBFS on riscv64

[Paul Gevers]

Source: apparmor
Version: 4.1.6-3
Severity: serious
Control: close -1 4.1.7-1
Tags: sid forky ftbfs
User: release.debian.org at packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-riscv at lists.debian.org
User: debian-riscv at lists.debian.org
Usertag: riscv64

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:apparmor has been trying to migrate for 31 
days [2], hence this bug report. The current output of the migration 
software for this package is copied to the bottom of this report and 
should list the reason why the package is blocked.

If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Blocked packages can have impact on other packages, 
which makes preparing for the release more difficult. The situation that 
caused this bug report might even be the result of such an issue. We 
expect maintainers to fix issues that hamper the migration of their 
package in a timely manner. If your package in this situation due to 
another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in 
unstable, so if that version or a later version migrates, this bug will 
no longer affect testing. This bug is also tagged to only affect sid and 
forky, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any 
comments with regards to the content or the process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=apparmor

Current text from [2]:
Migration status for apparmor (4.1.6-3 to 4.1.7-1): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on riscv64
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Autopkgtest for apparmor/4.1.7-1: amd64: Pass, arm64: Pass, i386: 
Pass, ppc64el: Pass, s390x: Pass
∙ ∙ Autopkgtest for libreoffice/4:26.2.2.2-3: amd64: Pass, arm64: Test 
triggered (failure will be ignored), i386: Test triggered (failure will 
be ignored), ppc64el: Pass, s390x: Pass
∙ ∙ Autopkgtest for podman/5.8.1+ds1-3: s390x: Pass ♻ (reference ♻)
∙ ∙ Lintian check waiting for test results on riscv64 - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/a/apparmor.html
∙ ∙ Reproduced on amd64
∙ ∙ Reproduced on arm64
∙ ∙ Reproduced on armhf
∙ ∙ Reproduced on i386
∙ ∙ Reproduced on ppc64el
∙ ∙ 31 days old (needed 5 days)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-apparmor-team/attachments/20260417/a59e50d0/attachment.sig>