Bug#1130024: src:cbor2: fails to migrate to testing for too long: FTBFS on armhf

Source: cbor2
Version: 5.8.0-1
Severity: serious
Control: close -1 5.8.0-3
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: 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:cbor2 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 
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 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=cbor2

Current text from [2]:
Migration status for cbor2 (5.8.0-1 to 5.8.0-3): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on armhf
∙ ∙ Lintian check waiting for test results on armhf - info
∙ ∙ Reproducibility check deferred on armhf: missing builds
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cbor2.html
∙ ∙ Autopkgtest for cbor2/5.8.0-3: amd64: No tests, superficial or 
marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked 
flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ 
(reference ♻), ppc64el: No tests, superficial or marked flaky ♻, 
riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, 
superficial or marked flaky ♻
∙ ∙ Reproduced on amd64
∙ ∙ Reproduced on arm64
∙ ∙ Reproduced on i386
∙ ∙ Reproduced on ppc64el
∙ ∙ 15 days old (needed 5 days)

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

wsC7BAABCABvBYJprE2CCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmf5mtNkt60kUaO3CKUKFoiKLAxQIuEM6punQLy2uqEv
UBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAACObggAgZyNLO7vGi+6A60AhHCoyQnq
kcwcGsgX3F7rwRyi7Bvc0GRpM+mHgiyV0by2xGIIBo2O8Xs+V7D5Ap7yfUBDOK9q
z5JgH3U9jyXTMHlUFU4Ixa4AhLj0m1i+AsCKWQBJnsLA495SgkuiWICR6380WdrJ
H1fwks5MIqAq+SiE0iSQzMMJYcnh9pPc8y1i1goknebjIzxC3U8sSUrns9cfwFqC
tda/pes3Xk9c+9WKReJlSVPs8zQE3U/ofnhMsG6J7HlfhpfzbA5VhQNRH526Wcce
sPhf/Vfi55xFtzTYt/xTjHripdSAfNMsDtxmp5XDKGp+38yCmRlrli52UUkLWw==
=IK2j
-----END PGP SIGNATURE-----