similar to: Unable to install R 3.1.2 on Debian:Testing

Dear Carl, the CRAN repository does not support Debian testing. I did think of adding support for jessie, as it is frozen now, but did not get around to do it yet. I believe you would have no problem when using Debian stable. Am Freitag, 16. Januar 2015, 21:44:25 schrieb Carl Boettiger: > Dear Johannes, R-sig-debian list, > > Along with Dirk Eddelbuettel I've been maintaining

Thanks Johannes to clarify this point. It makes more sense to me now. So I understand that the idea is to make it simpler without apt-pinning for less adventurous people (I mean normal people :)): just add jessie-cran3 repo and you're good to go. Am I also correct that jessie-cran3 is essentially a backport of Debian SID, with some (short?) delay? In other words, modulo a couple of days,

Dear Johannes, Thanks a lot for this work! I have to admit that I'm now a little bit puzzled, though. I'm running Debian Jessie (current testing) with great satisfaction. When it comes to R, I simply have the SID repository (official Debian) enabled, with some pining to get only R-related stuff. Now, I'm not sure to understand the benefit of using the CRAN repository for Jessie?I

Yes, but beware that I only do backports of the packages listed in the Debian README on CRAN. Kind regards, Johannes Am Donnerstag, 26. Februar 2015, 10:06:08 schrieb Mathieu Basille: > Thanks Johannes to clarify this point. It makes more sense to me now. So I > understand that the idea is to make it simpler without apt-pinning for less > adventurous people (I mean normal people :)):

Dear Mathieu, dear list, if you have successfully set up apt pinning for R packages, then you have the most up-to date Debian packages for R at your fingertips. I set up the repository for Debian jessie so people do not have to use apt pinning in order to get Debian 3.1.2 on jessie. Plus, when jessie is released, the repository is already there, and after the release of jessie it is likely

Hi Johannes, On 18 January 2015 at 20:47, Johannes Ranke wrote: | At the moment you are on your own with R 3.1.2 on jessie. The easiest safe bet in my opinion | would be to install from the Debian sources in unstable, i.e. add a deb-src entry for unstable | to your sources.list, do an apt-get build-dep r-base and then apt-get source --build r-base | and install the packages with dpkg. Ok. I

Le 18/01/2015 15:55, Dirk Eddelbuettel a ?crit : > > On 18 January 2015 at 14:14, Dirk Eddelbuettel wrote: > | Ok. I will set up a new toolchain for testing then. We need this for Rocker > | all the time---eg I just put something marvelous into littler which I need in > | Rocker, yet Debian is frozen with no timeline for release. And it is silly > | for us to keep rebuilding all

> | Is there a way to overcome this problem? Precompiled versions of R can be installed on various system configurations, so I guess that there should be a way to compile it in a version-agnostic manner. > > Yes, for example by > > -- using a Docker container which is portable across OSs (!!) and versions Docker R containers are north of 250 MB. I have checked experimentally

Dear Hartyun Khachatryan, thanks for your report. It seems not a lot of people are using the backport to squeeze, as I have forgot to update the package index after doing the backport for R 3.2.2 and nobody (including me) noticed... The updated index is on its way to the CRAN mirrors, it will take some time to be synchronised, so please try again tomorrow. Johannes Am Mittwoch, 16.

Dear all, I having a trouble installing R on debian 6 squeeze. Apt can not find some packages on repository. It seems like that some packages missed. Can you please help me with this? Thank you in advance. Harutyun khachatryan. P.S. It writing something like this. It doesn't depends on CRAN mirror. I have tried a lot of different CRAN mirrors with the same result. Err

On 7 September 2016 at 20:50, Pawe? Pi?tkowski wrote: | > | Is there a way to overcome this problem? Precompiled versions of R can be installed on various system configurations, so I guess that there should be a way to compile it in a version-agnostic manner. | > | > Yes, for example by | > | > -- using a Docker container which is portable across OSs (!!) and versions | |

> otherwise I will only have time in the weekend to do something (amend the > README or set up a new repo for jessie) on the weekend. The repository for jessie is in the works - but don't expect it to be up before next weekend. Johannes

Hi: I have a Dockerfile, which builds an image which installed R 3.3.2 in Ubuntu 14.04, but building using that Dockerfile seems to have stopped working and I am unclear why. I believe the relevant error is: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its

I am getting the following error when trying to update packages for jessie-cran3/ W: GPG error: http://cloud.r-project.org/bin/linux/debian jessie-cran3/ Release: The following signatures were invalid: 6212B7B7931C4BB16280BA1306F90DE5381BA480 E: The repository 'http://cloud.r-project.org/bin/linux/debian jessie-cran3/ Release' is not signed. N: Updating from such a repository

Hello! I'm trying to install R-3.0.1 on an Ubuntu machine (64 bit, version 13.04). I have uninstalled and installed several times, but to no avail. I keep getting errors about missing ldpaths, and installing packages does not work at all. Here is the information: erin@erin-Lenovo-IdeaPad-Y480:~$ sudo apt-get install r-base Reading package lists... Done Building dependency tree Reading

Thank you so much Johannes. Problem now sorted: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E084DAB9 sudo add-apt-repository deb https://cran.ma.imperial.ac.uk/bin/linux/ubuntu xenial/ # replaced the old repository link sudo apt-get update sudo apt-get install r-base r-base-core r-base-dev With my .Renviron file already fixed from previously with the correct paths inserted, my

On 04/29/2018 09:30 AM, Jeroen Ooms wrote: > On Sat, Apr 28, 2018 at 10:00 PM, Michael Rutter <marutter at gmail.com> wrote: >> These have not been mirrored to CRAN as I want to have the other r-cran >> packages built against R 3.5 before adding to CRAN. Worried about breaking >> working systems currently on R 3.4.4. > > Thanks, Michael. I did some simple tests,

CRAN has a package of mine in upload limbo because it failed UBSAN. I am not entirely ignorant on the topic of sanitizers and SAN / ASAN / UBSAN; we created not one but two Docker containers with ASAN and USBAN: https://registry.hub.docker.com/u/rocker/r-devel-san/ https://registry.hub.docker.com/u/rocker/r-devel-ubsan-clang/ as well as predecessors to them in earlier Docker repos. Yet I

Hi, $ more /etc/apt/sources.list.d/additional-repositories.list deb http://www.stats.bris.ac.uk/R/bin/linux/debian wheezy-cran3/ deb-src http://www.stats.bris.ac.uk/R/bin/linux/debian wheezy-cran3/ $ sudo apt-get update $ sudo apt-get install r-cran-rgl # works great $ sudo apt-get build-dep r-cran-rgl Reading package lists... Done Building dependency tree Reading state information...