Borked repo?

[Martin Pool]

Hi Anders,

This is probably caused by a lock/held/info file with no contents,
which in turn is probably caused by a previous run of bzr being
abruptly interrupted because of a machine crash or network
disconnection.  If you find that file and remove the whole 'held'
directory, things should be ok.  More recently bzrs give a better
message and we would recommend that you upgrade to 2.0.4 or 2.1rc1.

Hope that helps, if not please ask again,
-- 
Martin <http://launchpad.net/~mbp/>