similar to: Un-informative Error in re-building vignettes

Hi all, I am having an issue related to installing packages on windows with R-3.6.0. When installing a package that is in use, I expected R to stop with an error. However I am getting a warning that the DLL copy was not successful, but the overall package installation IS successful. This is quite dangerous because the old DLL and the new R code could be incompatible. I am definitely not the

thanks for the tip Jan. However it would be nice if I didn't have to handle this myself for all of my packages. (and teach my students how to do that) BTW I tried to disable staged installation, and the issue still happens: th798 at cmp2986 MINGW64 ~/projects/max-generalized-auc (master) $ R_INSTALL_STAGED=FALSE R --vanilla -e

thanks for your input Herv?. Glad to hear I'm not the only one still having this issue. In my opinion install.packages should stop with an error (instead of a warning) if this happens. However even if you want to keep the warning, at least make it so that users can set options(warn=2) to get an error if they want one. I tried setting options(warn=2) but for some reason I still get a warning.

Hi Toby, AFAIK it has not been addressed in R. You can handle the problem on your package side, see https://github.com/Rdatatable/data.table/pull/3237 Regards, Jan On Thu, May 30, 2019 at 4:46 AM Toby Hocking <tdhock5 at gmail.com> wrote: > > Hi all, > > I am having an issue related to installing packages on windows with > R-3.6.0. When installing a package that is in use, I

Also note that this can lead to people not being able to load the package if the set of .Call entry points has changed between the old and new versions of the package. We strongly suspect that this is what happened to this Bioconductor user: https://support.bioconductor.org/p/121228/ Note that she's installing the binary and in this case no warning is issued. All we see is: package

Dear all, winbuilder is down. Given current inspection results and circumstances, I expect a downtime of *at least* 24 hours. This applies to on-demand check services, CRAN check service results and CRAN binary builds for Windows. Best, Uwe Ligges

Hello, I am trying to submit a new package to CRAN. I had checked the packages with R-devel and R-release in windows 7 local and ubuntu 12.04 local. The package has a C file in src folder which successfully compiled in all the cases (there were few trivial warnings). I had submitted the package last week and was asked to resubmit with few changes in the description file. However upon

Hello, my package passes R CMD check without any warnings on my local machine (Mac OS), as well as on Uwe Ligges' Winbuilder. On RForge, however, we sometimes run into problems building the Sweave vignettes. Now here's my question: is it necessary for a CRAN submission that the Sweave vignettes can be compiled on CRAN, or is it possible to provide the (locally compiled) pdf vignette to

I've recently updated the coxme package, which calls internal routines from the bdsmatrix package.? (It is in fact mentioned as an example of this in the Extensions manual.) The call connections are a blocks like this, one for each of the 9 called C routines. void bdsmatrix_prod4(int nrow,??? int nblock,?? int *bsize, ??????????????????? double *bmat, double *rmat, ??????????????????? int

And remove the cast on the return value of R_GETCCallable. And check that your function is found before using it. #include <R.h> #include <Rinternals.h> #include <R_ext/Rdynload.h> void bdsmatrix_prod4(int nrow, int nblock, int *bsize, double *bmat, double *rmat, int nfrail, double *y) { DL_FUNC fun = NULL; if (fun==NULL)

Hello, The package cts on CRAN generated a note on some systems. For instance: checking compiled code ... NOTE File ?/home/ripley/R/Lib32/cts/libs/cts.so?: Found ?abort?, possibly from ?abort? (C) which can be found from the link http://www.r-project.org/nosvn/R.check/r-patched-solaris-sparc/cts-00check.html But the package uses Fortran subroutines only without any C subroutines. In

Dear R developers, I recently observed a NOTE on several MaxOS X package checks: sh: line 1: gs: command not found !!! Error: Closing Ghostscript (exit status: 127)! /usr/bin/texi2dvi: thumbpdf exited with bad status, quitting. See for details: http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/simecol-00check.html or

Can someone please add documentation for that environment variable to Writing R Extensions? An appropriate place would be section https://cloud.r-project.org/doc/manuals/r-release/R-exts.html#Suggested-packages which already discusses _R_CHECK_DEPENDS_ONLY_=true [[alternative HTML version deleted]]

Dear all, I run R CMD build --compact-vignettes="both" gRbase and/or R CMD build --compact-vignettes="gs+qpdf" gRbase and in the log from r-devel (on winbuilder) I get * checking sizes of PDF files under 'inst/doc' ... WARNING 'gs+qpdf' made some significant size reductions: compacted 'gRbase-arrays.pdf' from 421Kb to 115Kb consider

Dear all, I run R CMD build --compact-vignettes="both" gRbase and/or R CMD build --compact-vignettes="gs+qpdf" gRbase and in the log from r-devel (on winbuilder) I get * checking sizes of PDF files under 'inst/doc' ... WARNING 'gs+qpdf' made some significant size reductions: compacted 'gRbase-arrays.pdf' from 421Kb to 115Kb consider

I think the poster is interested in being able to try the build/check on a Mac in the fashion that Winbuilder does. That is, rather than have CRAN do all the platform checks, is there a way to submit a package to be tested for just one platform? It may be useful to have such a facility so package builders can test before submission, and from my own experience I believe would help to render

I am building a package that makes a simple visualization. A part of the code is in C++, and utilizes the functions srand() and rand() for purposes not related to statistics (introducing random noise in the visualization). The package compiles without problems on my workstation(s), but when I submitted it to the winbuilder service, I got the following weird message: * checking compiled code ...

I have a question regarding the build of my project papeR (hosted on R-forge http://r-forge.r-project.org/R/?group_id=1574) with respect to lme4. Both, Windows and MacOS are complaining that lme4 doesn't export summary: Error : object 'summary' is not exported by 'namespace:lme4' ERROR: lazy loading failed for package 'papeR' Linux however builds the project

>>>>> peter murage >>>>> on Tue, 4 Apr 2023 06:24:56 +0000 writes: > Which package in R replaced package prob? Well, if you google that you should quickly be lead to (something I even think makes sense to memorize as "rule" package=<pkg> ) : https://CRAN.R-project.org/package=prob which now says that the package was archived as it

Hello, macosx 10.13.6, Rdevel r76458 I'm trying to compile against openblas to reproduce an error on the CRAN check page (my package is clean under winbuilder and all but one of the checks). I've downloaded and installed openblas 0.3.7 but I am not 100% sure that it is being used by R. Using ./configure --with-blas="-lopenblas" Then running R to discover the PID I get: