Or you have been there at the wrong time when we enabled a new check
that was not able to correctly deal with check directories produced
under bi-arch check siutuations. This is fixed for wionbuilder and wil
be fixed in the R sources soon,
Uwe
On 07.06.2019 09:31, Georgi Boshnakov wrote:
It looks like you get the note when you run the check on the package directory,
rather than on the tarball of the package. Undoubtedly, you submitted the
tarball towinbuilder. develops::check also first builds the package and then
does the flecks on the tarball.
If unwanted files do creep into the tarball, use file.Rbuildignore to tell the
builder not to include them.
Georgi Boshnakov
________________________________________
From: R-package-devel [r-package-devel-boun...@r-project.org] on behalf of
Kassel Hingee [kassel.hin...@research.uwa.edu.au]
Sent: 07 June 2019 05:35
To: r-package-devel@r-project.org
Subject: [R-pkg-devel] checks on CRAN notes 'examples_i386', but checks
elsewhere do not
Hi All,
This is my first time submitting a package to CRAN, and posting here. I
hope I get everything right.
Checks ran by CRAN for Windows systems generated a note that I don't know
where to start to solve:
* checking for non-standard things in the check directory ... NOTE
Found the following files/directories:
examples_i386 examples_x64 lacunaritycovariance-Ex_i386.Rout
lacunaritycovariance-Ex_x64.Rout tests_i386 tests_x64
This note was not generated when I uploaded the package directly to
winbuilder in either release or development versions of R.
It also wasn't generated when I ran devtools::check() on my own (unix) computer.
The results of the CRAN check can be seen here for another few days:
https://win-builder.r-project.org/incoming_pretest/lacunaritycovariance_1.0-3_20190606_051128/
The check log containing the above note is here:
https://win-builder.r-project.org/incoming_pretest/lacunaritycovariance_1.0-3_20190606_051128/Windows/00check.log
The package source can bee seen here:
https://github.com/kasselhingee/lacunaritycovariance/tree/release
I haven't noticed a solution discussed earlier on this email list and
web searching gave me no joy. I am hoping you can help!
yours
Kassel
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
