Public bug reported: Imported from Debian bug http://bugs.debian.org/1120585:
Source: m2crypto Version: 0.42.0-3 Severity: serious Control: close -1 0.46.2-1 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:m2crypto 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=m2crypto Current text from [2]: Migration status for m2crypto (0.42.0-3 to 0.46.2-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/m/m2crypto.html ��� ��� Autopkgtest for m2crypto/0.46.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass ��� ��� Ignoring non-reproducibility on amd64 (not a regression) - info ��� ��� ��� Ignoring non-reproducibility on arm64 (not a regression) - info ��� ��� ��� Required age reduced by 3 days because of autopkgtest ��� ��� 31 days old (needed 2 days) ** Affects: m2crypto (Ubuntu) Importance: Undecided Status: New ** Affects: m2crypto (Debian) Importance: Undecided Status: New ** Tags: ftbfs update-excuse ** Bug watch added: Debian Bug tracker #1120585 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120585 ** Changed in: m2crypto (Debian) Remote watch: None => Debian Bug tracker #1120585 ** Tags added: ftbfs update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2131446 Title: src:m2crypto: fails to migrate to testing for too long: FTBFS on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/2131446/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
