Hi Paul, Dirk and everybody,
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
Le Tue, Feb 10, 2026 at 01:53:46PM -0600, Dirk Eddelbuettel a écrit :
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
It is the same issue with (r-cran-)rncl.
Yes indeed, it is an issue in r-cran-rncl 0.8.7-1 in Testing, which I
fixed in Unstable by upgrading to 0.8.9-1 two weeks ago.
r-cran-rncl 0.8.9-1 will not migrate to Testing untill all of its
reverse dependencies (transitively) have completed the transition to the
removal of non-64-bit non-little-endian architectures, which I hope to
complete befrore the end of March but I can not promise that for sure.
r-cran-rncl 0.8.7-1 will be automatically removed from Testing on March
8th because of the namespace issue above (#1126238). After that,
r-cran-rcpp can migrate to Testing because it will not break r-cran-rncl
anymore.
If there were a system empowering me to remove r-cran-rncl from the way,
I would surely use it, but I am not aware of such a tool.
Paul, could you place a hint that does what is needed for r-cran-rcpp
to migrate earlier than March 8th?
I really feel sorry that the current situation strains a lot of time
from all the parties but once the vast majority of the r-cran-* packages
are built only on supported architectures, there will me much less
migration bottlenecks like this one.
Have a nie day,
Charles
--
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
