Comment 22 for bug 390502

On Fri, 2009-07-24 at 18:23 +0000, Wouter van Heyst wrote:
> On Fri, Jul 24, 2009 at 02:35:44AM -0000, Robert Collins wrote:
> > On Fri, 2009-07-24 at 02:11 +0000, Tim Penhey wrote:
> > >
> > > Because when last checked, upgrading a branch that others are stacked
> > > on
> > > breaks the others, and the others can't be upgraded.
> >
> > This was fixed about 8-9 months ago; I noted when I wrote the draft docs
> > that we need more testing is all.
>
> This does not currently work.
>
> bzr upgrade lp:bzr-hookless-email --1.9 # (so I can stack)
> bzr push lp:~larstiq/bzr-hookless-email/390502 --stack
> bzr branch lp:~larstiq/bzr-hookless-email/390502
> bzr check lp:bzr-hookless-email
> bzr upgrade --2a lp:bzr-hookless-email
> bzr check lp:bzr-hookless-email
> cd 390502
> bzr log # tracebacks badly

This is local? I don't undersand why your local branch is dying. Details
- in a bug please!

> bzr upgrade --2a # same thing, ouch

Same.

> bzr upgrade --2a lp:~larstiq/bzr-hookless-email/390502 # Revision not present in..

Look at the 2.0 targeted bugs; I'm sure this is one of them. If not,
please file a bug.

> bzr log # Different Revision not present in.

This is local, so why is it breaking? More details please.

> bzr branch lp:~larstiq/bzr-hookless-email # The branch lp:~larstiq/bzr-hookless-email/390502 has no revision None.

Your line above doesn't make sense, perhaps you could attach the actual
transcript?

> Safe to say, no, it doesn't work.

I upgraded subunit inplace last weekend with no problems. 'Doesn't work'
is at best an overgeneralisation.

Complex upgrade instructions *will not be followed by everyone*. Lets
fix these bugs.

-Rob