Bug#1149587: src:lfortran: fails to migrate to testing for too long: FTBFS on armhf and i386

[Paul Gevers]

Source: lfortran
Version: 0.64.0-1
Severity: serious
Control: close -1 0.66.0-3
Tags: sid forky
User: release.debian.org at packages.debian.org
Usertags: out-of-sync

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:lfortran 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. Regularly, reporting 
issues against reverse (build/test/regular) dependencies is what needs 
to happen. If this has already been done, than this bug is just for 
tracking purposes.

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=lfortran

Current text from [2]:
Migration status for lfortran (0.64.0-1 to 0.66.0-3): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on armhf
∙ ∙ Missing build on i386
∙ ∙ Missing build on riscv64
∙ ∙ Autopkgtest deferred on armhf: missing arch:armhf build
∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Autopkgtest for lfortran/0.66.0-3: amd64: Pass, arm64: Pass, 
ppc64el: Pass, s390x: Pass
∙ ∙ Lintian check waiting for test results on armhf, riscv64, i386 - info
∙ ∙ Reproducibility check deferred on armhf: missing builds - info
∙ ∙ Reproducibility check deferred on i386: missing builds - info
∙ ∙ Too young, only 3 of 5 days old
∙ ∙ Depends: lfortran xeus
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/l/lfortran.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
-------------- 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/debian-science-maintainers/attachments/20261001/db1b7a82/attachment.sig>