Thanks Martin.
For reproducibility we use containers, alongside a a RStudio Server Pro
installation.
This issue was occurring on my rolling release machines that I use for
testing. One in particular (Siduction box) has been rolling since R 3.2,
there are very rarely any issues. Best practise?
Yes, remove BIocVersion (all copies)
I guess you have a library path, as shown by .libPaths() in R, that is shared
between the two versions. This is generally BAD PRACTICE. because it means
packages built for R-3.6 will be used by both of your R-3.5 and R-3.6
installations, and vice versa --
I had the same issue today, here's the note I made on our work Teams
channel:
Not too sure where to deposit this little piece of information. Just a
little 'hiccup' in the latest transition of R versions (3.5 -> 3.6) and
Bioconductor. The newest stable version of Bioconductor (3.9) depends on R
Hi,
I just installed R 3.6, but everything I try to get a BiocManager Version,
which works with R 3.6 were so far not successful.
I installed BiocManager from CRAN �
> install.packages("BiocManager")
� and from GitHub �
> devtools::install_github("Bioconductor/BiocManager")
� but both times
