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

[Aurelien Jarno]

control: tag -1 +patch

Hi,

On 2026-04-17 21:19, Paul Gevers wrote:
> 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

It happens that the FTBFS is just a timeout in the testsuite depending 
on the machine running the build. The following patch increases the 
timeout and fixes the issue:

--- apparmor-4.1.7.orig/utils/test/test-logprof.py
+++ apparmor-4.1.7/utils/test/test-logprof.py
@@ -66,7 +66,7 @@
         self.process.stdin.close()
         self.process.stdout.close()
         self.process.terminate()
-        self.process.wait(timeout=0.3)
+        self.process.wait(timeout=0.6)
 
     def _run_test(self, params, expected):
         auditlog = './logprof/%s.auditlog' % params
@@ -127,7 +127,7 @@
             output = self.process.stdout.readline().decode("utf-8").strip()
             self.assertEqual(output, line)
         # give logprof some time to write the updated profile and terminate
-        self.process.wait(timeout=0.6)
+        self.process.wait(timeout=1.2)
         self.assertEqual(self.process.returncode, 0)
 
Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                     http://aurel32.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-apparmor-team/attachments/20260420/883ac4a5/attachment-0003.sig>