[R-pkg-devel] Missing SystemRequirements on the build servers

[Sebastian Meyer]

Dear Philipp,

What kind of problems does the incoming check report?

If they are related to your package's vignette, a simple solution would
be to transform this toy example into a package test using
tools::buildVignette in the test script, which can be run conditionally
on specific system requirements being fulfilled (so probably not on CRAN
test machines).

Cheers,

	Sebastian


Am 22.11.19 um 10:44 schrieb Angerer, Philipp:
> 
> 
> Hi, 
> 
> I first submitted my package nbconvertR in 2015. It requires the command jupyter nbconvert to work. 
> 
> Since the first submission the SystemRequirements which provide that command changed, which I reflected in the SystemRequirements and lately in an INSTALL file: https://github.com/theislab/nbconvertR/blob/f30cbe03908dcf0c9301436fa9f2c06c7028baab/INSTALL 
> 
> 
> My problem now is that since 2017, my submission only gets until the mail “Dear maintainer, package nbconvertR_1.3.1.tar.gz does not pass the incoming checks automatically”. That mail later says “If you are fairly certain the rejection is a false positive, please reply-all to this message and explain” which I always do. But then nobody replies and my package gets kicked out of the incoming folder after 7 days or so. 
> 
> 
> What can I do? 
> 
> 
> Best, Philipp 
> 
>  
> 
> 
> Helmholtz Zentrum München
> 
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>