New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installed Rcpp version not supported by R-devel #95
Comments
|
@eddelbuettel @kevinushey @jjallaire: Could you please comment on this? |
|
See r-devel mailing list message by Luke Tierney. ALTREP is in the r-devel master branch now and requires all packages to be rebuilt against updated headers which is exactly what the error message says. |
|
Thanks, Dirk. To me this looks like we just need to wait until CRAN rebuilds their Windows packages, this shouldn't take more than a few days. Alternatively, |
|
Yup, specifying Thanks to both. |
This seems to be because the windows binary packages need to be rebuilt with this version of R, as some internals in R have changed. More details and pointers in krlmlr/r-appveyor#95 Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>
Based on information discussed in krlmlr/r-appveyor#95, we need to re-build packages from source to avoid the error > Error : package 'Rcpp' was installed by an R version with different internals; it needs to be reinstalled for use with this R version
Information discussed in krlmlr/r-appveyor#95
One of my appveyor builds has recently started failing on R-devel, having previously ran fine on similar builds, but still runs successfully on R-release. The problem seems to be that appveyor is trying to install a version of Rcpp that is not consistent with R-devel. Output logs are below.
This is also suggested as the problem by the fact that I had the exact same problem for my travis linux builds (passing on release, failing on devel) but this was fixed when I cleared the travis package cache and rebuilt it from scratch. I don't think that appveyor uses package caching, but could be wrong.
The appveyor.yml is here in case it's something in my setup that is prompting this.
The text was updated successfully, but these errors were encountered: