Edge case: conflicts with CRAN

[wlandau]

Right now, we have an edge case where crew is failing in Staging because it is trying to build against mirai 2.1.0 on CRAN instead of mirai 2.0.0 in Staging. We would expect Staging packages to be built against other Staging packages, but instead install.packages() just chooses the higher version.

@shikokuchuo, @jeroen, and I discussed. One proposal is:

1. For checks in Staging, freeze CRAN as well as Staging. Use the p3m snapshot from the day the freeze starts (c.f. https://r-multiverse.org/production.html#schedule).
2. Manually intervene to always prefer Staging when there are conflicts with CRAN.

[shikokuchuo]

We just need (1) I think. As the highest version number wins and it doesn't matter whether that's on staging or CRAN (at the freeze date).

[wlandau]

True. So then can we create a issue when the CRAN version of a package is later than the Staging one?

[shikokuchuo]

That would seem to be justified. If it happens, it's likely that it's been overlooked and the reminder would be welcome.

[wlandau]

Sounds good. BTW I realized this relies on (1). Otherwise, submitting to CRAN would be a backdoor to override the Staging freeze.

[wlandau]

Otherwise, submitting to CRAN would be a backdoor to override the Staging freeze.

Never mind,multiverse.internals can just check the p3m snapshot from the most recent staging freeze. Probably should do the same with Bioconductor.

[wlandau]

PR at r-multiverse/multiverse.internals#56

[jeroen]

OK I added an issue for myself here: r-universe-org/help#562

[jeroen]

Added support for a config.json with a cran_version date which I set to 2025-01-15 for now: https://github.com/r-multiverse/staging/blob/main/config.json

One caveat is that using p3m snapshots rules out building and checking on r-devel, because p3m only supports r-release and 4 older versions, but not r-devel. But I think that this is not an issue for us, as our production snapshot targets r-release anyway.

[wlandau]

Added support for a config.json with a cran_version date which I set to 2025-01-15 for now: https://github.com/r-multiverse/staging/blob/main/config.json

Thanks! Added Staging config.json support to r-multiverse/multiverse.internals#56.

One caveat is that using p3m snapshots rules out building and checking on r-devel, because p3m only supports r-release and 4 older versions, but not r-devel. But I think that this is not an issue for us, as our production snapshot targets r-release anyway.

R-multiverse sticks to R-release for Mac and windows, but it enforces R-devel on Linux. Will that be an issue?

[wlandau]

We could switch to R-release for Linux, but last time I checked R-universe didn't build that.

[jeroen]

This is mostly about the Windows/Mac binaries, so Linux is not an issue.

[wlandau]

Great! Then we should be good. We can check on things after r-multiverse/multiverse.internals#56 is merged. Everything should be set up, just wanted to check with @shikokuchuo first on that one.