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
ed hits.
>
> Theoretically this is just a warning and you can try submitting to CRAN,
> but CRAN may have even less luck accessing Posit than win-builder.
> Submitting anyway is recommended here [1].
>
> [1]
> https://stackoverflow.com/questions/66078248/invalid_url_in_cran_checks
&g
Hi,
I've got an update for my R package ready to go. It checks successfully on
my own machine for r-oldrel and r-release, but when I submit it to R Win
Builder for r-devel to be checked, it gives me a warning not seen before
with an uninformative message:
* checking whether the namespace can be
This is actually an issue that was just fixed.
package:vctrs has an error when installing under r86723 because it creates
delayed bindings at package install time that cannot be restored at package
load time.
It may be a small while before the newest R devel version is in use by the
CRAN farm,
Unless I'm misunderstanding, it sounds like you're storing data that your
package requires in an external location. You need to put your data into
your R package and then access that data with system.file(package =
"", )
Sometimes people will make a folder inst/extdata inside their R package
Unless I'm misunderstanding, you're trying to pass a value by name to a
function. That is not a thing in C nor C++. However if you want to name the
arguments, you can do so with comments:
/* print = */ print
On Thu, Jun 6, 2024, 19:16 Søren Højsgaard via R-package-devel <
To avoid the remapping of beta to Rf_beta, you should
define R_NO_REMAP_RMATH before you include Rmath:
#define R_NO_REMAP_RMATH
#include
On Sun, Jun 2, 2024, 19:33 Gregory Raskind wrote:
> Hi,
>
> I'm extending an R package that uses the R C API directly. I'd like to use
> some distribution
You cannot and should not ignore this.
An R package should never ever be assigning variables into environments for
which they haven't been granted permission to do so. You should ask the
user whether they want the object assigned in the global environment before
doing so, and the default should
I think 'package:renv' does a lot of the stuff you mentioned here. I
think they accomplished your issue by making an .Rprofile file for
each project. The working directory would be set to the root directory
of the project, the R profile runs and sets .libPaths() as
appropriate, then the scripts
The n in snprintf includes the room for the terminating nul. It should be
8191. If gcc is throwing a warning, it can be ignored.
On Mon, Nov 20, 2023, 04:04 Serguei Sokol wrote:
> Le 19/11/2023 à 02:07, Iris Simmons a écrit :
> > Yes, the reason for the error is the use of sprintf
Yes, the reason for the error is the use of sprintf. You can instead use
snprintf where n is the maximum number of bytes to write, including the
terminating nul character. For example:
char msg[8191];
snprintf(msg, 8191, "criteria: error (%d) -> %s\n", inErr, errStr);
Rf_error(msg);
or however
The packages that you imported are no longer available. As far as I
understand, rgeos, maptools, and a few other spatial related packages have
been archived and have been replaced with better alternatives.
On Tue, Oct 17, 2023, 03:13 cartograf...@gmail.com
wrote:
> Hi, I've put an update
The packages in additional repositories are not installed on the CRAN
checking machines. The NOTE is expected, but it's not a warning, so your
package should still be allowed to upload to CRAN. You should not remove
ionChannelData from Suggests because then the reference to that package in
your
You wrote
# create the plots directory if it does not exist
but then created a directory named outdir/plots/typ_Sys.time.tif
You need to rewrite the code like:
plotsdir <- file.path(outdir, "plots")
fp <- file.path(plotsdir, paste(typ, "_",
stringr::str_replace_all(Sys.time(),
You can add
\keyword{internal}
to the Rd file. Your documentation won't show up the in the pdf manual, it
won't show up in the package index, but you'll still be able to access the
doc page with ?levels.no or help("levels.no").
This is usually used in a package's deprecated and defunct doc
You put a space between "https:" and "//", you should definitely remove
that. Also, you need to indent your description. Right now, your
DESCRIPTION is being interpreted in this manner:
```
Package
"neotoma2"
Title
16 matches
Mail list logo
