Post

Quick poll: When would you like CRAN to archive your package? A: Umm, never? B: Three days before posit::conf, where you're giving a talk about said package

Perhaps your package wasn't compatible enough with an antiquated version of Solaris?

:) If only. Apparently we regex'd too hard for gcc to handle: github.com/apache/arrow....

Hmm, so basically, it's "we found a possible bug in your package so we archived it". 🙄

More or less. I can come up with more positive ways to spin it. The compounding issue here is that contacting CRAN for an exception can be hard.

Yep. CRANs policies have caused a lot of package maintainers to: 1. Remove tests 2. Remove runnable examples 3. Remove URLs in docs and references (CRAN checks URLS) It's not purely a negative thing though, it's complicated.

Complicated indeed! Consider URL checks: it is mucg better to ensure that documentation is reachable. Yet sometimes even an archive.org redirect times out. Or a primary site times out (as they defend against DDOS and 'count hits / ip'). All this imposes 'work' on us, but raises overall quality.

And ASAN checks, painful as they are, most often reveal genuine bugs. So checking those is good too. We have the same issues as Debian maintainers (when, say, obscure hardware breaks) and yes a common way out can be to ... disable a test conditionally. Been there, done that. Also at CRAN.