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:r-cran-broom.helpers 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
trixie, 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=r-cran-broom.helpers

Current text from [2]:
Migration status for r-cran-broom.helpers (1.14.0-3 to 1.20.0-1):
BLOCKED: Cannot migrate due to another item, which is blocked (please
check which dependencies are stuck)
Issues preventing migration:
∙ ∙ Build-Depends(-Arch): r-cran-broom.helpers r-cran-cards (not considered)
∙ ∙ Depends: r-cran-broom.helpers r-cran-cards (not considered)
∙ ∙ Invalidated by build-dependency
∙ ∙ Invalidated by dependency
Additional info:
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/r/r-cran-broom.helpers.html
∙ ∙ autopkgtest for r-cran-broom.helpers/1.20.0-1: amd64: Pass, arm64:
Pass, armel: Failed (not a regression), armhf: Failed (not a
regression), i386: Failed (not a regression), ppc64el: Pass, riscv64:
Pass, s390x: Pass
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙
Reproducible on i386 - info ♻ ∙ ∙ 31 days old (needed 5 days)

This package can't migrate during the soft freeze because the new
version adds a dependency on r-cran-cards, which is not currently in
testing at all.

Since there are no other Debian bugs in the testing version, and we can
do a +really revert if it does become necessary to fix a bug via
unstable, I do not expect this to be a problem.

This package can't migrate during the soft freeze because the new
version adds a dependency on r-cran-cards, which is not currently in
testing at all.

Since there are no other Debian bugs in the testing version, and we can
do a +really revert if it does become necessary to fix a bug via
unstable, I do not expect this to be a problem.

Hi,


For the record, I don't fully agree with this bug resolution.

Paul

There are two reasons why this package still hasn't migrated, both of
which will go away if (as proposed, see debian-r discussion from
2025-03/2025-04) r-cran* are made 64-bit only:

- This package depends on r-cran-cards, which fails its autopkgtest on
i386 (probably due to x87 excess precision, though I have not checked that).
- This package also test-depends on r-cran-glmmtmb, which is now
explicitly 64-bit only.

Control: severity -1 serious

Now that the trixie release happened, this bug is really RC again.

Paul