I cannot reproduce with any of the branches mentioned so far, which suggests it's either:
a) something transient (e.g. a particular revision graph shape that later pushes changes, or a race with a pack-names update?), or
b) something to about the local repositories?
I'm not sure how to proceed, as I don't have any good theories.
Did anyone experience this without a local shared repository (or with a pristine, freshly init-repo'd one)? That would suggest it is, or was, an issue with the data or logic on the server...
If it's a race with a concurrent write to a repo then perhaps there would be something in the server-side log? I'm not sure how feasible it is to track down the relevant bzr serve logs for Launchpad.
I cannot reproduce with any of the branches mentioned so far, which suggests it's either:
a) something transient (e.g. a particular revision graph shape that later pushes changes, or a race with a pack-names update?), or
b) something to about the local repositories?
I'm not sure how to proceed, as I don't have any good theories.
Did anyone experience this without a local shared repository (or with a pristine, freshly init-repo'd one)? That would suggest it is, or was, an issue with the data or logic on the server...
If it's a race with a concurrent write to a repo then perhaps there would be something in the server-side log? I'm not sure how feasible it is to track down the relevant bzr serve logs for Launchpad.