#CRAN discovery of the day (Read the website!) Sorry the html url isn't different from cran.r-project.org so I can't link directly to the source:

In the rare case a link to a specific (and hence likely outdated) version of the package's sources in needed, one can use <https://CRAN.R-project.org/package=PKG&version=VER> for version VER of package PKG.

This means that this works:

https://cran.r-project.org/package=testthat&version=0.7.1

Following #rstats packages were maintained and are back on #CRAN now thanks to Andrej Spiess

- #dpcR, 2025-06-18, Digital PCR Analysis <10.32614/CRAN.package.dpcR>
- #MBmca, 2025-06-11, Nucleic Acid Melting Curve Analysis (https://journal.r-project.org/articles/RJ-2013-024/)
- #qpcR, 2025-06-10, Modelling and Analysis of Real-Time PCR Data <doi10.1093/bioinformatics/btn227>
- #PCRedux, 2025-06-13, Quantitative #PCR (#qPCR) Data Mining and Machine Learning Toolkit as Described in <doi:10.21105/Joss.04407>

Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology

#RStats {yyjsonr} update!

'yyjsonr' is a super fast JSON reader/writer supporting JSON, NDJSON and GeoJSON

v0.1.21 is released and now on #CRAN!

* Bug fixes
* More config options
* Removed non-API calls
* Using latest yyjson C lib

https://github.com/coolbutuseless/yyjsonr
https://cran.r-project.org/package=yyjsonr

A new function appears,
Tunable parameters it clears,
CRAN release nears.

for tidyAML :)

Just released: RandomWalker 0.3.0! Now you can generate random walks in up to 3 dimensions. This is a must-read for R programmers looking to enhance their simulations.

Dive into the details: [https://www.spsanderson.com/steveondata/posts/2025-05-09/

My Friday Linux tip is taking a rain check—randomness called!

Tomorrow I’m dropping a deep-dive blog on RandomWalker 0.3.0, now live on CRAN.

Think 3-D walks, on-the-fly subsetting, built-in confidence intervals, and the “x” column reborn as step_number. More goodies already cooking—stay tuned for the link!

Some #R #rstats about the packages on the repositories: #CRAN has 722 packages that use Bioconductor (3%), #Bioconductor has 2802 packages that use CRAN's packages (77%).

1.3% CRAN and 0.6% Bioconductor respectively use package outside these two repositories. But 91% and 93% use packages on their respective repos. 8% and 3% do not have any dependency on external packages (but could depend on system dependencies).

Today version 0.3.2 of the swephR package for R made it unto CRAN. Main reason for the upgrade was that CRAN had found a new WARNING by also inspecting the intermediate static library file. Instead of patching the upstream sources, I opted for deleting the library after building the the symbolic library for the package. It does not help anybody when code is inspected that is not actually used.

Two things were really nice:
* The warning message displayed at https://cran.r-project.org/package=swephR disappeared even before all test machines had build the new version. Probably once the first tests of previously failing tests came in.
* This package suggests a larger data package, that is only available on r-universe. Therefore, there had always been one NOTE, which meant manual inspection when submitting. Now this NOTE has been demoted to INFO, which goes through automatically, speeding up the process and leaving less work for the CRAN maintainers.

FYI: 14% of #CRAN links require knowing alias present on the libraries to resolve them. 80% of links to duplicated targets are present on the package. Which results on just 3% of links in packages being ambiguos (I expected more).

In related news, just 5 packages have different documentation for unix and windows! One of them breaks my #rstats link resolver...

Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology

So the #CRAN repository for R packages was down for a few minutes, but it's up again.

Didn't find them on Mastodon, so thanking @R_Foundation for the fix instead.

A regular reminder: CRAN Task View: Analysis of Spatial Data is always open for contributions!

Let us know about great tools for working with spatial data in R!

https://buff.ly/487HU6S

#CRAN could halve their work on the "incoming" queue by doing the following:

"R CMD CHECK --as-cran" should fail for exported functions witthout examples - authors prompted to fix b4 submission

There. I've done it.

I've just saved CRAN XX hours a week of emailing people to "please add examples".

If someone has any inside clout with CRAN/R core please make this suggestion.

As they say "volunteer time is precious", and this trivial fix could save so much!

Sometimes (often) one ends up needing to run older versions of R using older versions of packages. Evercran might be just the tool to help with that: https://github.com/r-hub/evercran#readme #RStats #docker #Cran #Rcheology

Folks who have contributed to #rstats core:

i've added a diff to my bug report, what happens next? This is a fairly critical fix for the + story.

Hoping to get it merged into trunk before they publish 4.4.2

any and all tips welcomed!

https://bugs.r-project.org/show_bug.cgi?id=18806

when did the tricksy hobbitses running R switch from Calloc to R_Calloc (etc)? only noticing now that they're deprecating the old way in 4.5.0 as I'm updating a bunch of old packages for another breaking update. #rstats #cran

Idea: Can we as package developers (as a group) decide on a standard file in which to store all historical communication with CRAN?

CRAN-correspondence.txt ?

I don't mean any sanitized high-level summary, I mean a record of every CRAN interaction about your package submission. Emails could be redacted to "[CRAN member]" to avoid any privacy concerns.

I'm sick of feeling like I'm navigating CRAN blind. The lack of open discussion makes it really difficult.