Downstream effects from switching the CRAN env var to https://packagemanager.rstudio.com #50
Comments
lcolladotor
added a commit
to lcolladotor/rocker-versioned2
that referenced
this issue
May 19, 2020
As discussed at rocker-org#50 and r-lib/remotes#501, for using the RStudio Package Manager, it seems like the best option is to set the `RSPM` environment variable instead of changing the `CRAN` one. This commit reverts rocker-org@2dcd686 and adds the RSPM environment variable.
|
Hi, Given that resolving this issue (in appearance) seemed straight forward, I just sent a PR with the suggested code changes. Best, |
lcolladotor
added a commit
to LieberInstitute/recount3
that referenced
this issue
May 27, 2020
lcolladotor
added a commit
to lcolladotor/biocthis
that referenced
this issue
May 27, 2020
|
@lcolladotor given discussion in #51 I think we can close this? |
|
Yes, based on the promise of adding support for Thanks again for looking into this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I've noticed that GitHub Actions (GHA) workflows that depend on the rocker docker images have had a bit of a hiccup lately with
remotes::install_dev("pkgdown")as I reported at r-lib/remotes#501. It seems like the root issue was the recent change at 2dcd686 which switched theCRANenvironment variable fromhttps://cran.r-project.orgtohttps://packagemanager.rstudio.com/all/__linux__/bionic/latestin most cases. Jim Hester at r-lib/remotes#501 (comment) suggests thatoptions(repos = c(RSPM = "xyz", CRAN = 'abc'))is the better way to use the RSPM, so would it be ok to:CRANenvironment variable?RSPMenvironment variable tohttps://packagemanager.rstudio.com/all/__linux__/bionic/latest/(like you had done already)?I ignore if there were other reasons why you changed
CRAN, but if you want, I can send a PR that does these 2 changes.Best,
Leo
The text was updated successfully, but these errors were encountered: