[R-pkg-team] Bug#1125226: Bug#1125226: src:r-cran-admisc: fails to migrate to testing for too long

[Charles Plessy]

Hi Paul,

I am at the middle of removing some non-supported architectures and this
blocks migration of tons of R packages; I am well aware of the issue.
Can I ask you to not open bugs for them?  It will be a lot of painful
cut-and-paste to close them one by one later…

Have a nice day,

Charles


Le Sun, Jan 11, 2026 at 10:36:40AM +0100, Paul Gevers a écrit :
>Source: r-cran-admisc
>Version: 0.37-1
>Severity: serious
>Control: close -1 0.39-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:r-cran-admisc 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=r-cran-admisc
>
>Current text from [2]:
>Migration status for r-cran-admisc (0.37-1 to 0.39-1): BLOCKED: 
>Rejected/violates migration policy/introduces a regression
>Issues preventing migration:
>∙ ∙ r-cran-admisc unsatisfiable Build-Depends(-Arch) on armhf: 
>architecture-is-64-bit
>∙ ∙ r-cran-admisc unsatisfiable Build-Depends(-Arch) on i386: 
>architecture-is-64-bit
>∙ ∙ r-cran-admisc unsatisfiable Build-Depends(-Arch) on s390x: 
>architecture-is-little-endian
>∙ ∙ 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
>∙ ∙ Autopkgtest for r-cran-admisc/0.39-1: amd64: Pass, arm64: Pass, 
>ppc64el: Pass, riscv64: Pass
>∙ ∙ Lintian check waiting for test results on i386, s390x, armhf - info
>Additional info (not blocking):
>∙ ∙ Piuparts tested OK - 
>https://piuparts.debian.org/sid/source/r/r-cran-admisc.html
>∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ 
>∙ ∙ 31 days old (needed 5 days)




>_______________________________________________
>R-pkg-team mailing list
>R-pkg-team at alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team


-- 
Charles Plessy                         Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team         http://www.debian.org/devel/debian-med
Tooting from work,               https://fediscience.org/@charles_plessy
Tooting from home,                 https://framapiaf.org/@charles_plessy