Bug#1134699: src:gcc-15-cross-ports: fails to migrate to testing for too long: s390x binaries were rejected

Source: gcc-15-cross-ports
Version: 13
Severity: serious
Control: close -1 15
Tags: sid forky
User: [email protected]
Usertags: out-of-sync

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:gcc-15-cross-ports 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.

It turns out that gcc-15-cross-ports version 14 built the same binary 
versions as version 15 earlier that day on s390x. The uploads of version 
15 were rejected by DAK:
Version check failed:
Your upload included the binary package cpp-15-powerpc-linux-gnu, 
version 15.2.0-16cross1, for s390x,
however unstable already has version 15.2.0-16cross1.
Uploads to unstable must have a higher version than present in unstable.

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=gcc-15-cross-ports

Current text from [2]:
Migration status for gcc-15-cross-ports (13 to 15): 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
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/g/gcc-15-cross-ports.html
∙ ∙ Reproduced on amd64
∙ ∙ Reproduced on arm64
∙ ∙ Reproduced on armhf
∙ ∙ Reproduced on i386
∙ ∙ Reproduced on ppc64el
∙ ∙ 31 days old (needed 5 days)

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

wsC7BAABCABvBYJp6dzLCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmcsy4fNYA5oeWUJWhWD0esmZ3hmtgxdsEITYIYqX1Mc
YxYhBFi2bUhza+k7BS3mcpxcmesFvXUKAACiJgf/WBrI80/CiHcqvToUfGpraKK/
06YctoCrq00i56ksariWmDj7qNI4PZSgXjLs2Ay7zbWUyzAgPWeK+cR6iH+kCAI9
ZfFvA/xPFMF5cly4Tu48Hu2ojxLkIrypw0KtHlneW9nbqTSXTro4tbJmuoEQUDm+
s87QAdpB+Mt7Tx4deG8cfmIL0dG6HB1EKaepxGriOcIzdsDzRYzOjIGZ827hH/r5
IP+qOXypJwXrOhbVuC7YtClvIm+lVoCA1I8fddbbgxsHLpDyqwEijf8BfkvLpMgr
hAbxswryq21pMLudNOjhU6AlDE6T9Qx1F/ulEdQV5N6gH5I3FBlTrULrIlQ18g==
=UjPe
-----END PGP SIGNATURE-----