Deep link to CRAN checks: non-predictable URL

[HenrikBengtsson]

For example, raybevel was archived on:

Archived on 2024-03-10 as issues were not corrected in time.

but the check link on https://cran.r-project.org/web/packages/raybevel/index.html is for a different date:

https://cran-archive.r-project.org/web/checks/2024/2024-03-12_check_results_raybevel.html

This means, in order to find the check URL, we most likely need to parse the content of https://cran.r-project.org/web/packages/raybevel/index.html.

If we implement #7, this only has to be done once per package.

The archive of CRAN checks can be found under https://cran-archive.r-project.org/web/checks/

[HenrikBengtsson]

Alternatively it's vice versa, i.e. they typed the wrong date in X-CRAN-Comment. According to CRANberries, which diffs available.packages(), it was removed 2024-03-12. Also, if we look at https://cran.r-project.org/src/contrib/PACKAGES.in, we see that 'raybevel' comes on top despite following events have a later date.

Package: raybevel
X-CRAN-Comment: Archived on 2024-03-10 as issues were not corrected in time.

Package: docxtools
X-CRAN-Comment: Archived on 2024-03-11 at the maintainer's request.

Package: bsitar
X-CRAN-Comment: Archived on 2024-03-10 as issues were not corrected in time.

Package: konya
X-CRAN-Comment: Archived on 2024-03-10 for policy violation.
  .
  On Internet access.
...

[HenrikBengtsson]

Yeah, it was a typo that they now fixed;

Package: raybevel
X-CRAN-Comment: Archived on 2024-03-12 as issues were not corrected in time.

So, this reveals that at least the date information is manually entered.

[llrs]

I like they fix this but I am worried this is not somewhat automated.
I thought they would have a function that archives a packages and creates the message in the file...

(Noted for future suggestions/opportunities to collaborate with CRAN maintainers)