[R-pkg-devel] Issue with Biostrings-- can't find the base rgb function on r-devel

2019-12-04 Thread Dalgleish, James (NIH/NCI) [V] via R-package-devel
Question:

NIPTeR is experiencing new warnings when loading Biostrings. I have the exact 
same warnings with my package, CNVScope.

It seems a little odd that the base function rgb cannot be found. What can 
cause a base package to not be found? I can't replicate this issue on either of 
my linux or windows machines or on winbuilder.

I have already asked the Bioconductor community, but didn't get a response 
(https://support.bioconductor.org/p/126878/).

Thanks,
James Dalgleish
Maintainer, CNVScope
NIH/NCI
Source: https://cran.r-project.org/web/checks/check_results_NIPTeR.html
Check Details
Version: 1.0.2
Check: whether the package can be unloaded cleanly
Result: WARN
Error: package or namespace load failed for 'NIPTeR':
 .onLoad failed in loadNamespace() for 'Biostrings', details:
 call: rgb(1, 1, 1)
 error: could not find function "rgb"
Execution halted
Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0.2
Check: whether the namespace can be loaded with stated dependencies
Result: WARN
Error: .onLoad failed in loadNamespace() for 'Biostrings', details:
 call: rgb(1, 1, 1)
 error: could not find function "rgb"
Execution halted

A namespace must be able to be loaded with just the base namespace
loaded: otherwise if the namespace gets loaded by a saved object, the
session will be unable to start.

Probably some imports need to be declared in the NAMESPACE file.
Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0.2
Check: dependencies in R code
Result: NOTE
Error: package or namespace load failed for 'NIPTeR':
 .onLoad failed in loadNamespace() for 'Biostrings', details:
 call: rgb(1, 1, 1)
 error: could not find function "rgb"
Call sequence:
6: stop(msg, call. = FALSE, domain = NA)
5: value[[3L]](cond)
4: tryCatchOne(expr, names, parentenv, handlers[[1L]])
3: tryCatchList(expr, classes, parentenv, handlers)
2: tryCatch({
 attr(package, "LibPath") <- which.lib.loc
 ns <- loadNamespace(package, lib.loc)
 env <- attachNamespace(ns, pos = pos, deps, exclude, include.only)
 }, error = function(e) {
 P <- if (!is.null(cc <- conditionCall(e)))
 paste(" in", deparse(cc)[1L])
 else ""
 msg <- gettextf("package or namespace load failed for %s%s:\n %s",
 sQuote(package), P, conditionMessage(e))
 if (logical.return)
 message(paste("Error:", msg), domain = NA)
 else stop(msg, call. = FALSE, domain = NA)
 })
1: library(package, lib.loc = lib.loc, character.only = T
Execution halted
Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0.2
Check: R code for possible problems
Result: NOTE
Error: .onLoad failed in loadNamespace() for 'Biostrings', details:
 call: rgb(1, 1, 1)
 error: could not find function "rgb"
Execution halted
Flavor: r-devel-linux-x86_64-debian-clang


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] Solaris package installed size

2019-10-15 Thread Dalgleish, James (NIH/NCI) [V] via R-package-devel
On Solaris, I'm finding that my package, only on Solaris, is slightly above 
5MB. Is there a difference in install sizes for Solaris? I don't have a Solaris 
machine, so it's difficult to know what the size differences are and why.
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/CNVScope-00check.html
"checking installed package size ... NOTE
  installed size is 5.2Mb
  sub-directories of 1Mb or more:
doc 3.1Mb
extdata 1.8Mb"

If so, why might that be?
I've looked at R solaris documentation 
(https://cran.r-project.org/doc/manuals/r-release/R-admin.html#Solaris), but it 
says nothing other than suggesting that it will require more stack space 
(memory) to build the package... but this doesn't say anything about disk space 
or installation directory cleanup differences.

"At least when compiling with Oracle compilers, Solaris uses far more stack 
space than other platforms."  Perhaps there are additional files that are 
generated for Solaris that are not generated for other platforms?

Thanks,
James Dalgleish

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] Tarball can't be unpacked

2019-10-14 Thread Dalgleish, James (NIH/NCI) [V] via R-package-devel
* using log directory 'd:/RCompile/CRANincoming/R-devel/CNVScope.Rcheck'
* using R Under development (unstable) (2019-10-10 r77275)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking whether tarball can be unpacked ... ERROR
cannot unpack 'CNVScope_2.7.6.tar.gz'
* DONE
Status: 1 ERROR

I've submitted my package to win-builder, but just can't get it to check it. 
I've checked it locally and it passes with flying colors (no notes of any 
kind). I have used the package on my own machine to build from source. Is 
win-builder down? How can my tarball be broken? It works on my machine, so I 
can't imagine it's a broken tarball. Is there some compression flag I should 
change when building the package?
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel