Bug#1132093: src:ruby-re2: fails to migrate to testing for too long: FTBFS on s390x

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.ports.s390
Message-ID <7aff8299-c5c8-41d5-8e00-840a6dd35b4a__36672.352782783$1774647462$gmane$org@debian.org>
Source: ruby-re2
Version: 2.7.0-3
Severity: serious
Control: close -1 2.23.0-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
User: [email protected]
Usertags: s390x
X-Debbugs-CC: [email protected]

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:ruby-re2 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. 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=ruby-re2

Current text from [2]:
Migration status for ruby-re2 (2.7.0-3 to 2.23.0-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 ruby-re2/2.23.0-1: amd64: Pass, arm64: Pass, i386: 
Pass, ppc64el: Pass, riscv64: Pass
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/r/ruby-re2.html
∙ ∙ Reproducibility regression on amd64: ruby-re2
∙ ∙ Reproducibility regression on arm64: ruby-re2
∙ ∙ Reproducibility regression on armhf: ruby-re2
∙ ∙ Reproducibility regression on i386: ruby-re2
∙ ∙ Reproducibility regression on ppc64el: ruby-re2
∙ ∙ 32 days old (needed 5 days)
OpenPGP_signature.asc (application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJpxvfXCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmf/rrAE8RP1BmLlN3mOIj2fjUHgSPzajRY95iXgbt0K
2hYhBFi2bUhza+k7BS3mcpxcmesFvXUKAADIHgf/VTvhIUyP7qicQ5HoWRt16NE2
j1D+2wtHDrbkQd4Lbt3XVkV/fdz7qWPewolqTrVqLZfa4/eSu/FFRTW6GDpb6k4l
Xe/tz6HSrH7hMZhWIBeQm8pzI8fAkaGn2X5mfyLCnEYUsHdRwsJTQrNOFBwhi6NK
fr9ougklvQXcxrODH38akNfoUNYjCDdFE0ELIVJuw8W8nh9RT+MT4Kem3w12yrij
UUrGmn8xE0w59ARz6sHLCgw64GoYWjpZLAv+NYpEG4fRQKxM9DbO4TcX2x+sSQHE
OgUSjNS7AG72iHq1gHBXuRmX7mFtJs84T98SDvt/gtqQQLiaXDwcAJm2Kl5tCA==
=vVDZ
-----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.