Bug#1145090: src:python-fitsio: fails to migrate to testing for too long: FTBFS: test fails on s390x

Source: python-fitsio
Version: 1.4.0+ds-1
Severity: serious
Control: close -1 1.4.2+ds-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: s390x

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:python-fitsio 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=python-fitsio

Current text from [2]:
Migration status for python-fitsio (1.4.0+ds-1 to 1.4.2+ds-1): BLOCKED: 
Maybe temporary, maybe blocked but Britney is missing information (check 
below)
Issues preventing migration:
∙ ∙ Missing build on s390x
∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build
∙ ∙ Autopkgtest for python-fitsio/1.4.2+ds-1: amd64: Pass, arm64: Pass, 
armhf: Pass, i386: Pass, ppc64el: Pass
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/p/python-fitsio.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 31 days old (needed 5 days)

-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJqiXHdCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmf87Da9Qj7Rh26pNqPPqN6QXxA2Zk7PA2nFLNOn/+l3
cxYhBFi2bUhza+k7BS3mcpxcmesFvXUKAACSgQf/ZC2YrXVMVOSwHligLpsFM7Mw
Mljw5/pb7D/gpxa5pIv5jFX9sO0IWWXNSbujShL9Xd0KPcT280EQuBJTvvA9aw6X
hKeoUJSf9L8y84IPGKFdy/RokBOYM11ITjRf/pG8vG0Cp9vJ82zlEocJXJr3U/XL
wkKaPqGNiWTX5jWtjH9G1J+U71nlVp6Ss6BvfRK9g4iMvuYTyOEqONqfAIB4WoOL
r1TxWskmNtpts7Zc8K6CGQnoUK1mMiJOR6YKuGEM3Pwdea8NntPpdrWHD9GxHghR
jajvzQTG7J6LUMJeJ5ZE9drvxAITTwUKmIrAbh4jHcy/R4MfvRJUmhsch3iJxQ==
=WvMy
-----END PGP SIGNATURE-----