On 01.04.2021 07:55, Tim Hulsen wrote:
r-release-windows-ix86+x86_64
A new check, you declare LazyData in your DESCRIPTION file which is
meaningless. So please simply omit that line.
Best,
Uwe Ligges
Op wo 31 mrt. 2021 om 14:31 schreef Duncan Murdoch
:
On 31/03/2021 8:28 a.m., Tim H
On 4/2/21 4:05 AM, Daniel Kelley wrote:
The "oce" package for oceanographic analysis is failing a check on the
r-devel-windows-x86_64-gcc10-UCRT system (see
https://www.r-project.org/nosvn/R.check/r-devel-windows-x86_64-gcc10-UCRT/oce-00check.html).
The problem seems to relate to the checking
On 2 April 2021 at 09:45, Duncan Murdoch wrote:
| On 01/04/2021 9:06 p.m., David Cortes wrote:
| > Is it allowed to use such functions in packages? I see a few packages
| > currently in CRAN have the same note in the checks, such as "iotools",
| > and am wondering if I should just email the CRAN
On 01/04/2021 9:06 p.m., David Cortes wrote:
I’d like to ask for clarification about CRAN policies regarding usage
of functions that start with "RC_*", such as "RC_fopen".
I'm trying to upload a package which is meant for reading and writing
data from text files in a certain format, for which I
I’d like to ask for clarification about CRAN policies regarding usage
of functions that start with "RC_*", such as "RC_fopen".
I'm trying to upload a package which is meant for reading and writing
data from text files in a certain format, for which I want to use a C
file pointer which I obtain thr
The "oce" package for oceanographic analysis is failing a check on the
r-devel-windows-x86_64-gcc10-UCRT system (see
https://www.r-project.org/nosvn/R.check/r-devel-windows-x86_64-gcc10-UCRT/oce-00check.html).
The problem seems to relate to the checking vignette outputs.
According to
https://ww
