Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using renv on Arch Linux since 1.1.2 (sysreqs check) #2107

Open
mark-andrews opened this issue Mar 6, 2025 · 3 comments
Open

using renv on Arch Linux since 1.1.2 (sysreqs check) #2107

mark-andrews opened this issue Mar 6, 2025 · 3 comments

Comments

@mark-andrews
Copy link

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')
The following package(s) will be installed:
- stringi [1.8.4]
These packages will be installed into "~/tmp/foo/renv/library/linux-arch-rolling/R-4.4/x86_64-pc-linux-gnu".

Do you want to proceed? [Y/n]: Y

Error in case(nzchar(Sys.which("dpkg")) ~ "deb", nzchar(Sys.which("rpm")) ~  : 
  don't know how to check sysreqs on this system
Traceback (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't know how to check sysreqs on this system"))
1: stop("don't know how to check sysreqs on this system")

And

> renv::sysreqs()
Finding R package dependencies ... Done!
Error in 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?

@kevinushey
Copy link
Collaborator

Sorry, this was an oversight -- you can set that option as a workaround, but it shouldn't be necessary. I'll get this fixed up.

@mr-valente
Copy link

mr-valente commented Mar 10, 2025

Experiencing the same issue! Will use the workaround @mark-andrews suggested until a fix is released.

EDIT: The workaround does not work for me, unfortunately. Thought I had it working for a second, but then it failed again.

@ginolhac
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants