Bug#1128638: src:chuck: fails to migrate to testing for too long: FTBFS on ppc64el
Paul Gevers <[email protected]> Sun, 22 Feb 2026 07:57:12 +0100
| Newsgroups | gmane.linux.debian.ports.powerpc |
|---|---|
| Message-ID | <e683f3ca-3cae-4602-a4ca-414b1570b221__39792.1988669381$1771743575$gmane$org@debian.org> |
Source: chuck Version: 1.5.5.5-1 Severity: serious Control: close -1 1.5.5.7-1 Tags: sid forky User: [email protected] Usertags: out-of-sync X-Debbugs-CC: [email protected] User: [email protected] Usertags: ppc64el 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:chuck has been trying to migrate for 40 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=chuck Current text from [2]: Migration status for chuck (1.5.5.5-1 to 1.5.5.7-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: ∙ ∙ Missing build on ppc64el ∙ ∙ Autopkgtest deferred on ppc64el: missing arch:ppc64el build ∙ ∙ Lintian check waiting for test results on ppc64el - info ∙ ∙ Reproducibility check deferred on ppc64el: missing builds Additional info (not blocking): ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chuck.html ∙ ∙ Reproducible on amd64 ∙ ∙ Reproducible on arm64 ∙ ∙ Reproducible on armhf ∙ ∙ Reproducible on i386 ∙ ∙ 39 days old (needed 5 days)
OpenPGP_signature.asc
(application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE----- wsC7BAABCABvBYJpmqjICRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcme9VykCpS+7zjPS8n9ONTcheVfTWyK5uWp1xHx5aT8c pxYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAD9gAf/YMdMM3b8EPQXigq+U45SqAUS 3LbGuc+Cc+oQP4223ZWi0PTaXUIN9F5ilCVMWhOvOfR2kxROd6G9v/4NHxJHWITo ym7zG/h/g9BkRoL+TiBLlhKqH9bSqq0x0bDNTPkAZjJPJkCmpKhSkvcz7PwDAlRH rMRphbIPTcrv4RhabbSJdKjm1SX6341qkxG2YG/SFucI7DdIha2sJkEd+7WON3uv OR8z8ZDub8Tmy0xm6RiLg2LIL75EwGDIiF6yTzq8H+TakK5waUxUrR9rZolOjUEU 850idqZjN7BrUWqeCyQrR/0W9QU2xbD9WE5lVDdzhNIleX37lpNBePeElHScOA== =SiFW -----END PGP SIGNATURE-----