{"thread":{"id":"22641","subject":"cvsimport error when modulename is '.'","startedAt":"2010-02-13T11:51:42Z","lastAt":"2010-02-16T11:21:58Z","messageCount":3,"participants":["Daniel Black","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134424","messageId":"201002132251.42070.daniel.subs@internode.on.net","threadId":"22641","inReplyTo":null,"subject":"cvsimport error when modulename is '.'","fromName":"Daniel Black","fromEmail":"daniel.subs@internode.on.net","sentAt":"2010-02-13T11:51:42Z","receivedAt":"2010-02-13T11:51:42Z","isPatch":false,"sender":{"key":"daniel.subs@internode.on.net","avatar":null},"body":"\nin an empty directory I'm attempting the command:\n\ngit  cvsimport -A ../authcvs-conv -k -m -v -d:pserver:anonymous@opendkim.cvs.sourceforge.net:/cvsroot/opendkim .\n\nthis results in ...\n\nInitialized empty Git repository in /home/dan/software_projects/opendkim-import4/.git/                                                \nRunning cvsps...                                                                                                                      \nconnect error: Network is unreachable                                                                                                 \ncvs rlog: Logging .                                                                                                                   \nNOTICE: used alternate strip path /cvsroot/opendkim/.c                                                                                \nWARNING: file /cvsroot/opendkim/BRANCHES doesn't match strip_path /cvsroot/opendkim/.c. ignoring                                      \nWARNING: file /cvsroot/opendkim/FEATURES doesn't match strip_path /cvsroot/opendkim/.c. ignoring                                      \n....\nfor every file up until the end:\n....\nFetching vsignore   v 1.1\nUnknown: error\n\nThe resulting directory is empty apart from a empty initialised git repository.\n\ngit version 1.7.0.rc2.13.g8b233.dirty\ncvsps version 2.1\n\nnumerous permutations of attempting this import have failed. Also fails with\n the CVS module aliases 'world -> .' and attempting to use \"world\" as an alias name.\n\nI'm happy to assist in debugging this if required.\n\nDaniel\nOpenDKIM developer\n"},{"id":"134523","messageId":"20100214070757.GA22000@coredump.intra.peff.net","threadId":"22641","inReplyTo":"201002132251.42070.daniel.subs@internode.on.net","subject":"Re: cvsimport error when modulename is '.'","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-02-14T07:07:58Z","receivedAt":"2010-02-14T07:07:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Feb 13, 2010 at 10:51:42PM +1100, Daniel Black wrote:\n\n> git  cvsimport -A ../authcvs-conv -k -m -v -d:pserver:anonymous@opendkim.cvs.sourceforge.net:/cvsroot/opendkim .\n>\n> this results in ...\n>\n> Initialized empty Git repository in /home/dan/software_projects/opendkim-import4/.git/\n> Running cvsps...\n> connect error: Network is unreachable\n> cvs rlog: Logging .\n> NOTICE: used alternate strip path /cvsroot/opendkim/.c\n> WARNING: file /cvsroot/opendkim/BRANCHES doesn't match strip_path /cvsroot/opendkim/.c. ignoring\n> WARNING: file /cvsroot/opendkim/FEATURES doesn't match strip_path /cvsroot/opendkim/.c. ignoring\n\nThese messages are not coming from git-cvsimport, but rather from cvsps,\nwhich cvsimport uses to generate whole patchsets from the CVS data. Just\nrunning \"cvsps .\" results in similar errors, and I don't see an obvious\nway to do what you want. So probably it would require a patch to cvsps\nto fix.\n\nIf this is a one-shot import, you can try a few different things.\n\nAs a hack, if you can move files in the CVS repository (and if you\ncan't, try using cvssuck or similar to pull them locally, and then do\nthe import from there), then move everything to a submodule \"foo\", and\nimport that module.\n\nAlternatively, you might check out some of the alternative importers\nlike parsecvs or cvs2git. I don't know if they would handle this\nsituation better.\n\nAnd as a super-hacky alternative, you could import each module\nseparately and then stich them all together using git-filter-branch.\n\n-Peff\n"},{"id":"134729","messageId":"201002162221.58483.daniel.subs@internode.on.net","threadId":"22641","inReplyTo":"20100214070757.GA22000@coredump.intra.peff.net","subject":"Re: cvsimport error when modulename is '.'","fromName":"Daniel Black","fromEmail":"daniel.subs@internode.on.net","sentAt":"2010-02-16T11:21:58Z","receivedAt":"2010-02-16T11:21:58Z","isPatch":false,"sender":{"key":"daniel.subs@internode.on.net","avatar":null},"body":"On Sunday 14 February 2010 18:07:58 Jeff King wrote:\n> On Sat, Feb 13, 2010 at 10:51:42PM +1100, Daniel Black wrote:\n\n> These messages are not coming from git-cvsimport, but rather from cvsps,\n\nthanks for narrowing it down. I'll see if I can track down the maintainer \nthere.\n\n> which cvsimport uses to generate whole patchsets from the CVS data. Just\n> running \"cvsps .\" results in similar errors, and I don't see an obvious\n> way to do what you want. So probably it would require a patch to cvsps\n> to fix.\n\nthanks for confirming this.\n \n> If this is a one-shot import, you can try a few different things.\n\nwas hoping not too but i might be able to get the project team on board with a \none-shot.\n \n> As a hack, if you can move files in the CVS repository\n\non sf its easy as you've got read rsync access on the source\n\n> (and if you\n> can't, try using cvssuck or similar to pull them locally, and then do\n> the import from there), then move everything to a submodule \"foo\", and\n> import that module.\n\nmight to this .\n\n> Alternatively, you might check out some of the alternative importers\n> like parsecvs or cvs2git. I don't know if they would handle this\n> situation better.\n\nok\n\n> And as a super-hacky alternative, you could import each module\n> separately and then stich them all together using git-filter-branch.\n\nYep was thinking of this. Thanks for the expert advice on the stiching \ntogether because i had no idea how.\n\nMuch appreciate your time for putting together these options.\n\nThanks Jeff.\n"}]}