Open adamhsparks opened 1 month ago
As a workaround, you could try setting:
RENV_CONFIG_INSTALL_TRANSACTIONAL = FALSE
in your project .Renviron
. That will tell renv
to eschew the use of the 'staging' directory during package installation.
Thank you, @kevinushey, that worked perfectly as far as I can tell.
Spoke too soon. I thought it worked, but alas, no.
Some packages will install, while others won't.
I think I'll be OK with the current project, but it would be good to know how to deal with this for future work.
I think that using renv::hydrate()
gets me around the problem installing in this environment.
Sorry for the late response. Fixing this seems like it may be challenging, as the installation failure is happening in R CMD INSTALL
itself, so internally something that R is trying to do to install the package therein is failing.
Possibly we could alleviate the issue by installing the package into a separate temporary location, and then moving the installed package to the final location, but I'm not positive that would help. You could try setting this environment variable:
RENV_PATHS_LIBRARY_STAGING = /tmp
(or some other appropriate location) and see if that helps.
I'm attempting to use {renv} for an analysis project that I am currently handling. Our university policy dictates that the data must be stored on a specific shared drive that is mounted (on my Mac) by Samba shares.
However, I find myself unable to actually use {renv} in this setting. Attempts to install packages frequently fail with an error.
Which is frustrating since I can't find any reason for this. I'm able to cd in the terminal to this directory and browse it using Finder.