Hi Paul,
On 10 February 2026 at 20:00, Paul Gevers wrote: | Source: rcpp | Version: 1.1.0-1 | Severity: serious | Control: close -1 1.1.1-2 | 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:rcpp 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 is downstream from me. Looking at the error I see for (r-cran-)phylobase at e.g.g amd64 that > library('phylobase') Error: package or namespace load failed for ‘phylobase’: object ‘loadRcppModules’ is not exported by 'namespace:Rcpp' Execution halted so that is an error in the package's autpkgtest. Rcpp (for which I happen to be upstream) no longer exports loadRcppModules because it is a form of using Rcpp Modules that has been superceded for a decade (!!) -- see https://github.com/RcppCore/Rcpp/issues/1415 https://github.com/RcppCore/Rcpp/pull/1416 for more. It is the same issue with (r-cran-)rncl. I am cc'ing debian-r, hopefully someone from the Debian R Packager team wants to take care of this. (I can point to different Rcpp Modules resources if need be.) Cheers, Dirk | 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=rcpp | | Current text from [2]: | Migration status for rcpp (1.1.0-1 to 1.1.1-2): BLOCKED: | Rejected/violates migration policy/introduces a regression | Issues preventing migration: | ∙ ∙ Autopkgtest for r-cran-phylobase/0.8.12-1: amd64: Regression ♻ | (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ | (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression | ♻ (reference ♻), s390x: Regression ♻ (reference ♻) | ∙ ∙ Autopkgtest for r-cran-projpred/2.8.0+dfsg-1: amd64: Pass, arm64: | Pass, i386: Test triggered (failure will be ignored), ppc64el: Pass, | riscv64: Pass, s390x: Pass | ∙ ∙ Autopkgtest for r-cran-rncl/0.8.7-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/rcpp.html | ∙ ∙ Reproducible on amd64 | ∙ ∙ Reproducible on arm64 | ∙ ∙ Reproducible on armhf | ∙ ∙ Reproducible on i386 | ∙ ∙ Reproducible on ppc64el | ∙ ∙ 28 days old (needed 5 days) | x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature] -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
