The first NOTE is irrelevant. The second NOTE says that you must
reduce the running time of your examples (so that the longest of them
takes <10 seconds on the *slowest* CRAN testing platform). This thread
might be useful:
https://stat.ethz.ch/pipermail/r-package-devel/2021q4/007521.html
Hello everyone,
I hope this email finds you well.
I’m sorry to bother you, it’s the very first time I’m submitting a package to
CRAN.
Recently my submission got rejected with the following feedback:
Non-FOSS package license (file LICENSE)
Suggests or Enhances not in mainstream repositories:
Hello everyone
I need your attention. I have developed a new R package and submitted it to
CRAN. In return main i got two notes they are:
* using log directory 'd:/RCompile/CRANincoming/R-devel/drglm.Rcheck'
* using R Under development (unstable) (2024-07-05 r86875 ucrt)
* using platform: x86_64-w
I'm pretty sure this is from this R-devel commit:
https://github.com/r-devel/r-svn/commit/92c1d5de23c93576f55062e26d446feface07250
This turns on stricter boundary checking, specifically see
https://github.com/lme4/lme4/issues/794#issuecomment-2154948145
Arguably, accessing an element of
Seemingly starting with the most recent builds of R-devel, I�ve been getting
segfaults related to a piece of cpp code that indexes a zero-size
NumericVector. Essentially the same as this dummy example:
```
library(Rcpp)
sourceCpp(
code = '
#include
using namespace Rcpp;
// [[Rcpp::exp
On 08.07.2024 16:08, Iris Simmons wrote:
This is something I'd run into recently as well.
The R devs changed the default from building the manual to not building the
manual. Now if you want (or need) to build the manual, you should add
Well, not really, we still build manuals unless file(s)
Hi Mark,
As someone else affected by this issue, it is actually quite tough to
resolve. This is because quite literally every other day, the list of what
is and is not non-API is changing. It is particularly challenging since
this is in R-devel and not any stable R release.
If there were a stable
Have you contacted the maintainer directly (i.e. by e-mail)? (Yes,
they should be paying attention to Github, but trying another channel
never hurts.)
My personal experience is that I was succeeded in submitting a
package update to CRAN even though there were NOTEs of this sort (in
that
Dear R-pkg-dev folk,
The cpp11 package, which was developed yet is no longer maintained by
Jim Hester, now triggers warnings on some CRAN pre-submit checks for
"non-API calls to R" via "SETLENGTH", "SET_TRUELENGTH", and others. The
relevant issue is https://github.com/r-lib/cpp11/issues/355, with
This is something I'd run into recently as well.
The R devs changed the default from building the manual to not building the
manual. Now if you want (or need) to build the manual, you should add
BuildManual: TRUE
to your DESCRIPTION.
On Mon, Jul 8, 2024, 10:05 Michael Dewey wrote:
> Short ver
Short version
I have recently tried to update two of my CRAN packages and I am getting
the NOTE from R CMD check --as-cran
Package has help file(s) containing install/render-stage \Sexpr{}
expressions but no prebuilt PDF manual.
(It comes on one line in the check.log)
What am I doing wrong
11 matches
Mail list logo
