Source: ruby-active-storage-validations
Version: 3.0.5-2
Severity: serious
Control: close -1 4.1.0-1
Tags: sid forky
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-CC: debian-riscv@lists.debian.org

[Manual note: the autopkgtest fail consistently on riscv64]

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-active-storage-validations 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. Regularly, reporting issues against reverse
(build/test/regular) dependencies is what needs to happen. If this has
already been done, than this bug is just for tracking purposes.

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. Blocked packages can have impact on other packages,
which makes preparing for the release more difficult. The situation that
caused this bug report might even be the result of such an issue. We
expect maintainers to fix issues that hamper the migration of their
package in a timely manner. If your package in this situation due to
another package, consider helping out.

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. 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-active-storage-validations

Current text from [2]:
Migration status for ruby-active-storage-validations (3.0.5-2 to
4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a
regression
Issues preventing migration:
∙ ∙ Autopkgtest for ruby-active-storage-validations/4.1.0-1: amd64:
Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64:
Regression ♻ (reference ♻)
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/r/ruby-active-storage-validations.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 8 days old (needed 5 days)