Carl,
Consider performing these tasks without the use of the 'devtools' package,
running the following from a shell.
```shell
R CMD build .
R CMD INSTALL --with-keep.source ./SPAS_*.tar.gz
# (assuming you use roxygen2)
Rscript -e "roxygen2::roxygenize(load = 'installed')"
R CMD check --as-cran
I'm trying to update my SPAS package to respond to a CRAN check. Before
starting the changes, I tried to rebuild my package, but now get a segfault
when I try to do a devtools::document() or devtools::check(args =
c('--as-cran')). See below for output from the Rstudio "Build" window.
I've
-
The notes you get illustrate why they are useful, if you look at your rendered
documentation you probably will see something wrong. Thousands of packages on
CRAN, including some of mines have had this kind of infelicities for years.
Firstly, the two sets of braces suggest that you meant a
OK. Clear enough. CRAN applies a new "filter" as it was going through
without crying a note since decades ;-). However, indeed, re-checking
the manual "Writing R extensions" my syntax was wrong...
Thanks for the guidance,
Patrick
Le 23/01/2024 à 19:58, Dirk Eddelbuettel a écrit :
> On 23
В Tue, 23 Jan 2024 19:39:54 +0100
Patrick Giraudoux пишет:
> \itemize{
> \item{.}{lm and glm objects can be passed directly as the upper
> scope of term addition (all terms added).
Inside the \itemize and \enumerate commands, the \item command doesn't
take any arguments:
On 23 January 2024 at 19:39, Patrick Giraudoux wrote:
| Has anyone an idea about what is going wrong ?
\item has no braces following it. From a package I submitted today and for
which I still have NEWS.Rd in the editor (indented here):
\section{Changes in version 0.0.22 (2024-01-23)}{
Dear listers,
I meet a problem with the submission of the package pgirmess. In fact
the package goes through R CMD check --as-cran and R-wind-builder
smoothly with no problem, but submitted to CRAN, I get this:
Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64
Check: CRAN
