shared library directory between R-release and R-devel causes problems

[dtenenba]

The following sequence of commands:

docker run --name foo -ti --rm rocker/drd RD
# then in R-devel:
download.file("https://codeload.github.com/dtenenba/atestpackage/zip/master", './atestpackage.zip')
unzip("atestpackage.zip")
install.packages("atestpackage-master", repos=NULL)

Results in this:

...
** testing if installed package can be loaded
Error in get(name, envir = asNamespace(pkg), inherits = FALSE) :
  object 'checkCompilerOptions' not found
Calls: ::: -> get
Execution halted
ERROR: loading failed

The reason is that .libPaths() includes /usr/lib/R/library which is a library tree for R-3.2.3 (not devel) and the old version of the compiler package is picked up during installation of this sample package which has ByteCompile: TRUE in its DESCRIPTION.

Removing /usr/lib/R/library or changing .libPaths() to exclude it works around this issue.

The issue is also present in rocker/rstudio-daily, but the docker command needs to be replaced with:

docker run -ti --rm rocker/rstudio-daily /usr/local/bin/R

[eddelbuettel]

I am really not too interested in these reports.

edd@max:~$ docker run -ti --rm rocker/drd /bin/bash                                                                                                                                                                 
root@e3bb3645333c:/# apt-get update 2>&1 > /dev/null
root@e3bb3645333c:/# apt-get install git 2>&1 > /dev/null                                                                                                                                                           
y
debconf: delaying package configuration, since apt-utils is not installed
root@e3bb3645333c:/# cd /tmp
root@e3bb3645333c:/tmp# git clone https://github.com/dtenenba/atestpackage.git
Cloning into 'atestpackage'...
remote: Counting objects: 13, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 13 (delta 2), reused 13 (delta 2), pack-reused 0
Unpacking objects: 100% (13/13), done.
Checking connectivity... done.
root@e3bb3645333c:/tmp# RD CMD build atestpackage/
* checking for file ‘atestpackage/DESCRIPTION’ ... OK
* preparing ‘atestpackage’:
* checking DESCRIPTION meta-information ... OK
* checking for LF line-endings in source and make files
* checking for empty or unneeded directories
* building ‘atestpackage_0.0.0.9000.tar.gz’

root@e3bb3645333c:/tmp# RD CMD INSTALL atestpackage_0.0.0.9000.tar.gz 
* installing to library ‘/usr/local/lib/R/site-library’
* installing *source* package ‘atestpackage’ ...
** R
** byte-compile and prepare package for lazy loading
** help
No man pages found in package  ‘atestpackage’ 
*** installing help indices
** building package indices
** testing if installed package can be loaded
* DONE (atestpackage)
root@e3bb3645333c:/tmp# 

[dtenenba]

Yep, I get the same results. However, installing the package with install.packages() from within R causes the problem. Apparently the two different installation methods use different libPaths().

[eddelbuettel]

That should be traceable. I tend to always install at the command-line to that explicit use became the implicit service guaranty...

[jangorecki]

I get the same issue, as one function I've called with RDscript -e used install.packages.

RDscript -e 'p::f()'

This workaround helped me

RDscript -e '.libPaths(setdiff(.libPaths(), "/usr/lib/R/library")); p::f()'