{"thread":{"id":"11987","subject":"cvsimport infinite loop","startedAt":"2008-02-09T11:45:36Z","lastAt":"2008-02-10T16:38:01Z","messageCount":3,"participants":["Peter Eisentraut","Martin Langhoff","Michael Haggerty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"68070","messageId":"200802091245.38578.peter_e@gmx.net","threadId":"11987","inReplyTo":null,"subject":"cvsimport infinite loop","fromName":"Peter Eisentraut","fromEmail":"peter_e@gmx.net","sentAt":"2008-02-09T11:45:36Z","receivedAt":"2008-02-09T11:45:36Z","isPatch":false,"sender":{"key":"peter_e@gmx.net","avatar":null},"body":"I'm trying to convert the PostgreSQL CVS to Git, using Git 1.5.4 (but\nthe problem also occurs with earlier versions). To reproduce:\n\n$ rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/\n$ git-cvsimport -v -d $PWD/cvsroot pgsql\n\nThis runs for a while and then messages like this are repeating:\n\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'\n\n...\n\nWARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:\n src/include/c.h:1.18=after, src/include/executor/nodeNestloop.h:1.3=before. Treated as 'before'\nWARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:\n src/include/c.h:1.18=after, src/include/executor/nodeResult.h:1.3=before. Treated as 'before'\nWARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:\n src/include/c.h:1.18=after, src/include/executor/nodeSeqscan.h:1.4=before. Treated as 'before'\n\n...\n...\n...\n\nand then they start again\n\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'\nWARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'\n\nI've let this run all night and it doesn't stop.\n\nI don't want to exclude the possibility that the CVS repository has had some\nfunny business done to it over the years, but surely an infinite loop\nshouldn't happen in any case. Please advise.\n"},{"id":"68072","messageId":"46a038f90802090401n431659a5p1a9b457d4338695d@mail.gmail.com","threadId":"11987","inReplyTo":"200802091245.38578.peter_e@gmx.net","subject":"Re: cvsimport infinite loop","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2008-02-09T12:01:43Z","receivedAt":"2008-02-09T12:01:43Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Feb 10, 2008 12:45 AM, Peter Eisentraut wrote:\n> I've let this run all night and it doesn't stop.\n>\n> I don't want to exclude the possibility that the CVS repository has had some\n> funny business done to it over the years, but surely an infinite loop\n> shouldn't happen in any case. Please advise.\n\nMight be a bug in cvsps -- I tried an import earlier this year of the\nPg repo and had a similar problem. parsecvs did handle it, but cannot\ndo incrementals, which is a real shame.\n\ncheers.\n\n\nm\n"},{"id":"68226","messageId":"47AF2869.6030206@alum.mit.edu","threadId":"11987","inReplyTo":"200802091245.38578.peter_e@gmx.net","subject":"Re: cvsimport infinite loop","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2008-02-10T16:38:01Z","receivedAt":"2008-02-10T16:38:01Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"Peter Eisentraut wrote:\n> I'm trying to convert the PostgreSQL CVS to Git, using Git 1.5.4 (but\n> the problem also occurs with earlier versions). To reproduce:\n> \n> $ rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/\n> $ git-cvsimport -v -d $PWD/cvsroot pgsql\n> \n> This runs for a while and then messages like this are repeating:\n> \n> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n> src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'\n> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n> src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'\n> WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:\n> src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'\n> \n> [...]\n> \n> I've let this run all night and it doesn't stop.\n> \n> I don't want to exclude the possibility that the CVS repository has had some\n> funny business done to it over the years, but surely an infinite loop\n> shouldn't happen in any case. Please advise.\n\n*Every* CVS repository contains some measure of funkiness :-). I don't\nknow what caused this particular problem with cvsps, but judging from my\nexperience developing cvs2svn, a likely culprit would be a cycle in the\ngraph of dependencies between changesets that were inferred too naively.\n I had to teach cvs2svn graph theory to make it robustly handle\nsituations like this.\n\nI just tried converting the pgsql repository using the trunk version of\ncvs2svn (which also supports output to git [2]). It worked fine. If\nyou can work with a one-time conversion (as opposed to incremental) then\nconsider using cvs2svn.\n\nMichael\n\n[1] http://cvs2svn.tigris.org\n[2] http://cvs2svn.tigris.org/cvs2git.html\n"}]}