CRAN check

[pbiecek]

This concerns the CRAN packages

ASIP ApacheLogProcessor Bchron BigQuic CINOEDV COMBIA CREAM CompGLM
DeLorean ETLUtils EasyStrata FKF GENEAread Gmisc IGM.MEA MAGNAMWAR
PTXQC PlasmaMutationDetector R2GUESS RSMET RVowpalWabbit Rclusterpp
RcppProgress SamplerCompare Stickbreaker TTR WhiteStripe XLConnect
antaresProcessing archivist atsd aucm bibliospec biclique bigstatsr
data.table dendroextras eventstudies finch futile.matrix gap
geno2proteo genotypeR healthcareai heemod hrbrthemes hypergea knitr
krm lambda.r meaRtools measuRing micropan ndtv odfWeave pcadapt pdmod
pkgmaker prc pulsar pvar pxweb quantreg rngtools rodeo satscanMapper
schwartz97 tawny.types tcpl utilsIPEA yCrypticRNAs

These all show check problems on the Debian check systems caused by
attempts to write to the user library to which all packages get
installed before checking (and which now is remounted read-only for
checking).

Having package code which is run as part of the checks and attempts to
write to the user library violates the CRAN Policy's

Packages should not write in the user’s home filespace (including
clipboards), nor anywhere else on the file system apart from the R
session’s temporary directory (or during installation in the location
pointed to by TMPDIR: and such usage should be cleaned up).

Hence, please update your package(s) as quickly as possible to no longer
(attempt to) write to the user library (including, of course, the
location where the package itself was installed to).

[pbiecek]

fixed in a following way:

• in some examples the tempfile() was replaced by tempfile(tempdir=".") (files will be created in the local session directory
• in other examples the DONOTRUN block is used