Bug#1129008: src:rspamd: fails to migrate to testing for too long: FTBFS on armhf
Paul Gevers <[email protected]>
| Newsgroups | gmane.linux.debian.ports.arm |
|---|---|
| Message-ID | <bfc9cdea-86a1-4b8a-9b73-6f8900bf107c__35136.6116594122$1772044894$gmane$org@debian.org> |
Source: rspamd Version: 3.13.2-1 Severity: serious Control: close -1 3.14.3-1 Tags: sid forky User: [email protected] Usertags: out-of-sync X-Debbugs-CC: [email protected] User: [email protected] Usertags: armhf 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:rspamd 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=rspamd Current text from [2]: Migration status for rspamd (3.13.2-1 to 3.14.3-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 ∙ ∙ Reproducibility check deferred on armhf: missing builds Additional info (not blocking): ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rspamd.html ∙ ∙ Autopkgtest for rspamd/3.14.3-1: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass ∙ ∙ Reproducible on amd64 ∙ ∙ Reproducible on arm64 ∙ ∙ Reproducible on i386 ∙ ∙ Reproducible on ppc64el ∙ ∙ Required age reduced by 3 days because of autopkgtest ∙ ∙ 30 days old (needed 2 days)
OpenPGP_signature.asc
(application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE----- wsC7BAABCABvBYJpn0GeCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcme6ocP0tFrSb/XNbXsTnmJ/tO5xfpgJKn2CmKy4o+Tr fBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAD3KggAnW8LRcgHDv9Kmb7gXOOldP07 sAQHGKnrza+A/LEXxJOusFUGIIknkuulLK3ezAKO0iCEoOIE7OnatnjSq8qHNIgO +UNIDhYxH0NdABuYhVLjpJciTUTs34AbuPxrk91Z3W6ise8HO/LjkxuoqOZNsmOo ewHn+rGXU8tQmUrCDQ+pVLvZ2mkZVM5mS5umngKrkfaTAg02eEaDAROga+4Q98eM tJpX8/FbfoaKOi3NIfLK4bE6HQyYoDZ7NwKElwV8VmH7J5CMsu/0L5DZo18Si2Mb CvkfVTHWmGPC8FAnHBPDO7PuHlcfUNeWXp7/c5q272/BF9kSjamHKoaMdjABpA== =WNuu -----END PGP SIGNATURE-----