sourcetools | Tools for reading , tokenizing , and parsing R code | Parser library

I think this is ultimately a small bug in renv. Here's my guess at what's happening:

1. While this project has been initialized as an renv project, it does not have a lockfile for some reason. (Perhaps renv::activate() was called to initialize renv without explicitly creating a lockfile?)

2. The project has an renv autoloader; this is from a script at renv/activate.R. That script is configured to load renv 0.11.0.

3. When the project is loaded, renv finds that renv 0.12.0 is installed in the project library, not the expected version 0.11.0. This causes the warning to be emitted. (Perhaps renv was updated in that project previously?)

So, ultimately, the warning is misleading here -- the request for renv 0.11.0 comes directly from the autoloader, not from the lockfile (which does not exist). As for why the lockfile does not exist, I'm not sure -- but it most likely implies the project was initialized via renv::activate(), and not by renv::init().

All that said -- you can safely re-generate the lockfile via renv::snapshot().

I can't explain but this works by adding a setTimeout:

By setting dependencies=TRUE (rather than the default value of NA) you're getting not just imports/depends/linkingto, but also all of the suggested packages: from ?install.packages,

... ‘TRUE’ means to use ‘c("Depends", "Imports", "LinkingTo", "Suggests")’ for ‘pkgs’ and ‘c("Depends", "Imports", "LinkingTo")’ for added dependencies: this installs all the packages needed to run ‘pkgs’, their examples, tests and vignettes (if the package author specified them correctly).

The analog for package_dependencies is which="all".

I fixed that error thanks to Harutyun Khachatryan from the r-sig-debian mailing list.
The solution is here: https://askubuntu.com/questions/26498/choose-gcc-and-g-version

The only difference is that I used gcc and g++ with versions 4.8 and 4.9 (instead of 4.3 and 4.4).

All commands I used to fix it: