When I am running R version 4.2.2 and BiocManager 3.16, I can install the package "RefPlus" just fine:
> BiocManager::install("RefPlus", force = FALSE, ask = FALSE, update=FALSE, checkBuilt=FALSE);
> system.file(package="RefPlus")
[1] "/home/d/R/x86_64-pc-linux-gnu-library/4.2/RefPlus"
However, when I run R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
and BiocManager 3.18, Attempting to install RefPlus
fails:
> BiocManager::install("RefPlus", update=FALSE)
'getOption("repos")' replaces Bioconductor standard repositories, see
'help("repositories", package = "BiocManager")' for details.
Replacement repositories:
CRAN: https://cloud.r-project.org
Bioconductor version 3.18 (BiocManager 1.30.22), R 4.3.1 (2023-06-16)
Installing package(s) 'RefPlus'
Warning message:
package 'RefPlus' is not available for Bioconductor version '3.18'
A version of this package for your version of R might be available elsewhere,
see the ideas at
https://cran.r-project.org/doc/manuals/r-patched/R-admin.html#Installing-packages
> system.file(package="RefPlus")
[1] ""
> sessionInfo( )
R version 4.3.1 (2023-06-16)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 23.10
Matrix products: default
BLAS: /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.11.0
LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.11.0
locale:
[1] C
time zone: America/Los_Angeles
tzcode source: system (glibc)
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] BiocManager_1.30.22 compiler_4.3.1 tools_4.3.1
For reference, all other Bioc and rcran packages install just fine. The only package I'm having trouble with is RefPlus
on this specific version.
The two installs are not related. I'll try downgrading the OS, R, and BiocManager next. However, I would like for this not to be a blocker.
I see there is a 3.18 branch in RefPlus in the bioconductor repo, but I don't see RefPlus in the github bioconductor org. Did the package get missed when you made github your primary repository?
Hi Lori,
Does that make the Windows binary unavailable as well? In other words, when BiocManager checks for availability, does it look for the source package regardless?
I recall discussing this with Herve at somepoint. We both decided this was a bug, because clearly a usable version of the package is available on Windows, but when he reported it to R-core their view point was that a missing source tarball meant that the package was broken and should not be available. The issue was closed at that point. I'll try to dig up the issue he created.
Edit: Here is a discussion of this same phenomena for a different package at the time of the 3.17 release (https://community-bioc.slack.com/archives/CEQ04GKEC/p1686573089903459)
and here is Herve's bug report (https://bugs.r-project.org/show_bug.cgi?id=18554)
Thanks Mike. That's what I figured.
And as followup.
As documented