Comment 2 for bug 653307

on whether it's something odd that bzr-builddeb is doing: It uses
a tree transform to manipulate the working tree, and then just commits as normal, so
it's not serializing revisions directly or anything. If it's bzr-builddeb then it's
the tree transform putting the working tree in an odd state that bzr doesn't catch.

Help in working out what these errors mean is wrong with the repository would be
welcome.

Also, is there a chance that this is a stacking issue? We do monkey with stacking
at release time, but I don't think we've done that with Debian branches yet, and
most of the ones I checked were Debian.

Thanks,

James