similar to: R-1.4.1 scheduled for Jan 30

I've rolled up R-1.4.1.tgz a short while ago. This is a patch upgrade, fixing the most important bugs that cropped up after the 1.4.0 release. A set of recommended packages which have been tested with R-1.4.1 has been bundled up. Binary distributions are expected to include these packages. You can get the files from the developer site ftp://cvs.r-project.org/pub/CRAN/src/base/R-1.4.1.tgz

I've rolled up R-1.4.1.tgz a short while ago. This is a patch upgrade, fixing the most important bugs that cropped up after the 1.4.0 release. A set of recommended packages which have been tested with R-1.4.1 has been bundled up. Binary distributions are expected to include these packages. You can get the files from the developer site ftp://cvs.r-project.org/pub/CRAN/src/base/R-1.4.1.tgz

R 1.6.1 has been scheduled for November 1. We're makin interim beta versions available via http://cran.us.r-project.org/src/base (ftp://cran.us.r-project.org/pub/R/src/base used to work, but apparently FTP access has been disabled) The filename is R-1.6.1beta_*.tar.gz, where * is the creation date. If you want to help ensure that the final 1.6.1 works satisfactorily on *your* platform,

Hi, recently, tftp-hpa has started to fail to build on mips and mipsel with the following error: ---snip--- [...] make -C tftpd [...] gcc -g -O2 -W -Wall -Wpointer-arith -Wbad-function-cast -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -Wwrite-strings -Wundef -Wshadow -Wsign-compare -pipe -fno-strict-aliasing -I/build/buildd/tftp-hpa-5.0 -c

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

R 1.6.0 has gone into final feature freeze as of today. As a new feature, we'll make interim beta versions available via ftp://cran.us.r-project.org/pub/R/src/base alias http://cran.us.r-project.org/src/base (filename R-1.6.0beta_*.tar.gz, where * is the creation date). If you want to help ensure that the final 1.6.0 works satisfactorily on *your* platform, it might be a good idea to

As the subject says, the core team has decided to release R-1.5.1 next Monday, mainly to "officialize" the bug fixes in the current r-patched. It would be helpful that you check it out and report back if you find any bad problems, especially if you have an uncommon platform. (Or very minor nits. The intermediate ones are "out of bounds" at this stage.) -- O__ ---- Peter

We have now (actually a few days ago) declared a "Grand Feature Freeze" on the development sourcs, meaning that we might still add functionality and fix bugs, but we will not do any further major changes. It should be noted that there has been a couple of quite big changes compared to the 1.6.x series, notably namespaces and the methods package. Also, many more packages are now loaded

Hi: I downloaded klibc-1.5.17 and try to cross-compiled it for MIPS. Got following errors: usr/klibc/exit.o: In function `exit': exit.c:(.text+0x40): undefined reference to `_exit' usr/klibc/execl.o: In function `execl': execl.c:(.text+0x80): undefined reference to `execve' usr/klibc/execle.o: In function `execle': execle.c:(.text+0x84): undefined reference to `execve

> Test suite is green but I'm seeing two libc++ test failures when running check-all. What tests are failing? On Fri, Jun 10, 2016 at 5:13 PM, Nikola Smiljanic via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Uploaded Fedora and openSUSE binaries. Test suite is green but I'm seeing > two libc++ test failures when running check-all. I'm pretty sure these were >

In case you haven't already noticed, daily beta versions of R 1.6.2 are being made available via http://cran.us.r-project.org/src/base/ (also on the rest of CRAN, but the mirroring delays may make that less useful) The plan is to have the final release on January 10, so we are now entering the deep-freeze stage where only critical bugs will get fixed. As usual, it would be a good thing to

Hi, I've tagged 3.8.1-rc1, testers can begin testing. -Tom

Hello, In order to have llvm-3.0 into Debian Wheezy, I have to fix a last build failure under MIPS & MIPSEL. The full mipsel build log is available here: https://buildd.debian.org/status/fetch.php?pkg=llvm-3.0&arch=mipsel&ver=3.0-5&stamp=1324350511 [1] The error is the following: /build/buildd-llvm-3.0_3.0-5-mipsel-jV6EnH/llvm-3.0-3.0/build-llvm/Release/bin/llvm-tblgen -I

For the benefit of package maintainers (and others) we thought it would be a good idea to publish the release schedule well ahead this time. The plan follows below. Not everyone in R-core has had a chance to complain, but I'm off to the ISI tomorrow, so I thought it had better be done now. Platform testing has been a major problem with the previous releases. For some reason, people with

The release schedule has now been set with a release date on April 18. The detailed procedure can be found at http://developer.r-project.org/ (it is not quite there yet, but will appear after a short propagation delay.) The main point for non-developers is that we start making alpha tarballs on March 21 and beta tarballs on April 4. Only very simple and/or critical bugs are fixed in the last

The core team has decided to release R 1.5.0 on April 29th. Somewhat earlier than maybe expected, but we realized that we needed a phase-shift away from our usual cycle with main releases in June and December since it was placing feature freezes just when several members were in a creative phase due to end of teaching. The roadmap is as follows April 8 feature freeze on r-base April 15 code

The release of R-1.8.1 is scheduled for Friday, November 21. Automatic generation of daily alpha releases should start tomorrow (I'll do the first by hand later today) and switch to beta status on Friday, November 14. It would be good if package maintainers could get any planned changes done as soon as possible, and test their packages carefully against the alpha/beta releases. -- O__

The release of R-1.9.1 is scheduled for Monday, June 21. Automatic generation of daily alpha releases should start Monday, June 7 and switch to beta status on Monday, June 14. It would be good if package maintainers could get any planned changes done as soon as possible, and test their packages carefully against the alpha/beta releases. -- O__ ---- Peter Dalgaard Blegdamsvej 3

Hi, The only regression in 3.6.1 -rc1 was on MIPS and it has been confirmed fixed, so I have now tagged 3.6.1 -final. Testers can start building and uploading the final binaries. Thanks, Tom

As you may know, I look after the R package for Debian. My fellow Debianers make me follow a specific protocol -- a so-called "transition" in which all dependent packages on an identified potential breakge are rebuilt under the new (potentially breaking) change. We started adding an r-api-3.4 tag last (major) release. Now it is r-api-3.5 and the transition got started with the green