Inconsistency between CRAN packet check and R check CMD -as - cran

Question

I would like to send a package (DLMtool) to the CRAN repository. When I check the package with the R CMD check --as-cran , I get only 1 note regarding the new view.

However, when I send a packet, I get feedback from the main group R regarding errors that I do not receive. For instance:

 Quitting from lines 261-262 (DLMtool.Rnw) Error: processing vignette 'DLMtool.Rnw' failed with diagnostics: one node produced an error: NAs are not allowed in subscripted assignments 

I cannot recreate this error by running the code itself. But this is not the case: I am not worried about specific errors, but rather about my inability to detect them myself. Professor Ripley was very patient at this point. I desperately do not want to spend more time on him or any of the main R command, using them as a step-by-step verification process.

How can I recreate the CRAN package validation process if --as-cran not enough?

A similar question was asked regarding the previous version of R, which could not be answered satisfactorily, as far as I can tell:

CRAN packet check finds warning that R CMD check --as-cran is not working

Greetings

Tom

I am using Windows 7 x64, RStudio 0.98.507 and R 3.1.1 x64.

Answer 1

Sending a package to CRAN still fills me with a sense of concern, even though it was successful in a number of cases.

Some things to check:

• Make sure you are using the correct process.

In particular, use:

 R CMD build pkg R CMD check pkg_version.tar.gz 

2. Make sure you are using the current version of R, as well as the development branch, R-devel ( http://cran.r-project.org/bin/windows/base/rdevel.html )

3. Submit your package to the window builder ( http://win-builder.r-project.org/ )

4. Make sure you read and fully understand each proposal for a CRAN submission policy ( http://cran.r-project.org/web/packages/policies.html )

5. Submit your package using the online application form ( http://cran.r-project.org/submit.html )

Then I hope for the best.

Honestly, every person I came across in the CRAN build team was very patient and helpful.