Re: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

2019-03-25 Thread David Kepplinger
Dear Community, The issue persists and I don't know if it is something I can fix or if it's a false positive from the CRAN incoming checks. As a result, the package is archived as the old version has other issues with the new R version. Does someone have an idea how I can fix the issue? I have as

Re: [R-pkg-devel] package cartograflow_0.0.0.9000.tar.gz

2019-03-25 Thread Dirk Eddelbuettel
On 25 March 2019 at 22:12, cartograf...@gmail.com wrote: | Hello, | I've submitted my package cartograflow and I received an email from your teeam that it does not pass the incoming checks automatically.Debian:

Re: [R-pkg-devel] package cartograflow_0.0.0.9000.tar.gz

2019-03-25 Thread Uwe Ligges
I cannot beloeve it. But this is certainly not R-devel? Not sure about devtools which we do not use on CRAN, but simply R CMD check --as-cran with a recent R-devel version on the package tarball should reproduce the findings. Best, Uwe Ligges On 25.03.2019 23:12, cartograf...@gmail.com wr

[R-pkg-devel] package cartograflow_0.0.0.9000.tar.gz

2019-03-25 Thread cartograf...@gmail.com
Hello, I've submitted my package cartograflow and I received an email from your teeam that it does not pass the incoming checks automatically.Debian: Status: 1 ERROR, 2 WARNINGs, 1 NOT

Re: [R-pkg-devel] Should R be in single quotes in package Description filed in DESCRIPTION file?

2019-03-25 Thread Marta Karaś
Hi Max, Thank you for this excellent answer! I am going to go for what you suggested and skip R in Description field at all. All the best, Marta On Mon, Mar 25, 2019 at 11:26 AM Maxime Turgeon < maxime.turg...@mail.mcgill.ca> wrote: > Looking at `tools::CRAN_package_db()`, I can see 1433 package

Re: [R-pkg-devel] Should R be in single quotes in package Description filed in DESCRIPTION file?

2019-03-25 Thread Maxime Turgeon
Looking at `tools::CRAN_package_db()`, I can see 1433 packages that mention R in the Description field, and only 77 use single quotes around it. So I would say that the consensus seems to be to *not* use single quotes. On the other hand, I am not convinced you need to mention R at all in your D

[R-pkg-devel] Should R be in single quotes in package Description filed in DESCRIPTION file?

2019-03-25 Thread Marta Karaś
Should R be in single quotes in package Description filed in DESCRIPTION file? E.g. which of the following versions of Description file is correct? 1. Description: Created to host raw accelerometry data sets and their derivatives which are used in the corresponding 'adept' 'R' package. 2.

[R-pkg-devel] GDAL which version on CRAN ?

2019-03-25 Thread Jean-Loup Gaussen
Hi everyone ! I'm looking for the library GDAL >= 2.0.0 on windows and Mac OS to pass CRAN check and compilation. Do you know which version is installed on the CRAN for windows and Mac OS ? So far, I found 1.8.1 for windows and 2.1.3 for Mac OS ... Using rwinlib project for windows is not a sol

Re: [R-pkg-devel] What to do when a dependency falls off CRAN

2019-03-25 Thread Ralf Stubner
On 24.03.19 21:00, Neal Fultz wrote: > 3) Adopt package, push fixed one to CRAN - not sure what the exact process > is for un-orphaning, or if I would want to commit to maintaining it without > knowing more about why it was dropped and how much work it is to get it > passing. Eg if it were patholog

Re: [R-pkg-devel] active bindings in package namespace

2019-03-25 Thread Ralf Stubner
On 24.03.19 18:27, Jack O. Wasey wrote: > This is a good point. I would prefer to include all the data in the > package, but CRAN has strict limitations on package and subdirectory > size, which the potential data would easily exceed. You could use a separate data package distributed via drat, c.f

Re: [R-pkg-devel] What to do when a dependency falls off CRAN

2019-03-25 Thread David Winsemius
When I attempt to install it the error indicates that the maxent package is not available. Attempts to install that package fail with more errors than can fit on an Rstudio console, so I cannot even scroll to see the first error. You could simply remove the dependency on that package if your