From: Hans-Peter Nilsson <hp@bitrange.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: sim checkout broken
Date: Wed, 26 Jun 2013 17:58:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1306261316340.73224@arjuna.pair.com> (raw)
In-Reply-To: <878v1wrghn.fsf@fleche.redhat.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
next prev parent reply other threads:[~2013-06-26 17:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 17:33 [PATCH v5] don't keep a gdb-specific date Tom Tromey
2013-06-21 18:00 ` Pedro Alves
2013-06-24 14:56 ` Tom Tromey
2013-06-24 19:22 ` Joel Brobecker
2013-06-24 22:41 ` [commit] Fix host_name and target_name generation by common/create-version.sh Joel Brobecker
2013-06-24 22:59 ` [PATCH v5] don't keep a gdb-specific date Joel Brobecker
2013-06-24 23:58 ` [commit] Adapt sim to new version number & date locations Joel Brobecker
2013-06-25 0:52 ` Mike Frysinger
2013-06-25 1:53 ` Joel Brobecker
2013-06-25 15:51 ` Tom Tromey
2013-06-25 15:57 ` Tom Tromey
2013-06-25 15:46 ` Tom Tromey
2013-06-25 16:01 ` Eli Zaretskii
2013-06-25 15:28 ` Tom Tromey
2013-06-25 16:41 ` Mike Frysinger
2013-06-25 1:08 ` [PATCH v5] don't keep a gdb-specific date Hans-Peter Nilsson
2013-06-25 14:16 ` Tom Tromey
2013-06-25 14:25 ` Joel Brobecker
2013-06-25 14:43 ` Tom Tromey
2013-06-25 15:27 ` Tom Tromey
2013-06-26 11:23 ` sim checkout broken (was: [PATCH v5] don't keep a gdb-specific date) Hans-Peter Nilsson
2013-06-26 16:52 ` sim checkout broken Tom Tromey
2013-06-26 17:58 ` Hans-Peter Nilsson [this message]
2013-06-27 3:22 ` Tom Tromey
2013-06-27 4:05 ` Hans-Peter Nilsson
2013-06-27 15:22 ` Tom Tromey
2013-06-27 16:30 ` Tom Tromey
2013-06-27 17:09 ` RFC: move common/version.in to gdb/ (Was: sim checkout broken) Tom Tromey
2013-06-28 3:18 ` Hans-Peter Nilsson
2013-06-28 18:17 ` RFC: move common/version.in to gdb/ Tom Tromey
2013-06-27 17:27 ` sim checkout broken Hans-Peter Nilsson
2013-06-27 8:19 ` Andreas Schwab
2013-06-25 14:50 ` [PATCH v5] don't keep a gdb-specific date Pedro Alves
2013-06-25 14:53 ` Joel Brobecker
2013-06-25 15:01 ` Tom Tromey
2013-06-25 15:14 ` Pedro Alves
2013-06-26 2:45 ` Yao Qi
2013-06-26 16:06 ` Tom Tromey
2013-06-27 2:11 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.02.1306261316340.73224@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox