This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: sim checkout broken
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org
- Date: Wed, 26 Jun 2013 13:55:10 -0400 (EDT)
- Subject: Re: sim checkout broken
- References: <1371835865-15879-1-git-send-email-tromey at redhat dot com> <871u7rwodv dot fsf at fleche dot redhat dot com> <20130624224138 dot GC5326 at adacore dot com> <alpine dot BSF dot 2 dot 02 dot 1306242048260 dot 69392 at arjuna dot pair dot com> <87y59ythcd dot fsf at fleche dot redhat dot com> <20130625142141 dot GF5326 at adacore dot com> <87ppvatfsp dot fsf at fleche dot redhat dot com> <87bo6ute8b dot fsf at fleche dot redhat dot com> <alpine dot BSF dot 2 dot 02 dot 1306260702510 dot 73224 at arjuna dot pair dot com> <878v1wrghn dot fsf at fleche dot redhat dot com>
On Wed, 26 Jun 2013, Tom Tromey wrote:
> H-P> cvs checkout: ignoring module src/gdb/version.in
>
> H-P> Can the action causing that Emptydir please be reverted?
> H-P> And/or explained, maybe with a line indicating "better
> H-P> switch to CVS-N.M".
>
> Could you say exactly what you are doing?
Oh my, seems I'm a victim of the reproducibility-ignorance-demon
despite extensive training. Sorry about that. Hubris, I guess. :/
> Did you do a fresh checkout?
Nope, not that time, but below I just did.
> Or check out into an existing source tree?
Yes: a tree checked out prior to the recent changes.
(Exactly when is hopefully unimportant - decades ago.)
> If the latter, was that tree
> populated using a different module previously?
Just the same "sim" module as before the changes.
And apparently even that detail doesn't matter:
> Indeed, if I run the same "cvs co sim" command twice, the second time I
> get:
>
> cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not match /cvs/src/src/gdb
>
> ... but cvs still exits with status 0 for me.
Odd; it being 1 for me doesn't seem version-dependent.
Starting from scratch, at a second "cvs -d
:pserver:anoncvs@sourceware.org:/cvs/src co sim" I get:
cvs checkout: warning: src/config.if is not (any longer) pertinent
cvs checkout: warning: src/configure.in is not (any longer) pertinent
cvs checkout: warning: src/gettext.m4 is not (any longer) pertinent
cvs checkout: warning: src/ltcf-c.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-cxx.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-gcj.sh is not (any longer) pertinent
cvs checkout: warning: src/ltconfig is not (any longer) pertinent
cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not match /cvs/src/src/gdb
cvs checkout: ignoring module src/gdb/version.in
and then exit value 1 (cvs 1.11.5).
> I'm using cvs 1.11.23. I suppose you could try upgrading, but I don't
> know whether that would help or not.
I don't think it would. On another machine, at the second
checkout (with the first identical command populating the tree)
with a CVS version apparently matching yours, the same thing
happens:
[hp@derp sim]$ cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co sim
cvs checkout: warning: src/config.if is not (any longer) pertinent
cvs checkout: warning: src/configure.in is not (any longer) pertinent
cvs checkout: warning: src/gettext.m4 is not (any longer) pertinent
cvs checkout: warning: src/ltcf-c.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-cxx.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-gcj.sh is not (any longer) pertinent
cvs checkout: warning: src/ltconfig is not (any longer) pertinent
cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not match /cvs/src/src/gdb
cvs checkout: ignoring module src/gdb/version.in
[hp@derp sim]$ echo $?
1
[hp@derp sim]$ rpm -q cvs
cvs-1.11.23-25.fc17.x86_64
> Maybe I can reproduce the exit failure with more information.
>
>
> Not sure what else to do.
But what is the cause of the error? Can't we just remove that
Emptydir or revert what was done? The message above seems to
indicate an operational error in whatever was done.
Thanks for your efforts.
brgds, H-P