-
Notifications
You must be signed in to change notification settings - Fork 91
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
Bioconductor installation issue for R 3.6.0 #573
Comments
This should already be handled: Lines 341 to 357 in 29a4fdc
so I'd be curious to have a reprex or similar showing the failure. |
(Perhaps the issue only occurs if both BiocInstaller and BiocManager are available and we should check BiocManager first) |
We've had another user encounter this issue, https://community.rstudio.com/t/rstudio-connect-packrat-chokes-on-bioconductor-packages/36706/7 Setting the repo option manually appeared to resolve the problem, but was anyone else able to reprex? I'd really prefer if packrat and deployments worked magically like they did before! |
title: "reprex"
|
The simplest way to fix this is to ensure the Bioconductor repositories get set in the lockfile; e.g. something like:
|
@kevinushey we had another customer hit this issue today - do you know why the repos would not be active? It definitely appears that setting repos solves the problem, but it isn't clear to me why the code in packrat to recognize the repos isn't triggering. It would be awesome if we could poke at this some more, as it is becoming a recurring problem for support. |
I'm OOF so won't be able to take a look until next week. |
Summarizing what @slopp found concerning this most recent issue:
|
Packrat should already be handling this properly: Lines 299 to 316 in 448aafd
Packrat checks whether the package is from GitHub before querying the biocViews field, and |
@kevinushey I was able to re-produce an error by:
The deployment log showed that packrat was looking for the |
After a snapshot, I see in the lockfile:
I also see the package source correctly annotated when reading the lockfile:
Note that you need the development version of Packrat if your copy of remotes isn't writing out the |
If anyone else is on this issue due to problems with restoring the environment from both CRAN and Bioconductor, on my end the problem was
with
Of course the exact values will depend on your specific environment, but the above resolved major part of the issue. You can use Another problem was related to package |
https://community.rstudio.com/t/rstudio-connect-packrat-chokes-on-bioconductor-packages/36706
This community thread discusses changes to R 3.6.0, for which:
Potentially related to: #507
Particularly affects customers on RStudio Connect, who don't have a place to interactively tweak / install into the library.
The text was updated successfully, but these errors were encountered: