Bug#1125802: src:glslang: fails to migrate to testing for too long: FTBFS on armhf
Paul Gevers <[email protected]>
| Newsgroups | gmane.linux.debian.ports.arm |
|---|---|
| Message-ID | <71c25ba3-b847-4af7-96a5-755a92f2ddc1__28506.0810552508$1768727494$gmane$org@debian.org> |
Source: glslang Version: 16.0.0-3 Severity: serious Control: close -1 16.1.0-1 Tags: sid forky ftbfs User: [email protected] Usertags: out-of-sync User: [email protected] Usertags: armhf 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:glslang 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=glslang Current text from [2]: Migration status for glslang (16.0.0-3 to 16.1.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ Missing build on armhf ∙ ∙ Lintian check waiting for test results on armhf - info Additional info (not blocking): ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glslang.html ∙ ∙ Autopkgtest for glslang/16.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 30 days old (needed 5 days)
OpenPGP_signature.asc
(application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE----- wsC7BAABCABvBYJpbKMsCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcmd3b6Bsx7znEb8LR9ovYRMvJPAhjZh7KxB9tcLzgA5I qBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAAWEQf+JS18NdlrWrxOBv7cwWNOzvmC +3Oh/ckZ5hT7r+txDmAGkqo8V4V53PgNm5vdRZPLjn1FEyiNlptWHU6Jwqw25T1U l0sXJ+VV0v0JiNgqIRHM3e8I3KaclsFKoLN0XSVdmUJPeeYSVaZmBk03syC/cDsB VQ1P5MsBbRZRPvAN07jVK0Wv8fX/Izc+SmloN3lG8w3TjMh1dSIDW3CYHl7ZeALj ecKNEwnRzAmGp4RiIgSUKE8z4QhELpeJ+je4eXVmGgZn8UiRCuPMpYbUA+k7xZmR VHDgo9qmcZDuJw3QMNETYiCHpycbAZ7UhDEJSupb26pkUE33E/UA7GUtKSLRpw== =tlSM -----END PGP SIGNATURE-----