Closed alanocallaghan closed 1 year ago
Sure. It's an apt repo. So you must remove the listing.
Sorry you were unable to debug. Nobody is helped by that.
We explain what r2u: an apt-accessible repository to provide you with binaries in .deb
form for use by Ubuntu 20.04 and 22.04 installations using their system tools.
We explain that one can optionally use bspm
to access these facilities from R via install.packages()
.
That's really all that there is. We don't say or promise more. If you have concrete proposal to improve documentation we are all ears. We do this as volunteers, along with a number of other activities around open source. So are resources are finite, and this may not be for anybody. Driving by and asking 'yo would be good to have docs' doesn't make it so either.
Hi,
First of all, thank you :)
I set up r2u a while ago on my local laptop and haven't used it much because I was working on a remote server a lot.
Now installing some packages does not work and the output is not the same as normally with install.packages
. This gives me a hard time debugging. I wanted to remove r2u completely to see where I might have gone into a wrong direction, but following the steps above or the setup steps (backwards and removing instead of adding) does not help.
I am not too familiar with apt and system installations, so in this case some simple instructions on how to revert R to use the old way of installing would be great.
Best,
Quirin
@quirinmanz Fundamentally there are two aspects, and they interplay:
apt
knows, this is commonly done via a file added to the /etc/apt/sources.list.d/
directory. All you need to do is to remove (or renamed from default ending in `*.list``) the filebspm
package is installed and by default enabled via a line in /etc/R/Profile.site
. Just remove, or comment-out, that line.It would still be beneficial to debug what failed to work on your end. Sadly with "installing some packages does not work" is not enough information to go by.
@eddelbuettel, it looks like I did actually miss /etc/R/Profile.site
when going through the setup. I might have done something wrong with the RHOME.
Thanks for your help!
Anytime. In essence removal just amounts to looking at the four (or five, depending how you count) steps detailed in the README (and the corresponding setup shell script for a given Ubuntu release) and undoing each of them.
This took a while but I finally added a new question to the FAQ: https://eddelbuettel.github.io/r2u/vignettes/FAQ/#why-can-i-not-uninstall-packages-with-removepackages
It had been covered under 'known issue' in the main README and hence top-level of the documentation though.
Hey, this works well generally, but I ran into some problems on a laptop that I couldn't really be bothered debugging. I think I got through the removal process semi-okay by trial and error but it would be good to have some explicit ones.
The steps I followed were:
remove.packages("bspm")
or the system packager-cran-bspm
bspm::enable()
from yourRprofile.site
rm /etc/apt/sources.list.d/cran_apt.list