#cran

2026-02-02

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: github.com/r-hub/evercran#read #RStats #docker #Cran #Rcheology

2026-01-03

NSPanel Pro 120 (SONOF)
Qu’est-ce que le NSPanel Pro ?

Le Sonoff NSPanel Pro est un panneau de commande tactile pour maison intelligente qui va bien plus loin qu’un simple interrupteur. J'ai la version 120, c'est à dire avec un écran un peu plus grand que la version classique, mais ca ne change pas son usage. Bref..
dekloo.net/projets/domotique/s
#Domotique #HomeAssistant #domotique #cran #cranTactile #HomeAssistant #interface #sonof

ᴅʀ. ᴍᴏᴡɪɴᴄᴋᴇʟ'ꜱDrmowinckels@fosstodon.org
2025-12-26

We Made It! 🎉

25 days. Complete modern R package development workflow. From usethis automation to CRAN submission. You have everything you need!

Your Next Steps:
✨ Apply these tools to your packages
📚 Bookmark for reference
🤝 Share knowledge with community
🚀 Build amazing R packages

Thank you for following #RPackageAdvent2025! Now go make the R ecosystem better! 🎄📦
Keep Learning: r-pkgs.org | usethis.r-lib.org

#rstats #CRAN #RPackageAdvent2025 #ThatsAWrap

2025-12-08

08.12.2025

1. YUNK - our way
2. ALTE SAU - kleines Tier
3. SHRUDD - emt
4. CRAN - nate
5. FAMILY DOG - doom womb
6. PRISONER DU TEMP - la rose blanche
7. GÄNGSTGÄNG - livraison de repaces
8. SYNDROME 81 - les derniers jours
9. SHAM 69 - hersham boys

subjektiv.net/08-12-2025/

#2025 #ABRAUM #ALTESAU #CRAN #DURUTICOLUMNE #FAMILYDOG #FINALE #GNGSTGNG #MARABOOTS #PRISONERDUTEMP #PSYCHEDELICFURS #RUB #SHAM69 #SHRUDD #SLEAFORDMODS #SONICYOUTHOFTODAY #SYNDROME81 #YUNK

Darren Wilkinsondarrenjw@mastodon.org.uk
2025-12-05

The "netcontrol" #rstats package was recently removed from #cran - I have some instructions for installing the archived version: darrenjw.github.io/work/docs/n

Thorbjörn Sievertvolephd@fediscience.org
2025-11-13

Oh and don't get me started with all this package version mismatch in #Python.
What absolute nonsense!

#rstats #cran is not perfect, but I have never ever had an issue with versions not matching between packages.

2025-11-04

Thankfully temporary but I must have caught the CRAN website on a config change or something...back now but for the record I might need blood pressure medication if I see this again 😅

#CRAN #RStats

This site can't be reached

cran.r-project,.org refused to connect.

Try:
* Checking the connection
* Checking the proxy and the firewall

ERR_CONNECTION_REFUSED
2025-10-10

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: github.com/r-hub/evercran#read #RStats #docker #Cran #Rcheology

2025-10-05

Dear R developers and CRAN maintainers, I wonder if you can kindly help me understand how I should deal with the import of some packages and package functions. Despite reading "R Packages" (eg <r-pkgs.org/dependencies-mindse>) and "Writing R Extensions" (eg <cran.r-project.org/doc/manuals>), I'm still unsure how to deal with the following situation.

Suppose you have a package with the following requirements:

1. *One* function in your package, say "funA" requires a whole package, say PKGA. *However*, the function only uses PKGA in a separate (parallel::makeCluster) process. This function is fundamental to your package, in the sense that the user will surely use it at least once in their workflow.

2. Another function in your package, say "funB", requires two functions "aux1" and "aux2" from another package, say PKGB. The user might use this function, or maybe not. In your code (no parallel invocation), the functions are called with PKGB::aux1 etc.

3. The two functions "aux1" and "aux2" from PKGB are also available in PKGA. You'd like to be sure that the user can choose freely which ones they want in their workflow, alongside your package. In other words, no masking should take place a priori.

Given these conditions, what should NAMESPACE and DESCRIPTION contain? With Roxygen, where should I use @ import and @ importFrom? and what about usethis::use_import()?

Thank you very much for any tips or extra references to read!

Edit: for the moment, my solution has been to include PKGA, PKGB, and parallel in the Imports field of the DESCRIPTION file, but not to have these three packages in the NAMESPACE file as Import(). This seems to achieve what i want, but I'm not sure it's the "proper" solution.

#rstats #cran

Dirk Eddelbuetteleddelbuettel
2025-10-01

had its first 'three million packages delivered' month in September (outside that two-day Sep 2023 outlier) bringing the total to over 54 million packages shipped as .deb binaries.

. Fast. Easy. Reliable. Pick All Three.

Dual chart with #r2u cumulative downloads in millions on the left, and average weekly downloads (on a log scale) on the right.
2025-09-26

Dependencies and reverse dependencies: Python vs. R: Julie Tibshirani reflects on how the #R ecosystem uniquely manages dependencies through reverse dependency checks on #CRAN. R’s approach comes at a cost to developers, but also fosters a culture of empathy and responsibility among package...
spatialists.ch/posts/2025/09/2 #GIS #GISchat #geospatial #SwissGIS

Rod2ik 🇪🇺 🇨🇵 🇪🇸 🇺🇦 🇨🇦 🇩🇰 🇬🇱☮🕊️rod2ik
2025-09-24
Rod2ik 🇪🇺 🇨🇵 🇪🇸 🇺🇦 🇨🇦 🇩🇰 🇬🇱 ☮🕊️rod2ik.bsky.social@bsky.brid.gy
2025-09-24
2025-09-24

Problems with CRAN during R installation Ubuntu:

To reproduce the error:
sudo add-apt-repository "deb cloud.r-project.org/bin/linux/ $(lsb_release -cs)-cran40/"

Error message:
Repository: 'deb cloud.r-project.org/bin/linux/ plucky-cran40/'
404 Not Found [IP: 108.157.173.54 443]
E: The repository 'cloud.r-project.org/bin/linux/ plucky-cran40/ Release' does not have a Release file

Consequences:
If you don't add the CRAN repository,
sudo apt install r-base
will install the r-base old version

#CRAN #Rstats

Steven P. Sanderson II, MPHspsanderson.com@bsky.brid.gy
2025-09-02

Does anyone know why the CRAN logs have not been getting updated? #CRAN #R #RSTATS

Egor Kotov 🌐🏃‍♂️🚊🚋🚙EgorKotov@datasci.social
2025-08-31

New #rstats github.com/e-kotov/gridmaker Creates Eurostat GISCO compatible and INSPIRE-compliant grids with IDs that look like ‘CRS3035RES1000mN3497000E4448000’ or ‘1kmN3497E4447’. Input can be sf, or bounding boxes. Output can be sf polygons, centroids, or just data.frame with grid cell coordinates. The resulting grids are always aligned to rounded coordinates as per INSPIRE requirements. No more downloading 1.5-2.6 GB files from Eurostat. Do you think this is ready to go on #CRAN?

gridmaker: Create Standardized Spatial Grids
Transforming an sf object into a GISCO/INSPIRE-compliant grid
sf boundary object GISCO/INSPIRE standardized grid
or bounding box with IDs in form of CRS 3035 RES 1000m N3016000 E4032000gridmaker
Create GISCO/INSPIRE-compliant grids with IDs
library(gridmaker)
create_grid(
  grid_extent = bound_sf,
  cellsize_m = 5000,
  clip_to_input = TRUE
)
github.com/e-kotov/gridmaker
2025-08-29

terminalgraphics #rstats package is now on #CRAN (cran.r-project.org/web/package). I have also managed to add support for sixel, so the package now supports both terminals that support Terminal Graphics Protocol and Sixel.

wexterm terminal with R running and the following text: 

> library(terminalgraphics)
> library(tinyplot)
> sixel()
> plt(
  ~ Petal.Length | Species,
  data = iris,
  type = "density",
  fill = "by",
  main = "Distribution of petal lengths",
  sub = "Grouped by species"
)

followed by a density graph in the terminal.

So, #rstats package mlr3spatiotempcv got removed from CRAN because a dependency package of it got kicked earlier.

This package made it back to #cran 4 days before the deadline for mlr3spatiotempcv. However, checks continued to fail with the same reason of "package XY not being available" and eventually mlr3spatiotempcv was removed.

The maintainer of the dep package couldn't upload a new version for more than two weeks because CRAN was "on vacation".

Now I have to go through a resubmission process for basically nothing.

There must be a better process - or an alternative repository. (Yes, I know about R multiverse)

Science ouverte UnivRennesSO_UnivRennes
2025-08-25

tandis que le CRAN organise la cohérence entre les différentes versions de ses packages, ce travail d'alignement fait malheureusement défaut dans Pypi, raison pour laquelle Bruno Rodrigues plaide pour un meilleur contrôle des packages dans PyPi sous l'aspect de leur interopérabilité avec les autres packages qu'il contient brodrigues.co/posts/2025-08-22

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst