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

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

================================================= 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

Martyn Plummer <plummer@iarc.fr> writes: > On 12-Apr-00 Peter Dalgaard BSA wrote: > > Might be a good idea. Mind you, Splus 3.4 does exatly the same thing, > > and I'm a little worried that the uniqueness assumption might kill > > some bootstrapping applications: > > > > glm(y ~ x, data=test.data, subset=sample(seq(along=y),replace=T)) > > Splus

R-help Digest Friday, December 3 1999 Volume 01 : Number 034 In this issue: [R] model.tables Re: [R] Installing R on Slackware Linux Re: [R] Installing R on Slackware Linux [R] nlmin Re: [R] nlmin Re: [R] nlmin Re: Summary: [R] Wanted: online Introduction to R [R] Applying a function of several variables to data Re: [R] R and XML -- a near perfect

Dear friends, Over the past weeks, I have been asking a lot of questions about how to use R in Bayesian analysis. I am brand new to R, but I am very pleased with it. I started with winbugs but I found winbugs to be a limited software, not bad but has several limitations. By contrast, R allows the analyst to tackle any problem with a huge set of tools for any kind of analysis. I love R. In

> Date: Mon, 22 May 2000 16:52:59 +0200 (CEST) > From: Martyn Plummer <plummer@iarc.fr> > To: ripley@stats.ox.ac.uk > Subject: Re: [Rd] RE:bug 548 graphics '*' (PR#549) > Cc: R-bugs@biostat.ku.dk, r-devel@stat.math.ethz.ch > > On 22-May-00 ripley@stats.ox.ac.uk wrote: > > A little more followup. The gtk() device uses gdk_string_width to > > find the

bhoel@server.python.net (Berthold Höllmann) writes: > Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> writes: > > > I've rolled up R-1.0.0.tgz a short while ago. > > > I've build R-1.0.0 on my > > >uname -a > Linux pchoel 2.2.14 #3 Mit Jan 5 08:57:39 MET 2000 i686 unknown > > box. Calling "make check" fails with .... > >

bhoel@server.python.net (Berthold Höllmann) writes: > Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> writes: > > > I've rolled up R-1.0.0.tgz a short while ago. > > > I've build R-1.0.0 on my > > >uname -a > Linux pchoel 2.2.14 #3 Mit Jan 5 08:57:39 MET 2000 i686 unknown > > box. Calling "make check" fails with .... > >

Hi All, This question was brought up some time ago but I never saw a reply so I'd like to bring it up again. When using ROracle package (version 0.5-5), I am unable to run any queries that are greater than 4000 characters in length. If I do, I get the following message: Error in oraPrepareStatement(con, statement, bind=NULL) : RS-DBI driver: (too long a statement -- it must has less than

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