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

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

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

I managed to workaround this issue by addding "[arch=amd64]" to my apt source list for gluster like this: deb [arch=amd64] http://download.gluster.org/pub/gluster/glusterfs/3.8/3.8.14/Debian/jessie/apt jessie main In case that can help any others with the same siutation (where they also have i386 arch enabled on the computer). > -------- Original Message -------- > Subject:

What would the fix be exactly? The apt repos are built the same way they've been built for the last 3+ years and you're the first person to trip over whatever it is you're tripping over. And there have never been packages for i386 for Debian. ----- Original Message ----- > From: "mabi" <mabi at protonmail.ch> > To: "Gluster Users" <gluster-users

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

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

Hi, I have some problems of segfault at doveconf: Jul 2 08:13:16 mail kernel: [1415540.297823] doveconf[7103]: segfault at 560cb801e000 ip 00007f861da742d0 sp 00007ffe2d671548 error 6 in libc-2.23.so[7f861d9e5000+1c0000] Jul 2 15:45:38 mail kernel: [1442682.919193] doveconf[11915]: segfault at 563b32420000 ip 00007fcb127ae2d0 sp 00007ffecfc7b598 error 6 in libc-2.23.so[7fcb1271f000+1c0000]

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,

Is there a reason for jessie-cran3 rather than xenial? For Linux Mint 18 (admittedly not 18.1) I have deb https://cloud.r-project.org/bin/linux/ubuntu xenial/ as one of the apt entries. JN On 2017-04-27 02:57 PM, Clive Nicholas wrote: > 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