Bug in commit - did not return a token

[Kevin Littlejohn]

On 04/02/2008, at 1:04 PM, Jonathan Lange wrote:

> On Feb 3, 2008 8:36 PM, Kevin Littlejohn <darius at obsidian.com.au>  
> wrote:

>>     assert self._lock_token, 'Remote server did not return a token!'
>> AssertionError: Remote server did not return a token!
>>
>> bzr 0.92.0 on python 2.5.1.final.0 (darwin)
>> arguments: ['/opt/local/bin/bzr', 'commit', 'bzr+ssh://darius-obsidian@bazaar.launchpad.net
>> /%7Edarius-obsidian/pytd/darius/']
>> encoding: 'UTF-8', fsenc: 'utf-8', lang: 'en_AU.UTF-8'
>> plugins:
>>   launchpad            /opt/local/lib/python2.5/site-packages/bzrlib/
>> plugins/launchpad [unknown]
>>   multiparent          /opt/local/lib/python2.5/site-packages/bzrlib/
>> plugins/multiparent.pyc [unknown]
>>
>> ** Please send this report to bazaar at lists.ubuntu.com
>>    with a description of what you were doing when the
>>    error occurred.
>>
>> I have a series of local commits I'm trying to push up to launchpad -
>> I got the same effect trying to commit to main:
>>
>
>
> Intriguing.
>
> How can I reproduce this on my own machine?

I grabbed a branch of a new project off launchpad, made a change,  
tried to commit, and got that.  However, I upgraded to bzr 1.1 (from  
0.92), and the error appears to have gone away - so I'm writing it off  
as an old version issue at this stage.

Thanks,
KJL