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

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.ports.s390
Message-ID <d71e8fe8-064c-4251-9990-abde2bf3486b__32540.0843446673$1764234093$gmane$org@debian.org>
Source: ruby-murmurhash3
Version: 0.1.6-2
Severity: serious
Control: close -1 0.1.7-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:ruby-murmurhash3 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=ruby-murmurhash3

Current text from [2]:
Migration status for ruby-murmurhash3 (0.1.6-2 to 0.1.7-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-murmurhash3/0.1.7-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-murmurhash3.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
∙ 31 days old (needed 5 days)
OpenPGP_signature.asc (application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJpKBLECRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmeUja/gNaRRiPKEur703NI42FRCuDezZoZClXvuOZz7
sRYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAAeswf+Oeyuko89XrnmtnKU1KnEnBkM
PwPg6jHQyl31e2TlDGBH26xopokYg7r1vtCJVqypsGI0vd8Qqu6rLyZFkrGoAGup
LU9vBlkI2aV9qc/qN0LbGjbuJCjioESrQ9jB0MS3ugKbu6x0UopZK35dICfbJYql
9bsLS0v37lXWHQXYc30u4hC0iIbU1Yx2KJlbB5qJ0Lb4zkexX1cM90LF6Twd951J
EH80nhcI6aMrfA05oj4u49aU7TqwncqkcUSj7WznxOFS4s1DZqytWtvvWL1Fd5hk
/BZwT5+cqQCcXS89gfOpWYzQKP7ar4xTA+2ApF6LPWchETBPlUz03cy2BgmQUw==
=peDS
-----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.