sorry, I got sloppy - I had played around before with the DESCRIPTION file,
that does not seem to be the culprit. But you are right of course, it should
run without warnings in any case.
* using log directory
�/Users/spaceicons/code/R_package_dev/helpers2/helpers2.Rcheck�
* using R version 3.
It tells you what the warning is. You need to specify a license in your
DESCRIPTION file. You should really fill the entire thing out properly
anyways.
On Aug 10, 2017 12:39 PM, wrote:
> Thank you for pointing that out, this solved the ERROR in the R CMD check.
> I've updated the repo.
>
> Unfor
Thank you for pointing that out, this solved the ERROR in the R CMD check. I've
updated the repo.
Unfortunately, it did not solve the problem. So when you clone/pull the repo
now, the error should persist.
* using log directory
‘/Users/spaceicons/code/R_package_dev/helpers2/helpers2.Rcheck’
*
Your log says you have no examples but you do in your Rd file.
Your examples look the wrong way round x(function) rather than function(x)
Not sure whether those are relevant issues but perhaps they help.
On 10/08/2017 15:47, david.kaeth...@dlr.de wrote:
Thank you for the replies!
First of all,
Thank you for the replies!
First of all, here is the test package:
https://github.com/c06n/helpers2
Session info and the log of R CMD check at the end. There is an error: "LaTeX
errors when creating PDF version." However, it says "checking Rd files ... OK".
I have tried the install now on
Dear list,
I'm getting some false 'R CMD check' positives on rhub / Fedora: errors
appearing on rhub that are not reproduced by CRAN. I have reported the
matter here:
https://github.com/r-hub/rhub/issues/92
It happens reproducibly for at least two of my packages: validate and
lumberjack (I have
On 9 August 2017 at 08:38, Duncan Murdoch wrote:
| Nothing that you've written is reproducible by others. See if you can
| put together a short self-contained series of instructions that display
| the problems (or just one of them). It might involve installing from
| Github, or making a packa
hi duncan,
Thank you, it refreshed my memories on "local", cool.
About the dummy function to load packages, it lets Rstudio bring them in
the Namespace, kind of a tradeoff because of the warning I get in NAMESPACE
after building the documentation:
>>> # Generated by roxygen2: do not edit by hand
Hello,
Package 'ggplot2' defines `ggplot()` as an S3 generic.
My package 'ggspectra' defines some specializations of ggplot() for
additional classes, which work as expected together with all packages
extending 'ggplot2' that I have tested, except for 'ggtern'.
Package 'ggtern' imports 'ggplot2
