Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: sim checkout broken
Date: Thu, 27 Jun 2013 03:22:00 -0000	[thread overview]
Message-ID: <87bo6spakh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1306261316340.73224@arjuna.pair.com> (Hans-Peter	Nilsson's message of "Wed, 26 Jun 2013 13:55:10 -0400 (EDT)")

Tom> Could you say exactly what you are doing?

H-P> Oh my, seems I'm a victim of the reproducibility-ignorance-demon
H-P> despite extensive training.  Sorry about that.  Hubris, I guess. :/

Don't worry about it.

Tom> Indeed, if I run the same "cvs co sim" command twice, the second time I
Tom> get:
Tom> 
Tom> cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not
Tom> match /cvs/src/src/gdb
Tom> 
Tom> ... but cvs still exits with status 0 for me.

H-P> Odd; it being 1 for me doesn't seem version-dependent.

Ugh.

H-P> cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not
H-P> match /cvs/src/src/gdb

H-P> I don't think it would.  On another machine, at the second
H-P> checkout (with the first identical command populating the tree)
H-P> with a CVS version apparently matching yours, the same thing
H-P> happens:

H-P> cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not
H-P> match /cvs/src/src/gdb
H-P> cvs checkout: ignoring module src/gdb/version.in
H-P> [hp@derp sim]$ echo $?
H-P> 1
H-P> [hp@derp sim]$ rpm -q cvs
H-P> cvs-1.11.23-25.fc17.x86_64

There must be some difference since:

barimba. cvs -d  :pserver:anoncvs@sourceware.org:/cvs/src co sim
[...]
cvs checkout: Updating src/intl
cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not match /cvs/src/src/gdb
cvs checkout: ignoring module src/gdb/version.in
barimba. echo $?
0

I have:

barimba. rpm -q cvs
cvs-1.11.23-29.fc18.x86_64

Based on "rpm -q --changelog" it is hard to believe that anything
between -25 and -29 changed this.

H-P> But what is the cause of the error?  Can't we just remove that
H-P> Emptydir or revert what was done? The message above seems to
H-P> indicate an operational error in whatever was done.

Based on my searches it seems to be a CVS issue.
CVS, IIUC, puts "Emptydir" into the Repository file of some directories
in some situations.  This later confuses it.
I don't really understand this, though, since no Repository file in my
checkout actually has this.


Maybe we should just give up on part of this patch and move the
version.in file back out of "common".

sim really should not be using this file.

Tom


  reply	other threads:[~2013-06-27  2:11 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
2013-06-27  3:22                     ` Tom Tromey [this message]
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=87bo6spakh.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hp@bitrange.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