Dashboard: ignore too old CRAN incoming submissions

[HenrikBengtsson]

Some packages have been submitted to CRAN and ended up in the 'archive' folder. Later, they were archived on CRAN.

When this happens - archival date is after submission date - the package should not be listed as 'resubmitted'.

[llrs]

I am not sure I follow this issue. In principle the archival date must always be after the submission date or at most from the same day.

Do you mean the package is submitted but not accepted but even so it end up in the archive? Or that the submission is so late after the archival that it doesn't make sense to label it as resubmitted?

[HenrikBengtsson]

'rglwidget' might be an example of this. It was submitted on 2024-03-07 sits in cran incoming archive. It was archived on the same date. It could very well be that they submitted the package, got a rejection, and said "that's it, please just archive it"

[llrs]

Hi, checking again, I see that PACKAGES.in has a field for this package: Replaced_by: rgl.
Maybe the author decided to add the functionality to rgl.
I think those that have "Replaced_by" could be omitted from the dashboard too (there are currently 119 cases).
Seems more used recently but I found it in use since 2012

[HenrikBengtsson]

I think those that have "Replaced_by" could be omitted from the dashboard too

I don't we should any omit packages that are archived. Whenever there's a package archived on CRAN, we want the user to be able to go there and see why that happened (within our current 35-day limit(*)). Instead, I think we should present this information, hence feature request #15.

FYI, this is issue was created because I though, and I could be wrong, that there might be stray packages sitting in the CRAN incoming folders that CRAN forgot to remove. In this particular case (rglwidget), it looks like CRAN has since removed the entry; https://nx10.github.io/cransubs/pkg#rglwidget says "Package does not exist (anymore?)".

(*) We could eventually have another "all-time" table that shows all CRAN events that ever happened, but let's not worry about that now; the main objective for CRANhaven is to provide a grace period for archived CRAN package, and the second is to convey useful information about that.