Closed gavinsimpson closed 9 years ago
Thanks @gavinsimpson
I just pushed up a .Rbuildignore
to the repo. Did you test the package on your build system?
Yep, just needed to update R-devel first. You'll take care of all NOTEs except
* checking CRAN incoming feasibility ... NOTE
and you can't do, nor need to do, anything about that as your Maintainer info and LICENSE
file are in order.
I checked this with the --as-cran
option, which turns on checks that CRAN runs.
Thanks. Ok I'll try submitting to CRAN again.
With the new .Rbuildignore
you should be good to go for CRAN. Nothing wrong that i can see under R-devel. Do use the optional comment box when submitting via the web interface to explain that you've fixed the problems and checked under R-Devel on Linux (and I presume Windows) and only NOTE is the CRAN Incoming Feasibility check.
Checking package (under R-devel but R-patched should be picking this up too) results in:
To fix this, add an
.Rbuildignore
file with following content:you could add the following too
but R must already be ignoring those by default, though it is complaining about
.travis.yml
in a separate, earlier note: