[R-pkg-devel] New Package olr 4 NOTES

Mat Fok qu|k@||ver67213 @end|ng |rom y@hoo@com
Wed Dec 4 23:25:47 CET 2019


Hi,
Thank you. I am wondering why the log would output .Rproj.user when it was already in the .Rignorefile. Hope the .Rignore file is correct anyways as I have mentioned below.
Thanks,
Mathew


Sent from Yahoo Mail for iPhone


On Wednesday, December 4, 2019, 2:11 PM, Duncan Murdoch <murdoch.duncan using gmail.com> wrote:

On 04/12/2019 1:02 p.m., Mat Fok via R-package-devel wrote:
> Hi All,
> This is the first time I am trying to upload a package. It is fun learning this stuff.
> Thank you all for kindly looking at the NOTES.
> This is the log I recevied from CRAN volunteers: https://win-builder.r-project.org/incoming_pretest/olr_1.0.0.2000_20191129_024844/Windows/00check.log
> (I was wondering how to reproduce that log. I have run other things like devtools::check())
> 
> The package is here: https://github.com/MatHatter/olr_r/tree/master/Rstuff
> 
> I will address every problem below:
> 1. OK. Not misspelled:
> Possibly mis-spelled words in DESCRIPTION:
>    olr (8:18, 9:20)
> 2. FIXED thisThe Description field should not start with the package name,
>    'This package' or similar.
> 3. FIXED thisThe Description field contains
>    https://pypi.org/project/olr/.
> Please enclose URLs in angle brackets (<...>).
> 4. Don't know how to fix this, unless it is not anything.
> The build time stamp is missing.

That's a sign that you didn't build the package using "R CMD build" at 
the command line (or one of the R functions that calls it).  Don't use 
tar directly to create it, let R do it (because adding a timestamp is 
not the only thing it does).

If you used a devtools function to build the tarball, then you probably 
did something wrong, but it's hard to say what without seeing the 
command you used.  Or maybe devtools has a bug, but it's pretty widely 
used, so I doubt that.

> 5. First I took these files out of the folder completely, but then I thought that it might be needed for something and .Rhistory probably will be there no matter what so I used the function
>> usethis::use_build_ignore(c(".Rproj.user", ".gitignore", ".Rhistory"))✔ Setting active project to 'C:/Rstuff/olr'✔ Adding '^\\.gitignore$', '^\\.Rhistory$' to '.Rbuildignore'
> but as you see .Rproj.user was already in my .Rbuildignore so I don't know if this is going to work.* checking for hidden files and directories ... NOTE
> Found the following hidden files and directories:
>    .Rhistory
>    .gitignore
>    .Rproj.user
> These were most likely included in error. See section 'Package
> structure' in the 'Writing R Extensions' manual.

If you had .Rbuildignore set to ignore them, then R would not put them 
in the tarball.

Duncan Murdoch

> 
> 6. Lastly, I do not know how to fix this. I used the use_gpl3_license() I believe.
> * checking top-level files ... NOTE
> Non-standard files/directories found at top level:
>    'LICENSE.md' 'olr.Rproj'
> FYI,This is what my .Rbuildignore file looks like^olr\.Rproj$^\.Rproj\.user$^LICENSE\.md$^\.gitignore$^\.Rhistory$
> Thank you all so much.
> From,
> Mathew Fok




	[[alternative HTML version deleted]]



More information about the R-package-devel mailing list