similar to: Docker build issue

I continue to receive an error installing R via dockerfile on a buster image python:3. E: The value 'buster-cran40' is invalid for APT::Default-Release as such a release is not available in the sources My starting point is the debian buster based Python:3 image adding a couple of python specific configurations and then using the commands in the R project documentation for installing R on

My dockerfile: FROM python:3 WORKDIR /usr/src/app COPY requirements.txt ./ COPY languageserver-master ./ COPY radian-master ./ RUN pip3 install --no-cache-dir -r requirements.txt EXPOSE 8080 RUN apt-key adv --keyserver keys.gnupg.net --recv-key 'E19F5F87128899B192B1A2C2AD5F960A256A04AF' RUN echo "deb http://cloud.r-project.org/bin/linux/debian buster-cran40/" >>

I want to build a couple of containers by function instead of replicating even slim images for every single package. My current base image provides an updated debian and python3 image. Dave Lange Kenmore, WA On Wed, Jun 24, 2020 at 3:18 PM Sean Southard <sean.m.southard at gmail.com> wrote: > Dave is there a specific reason you want to install both in one container? > > It is

Am Donnerstag, 25. Juni 2020, 04:52:37 CEST schrieb Dave Lange: > My dockerfile: > ... > RUN apt update \ > && apt-get install -y --no-install-recommends \ > ca-certificates \ > wget \ > && rm -rf /var/lib/apt/lists/* Any reason why you remove the contents of /var/lib/apt/lists? On my system, this directory holds PGP signed information about each

On 24 June 2020 at 15:15, Dave Lange wrote: | I continue to receive an error installing R via dockerfile on a buster | image python:3. | E: The value 'buster-cran40' is invalid for APT::Default-Release as such a | release is not available in the sources Do you have the Dockerfile in public repo we can look at? | My starting point is the debian buster based Python:3 image adding a couple

Hi Dave and Dirk, sorry, I do not understand half of this, as I do not use docker myself. Buf if Dirk does not use Debian buster as the basis for his Rocker container, then you should probably not try to install the backport to buster. Shouldn't these docker containers be there to avoid the need to install R? Johannes Am Montag, 22. Juni 2020, 19:15:56 CEST schrieb Dirk Eddelbuettel:

On 5 June 2020 at 08:52, Johannes Ranke wrote: | Hi Mark, | | Am Freitag, 5. Juni 2020, 00:31:34 CEST schrieb Mark van der Loo: | > Hi all, | > | > I just spun up a fresh Debian Buster instance, then I added: | > | > deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ | > | > to /etc/apt/sources.list. I also ran the apt-key command as described here: | >

Hi all, I just spun up a fresh Debian Buster instance, then I added: deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ to /etc/apt/sources.list. I also ran the apt-key command as described here: https://cran.r-project.org/bin/linux/debian/#secure-apt So far so good, now when I do the following, I get no joy: $ sudo apt-get install r-base Reading package lists... Done Building

Hello, I have tried to upgrade R to 4.0. I have added `deb http://cloud.r-project.org/bin/linux/debian buster-cran40/` to `/etc/apt/sources.list` (but I removed cran35). Btu when I run `apt-get update; apt-get install r-base r-base-dev` I get an error. I think it depends on r-base-core, since it depends on these obsolete libraries: ``` $ sudo apt-get install r-base-core Reading package lists...

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

Dear list, I've drafted an article on installing geographic R packages on Linux computers and would appreciate any feedback. Is the following text correct, useful and future-proof?: R?s spatial packages can be installed from source on recent (since Ubuntu 19.04) versions of this popular operating system, once the appropriate repository has been set-up, meaning faster install times (only a

Hi friends, R-gh's latest version grew a dependency on httr2 (which has a suggests for %check on docopt), so I made two new packages for Fedora. They're both noarch and simple, should be quick reviews for someone. Any help here is appreciated. R-docopt: https://bugzilla.redhat.com/show_bug.cgi?id=2176170 R-httr2: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2176171 Thanks in

I just upgraded from Linux Mint 20 to 21 and am no longer able to add the CRAN Ubuntu repository to my list of repositories. ?I am getting: $> sudo /usr/bin/add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" $> sudo apt update Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy

Thanks! ?"jammy" made it work. ? For some reason, ?lsb_release -cs is returning "victoria" rather than "jammy", and $> sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:2 http://packages.linuxmint.com victoria InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Hit:4 http://packages.linuxmint.com victoria

Am Freitag, 5. Juni 2020, 20:04:48 CEST schrieb Dirk Eddelbuettel: > On 5 June 2020 at 08:52, Johannes Ranke wrote: > | Hi Mark, > | > | Am Freitag, 5. Juni 2020, 00:31:34 CEST schrieb Mark van der Loo: > | > Hi all, > | > > | > I just spun up a fresh Debian Buster instance, then I added: > | > > | > deb http://cloud.r-project.org/bin/linux/debian

I've hit a bug on Ubuntu 20.04. The issue occurred both with the R version that shipped with Ubuntu last week, and it is occurring now with the CRAN packages from one of the mirros (deb http://cran.mirror.garr.it/mirrors/CRAN/bin/linux/ubuntu/ focal-cran40/). The issue occurs whether I use the deb package for viridis in the Ubuntu repos, or I install it with `install.packages()` in R.

Over a week ago (on r-help, my bad!) I raised a question of why the ubuntu install instructions https://cran.r-project.org/bin/linux/ubuntu/README.html instruct users with a xenial-based system to use deb https://cloud.r-project.org/bin/linux/ubuntu xenial-cran40/ Looking at https://cloud.r-project.org/bin/linux/ubuntu/ there is no xenial-cran40 directory. However,

On Mon, 04 Dec 2023 13:41:47 -0500 Steve Gutreuter <sgutreuter at gmail.com> wrote: > $> sudo /usr/bin/add-apt-repository "deb > https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release > -cs)-cran40/" Looks like `lsb_release -cs` returns a Mint codename for you. Thankfully, since we know that Linux Mint 21 is based on Ubuntu 22.04 "Jammy Jellyfish", it

On 22 June 2020 at 19:37, Johannes Ranke wrote: | sorry, I do not understand half of this, as I do not use docker myself. Buf if | Dirk does not use Debian buster as the basis for his Rocker container, then | you should probably not try to install the backport to buster. Shouldn't these | docker containers be there to avoid the need to install R? That is what they do, and do well! After I