[Debian-med-packaging] Bug#1101873: src:bali-phy: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Source: bali-phy
Version: 3.6.1+dfsg-3
Severity: serious
Control: close -1 4.0-1
Tags: sid trixie ftbfs
User: release.debian.org at packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-arm at lists.debian.org
User: debian-arm at lists.debian.org
Usertags: armel armhf

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:bali-phy 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. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or its 
(reverse-)dependencies. We expect maintainers to fix issues that hamper 
the migration of their package in a timely manner.

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 
trixie, 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 and has only been sent 
manually. 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=bali-phy

Current text from [2]:
Migration status for bali-phy (3.6.1+dfsg-3 to 4.0-1): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ missing build on armel
∙ ∙ missing build on armhf
∙ ∙ arch:armel not built yet, autopkgtest delayed there
∙ ∙ arch:armhf not built yet, autopkgtest delayed there
∙ ∙ autopkgtest for bali-phy/4.0-1: amd64: Pass, arm64: Pass, i386: 
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
Additional info:
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/b/bali-phy.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Waiting for reproducibility test 
results on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 31 days 
old (needed 5 days)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20250401/700781ec/attachment.sig>