Hi Paul,
On 21 March 2026 at 08:27, Paul Gevers wrote: | Source: r-cran-rms | Version: 8.1-0-1 | Severity: serious | Control: close -1 8.1-1-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:r-cran-rms 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. 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. 100% "due to issue beyond my control" -- this is once again the debian-r team, these days effectively reduced to Charles, who is currently on vacation, deciding they need to test _suggested packages_ as _dependencies_ across all architectures. CRAN upstream does not do that. While they have less 'breadth' than we do in machine architecture, they do test on more OSs (!!) and R releases. And 'rms' is of course spotless: https://cran.r-project.org/package=rms # overview page https://cran.r-project.org/web/checks/check_results_rms.html # test summary I can only throw my arms up in the air and sigh ... Dirk | 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=r-cran-rms | | Current text from [2]: | Migration status for r-cran-rms (8.1-0-1 to 8.1-1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) | Issues preventing migration: | ∙ ∙ Missing build on armhf | ∙ ∙ Missing build on i386 | ∙ ∙ Missing build on s390x | ∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build | ∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build | ∙ ∙ Lintian check waiting for test results on i386, s390x, armhf - info | ∙ ∙ Reproducibility check deferred on armhf: missing builds | ∙ ∙ Reproducibility check deferred on i386: missing builds | Additional info (not blocking): | ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rms.html | ∙ ∙ Reproduced on amd64 | ∙ ∙ Reproduced on arm64 | ∙ ∙ Reproduced on ppc64el | ∙ ∙ 31 days old (needed 5 days) -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
