You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
January is around the corner, and a new release date for Rcpp is coming. So I ran another set of reverse depends (summary available as usual). (And I am currently running a follow-up run partly in response to a new r-devel issue). This finished run had a couple of i) missing dependencies for newer packages, ii) known unrelated issues (here: BH and RcppEnsmallen upgrades leaving some packages in need of love), iii) 'random' (?) network issues, iv) packages also failing at CRAN we can ignore and v) residuals to lok at.
Here we see two residuals:
recurse (version 1.4.0, maintained by @cbracis, emailed 2024-12-21)
(IMHO a false positive, sent PR on 2025-01-11 to address)
symengine (version 0.2.6, maintained by @Marlin-Na, emailed 2024-12-21)
(not an issue at CRAN on 2025-01-12 in their reverse-depends checks but consistently for me to maybe just "fragile")
I will attempt to also email the maintainers with a copy of the error I saw and will ask for help but as a first step I also include the errors below under 'details'.
Release candidates of Rcpp can as always be installed via
Rcpp 1.0.14 is now getting onto CRAN without any rev.dep issues 1 so closing this. @Marlin-Na what I reported happens on the machine I tested on but apparently not on the CRAN machine that matters :) If you have some time maybe we can try to sort out why it fails for me? It seems Boost related...
Footnotes
There was one other false positive / repeat occurence that also happens with 1.0.13 and is hence ignored. ↩
January is around the corner, and a new release date for
Rcpp
is coming. So I ran another set of reverse depends (summary available as usual). (And I am currently running a follow-up run partly in response to a new r-devel issue). This finished run had a couple of i) missing dependencies for newer packages, ii) known unrelated issues (here: BH and RcppEnsmallen upgrades leaving some packages in need of love), iii) 'random' (?) network issues, iv) packages also failing at CRAN we can ignore and v) residuals to lok at.Here we see two residuals:
(IMHO a false positive, sent PR on 2025-01-11 to address)
(not an issue at CRAN on 2025-01-12 in their reverse-depends checks but consistently for me to maybe just "fragile")
I will attempt to also email the maintainers with a copy of the error I saw and will ask for help but as a first step I also include the errors below under 'details'.
Release candidates of
Rcpp
can as always be installed viaas detailed in the R-universe page for Rcpp.
recurse
One test fails on Debian with g++-14 in
symengine
One test fails on Debian with g++-14 in
This could of course also be another required package being out of sync.
The text was updated successfully, but these errors were encountered: