similar to: Planning fixing '--force not working'

Displaying 20 results from an estimated 10000 matches similar to: "Planning fixing '--force not working'"

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 16
1
eval problem in Math.data.frame [.. DispathGroup / mean==sum ..] (PR#84)
>> log(data.frame(x=1:4),base=2) > Error: Object "base" not found This one seems to be fixed. Move to Language-fixed. (Note: there seems to be some strangeness with composing replies like this in the web interface to JitterBug. Watch the headers if you want to followup.) -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list --
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)
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
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
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
2007 May 02
1
? R 2.5.0 alpha bug
This email is intended to highlight 2 problems that I encountered running R 2.5.0 alpha on a Windows XP machine. #1 - Open script error If I click the "Open folder" icon on the toolbar, R opens my script files perfectly. However, when I select "File > Open Script > MyFileLocation", I get a fatal error that causes R to close immediately. This error was reproduced on 3
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(
2004 Dec 24
1
4beta gpg key
Hi, Maybe a stupid question: I just installed centos 4beta on a Dell inspiron 3500 laptop. So far so good. But where do I find the gpg key? Transaction Listing: Update: firefox.i386 0:1.0-6.centos4.2 Is this ok [y/N]: y Downloading Packages: warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 4fe06303 public key not available for
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
2002 Aug 12
0
help with pseudo-random numbers
Dear People, I have a vexing problem related to pseudo-random number generation, and would appreciate any help and advice. This problem is not directly related to R, and the only reason I am posting it to this list is that my implementation is using R. Let me describe my problem by giving an example, that is close to what I am trying to do. Suppose we are given a stream of pseudo-random numbers,
2010 May 20
0
Installation problem with "geepack"
Hi there, I just installed the package under windows, and it works very well. However, as I tried to install it on a cluster which uses linux OS, "Linux lionxc.aset.psu.edu 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux" I always failed. The message during the installation process is as follows: > install.packages("geepack") Warning
2002 May 03
1
rsync.samba.org
Howdy everybody, Dunno if anyone's got a log monitor or mailing script set up for 404 errors on rsync.samba.org, but http://rsync.samba.org/rsync/fom-serve/cache/1.html emits a 404. It's where the the FAQ-O-Matic nav link that's found throughout the site eventually sends the browser. Sorry about posting this to the listserv, couldn't find a "tell the webmaster" link
2006 Jun 30
0
SAS Proc Mixed and lme
I am trying to use lme to fit a mixed effects model to get the same results as when using the following SAS code: proc mixed; class refseqid probeid probeno end; model expression=end logpgc / ddfm=satterth; random probeno probeid / subject=refseqid type=cs; lsmeans end / diff cl; run; There are 3 genes (refseqid) which is the large grouping factor, with 2 probeids nested within each refseqid,
2006 Jun 30
1
lme and SAS Proc mixed
I am trying to use lme to fit a mixed effects model to get the same results as when using the following SAS code: proc mixed; class refseqid probeid probeno end; model expression=end logpgc / ddfm=satterth; random probeno probeid / subject=refseqid type=cs; lsmeans end / diff cl; run; There are 3 genes (refseqid) which is the large grouping factor, with 2 probeids nested within each refseqid,
2009 Nov 16
2
on gsub (simple, but not to me!) sintax
Dear R users, my problem today deals with my ignorance on regular expressions. a matter I recently discovered. Consider the following foo <- c("V_7_101110_V", "V_7_101110_V", "V_9_101110_V", "V_9_101110_V", "V_9_s101110_V", "V_9_101110_V", "V_9_101110_V", "V_11_101110_V", "V_11_101110_V",