Comment 1 for bug 648075

We seem to be consistently getting problems committing to your branch since August 4th:

2010-08-04 03:52:44 INFO Exporting Trackservice trunk series.
2010-08-04 03:52:45 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)
--
...
2010-09-22 05:44:02 INFO Exporting Trackservice trunk series.
2010-09-22 05:44:03 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)
--
2010-09-24 05:24:50 INFO Exporting Trackservice trunk series.
2010-09-24 05:24:51 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)
--
2010-09-25 05:26:19 INFO Exporting Trackservice trunk series.
2010-09-25 05:26:20 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)
--
2010-09-26 05:27:51 INFO Exporting Trackservice trunk series.
2010-09-26 05:27:52 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)
--
2010-09-27 05:25:56 INFO Exporting Trackservice trunk series.
2010-09-27 05:25:57 ERROR Failure: ConcurrentUpdateError('Branch has been changed. Not committing.',)

Provided you don't hold any locks on the branch, we'll need to have our LP Code guys investigate into this problem. Can you try committing and pushing the branch yourself, or using "bzr break-lock" to see if there are any active locks.

Once you provide information about how this goes, please update the bug report back to 'New' so we act on it asap.