Well, it looks like i have to round trip through git anyhow, as a lot of the repos created by direct "bzr fast-export | fossil import" come up empty past the initial commit. Curious and curiouser.
On 10 September 2014 17:47, Richard Hipp <[email protected]> wrote: > > > On Wed, Sep 10, 2014 at 11:38 AM, Dömötör Gulyás <[email protected]> > wrote: >> >> I wish to migrate several bzr repos to fossil 1.29, and have gotten >> stuck at fossil telling me "cannot handle R records, use --full-tree" >> trying to import the fast-import dumps. Is there a workaround for this >> issue? I have seen only one reference to this issue on this ML, from >> last May, but no solution was offered. What can I do to solve this, >> short of creating an intermediate git repo? > > > This is the first report of the issue, as far as I am aware. So there is no > work-around. > > If you want to try to hack the Fossil import logic so that it is able to > handle R ("rename") records, you are welcomed to try. Be warned: The > documentation for the "fast-import" file format is fuzzy, so you'll need to > have a number of examples to figure out how it is suppose to work. Probably > part of the reason that R records are not currently supported is that we > never could figure out their semantics. > > -- > D. Richard Hipp > [email protected] > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
