Comment 6 for bug 937101

> If you've updated it this way once (which has added the problematic
> entry), you should then be able to replace the upstream copy with the
> fixed copy. Have you tried this?

If I try to "bzr co" from my local branch (which I had to first checkout to -r170 and then to update to the latest revision), I get the same problem. Even a lightwieght checkout bumps into the problem. So the "added entry" that makes my local branch work, seems to be only present in the checkout but not in the branch/repository.