{"thread":{"id":"1534","subject":"Importing from CVS issues","startedAt":"2005-08-16T10:41:34Z","lastAt":"2005-08-16T16:09:13Z","messageCount":5,"participants":["Alex Bennee","Martin Langhoff","David Kågedal"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7356","messageId":"1124188894.7444.9.camel@okra.transitives.com","threadId":"1534","inReplyTo":null,"subject":"Importing from CVS issues","fromName":"Alex Bennee","fromEmail":"kernel-hacker@bennee.com","sentAt":"2005-08-16T10:41:34Z","receivedAt":"2005-08-16T10:41:34Z","isPatch":false,"sender":{"key":"kernel-hacker@bennee.com","avatar":null},"body":"Hi,\n\nWe've been having issues with CVS for some time and I thought I'd give\ngit a spin. To do some like-for-like tests I'm having a go at importing\nour cvs repository into git so I can do some benchmarks on things like\nbranch creation as well as play around with the visualisation tools.\n\nObviously the CVS repo is non-trivial as we have many branches (one per\nchange developed). I've been trying to import script but it seems to\nfalling over. For starters cvsps is spitting out lots of messages along\nthe lines of:\n\nWARNING: revision 1.3.2.1 of file scripts/xmltools/t/runtests.pl on\nunnamed branch\n\nBefore the import script finally dies with:\n\nWARNING: revision 1.3.2.1 of file\nscripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch\nDONE; creating master branch\ncp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such\nfile or directory\nusage: git-read-tree ( | -m [-u] [ []])\n\nIs this a just a case of the cvsps not giving output the script can deal\nwith? Any suggestions on how I can proceed with diagnosing what went\nwrong?\n\n--\nAlex, homepage: http://www.bennee.com/~alex/\nBarometer, n.: An ingenious instrument which indicates what kind of\nweather we are having. -- Ambrose Bierce, \"The Devil's Dictionary\"\n"},{"id":"7358","messageId":"46a038f90508160426450eff12@mail.gmail.com","threadId":"1534","inReplyTo":"1124188894.7444.9.camel@okra.transitives.com","subject":"Re: Importing from CVS issues","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2005-08-16T11:26:13Z","receivedAt":"2005-08-16T11:26:13Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"I haven't seen this problem myself. There are some recent patches\nJunio merged that handle some oddities better. Give the 'pu' branch a\ngo if you can.\n\nI take it that the repo is not public. I'd like to try and reproduce\nthe problem. Can you get it to happen with a public repository?\n\nFor debugging, I'd say proofread the cvsps output, see ~/.cvsps/#repo\n. that could give you hints as to the 'nameless' branches. Why is\norigin missing is a different problem.\n\nAh! Important: if you're adding debugging statements by hand, bear in\nmind that part of the code is executed in a forked child process, and\nprints there will mess things up.\n\ncheers,\n\n\nmartin\n"},{"id":"7360","messageId":"u5toe7y2i28.fsf@fidgit.hq.vtech","threadId":"1534","inReplyTo":"1124188894.7444.9.camel@okra.transitives.com","subject":"Re: Importing from CVS issues","fromName":"David Kågedal","fromEmail":"davidk@lysator.liu.se","sentAt":"2005-08-16T12:16:15Z","receivedAt":"2005-08-16T12:16:15Z","isPatch":false,"sender":{"key":"davidk@lysator.liu.se","avatar":"https://avatars.githubusercontent.com/u/60530?v=4"},"body":"Alex Bennee writes:\n\n> Before the import script finally dies with:\n>\n> WARNING: revision 1.3.2.1 of file\n> scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch\n> DONE; creating master branch\n> cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such\n> file or directory\n\nWas this done with an empty destination dir? I've seen similar things\nhappen in a dir where an interrupted cvs import was done previously,\nand the 'origin' branch was never created.\n\n-- \nDavid Kågedal\n"},{"id":"7361","messageId":"1124200099.7444.37.camel@okra.transitives.com","threadId":"1534","inReplyTo":"u5toe7y2i28.fsf@fidgit.hq.vtech","subject":"Re: Importing from CVS issues","fromName":"Alex Bennee","fromEmail":"alexjb@transitive.com","sentAt":"2005-08-16T13:48:19Z","receivedAt":"2005-08-16T13:48:19Z","isPatch":false,"sender":{"key":"alexjb@transitive.com","avatar":null},"body":"On Tue, 2005-08-16 at 14:16 +0200, David Kågedal wrote:\n> Alex Bennee writes:\n> \n> > Before the import script finally dies with:\n> >\n> > WARNING: revision 1.3.2.1 of file\n> > scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch\n> > DONE; creating master branch\n> > cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such\n> > file or directory\n> \n> Was this done with an empty destination dir? I've seen similar things\n> happen in a dir where an interrupted cvs import was done previously,\n> and the 'origin' branch was never created.\n\nYes, in fact I let the script create the new destination dir. So I don't\nthink its an issue with stale data from a previous attempt being left\naround.\n\n> \n--\nAlex Bennee - alexjb@transitive.com\n\"The world is beating a path to our door\" -- Bruce Perens, (Open\nSources, 1999 O'Reilly and Associates)\n"},{"id":"7367","messageId":"1124208553.7444.47.camel@okra.transitives.com","threadId":"1534","inReplyTo":"46a038f90508160426450eff12@mail.gmail.com","subject":"Re: Importing from CVS issues","fromName":"Alex Bennee","fromEmail":"kernel-hacker@bennee.com","sentAt":"2005-08-16T16:09:13Z","receivedAt":"2005-08-16T16:09:13Z","isPatch":false,"sender":{"key":"kernel-hacker@bennee.com","avatar":null},"body":"On Tue, 2005-08-16 at 23:26 +1200, Martin Langhoff wrote:\n> I haven't seen this problem myself. There are some recent patches\n> Junio merged that handle some oddities better. Give the 'pu' branch a\n> go if you can.\n\nI'll look at that in a bit. I already picked up a few of the patches\nmentioned on the list.\n\n> I take it that the repo is not public. I'd like to try and reproduce\n> the problem. Can you get it to happen with a public repository?\n\nI'm afraid not. However I think I've found a problem when I tried\nrunning cvsps on its own to generate the patchset. It seems that\nREV_STR_MAX (cvsps-2.1/cvsps_types.h) wasn't big enough to contain some\nof our version strings.\n\nThis will be a feature of our development process which means all\nchanges are based of branches, some of which branch multiple times and\nlive for a long time before code is merged into the mainline. I don't\nknow if any open source projects use CVS in such a way.\n\nMy import seems to be getting a lot further now. I now just need to\nclean out the corrupted files that are breaking cvs log.\n\n--\nAlex, homepage: http://www.bennee.com/~alex/\nNew systems generate new problems.\n"}]}