Comment 20 for bug 304134

Hi Wesley,

On Wed, Jan 14, 2009 at 03:28:53PM -0000, Wesley J. Landaker wrote:
> I just wanted to point out two other aspects of this bug:

> 1) Since we got to the bottom of this, the summary is actually
> misleading. This doesn't just affect lightweight checkouts, but also any
> other bzr operation on a subtree with the property demonstrated above.
> This prevents branch, checkout on a subtree where this already exists,
> and bzr pull if it happens after-the-fact.
I haven't seen this being reproduced without a lightweight checkout
or stacked branch yet. At least the cases in the bug report so far are
all related to lightweight checkouts.

> 2) This cannot always be worked around. In my case, I was able to
> operate on a different subtree (since it was a lightweight checkout),
> but I've found a case much more insidious. We have some repositories
> that used to use /some/path/project and later switched to using
> /some/path/{trunk,tags,branches}/project. But since now trunk contains
> directories that used to be peers, and many of them had simultaneous
> modifications[*], now it's impossible to use bzr-svn on trunk, which
> pretty much rules out it's use entirely.
If you remove the svn-cache for your repository, you should be able to
do a normal "bzr branch" on the svn url. The problem is that this bug
corrupts the cache when used on a lightweight checkout.

I do plan to get this bug fixed before 0.5 final. Thanks for looking
into it.

Cheers,

Jelmer