bug 504715 seems to reproduce this in 2.0.1 - or at least the same secondary exception.
Perhaps we can use bzrlib.cleanup to make this more transparent.
bug 504715 seems to reproduce this in 2.0.1 - or at least the same secondary exception.
Perhaps we can use bzrlib.cleanup to make this more transparent.