Skip to content

[R-pkg-devel] Package update submission to CRAN fails on pretest

8 messages · Wolfgang Lenhard, Georgi Boshnakov, Peter Dalgaard +2 more

#
Dear list,
I am getting problems when trying to submit an update of the package 
cNORM to CRAN. I am developing the package with RStudio and devtools and 
I am using Travis for automatic testing. The package is tested locally 
on Win10 and Mac OS X and on Travis with Ubuntu and Mac both for 
development and release versions of R. All local tests and tests on 
Travis work flawlessly - no errors, warning or notes. When submitting to 
CRAN, a note and an error show up on some of the Linux OS (Fedora & 
Solaris) and Mac OS X, while others display an 'OK' (Win, Debian). The 
results: https://cran.r-project.org/web/checks/check_results_cNORM.html

- error: This seems to be related to the vignette with the following 
message:
I can however not identify the location of the error

- Note: Check: data for non-ASCII characters

The strange thing is: I checked all data files multiple times. They 
mainly consist of data.frames with numerics and all colnames? are ASCII. 
I am not able to replicate the issue. The same is true for the error, 
which does not show up on Travis and as well locally. And finally, the 
results state, that the version of the package is 1.0.1, which had been 
the first submission to CRAN a month ago. The current version of the 
package is 1.1.1. Could this be the reason for the problem?

Do you have an idea how to progress with the testing or how to locate 
the errors? Any help is welcome.

Best regards,
 ??? Wolfgang Lenhard
#
The link you gave, https://cran.r-project.org/web/checks/check_results_cNORM.html,
is to the check results for the package currently on CRAN and it is indeed v. 1.0.1
(it is linked from https://CRAN.R-project.org/package=cNORM).

Was this really the link you got from CRAN's pretest? Sometimes they ask if care has been taken about NOTEs/WARNINGs for the current CRAN version, since some tests are not done during submission, but this doesn't seem the case here.

Georgi Boshnakov


-----Original Message-----
From: R-package-devel [mailto:r-package-devel-bounces at r-project.org] On Behalf Of Wolfgang Lenhard
Sent: 07 December 2018 07:55
To: r-package-devel at r-project.org
Subject: [R-pkg-devel] Package update submission to CRAN fails on pretest

Dear list,
I am getting problems when trying to submit an update of the package 
cNORM to CRAN. I am developing the package with RStudio and devtools and 
I am using Travis for automatic testing. The package is tested locally 
on Win10 and Mac OS X and on Travis with Ubuntu and Mac both for 
development and release versions of R. All local tests and tests on 
Travis work flawlessly - no errors, warning or notes. When submitting to 
CRAN, a note and an error show up on some of the Linux OS (Fedora & 
Solaris) and Mac OS X, while others display an 'OK' (Win, Debian). The 
results: https://cran.r-project.org/web/checks/check_results_cNORM.html

- error: This seems to be related to the vignette with the following 
message:
I can however not identify the location of the error

- Note: Check: data for non-ASCII characters

The strange thing is: I checked all data files multiple times. They 
mainly consist of data.frames with numerics and all colnames? are ASCII. 
I am not able to replicate the issue. The same is true for the error, 
which does not show up on Travis and as well locally. And finally, the 
results state, that the version of the package is 1.0.1, which had been 
the first submission to CRAN a month ago. The current version of the 
package is 1.1.1. Could this be the reason for the problem?

Do you have an idea how to progress with the testing or how to locate 
the errors? Any help is welcome.

Best regards,
 ??? Wolfgang Lenhard



______________________________________________
R-package-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
#
Hmm, no ERRORs in the CRAN checks at this moment? 

Re. utf-8, on Mac OS, the CRAN checks have a note about 90 strings marked as utf8.

I see 57 of them in
[1] "Korea, Dem. People?s Rep." "Korea, Dem. People?s Rep."
 [3] "Korea, Dem. People?s Rep." "Korea, Dem. People?s Rep."
 [5] "Korea, Dem. People?s Rep." "Korea, Dem. People?s Rep."
...

and 32 more in "mortality". You go find the remaining 1...

This seems to be an issue with the quote symbol:
[1] "UTF-8"
[1] "Korea, Dem. People\\xe2\\x80\\x99s Rep."


I have no clue why this is not an issue on only some platforms.

-pd

  
    
#
Many thanks for the remark. It seems, it has something to do with 
submitting via the devtools (maybe I did something wrong with tagging 
the prior release). Submitting it manually at least does not result in 
pretest rejection. I guess there is something out of sync which resulted 
in rechecking and old version.

Am 07.12.2018 um 13:46 schrieb Georgi Boshnakov:

  
    
#
Thanks for pointing that out. I rebuilt everything from scratch. Indeed 
I thought, there were no UTF-8 encodings in the data and neither Travis, 
checking it locally and R-Hub (all kinds of OS) resulted in errors.

Am 07.12.2018 um 13:58 schrieb peter dalgaard:

  
    
#
Daniel Marcelino

"Small steps toward a much better world"
#
You might try reinstalling devtools and dependencies - there was
unfortunately a brief combination of versions that lead to build()
failing to overwrite existing files.

Hadley
On Fri, Dec 7, 2018 at 10:46 AM Wolfgang Lenhard
<wolfgang.lenhard at uni-wuerzburg.de> wrote:

  
    
#
Dear Hadley,
many thanks for your comment and much more for your fantastic tutorial 
and packages! I essentially learned (and still learn) package 
development by your tutorial. In the concrete case, changing some 
settings finally did it and devtools worked like charm. I want to thank 
you for your really great work.

There was a strange thing, though, that I do not yet understand. The 
submission failed on some systems (fedora and Mac OS X; not on Win and 
Ubuntu) because of errors building the vignette. Adding rmarkdown to 
imports in the description file solved the pretest rejection and the new 
version of cNORM is on CRAN, but now, I have the following note:
Apart from the note, it works now. Maybe, I remove the code from the 
vignette in future releases and.

Best regards,
Wolfgang

Am 08.12.2018 um 15:31 schrieb Hadley Wickham: