Comment 9 for bug 2016003

This is still affecting me. The only workaround is to rely on the fact that I have one old machine on a distro that no longer provides updates which runs a very outdated version (). I have to manually copy my modified files to that host, then commit those changes *there*, and then remote-merge and commit them back here. That gives me a more-or-less stable local repo until the next time I do something completely normal (adding an entry to ~/.bzrignore, for instance, which I track) that sets off this frustrating and potentially crippling bug.