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 yo
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
wrote:
>
> Many thanks for the remark. It seems, it has something to do
Daniel Marcelino
"Small steps toward a much better world"
From: R-package-devel on behalf of
Wolfgang Lenhard
Sent: December 7, 2018 2:15 PM
To: Georgi Boshnakov; r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Package update sub
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:
Hmm, no ERRORs in the CRAN checks
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 a
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
> life$Country[Encoding(life$Country)!="unknown"]
[1] "Korea, Dem. People’s Rep." "Korea, Dem. People’s Rep."
[3] "Korea, Dem. People’s Re
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 the
