From: Michael Haggerty <mhagger@alum.mit.edu>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: cvsimport infinite loop
Date: Sun, 10 Feb 2008 17:38:01 +0100 [thread overview]
Message-ID: <47AF2869.6030206@alum.mit.edu> (raw)
In-Reply-To: <200802091245.38578.peter_e@gmx.net>
Peter Eisentraut wrote:
> I'm trying to convert the PostgreSQL CVS to Git, using Git 1.5.4 (but
> the problem also occurs with earlier versions). To reproduce:
>
> $ rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/
> $ git-cvsimport -v -d $PWD/cvsroot pgsql
>
> This runs for a while and then messages like this are repeating:
>
> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
> src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'
> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
> src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'
> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
> src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'
>
> [...]
>
> I've let this run all night and it doesn't stop.
>
> I don't want to exclude the possibility that the CVS repository has had some
> funny business done to it over the years, but surely an infinite loop
> shouldn't happen in any case. Please advise.
*Every* CVS repository contains some measure of funkiness :-). I don't
know what caused this particular problem with cvsps, but judging from my
experience developing cvs2svn, a likely culprit would be a cycle in the
graph of dependencies between changesets that were inferred too naively.
I had to teach cvs2svn graph theory to make it robustly handle
situations like this.
I just tried converting the pgsql repository using the trunk version of
cvs2svn (which also supports output to git [2]). It worked fine. If
you can work with a one-time conversion (as opposed to incremental) then
consider using cvs2svn.
Michael
[1] http://cvs2svn.tigris.org
[2] http://cvs2svn.tigris.org/cvs2git.html
prev parent reply other threads:[~2008-02-10 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 11:45 cvsimport infinite loop Peter Eisentraut
2008-02-09 12:01 ` Martin Langhoff
2008-02-10 16:38 ` Michael Haggerty [this message]
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=47AF2869.6030206@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=peter_e@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).