False negatives due to timestamps in CRAN checks

[lionel-]

Comparing against CRAN checks causes false failures because they include timestamps:

[[1]]
── R CMD check comparison ───────────────────────────── HyperbolicDist 0.6-2 / 0.6-2 ────
Status: BROKEN

── Fixed

✔ checking R code for possible problems ... [21s/24s] NOTE

── Newly failing

✖ checking R code for possible problems ... NOTE


[[2]]
── R CMD check comparison ───────────────────────────────── GlobalDeviance 0.4 / 0.4 ────
Status: BROKEN

── Fixed

✔ checking R code for possible problems ... [6s/8s] NOTE

── Still failing

✖ checking DESCRIPTION meta-information ... NOTE

── Newly failing

✖ checking R code for possible problems ... NOTE

Perhaps these could be safely stripped with a simple regexp?

[gaborcsardi]

Yeah, or we could have an option to not include them at all. I am actually surprised that they are included.

[lionel-]

This seems to solve it: b5f1fbd

[gaborcsardi]

Right, we should probably remove it from the local checks as well, in case they are requested via an option.