[DRE-maint] Bug#1122905: src:ruby-sshkey: fails to migrate to testing for too long

[Paul Gevers]

Source: ruby-sshkey
Version: 2.0.0-3
Severity: serious
Control: close -1 3.0.0-1
Tags: sid forky
User: release.debian.org at packages.debian.org
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:ruby-sshkey 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=ruby-sshkey

Current text from [2]:
Migration status for ruby-sshkey (2.0.0-3 to 3.0.0-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ migrating ruby-sshkey/3.0.0-1/amd64 to testing makes 
trocla-puppetserver/0.6.0-1/amd64 uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/arm64 to testing makes 
trocla-puppetserver/0.6.0-1/arm64 uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/armhf to testing makes 
trocla-puppetserver/0.6.0-1/armhf uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/i386 to testing makes 
trocla-puppetserver/0.6.0-1/i386 uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/ppc64el to testing makes 
trocla-puppetserver/0.6.0-1/ppc64el uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/riscv64 to testing makes 
trocla-puppetserver/0.6.0-1/riscv64 uninstallable
∙ ∙ migrating ruby-sshkey/3.0.0-1/s390x to testing makes 
trocla-puppetserver/0.6.0-1/s390x uninstallable
∙ ∙ Autopkgtest for ruby-sshkey/3.0.0-1: amd64: Pass, arm64: Pass, i386: 
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
∙ ∙ Autopkgtest for trocla/0.6.0-1: amd64: Regression ♻ (reference ♻), 
arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), 
ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference 
♻), s390x: Regression ♻ (reference ♻)
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/r/ruby-sshkey.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
∙ 30 days old (needed 5 days)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20251214/efc9ecf7/attachment-0001.sig>