similar to: Unable to add the CRAN apt repository

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

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

Hi All, I am building a Docker image that uses Ubuntu 22.04 and am having issues installing the latest version of R (R 4.4.1). The current R version is 4.1.2: :/# apt-cache policy r-base-core r-base-core: Installed: 4.1.2-1ubuntu2 Candidate: 4.1.2-1ubuntu2 Version table: *** 4.1.2-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100

Lauren, here?s my Dockerfile I use to build r-base from the repos, it builds on both Arm64 (Mac with Apple M2 chip) and Amd64 (AWS m5.4xlarge instance running Ubuntu 24.04). I rebuilt the docker image this morning and it builds fine with R 4.4.1 The last RUN is for installing a bit of custom configuration as well as the base of Bio Conductor. Hope this helps (I also have a Dockerfile for

Hi Marco, Thank you for the follow up email. In the line below, do I replace $(lsb-release -cs) with jammy (Ubuntu 22.04) or leave it alone: Add-apt-repository ?deb https://cloud.r-project.org/bin/linux/ubuntu jammy-cran40/? It?s good to know about installations for Bioconductor. I am not currently using it, but I may need it in the future for other projects. Br, Lauren -- Lauren J. Gerber

Yes, keep the $(lsb-release -cs) there. This allows you to change the version of the OS without having to change anything else (for instance we are migrating all of our docker to 24.04 LTS right now, so we only have to modify the FROM entry and all of our Dockerfile will still work). From: Gerber, Lauren J <lauren.gerber at helsinki.fi> Date: Thursday, July 11, 2024 at 2:21?AM To:

Lauren, little oversight from my Dockerfile, if you want to follow the CRAN steps and get the R from the cloud.r-project.org server, you want to replace && add-apt-repository -y "ppa:marutter/rrutter4.0" With && add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" The ppa repo is Michael Rutter personal repo

Hi Dirk, Thank you so much for looking into this when you got home. I greatly appreciate it. I was actually in the midst of writing to everyone the following message: ?. ?. ?. Hi All, I have some good news. ? My docker image is now up-to-date with R version 4.4.1. I first had to clear a bunch of unused data using docker system prune ?force. Apparently, it cleared over 32.53 gigs of data, and

Hello, When doing "apt-get update" on Debian Stretch, I am experimenting the following error: # apt-get update Ign:1 http://ftp.fr.debian.org/debian stretch InRelease Ign:2 http://apt.van-belle.nl/debian stretch-backports InRelease Hit:3 http://security.debian.org/debian-security stretch/updates InRelease Hit:4 http://ftp.fr.debian.org/debian stretch-updates InRelease Hit:5

Lauren, I am now back home where looking into these things is a little easier. From your first email to me, I started off with the selenium container you mentioned as your starting point. And that basically is your issue. It is a 'high-level' container, and it sets a user. (Essentially) all other Dockerfiles you have seen and been pointed at are 'lower-level' and operate as root

When I follow the directions at http://docs.gluster.org/en/latest/Install-Guide/Install/ to install the latest gluster on a debian 9 docker container, I get the following error: Step 6/15 : RUN echo deb [arch=amd64] https://download.gluster.org/pub/gluster/glusterfs/3.13/9/Debian/stretch/amd64/apt/ stretch main > /etc/apt/sources.list.d/gluster.list ---> Running in 1ef386afb192 Removing

On 03/06/2018 05:50 PM, Paul Anderson wrote: > When I follow the directions at > http://docs.gluster.org/en/latest/Install-Guide/Install/ to install > the latest gluster on a debian 9 docker container, I get the following > error: Files in the .../3.13/3.13.2 directory had the wrong owner/group, (rsync_aide). I'm not sure why, maybe an incomplete rsync? I've fixed the owners

Okay folks, I give up and - frankly - I'm fed up! I thought I'd sorted all this last week, but clearly not. I've tried using mirrors from here in the UK, Ireland, France and the USA and whichever mirror I use, all I get is this: clive at climate ~ $ sudo apt-get update Hit:1 http://ubuntu.mirrors.uk2.net/ubuntu xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable

Hi, I apologise for the naiveness of this question, but I experienced an error when running apt-get update on Debian 9. It’s telling me that it can’t update the xiph repository. Not sure if I should be asking for help about this here, but if not… please let me know where I should take this issue. Any help is appreciated. Damian Get:1 http://security.debian.org/debian-security stretch/updates

Still something wrong. I've uncommented the deb-src lines in sources.list as you suggested (and I thought it couldn't hurt to try --allow-unauthenticated as well) and: root at limpet:/etc/apt# apt-get update --allow-unauthenticated Hit:1 http://nz.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://repo.steampowered.com/steam precise InRelease Hit:3

Dear Robin and Tomas, By changing the CC, I'm hereby trying to move this to R-SIG-Debian (Ubuntu a flavor of Debian) where it belongs ... Martin >>>>> robin hankin >>>>> on Fri, 1 Mar 2019 21:43:07 +1300 writes: > Still something wrong. I've uncommented the deb-src lines in > sources.list as you suggested (and I thought it

*Thank you Louis. That solves my problem. Have a good week-end. -- L?a * * * *L.P.H. van Belle* belle at bazuin.nl <mailto:samba%40lists.samba.org?Subject=Re%3A%20%5BSamba%5D%20Debian%20Stretch%20-%20apt-get%20update%20-%20Van%20Belle%20repository%0A%20not%20found&In-Reply-To=%3Cvmime.5dde8374.74b7.683da6252766c723%40ms249-lin-003.rotterdam.bazuin.nl%3E> /Wed Nov 27 14:08:52 UTC 2019/

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

Still doesn't work: a at a-VirtualBox:~$ sudo add-apt-repository 'deb http://llvm.org/apt/trusty/ llvm-toolchain-trusty-3.8 main' a at a-VirtualBox:~$ sudo apt-get update Ign http://ppa.launchpad.net trusty InRelease Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB] Ign http://ie.archive.ubuntu.com trusty InRelease Hit http://ppa.launchpad.net trusty Release.gpg

Hello, I want to upgrade from 3.8.11 to 3.8.14 on my Debian 8 (jessie) servers but it looks like the official GlusterFS apt repository has a mistake as you can see here: Get:14 http://download.gluster.org jessie InRelease [2'083 B] Get:15 http://download.gluster.org jessie/main amd64 Packages [1'602 B] Fetched 23.7 kB in 2s (10.6 kB/s) W: Failed to fetch