Some packages need updated version of R (3.2). But sometimes you need a R dependent software which needs former versions (flexarray: R version 2.15). I have both versions installed but the latest installed version is recognized as default. Then I should reinstall R.2.15 for flexarray. Do you have any recommendation to stop reinatallations? Thanks
Related
When we ssh onto this Linux server, it says Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.4.0-193-generic x86_64), so this is the type of server we are on.
When we run R to launch R in the server from terminal, and then version, we get:
What is the easiest way to upgrade from version 3.4.4 to version 3.5.3? We don't want to upgrade to v4 or to the latest version quite yet until we ensure no breaking issues with our codebase on R v4, however we would like to make this upgrade to 3.5.3 so we can run an R library that requires 3.5.3+.
How can we do this from the command line on the server here, and after switching from 3.4.4 to 3.5.3 do we then need to re-install all R libraries on the server as well? I'm worried if I start running stuff from the command line and I mess up that I'll break our current R app.
I would be surprised if there is a .deb available for this OS release/R release combination.
This page only offers R 4.1, but as far back as 16.04 LTS
This page offers older R versions, but only back to 18.04 LTS
It's also possible that one of the backports on the Debian packages page would work on your system (it reports that 3.5.3 is available for Debian "jessie", although I have no idea how that lines up with Ubuntu releases).
I guess it's possible that one of those .debs works for your system though ... ? If you do install from .deb, you may have to be careful not to clobber your current version (e.g. using the --instdir argument to dpkg).
Building from source:
download the source tarball for R 3.5.3
untar, ./configure, make, sudo make install (assuming you have all the necessary development tools, system libraries, etc.; you'll have to troubleshoot/install as you go along)
It might be worth ./configure --prefix=/path/to/testdir to put the new version in a completely separate location, just to make extra-sure you don't stomp on your current install. (This would also simplify the library-path stuff below.)
Packages do need to be re-installed when switching major versions (e.g. 3.4.x to 3.5.x); one way to do it is to copy the system library of packages to a new place (adjust library paths as necessary; see R installation and administration manual).
Then, you should be able to update.packages(checkBuilt=TRUE, ask=FALSE) to update everything.
The tricky spots are (1) getting the library paths right (this will depend a bit on how things are set up in your existing installation; (2) it's conceivable that some current versions of packages on CRAN will fail to re-install/re-build under R 3.5.3. devtools::install_version() would help, although you'd have to track down the correct version manually. I recall someone posting about a package that would install an archived version by date, which could save a lot of poking around ...
If you look at the grf package here, you will notice that it has three versions:
It seems that r-devel is the developing version, r-release is the released version and r-olderel is the older version. However, what is weird is that they share the exact same version number 0.10.2. Why don't they change the version number if the versions are different?
Because it's the same version. What that is telling you is that for grf which version is the most up to date if you're using r-devel, or r-release, or r-oldrel. In some cases the versions can be different. For instance if a package just updated and now requires the latest and greatest version of R then the version that shows up in r-oldrel will reflect that those running the previous release (i.e. r-oldrel) will need to use the previous version of the package since they won't be able to install the newest version since it requires the newest version of R.
So in short - those aren't codenames for the version of the package you're looking at. They're referring the version of R.
As in R documentation:
The last version known to run on Windows 2000 was 2.12.2. Windows XP is no longer supported.
I tried to install R 3.4.3 on windows xp , but i faced problems when installing packages that i didn't face when installing them on Windows 7 system. I think it is safe to assume that R 2.12.2 runs on Windows xp as windows 2000, but does a version later than R 2.12.2 runs on windows xp also? what is the highest version ?
The latest version officially supported on XP was one version below, 3.4.2. Nevertheless, R as high as 3.6.0 installs and runs well on XP (though is not officially QA tested).
Starting from v.3.6.1, R is packed with InnoSetup v.6.0.0 (that means, installing on WinXP will not succeed and end up with an error "not valid Win32 application"). However, one may try to unpack the installer and deploy the files manually (still may help to launch R itself). Another option which may be useful is One Core API.
But... All this stuff is relevant if one is going to use plain R or integrated R environment in some old application. Many 3rd-party R packages require the most up-to-date versions of R, what will cause inconveniences on WinXP.
Thought I'd give MRO a spin, to see if it speeds up my usage in general.
I can't find the installed R though. Not as a separate, not as an overwrite.
/usr/local/bin/R contains R version 3.4.0 (2017-04-21) -- "You Stupid Darkness", which is also the one used by RStudio.
/Library/Frameworks/R.framework/Versions/ also only contains 3.4.
The GUI "Microsoft R Open.app" has the description R 3.3.0 GUI 1.68 Mavericks build... but it also returns 3.4.
What am I missing?
You've identified a bug in the installer. Thanks!
Looks like we are not installing the MRO framework files because the package installer is detecting a newer version (CRAN 3.4). We will get this fixed in the next release.
In the meantime, you can work around this by renaming /Library/Frameworks/R.framework/Versions/3.4 to /Library/Frameworks/R.framework/Versions/0.3.4 and reinstalling MRO. Then go ahead and rename it back.
Please note, as a part of the install we update the symlinks to point to our version, so if you would prefer the default R installation to be CRAN 3.4 please do the install in the reverse order or manually update the symlink to Current in the Versions folder.
I'm trying to use R through SPSS syntax (I'm using SPSS 18 on windows 7) which requires installing a special plugin: PASWStatistics_RPlugIn_1802_win32.exe. Also I had to install an older version of R(2.8.1 - required by my older version of SPSS - i like it better than the new ones). The plugin now works, R (both versions) works, but Rstudio stopped working and won't start even after uninstalling and re-installing.
Does anyone have any similar experience and could suggest a solution?
The following link specifies how you can configure Rstudio to work with a specific R version you have installed:
http://www.rstudio.com/ide/docs/advanced/versions_of_r
Just install R 2.8 and 2.14 and let spss use one, and Rstudio another.
You are taking a risk by using old versions of spss and R (bugs that have been fixed in newer versions, decreased performance, possible incompatibility with other software e.g. R packages, missing functionality).
You can have multiple versions of R installed at the same time - I have five. The current version of Statistics, 21, goes with R2.14. I don't know how Rstudio determines which version to use. You might need to reset the R environment variables or your path settings.