similar to: Bug list summary (automatic post)

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

R-devel Digest Monday, September 24 2001 Volume 01 : Number 314 In this issue: [Rd] R 1.3.1 fails 'make check' on arm in the Bessel example (PR#1097) [Rd] Bug list summary (automatic post) [Rd] (PR#1089) Can be closed See the end of the digest for information about r-devel-digest ---------------------------------------------------------------------- Date: Fri, 21

In looking over the bugs list, it seems to me that most of them are things we can no longer do anything about, because they are on old versions or broken systems or were features or .... There are now so many they obscure the bugs needing attention. I am about the remove the following. If anyone thinks they are still relevant, could you please send a follow-up to R-bugs with details under 1.2.0

I downloaded R v2.1.1 earlier this morning to compile under Fedora Core 4. It compiled without incident, but 'make check' failed. Below is the relevant part of its report. Is this a known problem? I used a locally compiled version of GCC v4.0.0 that reports [kent at d89h102 R-2.1.1]$ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0.0/configure

plot(1:4,1:4,xlim=c(5,0),ylim=c(5,0)) shows axis labels as: | | | | | | 0 rather than | | | | | | 5 4 3 2 1 0 as I believe it used to do in some earlier version. Thank you for R. Rashid Nassar --please do not edit the information below-- Version: platform = i586-unknown-linux arch = i586

Hi, I wonder whether the mechanism of parsing parameters to functions has changed between 0.63.1 and 0.63.3? The following code yeils different results in R 0.63.1 (Version 0.63.1 (Dec 5, 1998)) and R 0.63.3. cave<-function(x,a,b) { return(c(mean(x[a],na.rm=T),mean(x[b],na.rm=T))) } datx <- data.frame(rbind(c(1,2,3,4),c(4,5,6,7)))

Hi, I wonder whether the mechanism of parsing parameters to functions has changed between 0.63.1 and 0.63.3? The following code yeils different results in R 0.63.1 (Version 0.63.1 (Dec 5, 1998)) and R 0.63.3. cave<-function(x,a,b) { return(c(mean(x[a],na.rm=T),mean(x[b],na.rm=T))) } datx <- data.frame(rbind(c(1,2,3,4),c(4,5,6,7)))

At 10 Sep 1999 06:53:01 -0000, Mitsuru Oka <oka@debian.or.jp> wrote: > > > I found problem in R-0.65.0/src/scripts/R.sh.in script. > When I run R program with `R -d gdb', R script say, > > /usr/local/bin/R[104]: shift: bad number > > I fixed this problem by applying following patch to the script: ... > > Version: > platform = i586-unknown-linux

Full_Name: Dan B Version: na OS: na Submission from: (NULL) (80.6.127.185) I can't log into the bug tracker (I can't find where to register / login). In this way I can't add the following context diff (hopefully in the right order) for my changes to the matrix.Rd... Hmm... I guess this should be a separate report anyway... The first diff explains how the dimnames list should

Dear all, I've found a bug report for R when installing it on an AIX5.1 system. There's a followup (number 4) that comments a segmentation fault on R when quitting "q()". I'm using a newer version of R but on the same operating system and I obtain the same error. There was a way to solve this problem? Best regards and thanks, --