Open
Description
Everything was fine until 0.8.0.2, since 0.9.0 we see
> options(Ncpus = 4); renv::restore(); rcmdcheck::rcmdcheck(args = c("--no-manual", "--as-cran"), error_on = "warning")
# Downloading packages -------------------------------------------------------
- Downloading pak from r-lib ... OK [9.6 Mb in 0.44s]
Successfully downloaded 1 package in 0.93 seconds.
The following package(s) will be installed:
- pak [0.9.0]
These packages will be installed into "~/.cache/R/renv/library/vsCustomers-d05005b0/linux-alpine-3.21.3/R-4.4/aarch64-unknown-linux-musl".
# Installing packages --------------------------------------------------------
- Installing pak ... OK [installed binary and cached in 0.62s]
Successfully installed 1 package in 0.92 seconds.
✔ Updated metadata database: 1.38 MB in 1 file.
ℹ Updating metadata database
✔ Updating metadata database ... done
Error:
! error in pak subprocess
Caused by error:
! Could not solve package dependencies:
* hrbrmstr/bom: dependency conflict
* r-lib/rcmdcheck@6125f2097b323154e49220528155969552f5af38: dependency conflict
* [email protected]: dependency conflict
* [email protected]: dependency conflict
* [email protected]: Platform mismatch
* [email protected]: dependency conflict
* [email protected]: dependency conflict
* [email protected]: dependency conflict
* [email protected]: dependency conflict
[...]
Note that because pak is dynamically bootstrapped and used through renv (via renv.config.pak.enabled = TRUE), we can't really control its version here.