> Nicola: do you know if that branch was pushed with 1.14rc2
> (and never any older version)? If so this is expected behaviour
> (unfortunately), not another case of this bug.
AFAIK, that branch was pushed at least yesterday, before today's upgrade to 1.14rc2, so no. I'll ask thisfred confirmation later, when I get hold of him.
As a workaround, I downgraded to 1.13.1, and get no errors anymore.
We do use stacked branches. What's the fix for the real bug? Do we need to change something in the local, stacked branches? Does anything in bzr code need to change?
> Nicola: do you know if that branch was pushed with 1.14rc2
> (and never any older version)? If so this is expected behaviour
> (unfortunately), not another case of this bug.
AFAIK, that branch was pushed at least yesterday, before today's upgrade to 1.14rc2, so no. I'll ask thisfred confirmation later, when I get hold of him.
As a workaround, I downgraded to 1.13.1, and get no errors anymore.
We do use stacked branches. What's the fix for the real bug? Do we need to change something in the local, stacked branches? Does anything in bzr code need to change?