-
Notifications
You must be signed in to change notification settings - Fork 12
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
Problem during install #19
Comments
hi, please update R and related packages before trying to install RRegrs. In the DESCRIPTION file, lazy load is set to true. |
Hi Carlos, Many thanks for your comments. I tried updated the R and all the packages: But the errors remain appeared like this:
So could you please inform me where the problem lie. Best, Xianjun |
Dear Xianjun, I performed a clean install of RRegrs without problems using the README steps, it seems that this is not a problem directly related with the RRegrs package installation. So please, try to perform a clean install. R version 3.2.3 (2015-12-10) -- "Wooden Christmas-Tree" RRegrs 0.0.5 RStudio-0.99.491 |
Dear Carlos, |
Xianjun, can you maybe have a look at this similar report: r-lib/devtools#886 There they also have trouble with unloading Rcpp... does that look similar to you? That report suggests we may want to play the order in which we depend/require packages. |
Hi Egon, Many thinks, I will look and try. Best |
For the next release, we may want to import specific methods, rather than full packages. See issue #4 |
I just went to the packages tab and clicked update. Selected all suggested updates and updated all and viola it worked. |
Hi All,
When I install, I get the erro information like this:
Error in unloadNamespace(package) :
namespace ‘Rcpp’ is imported by ‘scales’, ‘reshape2’, ‘plyr’, ‘minqa’ so cannot be unloaded
Error in library(pkg, character.only = TRUE, logical.return = TRUE, lib.loc = lib.loc, :
Package ‘Rcpp’ version 0.12.2 cannot be unloaded
ERROR: lazy loading failed for package ‘RRegrs’
How can I resolve it?
Any advice would be greatly appreciated.
Xianjun
The text was updated successfully, but these errors were encountered: