search for: cran34

Hello Johannes: I'm sorry, but I still have the same problem with Rkward. After running apt-get update, I still can not find the amd64 version of the Rkward package. I have tried it with the following sources: deb http://cran.r-project.org/bin/linux/debian stretch-cran34/ deb http://chem.uft.uni-bremen.de/ranke/r-cran stretch-cran34/ deb http://chem.uft.uni-bremen.de/ranke/r-cran jessie-cran34/ (the source you tell me in the answer) On the other hand, the package does not seem to be in https://cran.r-project.org/bin/linux/debian/stretch-cran34/. I ca...

...orry, but I still have the same problem with Rkward. > > > > After running apt-get update, I still can not find the amd64 version of the > > Rkward package. I have tried it with the following sources: > > > > deb http://cran.r-project.org/bin/linux/debian stretch-cran34/ > > deb http://chem.uft.uni-bremen.de/ranke/r-cran stretch-cran34/ > > deb http://chem.uft.uni-bremen.de/ranke/r-cran jessie-cran34/ (the > > source you tell me in the answer) > > > > On the other hand, the package does not seem to be in > > https:...

...bin/linux/debian/ but after updating, Rkward does not work (Error in RK: Graphics API version mismatch). Analyzing the problem, I notice that the Rkward package is not available in the amd64 version (yes in the i386 version), for example here: https://cran.r-project.org/bin/linux/debian/stretch-cran34/ It is not necessary? Can anyone help me on how can I solve the problem that Rkward does not work? Thanks a lot. Griera

...nes: > > I'm sorry, but I still have the same problem with Rkward. > > After running apt-get update, I still can not find the amd64 version of the > Rkward package. I have tried it with the following sources: > > deb http://cran.r-project.org/bin/linux/debian stretch-cran34/ > deb http://chem.uft.uni-bremen.de/ranke/r-cran stretch-cran34/ > deb http://chem.uft.uni-bremen.de/ranke/r-cran jessie-cran34/ (the > source you tell me in the answer) > > On the other hand, the package does not seem to be in > https://cran.r-project.org/bin/linux...

Hello: I just upgraded my Debian Stretch to version 3.5 by following the instructions here: https://cran.r-project.org/bin/linux/debian/stretch-cran34/ Then I have updated as root the R from inside with: update.packages(.libPaths()[1], ask = F, checkBuilt=TRUE, dependencies = F, repos = "http://mirror.ibcp.fr/pub/CRAN/") When finalizing the update of the R, I execute RKWard and I get the error: "unable to initialize the JIT"...

I got a new laptop in September and installed Stretch (I had been using Jessie), and I tried to follow the instructions on https://cran.r-project.org/bin/linux/debian/, as I had multiple times in the past: I added deb http://cran.wustl.edu/bin/linux/debian stretch-cran34/ to the end of sources.list, I followed the rest of the above directions as of early September, as best I recall, and I only got a partial installation. 3.4.2 is installed, but I'm limited in what packages I can load using aptitude (I haven't tried install.packages()). From my reading, t...

...ut after updating, Rkward does not work (Error in RK: Graphics API version > mismatch). Analyzing the problem, I notice that the Rkward package is not > available in the amd64 version (yes in the i386 version), for example here: > > https://cran.r-project.org/bin/linux/debian/stretch-cran34/ Thanks for reporting. The build for amd64 failed, because somehow apt-get source does not see the source package of rkward in the repository any more. I had to adapt my build script https://cgit.jrwb.de/r-backports/commit/?id=56157ad9495765d9 The amd64 deb is on its way to CRAN, I think it...

...rybody, if one installs R >= 3.4.2 from any source, then some Debian packages will be broken. The change of r-api virtual dependency prevents this to happen. Since you install R from CRAN's Debian packages, can't you also upgrade the r-cran-* packages using `apt-get install -t stretch-cran34` as suggested in <https://cran.r-project.org/bin/linux/debian/#debian-stretch-stable> ? Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan

...bin/bugreport.cgi?bug=861333 where there is also a summary (but no list at the moment) of affected packages, provided by Dirk. In order to avoid breaking packages without the user being prepared for it, I have created a new repository for R 3.4.0, so you need to replace jessie-cran3 with jessie-cran34 if you are using the CRAN backports on jessie. Before the upgrade, you should deinstall r-cran-* or r-bioc-* packages from the jessie or stretch archives that use .C or .Fortran as they will not work with R 3.4.0. You can replace them by locally compiled versions installed from within R using i...

...te: > I got a new laptop in September and installed Stretch (I had been using > Jessie), and I tried to follow the instructions on > https://cran.r-project.org/bin/linux/debian/, as I had multiple times in > the past: I added > > deb http://cran.wustl.edu/bin/linux/debian stretch-cran34/ > > to the end of sources.list, I followed the rest of the above directions as > of early September, as best I recall, and I only got a partial > installation. 3.4.2 is installed, but I'm limited in what packages I can > load using aptitude (I haven't tried install.packages...

...erlying issue was rather minute [1] yet the imposition of the r-api change imposes this "omg everything is borked" side effect I consider overkill. | Since you install R from CRAN's Debian packages, can't you also upgrade | the r-cran-* packages using `apt-get install -t stretch-cran34` as | suggested in | <https://cran.r-project.org/bin/linux/debian/#debian-stretch-stable> ? In short, you need matching toolchains. For a given r-base-core package, you need the corresponding r-cran-* Personally, I don't use these backports. My 'development' work happens where D...

...with the R 3.5.2 backports. Cheers, Johannes Am Dienstag, 29. Januar 2019, 09:00:24 CET schrieb griera at yandex.com: > Hello: > > I just upgraded my Debian Stretch to version 3.5 by following the > instructions here: > > https://cran.r-project.org/bin/linux/debian/stretch-cran34/ > > Then I have updated as root the R from inside with: > update.packages(.libPaths()[1], ask = F, checkBuilt=TRUE, dependencies = F, > repos = "http://mirror.ibcp.fr/pub/CRAN/") > > When finalizing the update of the R, I execute > RKWard and I get the error: &quot...

> > Date: Sat, 5 May 2018 18:02:12 -0500 > From: Dirk Eddelbuettel <edd at debian.org> > To: Matthieu S <matthieu.stigler at gmail.com> > Cc: r-sig-debian at r-project.org > Subject: Re: [R-sig-Debian] Ubuntu 18.04 bionic: availability of R > Ubuntu packages/ppa? > Message-ID: <23278.14324.913149.453495 at rob.eddelbuettel.com> > Content-Type:

Dear All, I have a fresh Debian Stretch (now the official Debian stable) installation on my machine. Based on what written here https://cran.r-project.org/bin/linux/debian/#debian-jessie-stable I added the line deb https://stat.ethz.ch/CRAN/bin/linux/debian stretch-cran34/ to my sources in order to have a backport of R 3.4. The issue is that I am now experiencing some troubles to install some packages from cran which did not give me any trouble in the past. The worst is that all I get is an uninformative segmentation fault error. For instance, consider the RJSDMX...

...o my raspi started to compile the file fastLm.cpp ... I will let you know if I succeed. But Dirk is right when he points out that the efficiency of using such a system to compile lots of source packages is questionable. Maybe it would be a solution to deinstall the backport, remove the stretch-cran34 line from your sources.list and install everything from the stretch archive. R version 3.3.3 from stretch is still sort of recent... Johannes > > It looks like you may have repos mixed, or they are out of sync. > > The r-base-core you use should provide r-api-3. Maybe it is newer...

Thanks very much, Dirk! I gave that a try and got the following: pi at raspberrypi:~ $ sudo apt-get install r-cran-car Reading package lists... Done Building dependency tree Reading state information... Done 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 been