Re: [R-pkg-devel] Tool for advanced man/doc page check?

On 10 July 2025 at 15:19, Ghislain Durif wrote: | @Duncan Murdoch I was indeed running the check with the release version | of R, I'll check with the development version. There are also regularly updated Docker containers if you want to run checks locally rather than as an action. See for examp

Re: [R-pkg-devel] Tool for advanced man/doc page check?

They also weren't found when checking on winbuilder (https://win-builder.r-project.org/)? Especially when checking with r-devel? Jan On 10-07-2025 12:13, Ghislain Durif wrote: Hi, I am the maintainer of a package for which we have done a major refactoring (work in progress, can be found h

Re: [R-pkg-devel] Tool for advanced man/doc page check?

Hi Ghislain, You may be interested in checkhelper::find_missing_tags(). More generally, there's a nice list of tools to prepare for CRAN submission here: https://github.com/ThinkR-open/prepare-for-cran Best, Etienne Le jeudi 10 juillet 2025 à 12:14 PM, Ghislain Durif a écrit : > > > Hi,

Re: [R-pkg-devel] Tool for advanced man/doc page check?

Am 10.07.25 um 12:13 schrieb Ghislain Durif: Upon my last resubmission to CRAN, some issues regarding some man pages (that I obviously missed) were found, e.g. function doc without a \value{} tag, or examples for (purposely) unexported functions. These issues were not raised during package check

Re: [R-pkg-devel] Tool for advanced man/doc page check?

Among other tests, CRAN uses the development version of R (R-devel) for checks. It usually contains more stringent tests than the release version of R, so possibly you were using a release version for tests and that test wasn't in it. The Github action r-lib/actions/check-r-package@v2 will ru

Re: [R-pkg-devel] Tool for advanced man/doc page check?

Hi again, Thanks for the responses! @Jan van der Laan our package is unix-only so I did no try to check it with winbuilder. @Etienne Bacher `checkhelper::find_missing_tags()` does actually find some issue, even running with the release version of R. @Duncan Murdoch I was indeed running the

Re: [R-pkg-devel] A way to prepend/append some code before/after running package examples? (e.g. to setup CPU resource usage limits for package example run or to clean up generated files)

Ghislain, That email was unreadable for me in two different email clients. A common pattern for resource minimalisation is to add a snippet setting the resources in a way CRAN prefers at the beginning of each examples block, often wrapped in a \dontshow{} block, and possibly resetting at end. T

[R-pkg-devel] Tool for advanced man/doc page check?

Hi, I am the maintainer of a package for which we have done a major refactoring (work in progress, can be found here ). Upon my last resubmission to CRAN, some issues regarding some man pages (that I obviously missed) we

[R-pkg-devel] A way to prepend/append some code before/after running package examples? (e.g. to setup CPU resource usage limits for package example run or to clean up generated files)

OpenPGP_signature.asc Description: OpenPGP digital signature __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] ggsmc: failed check

Hi, My R package ggsmc has been removed from CRAN after a failed check (see here https://cran-archive.r-project.org/web/checks/2025/2025-07-05_check_results_ggsmc.html). I have not been able to reproduce locally the error mentioned in the check. The check fails on a vignette. I