-
Notifications
You must be signed in to change notification settings - Fork 26
Description
rig
commands return errors with pop_os
distribution. My Linux distribution information:
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
rig add release
and rig available
return errors, and rig list
returns nothing.
~$ rig add release
[INFO] Running `sudo` for adding new R versions. This might need your password.
[ERROR] Failed to resolve R version: Cannot download JSON: HTTP status client error (404 Not Found) for url (https://api.r-hub.io/rversions/resolve/release/linux-pop-22.04/x86_64)
~$ rig available
[ERROR] Cannot download JSON: HTTP status client error (404 Not Found) for url (https://api.r-hub.io/rversions/available/linux-pop-22.04/x86_64)
After setting environmental variable RIG_PLATFORM
to 'ubuntu-22.04', rig list
returns expected installations, but rig add release
returns the above errors unless unless prepended with sudo -E add release
(per this issue). sudo -E add release
succeeds up until the install pak
step (error below), unless --without-pak
is added (in which case the command runs successfully).
[INFO] Installing pak for R 4.2.3 (if not installed yet)
[ERROR] Failed to to install pak for R 4.2.3: command ["su", "username", "-s", "/bin/bash", "--", "/opt/R/4.2.3/bin/R", "-s", "--vanilla", "-e", "invisible()"] exited with code 1
I tried using rig because I was having issues with R after I tried to update it, and after I tried to uninstall/reinstall R normally to resolve those issues--where R exits immediately upon startup, and RStudio fails to recognize that R is installed--and it seems like I'm running into the same issue with rig
(although this might be something specific to whatever I did to mess up updating R previously/not an issue with rig).
~$ rig run
~$