Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.ports.s390
Message-ID <9a42bb4a-6e72-4f58-a55c-5519faec7712__37655.8325182245$1744446091$gmane$org@debian.org>
Source: frr
Version: 10.2.1-6
Severity: serious
Control: close -1 10.3-1
Tags: sid trixie ftbfs
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:frr 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=frr

Current text from [2]:
Migration status for frr (10.2.1-6 to 10.3-1): BLOCKED: Maybe temporary, 
maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ missing build on s390x
∙ ∙ arch:s390x not built yet, autopkgtest delayed there
∙ ∙ autopkgtest for frr/10.3-1: amd64: Pass, arm64: Pass, armel: Pass, 
armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 
Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days)
OpenPGP_signature.asc (application/pgp-signature, 495 B)
-----BEGIN PGP SIGNATURE-----

wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmf6IfoFAwAAAAAACgkQnFyZ6wW9dQqx
oQf9Fu3Q/PeyNLCqUJ9mJ5ZzOCqnXR5kDCWdPQbpM8+5l45dXAEuGrAndGHeZ6rR9ugmCKgrDev1
7EH6WsyrulBzu86Tz08peaMfp7MP94vgXxqsAsjUbf1nhkt87J9E5wMYHhXAU5uauiiCFvsE1qkk
E4bh7dHUrUuRM0CmtIiSZAej8G/Dr20YZxe4iySewZ6fyxssFeIfroyrnJvOfzLtuRVJ5wPVrbqQ
GxQpbZumXDJJrQTuos7iQR8L0Zr5NqTzCxDElcpUoDqyPlFoJzge/k1KtNKBZg1RUd+24QBImMwx
OVld9nWuJsBhy+EKjCx+csvpFH/OaK1U23b3O1kTFg==
=4zMY
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.