Bug#1121916: src:scalapack: fails to migrate to testing for too long: FTBFS on s390x
Paul Gevers <[email protected]>
| Newsgroups | gmane.linux.debian.ports.s390 |
|---|---|
| Message-ID | <4cce410b-2b5a-4dc8-b284-32c76856dbc0__26988.5445873783$1764871410$gmane$org@debian.org> |
Source: scalapack Version: 2.2.2-1 Severity: serious Control: close -1 2.2.2-2 Tags: sid forky 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:scalapack 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=scalapack Current text from [2]: Migration status for scalapack (2.2.2-1 to 2.2.2-2): 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): ∙ ∙ Updating scalapack will fix bugs in testing: #1097848, #1113484 ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scalapack.html ∙ ∙ No reference result, but not reproducibility on amd64 - info ♻ ∙ ∙ No reference result, but not reproducibility on arm64 - info ♻ ∙ ∙ 30 days old (needed 5 days)
OpenPGP_signature.asc
(application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE----- wsC7BAABCABvBYJpMcyUCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcmfrkixSuseEiTN/rLVJbPY+Bz6oeZwD7+OtRKy+48tf PRYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAA9gAgAgrLlBXU1JfNVzrTLADY9JEMe lt0KDLdREQvOtRE1NLqpvERRYAKWXvlertA/6vBxN40dK/XNSezYcrfZkLFRT6NB pEws1qah4XMDrhhcJrmmr6/aI1NIm6W58vZ71LRZ9EIrN7YQCdPL5j8pDHSSmBzU g1k/Us8IaRUzDWPCy1v3TIOJvEFxdgNFTTrTu2+HNla+lIy3eoULCWoLr5WKU60T DoWc/2Oo1TqAPOtfU/Qk0wFWZ9LmvsyGJ6Qf1ydLGrRwzDe75pIhUY6aNqDsNF+2 Ov3fzHDohB6ilZe3Zc1UopeFLgRgPpZHUAFK9ZZ+uJzg2pX7vbyVpRTP8TsDgg== =U7IN -----END PGP SIGNATURE-----