You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating renv to 1.1.2 on Arch Linux, I could no longer use it because the new sysreqs check was failing. For example
>renv::install('stringi')
Thefollowing package(s) willbeinstalled:-stringi [1.8.4]
Thesepackageswillbeinstalledinto"~/tmp/foo/renv/library/linux-arch-rolling/R-4.4/x86_64-pc-linux-gnu".Doyouwanttoproceed? [Y/n]:YErrorin case(nzchar(Sys.which("dpkg")) ~"deb", nzchar(Sys.which("rpm")) ~:don't know how to check sysreqs on this systemTraceback (most recent calls last):4: renv::install("stringi")3: renv_sysreqs_check(sysreqs, prompt = prompt)2: case(nzchar(Sys.which("dpkg")) ~ "deb", nzchar(Sys.which("rpm")) ~ "rpm", ~stop("don'tknowhowtochecksysreqsonthissystem"))1: stop("don't know how to check sysreqs on this system")
And
>renv::sysreqs()
FindingRpackagedependencies...Done!Errorin case(nzchar(Sys.which("dpkg")) ~"deb", nzchar(Sys.which("rpm")) ~:don't know how to check sysreqs on this system
To workaround, I did
options(renv.config.sysreqs.check=FALSE)
and then seemingly everything was fine again.
Is that options setting my only or recommended option for use on Arch Linux?
The text was updated successfully, but these errors were encountered:
@mr-valente{renv} restarts the session so the workaround needs to be applied every single time.
Just got the same and had to do it after each init/activate steps
After updating renv to 1.1.2 on Arch Linux, I could no longer use it because the new sysreqs check was failing. For example
And
To workaround, I did
and then seemingly everything was fine again.
Is that options setting my only or recommended option for use on Arch Linux?
The text was updated successfully, but these errors were encountered: