Dear Duncan,
Thanks for taking the time to read my message and for the constructive
idea. You are right that it is a bit late for us to do this now. Given
that spatstat (<=1.65) exports >2,500 objects which are now spread
across sub-packages we would obviously have to make a script to help us
reex
On Thu, 11 Mar 2021 12:57:00 -0800
Jonathan Callahan wrote:
> I am building a package using R 4.0.4 on OS X 10.15.7.
>
> In a terminal I type:
>
> R CMD build --resave-data AirSensor
>
> Then, I check with:
>
> R CMD check --as-cran AirSensor_1.0.8.tar.gz
>
> Everything is fine until I see
This is a bug in R 4.0.0 - R 4.0.4 affecting packages using LazyData.
Two possible workarounds:
- Manually run tools::resaveRdaFiles() on your data directory before
building the package.
- Use a current development version of R (4.0.4-patched >= r80069 or
R-devel >= r79573)
Best regards,
Hmm, I may have written too quickly. I find these lines from R CMD
build --help confusing:
--resave-data=re-save data files as compactly as possible:
"no", "best", "gzip" (default)
--resave-data same as --resave-data=best
The first line suggests th
maybe R CMD build --resave-data=best ... ?
On 3/11/21 3:57 PM, Jonathan Callahan wrote:
I am building a package using R 4.0.4 on OS X 10.15.7.
In a terminal I type:
R CMD build --resave-data AirSensor
Then, I check with:
R CMD check --as-cran AirSensor_1.0.8.tar.gz
Everything is fine un
I am building a package using R 4.0.4 on OS X 10.15.7.
In a terminal I type:
R CMD build --resave-data AirSensor
Then, I check with:
R CMD check --as-cran AirSensor_1.0.8.tar.gz
Everything is fine until I see:
* checking data for ASCII and uncompressed saves ... WARNING
Note: significan
As far as I know, this is a harmless note and can be disregarded.
(And, can't be eliminated.) (It would be nice if that were clearer in
the documentation ... maybe it is and I just haven't checked lately ...)
On 3/11/21 2:16 PM, William Andrés Herrera Cáceres wrote:
Hi everyone,
I am a begi
Hi everyone,
I am a beginner in developing R packages in CRAN. Now I am trying to submit my
package to CRAN but I cannot solve this issue:
Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64
Check: CRAN incoming feasibility, Result: NOTE
Maintainer: 'William Herrera-C�ceres '
It may be too late to do this now, but you could use the approach that
devtools used when it was broken up: The main package imports functions
from the new spatstat. packages and exports them. This way it could
be done with no breaking changes. Reverse dependencies could change to
depend
Dear all,
I'm seeking advice on how to submit a new package version with breaking
changes to CRAN. I will try to make this short:
1. spatstat (<= 1.65) had grow to be very large with extensive
examples, tests, and documentation.
2. CRAN asked us to reduce package size and check time.
3. We reorga
10 matches
Mail list logo
