Anyone know what is wrong with the CVS?
null:~/coreutils$ cvs up -Pd
Invalid CVSROOT (2)
cvs update: invalid data from cvs server
null:~/coreutils$
CVSROOT is :ext:[EMAIL PROTECTED]:/cvsroot/coreutils...
Cheers.
___
Bug-coreutils mailing list
Anyone know what is wrong with the CVS?
Not I. I just asked savannah-hackers what's going wrong.
Thanks, I might note for the record that the only repo that isn't
working for me from savannah is the coreutils one, all other usual
projects that I hack on work.
Cheers.
Roberto Nibali [EMAIL PROTECTED] wrote:
...
Oh. I see that this has been fixed since 5.2.1.
...
Hmmm, has it really? Could you show me the changeset, please?
My use of `since' was misleading.
This was fixed *after* coreutils-5.2.1.
You can find the development version here:
ls used quotearg_colon when the context didn't have a colon. I
installed this fix:
2004-12-16 Paul Eggert [EMAIL PROTECTED]
* src/ls.c (print_dir): Use %s: not listing already-listed
directory, not not listing already-listed directory: %s, to
format already-listed
I installed the following patch to sync coreutils from gnulib:
2004-12-16 Paul Eggert [EMAIL PROTECTED]
* config/mdate-sh: Sync from gnulib.
--- config/mdate-sh 11 Nov 2003 07:13:26 - 1.4
+++ config/mdate-sh 17 Dec 2004 05:23:44 - 1.5
@@ -1,9 +1,9 @@
Alfred M. Szmidt [EMAIL PROTECTED] writes:
Anyone know what is wrong with the CVS?
Not I. I just asked savannah-hackers what's going wrong.
The web interface is up, e.g.,
http://savannah.gnu.org/cgi-bin/viewcvs/coreutils/coreutils/doc/ChangeLog
is up-to-date. Not that this solves your
