Comment 1 for bug 629212

So, sodium's master tree that gets rsynced from A to B,C,D etc had this issue:
14:47 < spm> launchpad@asuka:/srv/staging.launchpad.net/staging/launchpad$ bzr update
14:47 < spm> bzr: ERROR: This tree contains left-over files from a failed operation.
14:47 < spm> Please examine /srv/staging.launchpad.net/staging/launchpad/.bzr/checkout/limbo to see if it contains any files you wish to
14:47 < spm> keep, and delete it when you are done.
1

There are some issues here:
 - sodium, el crasho
 - the staging update process did not detect that this issue existed.
 - there is so much cronspam noise that the issue (if reported in cron errors) was not observed by anyone (and I would be getting those mails too: this isn't a criticism of anyone).

Dropping to high as we've figured the problem and can resolve. I will update the RT about sodium too, pointing out that it can break prod and staging rollouts.