problems converting from CVS to mercurial (via fastimport)
Thomas Klausner
tk at giga.or.at
Mon Jun 8 08:58:24 UTC 2015
Hi Matt!
On Sun, Jun 07, 2015 at 10:40:39PM -0500, Matt Mackall wrote:
> On Sat, 2015-06-06 at 22:18 +0200, Thomas Klausner wrote:
> > I'm currently trying to convert the pkgsrc-wip CVS repository
> > (pkgsrc-wip.sf.net) to a mercurial repository.
> >
> > I've been doing it by converting to fossil using cvs2fossil[1]
> > (http://www.sonnenberger.org/2014/05/02/bug-fix-update-cvs2fossil/)
> > and using fossil's export command to create a git fastimport stream
> > (~800MB), which I can successfully import into git. A checkout of
> > 'trunk' then gives me the same state as a CVS checkout.
>
> If you've got a Git repo you're happy with, I recommend converting it
> with hg-git. Putting CVS in the subject line is misleading at that point
> though.
My idea was to convert the CVS repository to a hg repository and use
that as master. It seems that using hg-git I would stop at the git
repository step.
> > I've tried importing the same fastimport stream into mercurial using
> > the hg-fastimport extension, but it failed with:
> >
> > Removing blob dir '/home/wiz/Projects/pkgsrc-wip-hg-repo/.hg/blobs' ...
> > ** Unknown exception encountered with possibly-broken third-party extension fastimport
>
> This pretty much says it all. I've never even heard of that extension,
> so I can't say I'd recommend it. While the fastimport scheme is
> advertised as being agnostic.. it's really pretty Git-centric in its
> design and data choices and thus we've never been very interested in it.
I found the extension on
https://mercurial.selenic.com/wiki/FastImportExtension
Anyway, I've filed a bug report for that extension.
What should I do about the problem I see with 'hg convert', where the
hg repository converted from the git repository has differences?
Would it help if I made the git repository available (418MB)?
Thomas
More information about the Mercurial
mailing list