fast-export produces incorrect trees

On Mon, Aug 03, 2020 at 11:58:04PM -0000, Ben Hutchings wrote:
> Public bug reported:
>
> Compare the results of fast-export from Bazaar and Breezy:
>
> $ bzr checkout lp:libmemcached
> $ git init libmemcached.git
> $ bzr fast-export --git-branch=trunk-bzr libmemcached - \
> | git -C libmemcached.git fast-import
> $ brz fast-export --git-branch=trunk-brz libmemcached - \
> | git -C libmemcached.git fast-import
> $ git -C libmemcached.git diff --stat trunk-{bzr,brz}
>
> Lots of files end up in the wrong places, as if renames aren't being
> exported correctly.
>
> (Bazaar's fast-export also seems to produce incorrect results, unless
> I'm very confused. However, the differences between the content on
> Bazaar's trunk and the trunk-bzr that appears in git are much smaller.)

Ah, no wonder this is broken. There are tests for the fastimport
plugin but they all cover the import side and not the export side..

https://code.launchpad.net/~cjwatson/brz/fastimport-fix-directory-renames/+merge/410767 might conceivably be relevant to this, though I haven't checked.

This bug is marked as critical since 2.5 years and a fix is available since 1.5 years.
Will this ever get fixed?
Here another user struggling with this bug: https://stackoverflow.com/questions/75953013/migrating-a-bazaar-repo-to-git-path-not-in-branch-error/75994452

I agree it would be great to get this resolved, but breezy is a small community.

There is a change available that *might* be relevant for this bug, but that is also incomplete (it lacks tests and changes a fragile bit of code). As a start, it would be great if somebody could confirm that it actually fixes this bug.