search for: _upgrade_

In the past I have been told, very firmly, by those who are knowledgeable that when upgrading R I should install the binary R provided for the Ubuntu OS. Being a docile and biddable young ( :-) ) fellow, I have tried to do so, following the instructions made available at: https://cran.r-project.org/bin/linux/ubuntu/README.html I have made sure that the line deb

...er). However, R enforces wrong permissions on directories and files there (removing group-write) which effectively defeats this purpose, and breaks multiuser installation: if Tom, Dick and Harry are members of group 'r-users', each one can install in the directory, but neither can _upgrade_ a package installed by one of the others. I would like to correct this. Details: For a while now, R CMD INSTALL dispatches installation work to the R function tools:::.install_packages() from the file tools/install.R. The function does a lot of hardcoded 'chmod' with cons...

...deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ > | > | is present in my /etc/apt/sources.list file and I then do: > | > | sudo apt-get update > | > | (which seems to go OK) and then: > | > | sudo apt-get install r-base > > If you want is to _upgrade_ already installed packages use > > sudo apt-get dist-upgrade > > instead. There is no apt sub-command to upgrade just one. > > The point with packages is that they may have further dependencies; the > strength of this tool is to resolve that graph for you. And I have...

Before you read this, I want to state (for reasons listed below) that I don't expect an answer (advice is welcomed, but please read this email carefully before answering). I'm sharing this with the community with the hope that better software results from our sad experience... BACKGROUND I've been using NT for 4 years, Netware and Linux for 3 years, and Samba for almost 2. I work