similar to: R 2.7.0 in Debian unstable

R 2.6.1 is on its way to Debian unstable. I removed the references to gcc-4.2, so backporting should be easier. One thing I lfet in was the shlibs.local which will make R depend on tk8.4 newer than what testing and Ubuntu have, so Johannes and Vincent may need to remove the file. Debian testing users cannot run the unstable binaries as libc6 is ahead on unstable. We'll have to wait for libc6,

Ben Goodrich alerted me to some breakage coming from read.dcf() meaning you can no longer install or upgrade R packages. ChenLiang Xu was eagle-eyed and related this to gzfile() and he and Johannes Fichting confirmed that a downgrade to zlib1g from testing fixes things. Ben already filed a Debian bug report, you can see the gory details at http://bugs.debian.org/562755 and we are in contact

Hi Johannes and Dirk: A Divendres 27 Juny 2008 17:05, Johannes Ranke va escriure: > Hi, > > I just added RODBC to the list of packages maintained for the Debian > etch backports on CRAN. The r-cran-rodbc packages are on their way to > CRAN - if you want them now, you can use > > deb http://chem.uft.uni-bremen.de/r-cran etch-cran/ > > as an alternative. Thank you

Hi Dirk, hi all, ---------- Weitergeleitete Nachricht ---------- Betreff: Accepted mgcv 1.8-32-1 (source) into unstable Datum: Donnerstag, 20. August 2020, 18:06:49 CEST Von: Debian FTP Masters <ftpmaster at ftp-master.debian.org> An: debian-devel-changes at lists.debian.org Format: 1.8 Date: Thu, 20 Aug 2020 10:41:33 -0500 Source: mgcv Architecture: source Version: 1.8-32-1

On 9 May 2019 at 16:35, Kurt Hornik wrote: | >>>>> 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. | | Tomas recently wrote to R Core that | | ********************************************************************* | - gfortran is leaning to

Hi, requests regarding the backports in the official Debian backport repositories (like jessie-backports) should go to the debian-science list. For stretch, I uploaded a backport of R 3.4.3 including the armhf architecture to CRAN https://cran.r-project.org/bin/linux/debian/#supported platforms but I don't know if you are looking for arm64? Kind regards, Johannes Am Donnerstag, 4.

On 19 November 2017 at 19:02, Charles Plessy wrote: | Le Sat, Nov 18, 2017 at 03:26:53PM -0800, Bill Harris a ?crit : | > Incidentally, you can see a bit more complete description at | > https://unix.stackexchange.com/questions/402560/how-do-i-install-r-on-debian-stretch-given-the-r-api-3-issue | > . | | Hi Bill and everybody, | | if one installs R >= 3.4.2 from any source, then some

On 13 May 2018 at 09:03, Bill Harris wrote: | In these interesting times, I think you're saying that things will resolve | themselves at some point, but we're in a transition. I see a number of | postings on Ubuntu, but I'm on Debian Stretch, trying to figure out the | safest way to go. Does something like this make sense: | | | 1. aptitude safe-upgrade should be safe: there

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

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

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

Morgan, On 4 January 2018 at 15:05, Morgan Morgan wrote: | Hi Dirk, | | On the website: | https://packages.debian.org/jessie-backports/r-base ^^^^^^^^^^^^^^^^ | | I see that you are the maintainer. ... of r-base in Debian, ie unstable / testing / stable. I have nothing to do with the backport. Talk to its maintainer. | I was wondering if you know when the

Hi, apparently you are using the backport of R 3.4.2, which provides r-api-3.4. With this backport installed, you cannot use the binary packages from the stretch archive. > | The following packages have unmet dependencies: > | r-cran-car : Depends: r-api-3 > | > | Depends: r-cran-pbkrtest but it is not going to be installed > | Depends:

Dear users of the Debian backports on CRAN, Because of an inconsistency of the README file with the actual situation on CRAN, which Ted Harding gratefully reported, I changed the archive on CRAN so the /etc/apt/sources.list entry has to be changed in case you would like to get updates of R backports to Debian stable in the future: Instead of deb

On 27 April 2017 at 23:41, Charles Plessy wrote: | Le Thu, Apr 27, 2017 at 07:24:18AM -0500, Dirk Eddelbuettel a ?crit : | > | > On 27 April 2017 at 13:58, Johannes Ranke wrote: | > | Am Donnerstag, 27. April 2017, 06:32:13 schrieb Dirk Eddelbuettel: | > | > On 27 April 2017 at 12:01, Johannes Ranke wrote: | > | | > | > This may be a use case for r-api-4. Or not as it

Hi Mathieu, thanks for contributing your tips on apt pinning on Debian testing. I have included similar instructions in the Debian README for the situation where testing was frozen. This time I thought I would get around to provide proper binaries for testing quickly enough, but I need to get some other work done, so I am lagging behind here. If someone could provide some lines with nice

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.

On 10 May 2019 at 13:46, Kurt Hornik wrote: | >>>>> 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,

I just uploaded R 2.5.0 to Debian's unstable distribution. As Peter's announcement says, it now contains two new packages'rcompgen' and 'codetools'. About two or three weeks ago, I also packaged these, just like other 'recommended' packages as r-cran-rcompgen and r-cran-codetools. However, as "new" packages, they are still in the NEW queue awaiting

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