On 11.12.2025 20:07, Kenny, Christopher wrote:
Hello all,
I was looking for advice on best practices for resubmitting packages that were
archived.
This morning, Brian Ripley erroneously archived one of my packages (geomander)
prior to the deadline to fix a broken example. He then archived its reverse
dependencies a few minutes later.
Why erroneously? Your deadline passed.
A new deadline was set for the reverse dependencies, but as mail to the
maintainer bounced, that new deadline was not needed as the reverse
dependencies got archived for themselves as they are unmaintained.
Given that CRAN is closing for the winter soon, I would like to fix this issue
quickly. I have already resubmitted geomander this morning, as I had originally
planned. However, as the packages are archived, each now must undergo a manual
review, which takes more time.
Is it acceptable to submit the other downstream packages while the first is
awaiting manual checks, as long as they are submitted in order of the
dependency tree? As the original package had only a broken example and the
reverse dependencies were actively passing checks, the review should be simple.
Please submit geomander and get it accepted first. The others will be
auto-archived otherwise.
Best,
Uwe Ligges
I would appreciate any advice or wisdom on how to reupload them expeditiously.
Best,
Chris
christophertkenny.com - [email protected]
Christopher T. Kenny, PhD
Postdoctoral Research Associate, Data-Driven Social Science, Princeton
University
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
