Re: [R-pkg-devel] How to deal with issues when using devtools::check_rhub(), rhub::check(), and web form

2024-01-24 Thread Ivan Krylov via R-package-devel
В Wed, 24 Jan 2024 16:14:05 -0800 Carl Schwarz пишет: > I tried using the web interface at https://builder.r-hub.io/ to > select the denebian machines, and it returns a message saying > > We're sorry, but something went wrong. > If you are the application owner check the logs for more

Re: [R-pkg-devel] New Package Removal because Shared Library Too Large from Debugging Symbols

2024-01-24 Thread Ivan Krylov via R-package-devel
On Mon, 22 Jan 2024 17:14:04 +0100 Tomas Kalibera wrote: > Yes, inside a bigger email, reports can get overlooked, particularly > when in a thread with a rather different subject. It wasn't > overlooked this time thanks to Martin. Then additional thanks goes to Martin, and I'll make sure to

[R-pkg-devel] How to deal with issues when using devtools::check_rhub(), rhub::check(), and web form

2024-01-24 Thread Carl Schwarz
I fixed all of the new issues identified by CRAN, and these seem to be from the r-devel-linux-x86_64-fedora-gcc and similar machines where it flags documentation in a function. However, when I use devtools::check_rhub(), it just "hangs", i.e. generates messages saying to check a web file that

Re: [R-pkg-devel] R-package-devel Digest, Vol 105, Issue 19

2024-01-24 Thread Simon Urbanek
This is a reminder why one should never build packages directly in their source directory since it can only be done once (for packages with native source code) - always use R CMD build --no-build-vignettes foo && R CMD INSTALL foo_*.tar.gz if you plan to edit files in the source directory and

Re: [R-pkg-devel] R-package-devel Digest, Vol 105, Issue 19

2024-01-24 Thread Carl Schwarz
Solved... The src/ directory also included a .o and .so objects from the last build of the package that must be "out of date" because once I removed those older objects, the Build -> Document and build -> Check package now work fine without crashing...A newer version of the .o and .so objects are

Re: [R-pkg-devel] new maintainer for CRAN package XML

2024-01-24 Thread Uwe Ligges
On 24.01.2024 15:59, Jeroen Ooms wrote: On Mon, Jan 22, 2024 at 3:51 PM Uwe Ligges wrote: Dear package developers, the CRAN team (and Professor Ripley in particular) has been the defacto maintainer of CRAN package 'XML'. Our hope was that maintainers of packages depending on XML will

Re: [R-pkg-devel] new maintainer for CRAN package XML

2024-01-24 Thread Uwe Ligges
On 24.01.2024 16:38, Emmanuel Blondel wrote: if XML is deprecated, then what would be the choice for a package maintainer? Move to xml2 probably at some point I assume I use XML in the R packages I've been developing. For some of them, I started before CRAN started being the maintainer, and

Re: [R-pkg-devel] new maintainer for CRAN package XML

2024-01-24 Thread Emmanuel Blondel
if XML is deprecated, then what would be the choice for a package maintainer? Move to xml2 probably at some point I assume I use XML in the R packages I've been developing. For some of them, I started before CRAN started being the maintainer, and before xml2 inception. The thing is that XML

Re: [R-pkg-devel] new maintainer for CRAN package XML

2024-01-24 Thread Jeroen Ooms
On Mon, Jan 22, 2024 at 3:51 PM Uwe Ligges wrote: > > Dear package developers, > > the CRAN team (and Professor Ripley in particular) has been the defacto > maintainer of CRAN package 'XML'. > Our hope was that maintainers of packages depending on XML will migrate > to other packages for reading

Re: [R-pkg-devel] How to debug segfault when running build -> document in Rstudio that includes TMB module

2024-01-24 Thread Serguei Sokol
Le 24/01/2024 à 04:22, Carl Schwarz a écrit : 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