similar to: installation problem for R 4.0 on Debian buster

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: | >

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

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: > https://cran.r-project.org/bin/linux/debian/#secure-apt > > So far

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 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

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 Dirk, Thanks for the suggested workarounds. This was just a VM I had spun up so I could test R4.0.0. I'm happy to wait for Michael to fix it when he has time. Greg On Tue, 28 Apr 2020 at 13:10, Dirk Eddelbuettel <edd at debian.org> wrote: > > Hi Greg, > > On 28 April 2020 at 12:05, Greg Siemon wrote: > | I noticed that R 4.0.0 is now available for ubuntu on CRAN. I

I noticed that R 4.0.0 is now available for ubuntu on CRAN. I attempted to do a clean install on 18.04 using: sudo apt install r-base after adding deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran40/ to /etc/apt/sources.list. Unfortunately, apt reports that r-recommend is a dependency and it won't be installed. Upon inspecting the R4.0 repos r-recommend is missing not only for

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.

Count me as a docker newbie building a debian python and R mytools container. My first post. This was working a couple of weeks ago. My last successful build was a R 4.01 release when the R:base docker hub project used to list a number of base images and I used sections of a posted docker file in that area. Then the install directions at Cran:R listed buster:4.01 instructions that I also added to

Hi Dirk, Could there be a typo on https://cloud.r-project.org/bin/linux/ubuntu/README.html? The installation entries mention cran35 for R 4.0. Should that be cran40? Best regards, Thierry ir. Thierry Onkelinx Statisticus / Statistician Vlaamse Overheid / Government of Flanders INSTITUUT VOOR NATUUR- EN BOSONDERZOEK / RESEARCH INSTITUTE FOR NATURE AND FOREST Team Biometrie &

Ok, Run : apt install samba winbind acl Dont worry if it errors out. I m out for a quick run for some food, im back in about 30 min. Louis > -----Oorspronkelijk bericht----- > Van: Lmloge [mailto:lmloge at orange.fr] > Verzonden: vrijdag 20 december 2019 12:11 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] Upgrading from Debian Stretch

On 29 April 2019 at 15:03, Kurt Hornik wrote: | >>>>> Johannes Ranke writes: | | > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: | >> >>>>> Johannes Ranke writes: | >> Thanks. You may have seen that with current gfortran in | >> testing/unstable, there are problems with the R BLAS/LAPACK API entries | >> using a Fortran

Dear all, I whish to relate my installation of R-4.0.0 on Debian. I am mainly a Windows user and occasionnaly verify the CRAN checks of my packages on a second laptop equipped with Linux Mint Debian Edition 3 (LMDE3) based on Debian Stretch. On Friday, April 24, it took me a few hours to have R-4.0.0 installed on Windows and the sources compiled, thanks to the instructions provided by

Kurt, Am Donnerstag, 9. Mai 2019, 16:35:24 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > Johannes, > > It seems that one can avoid the gfortran problems with Fortran > BLAS/LAPACK implementations by compiling with > -fno-optimize-sibling-calls. ... > Yesterday I changed R-devel and R-patched to use > -fno-optimize-sibling-calls for gfortran

>>>>> Dirk Eddelbuettel writes: > On 10 May 2019 at 10:52, Johannes Ranke wrote: > | Thanks, that sounds good. But I need some help as I do not know much about > | autoconf and Debian packaging: Is it enough to patch configure.ac (r76467) or > | do we need to update configure as well (r76468)? > Again, that would happen in the sources you pick up from me, and per

Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > Thanks. You may have seen that with current gfortran in > testing/unstable, there are problems with the R BLAS/LAPACK API entries > using a Fortran interface (and hence in particular when using the BLAS > and LAPACK sources that ship with R). No, I wasn't aware of

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

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

I don't know about the configuration. I installed R using the standard protocol for Chromebook http://blog.sellorm.com/2018/12/20/installing-r-and-rstudio-on-a-chromebook/ the rest, it was done by the system itself... On Tue, Jul 14, 2020 at 1:30 PM Dirk Eddelbuettel <edd at debian.org> wrote: > > > There is something wrong with your system / setup I did not notice first: >