similar to: Problems with signature Debian testing

I am trying to update R on debian testing and am getting the following error from the package manager. Do I need to change the website link? Is there a new signature for the repository that is compliant? W: GPG error: http://cloud.r-project.org/bin/linux/debian jessie-cran3/ Release: The following signatures were invalid: 6212B7B7931C4BB16280BA1306F90DE5381BA480 E: The repository

On Thu, Apr 2, 2015 at 5:49 AM, Johannes Ranke <jranke at uni-bremen.de> wrote: > Hi Marius, > > thanks for your reply. > >> > So maybe you could modify your instructions to the case where someone >> > wants to have R-devel in addition to the released R version, if that is >> > what you are aiming at? I could then add it to the README for Debian on

On Tue, Mar 31, 2015 at 2:05 AM, Johannes Ranke <jranke at uni-bremen.de> wrote: > Dear Marius, > > thanks for sharing your thoughts on this. I am not very happy that you provide > instructions to install R 3.1.3 from sources when binaries are already > provided on CRAN. Dear Johannes, ... no one in his/her clear mind would go that way unless necessary. I have given reasons

Dirk, I appreciate that you were trying to help, but I would suggest you don't answer a question if you find it irritating or think it is posed by someone who hasn't taken the time to figure things out on his own... others might be able to spare a bit more time and be more patient, however basic the question is. There is a lot of material covered in the page and I found your "read

Dear Johannes, R-sig-debian list, Along with Dirk Eddelbuettel I've been maintaining Debian-based Docker containers for R. Recently our container installing r-base has started to fail. This seems to be due to a problem with the libjpeg dependencies. The example I show below was working with debian:jessie on Jan 5th, but has been failing since then.

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

Dear all, With this email I would like to announce the availability of R 3.4.0 for jessie and stretch on CRAN. Please excuse the delay, caused by some uncertainty about how to deal properly with the incompatibility of R 3.4.0 with packages compiled with earlier versions that use calls to .C and .Fortran in their code as described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861333

Hi! I am a new user of Debian and am having an issue loading RStudio Server, which may or may not be related to a previous 'Release file expiration error' when trying to perform apt-get update prior to installing r-base into my remote Debian system. E: Release file for http://mirror.optus.net/debian/dists/jessie-updates/InRelease is expired (invalid since 13d 17h 49min 2s). Updates for

Dear Dirk, Dear Johannes, Thanks for helping, I could solve the problem. By reading your posts, I got a bit of the impression that questions beyond the 'standard installation' process are not really welcome on R-SIG-Debian. If this is the case, I'm sorry for my post. I wasn't aware of this, but Dirk makes it clear why on

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

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

My Emails a week or so back were about installing Rstudio and the R shiny server on Debian. I was using an old Toshiba laptop as a sandbox for that and it would only install i386 (same for Ubuntu). Using the information at https://cran.r-project.org/bin/linux/debian/ I did get to the point where I had R 3.5.2, Rstudio and the server on there (with some help from Dirk that is in the list archives).

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

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

Hai, I've updated the repo with the Debian Stretch 4.9.4 packages. No changes on my side, so check the samba changelogs for whats fixed. Info : https://apt.van-belle.nl Buildlogs : https://downloads.van-belle.nl/samba4/Buildlogs/stretch/ The repo setup. 1) Choose http or https for you apt, both work, for https you need to : apt-get install apt-transport-https 2) Import my public key

I had to bust the cache on one of my Docker images and when I rebuilt it I noticed something rather concerning from the `apt-get install` step: gpg: requesting key E084DAB9 from hkp server ha.pool.sks-keyservers.net gpg: key E084DAB9: public key "Totally Legit Signing Key < mallory at example.org>" imported gpg: key E084DAB9: public key "Michael Rutter <marutter at

Am Donnerstag, 27. April 2017, 15:05:32 schrieb J C Nash: > 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 Seconded. You should not expect that mixing apt entries for Ubuntu and Debian will work. > > It

Hi, Am Freitag, 18. September 2015, 15:25:10 schrieb George N. White III: > On Fri, Sep 18, 2015 at 8:35 AM Francois-Xavier Jollois < > > francois-xavier.jollois at parisdescartes.fr> wrote: > > Hi everybody > > > > I try to update R 3.1.1 to R 3.2.2 on a Debian Jessie (8.2) server. I > > try to do the following steps : > > > > - Adding