similar to: eval problem in Math.data.frame [.. DispathGroup / mean==sum ..] (PR#84)

Displaying 20 results from an estimated 20000 matches similar to: "eval problem in Math.data.frame [.. DispathGroup / mean==sum ..] (PR#84)"

1999 Dec 08
1
plot math - segfault and "frac", "^" bug(s).. (PR#365)
MM> I've sent two bug reports that both haven't been forwarded to R-devel MM> and haven't should up at the jitterbug repository. MM> ?? MM> Martin Well, actually only one [the other went to R-core alone] Here it is : From: Martin Maechler <maechler@sophie> To: R-bugs Subject: plot math - segfault and "frac", "^" bug(s).. Date: 8
2004 Jul 02
1
jitterbug
Jitterbug is just what I want. Bugzilla is great but not for a non-programming (issue-tracking) audience. Can I get jitterbug somewhere please (it seems you have removed it) ? Cheers andy -- andy _______________________________________________ Andy Heath a.k.heath@shu.ac.uk
2004 Jun 01
1
Bug reporting
On 1 Jun 2004, John Summerfield <john@Corridors.wa.edu.au> wrote: > The jitterbug link on http://rsync.samba.org/nobugs.html no longer works. I > suggest it either be fixed or removed. Thanks, fixed. > You make bug-reporting needlessly difficult, I think. I dislike the need to > subscribe to a mailing-list and potentially receive lots of email that > doesn't interest
1999 Feb 08
1
R-bugs interfacing to R-devel mailing list
I've been hacking at the JitterBug sources a little, so that it should work better with mailing lists. It has been running with the core team list for a while and seems to be OK. I will now move the forwarding address to the r-devel list where it really belongs. I hope this will make it easier for people outside the core team to contribute to the development of R by participating in the
1999 Feb 08
1
R-bugs interfacing to R-devel mailing list
I've been hacking at the JitterBug sources a little, so that it should work better with mailing lists. It has been running with the core team list for a while and seems to be OK. I will now move the forwarding address to the r-devel list where it really belongs. I hope this will make it easier for people outside the core team to contribute to the development of R by participating in the
2007 Apr 30
1
mirror's choice when installing a package for R-2.5.0 (PR#9643)
Hello, Just a quick message to say that, ------------------------------------------------------------------------ ------- when choosing (with or without the tcltk window) "Bern 1 (swiss)" as CRAN mirror to install a package (function install.packages) for R-2.5.0, the list of available packages for osx seems not complete: AMORE, AdaptFit, AlgDesign, AnalyzeFMRI, SemiPar,
2007 Dec 11
2
range( <dates>, na.rm = TRUE ) (PR#10508)
(Drats! Jitterbug is playing tricks with the PR# again. Attempting to refile so that we can kill PR#10509) Peter Dalgaard wrote: > Kurt.Hornik at wu-wien.ac.at wrote: > =20 >> ------- Start of forwarded message ------- >> Date: Tue, 13 Nov 2007 21:44:57 +0100 >> To: Steve Mongin <sjm at ccbr.umn.edu> >> Cc: cran at r-project.org >> Subject: Re: range(
2002 Aug 09
0
summary.data.frame with compound elements problem (PR#1891)
Full_Name: Barry Rowlingson Version: 1.5.0 OS: x86 linux Submission from: (NULL) (130.95.16.114) Elements of a dataframe may be a matrix or another dataframe. In this case the summary() method can do bad things: > x <- data.frame(1:10) > x$z <- data.frame(x=1:10,y=1:10) > summary(x) X1.10 z Min. : 1.00 NULL:Min. : 1.00 1st Qu.: 3.25
2001 Jan 30
1
screen can't go back to log="y" plot (PR#831)
[I have abbreviated the subject as jitterbug has been having probems with long subjects.] The issue here is that one cannot mix log/non-log axes in the calls to screen(), as the appropriate par() parameter is read-only, but the meaning of yaxp depends on it. But beyond that you can't set x/yaxp for log axes. You should be able to do this: you can in the S original. A simpler version: plot
2008 Sep 02
1
Moving to a new bug reporting system?
Hi all This may be an issue that has been discussed at length before, so apologies if I have missed that discussion, but is there any desire to switch from Jitterbug to something more capable and modern? Say JIRA, for instance? Rory Rory Winston RBS Global Banking & Markets Office: +44 20 7085 4476 *********************************************************************************** The
1999 Mar 01
1
"xpdrows.data.frame" (PR#131)
This is a follow-up to bug sent to days ago, which bounced from r-devel because the example was to large. Now example is smaller, and behaviour is as belo, EXEPT that r-windows not any more bombs, so main problem is "xpdrows.data.frame"??? By the way, how to debug this example under windows? debug() doesnt accept the functions used (.Primitive), and R wont run under gdb --- may have
2000 Jul 06
1
Notification: PR#9
JitterBug notification ivo moved PR#9 from incoming to wishlist Message summary for PR#9 From: vdongen@hetisw.nl Subject: map Date: Sun, 2 Jul 2000 18:23:20 0200 (CEST) 0 replies 0 followups Notes: This is a nice idea on itself, but not really doable in tinc itself. What would be nice is the ability to control tinc realtime with some sort of GUI tool. This tool can then be used for much
2010 Feb 10
0
(PR#14210) incoming/14210 system.time provides inaccurate
Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez wrote: > Patch against current trunk attached. It is a one-liner, so I do not > believe anyone can claim copyright over it. Fixed for r-devel (r51115). > Cheers, >=20 > Manuel. >=20 > BTW, bugs.r-project.org is painfully slow. I cannot login, I cannot pos= t > messages, I cannot attach files. And it doesn't handle accents in my
2001 Jan 02
1
minor problems (if problems at all): <ESC> in RGui; finding (PR#800)
On Tue, 2 Jan 2001 H.RINNER@TIROL.GV.AT wrote: > [These things don't seem to be of too great importance and may well not meet > the criteria of a "bug", but, for what it's worth,I thought I'd submit them > to r-bugs anyway:] > > This is the R version: > > version > _ > platform i386-pc-mingw32 > arch x86
2000 Jun 12
0
Samba patches - where best to send them?
Hi Folks, Where is the best place to feed back patches and problem reports for Samba these days? Should I be using "samba-patches@samba.org"? This list? The samba-technical list? The samba-bugs address bounces back an auto-response telling one to use samba-patches for well-formed patches, but if the Jitterbug web interface is to be believed then submissions to samba-patches seem to be
2003 Jul 17
2
Samba 3.0.0 beta3 available for download
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)
2003 Jul 17
2
Samba 3.0.0 beta3 available for download
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)
2001 Dec 23
1
Planning fixing '--force not working'
Hi folks! I'm in desperate need of getting the '--force' option working. I've written a jitterbug entry on this already #3500 Just curious to know if this is already being worked on, so I'm not duplicating anyone's efforts if I was to try and work on this myself? Or... will this be my first contribution to this fine program? :) ("`-/")_.-'"``-._
2003 Jul 02
3
Samba 3.0.0 beta2 available for download
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/beta/ The
2003 Jul 02
3
Samba 3.0.0 beta2 available for download
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/beta/ The