Error having upgraded from Bazaar 1.1.0 to 1.4

[Matt Scarisbrick]

Ok, I've solved the problem and in the process solved another problem a 
colleague was having. It turns out that we seem to have found two bugs:

On Windows Vista or XP with bzr >=1.3, Putty 0.6 and OpenSSH 3.8:

a) If you have Putty in your path bzr will just give you the EOF error 
when you try to connect to a repository over ssh. Removing Putty from 
you path solves the problem.
b) If you have OpenSSH in your path bzr will happily connect but cannot 
take input after the password stage. This makes it impossible to, for 
example, reply 'y' to confirm a break lock. Removing OpenSSH from your 
path solves the problem.

This is, of course, slightly frustrating as it's nice having OpenSSH and 
or Putty in your path! I'll see if I can log these as bugs if no one 
thinks they're already in the list.

Matt

Matt Scarisbrick wrote:
> Matt Scarisbrick wrote:
>> Aaron Bentley wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Matt Scarisbrick wrote:
>>>> Is there a way I can get bzr to output very
>>>> verbosely what it's doing? The verbose option doesn't give me anything
>>>> and I can't find any logs anywhere.
>>>
>>> bzr --version should tell you where it's putting the logs.
>>>
>>> Aaron
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.6 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>>
>>> iD8DBQFIKZKH0F+nu1YWqI0RAmxyAJ9ASy/7Q0Evkzn0h8k6zlDmuLuLzQCdGHlI
>>> i7UaTsh35y4O4dFLYc8nJfQ=
>>> =347c
>>> -----END PGP SIGNATURE-----
>>
>> Ok, thanks. This is what it says:
>>
>> 0.106  encoding stdout as sys.stdout encoding 'cp850'
>> 0.106  bzr arguments: [u'cm', u'-v']
>> 0.107  looking for plugins in 
>> C:/Users/matt/AppData/Roaming/bazaar/2.0/plugins
>> 0.107  looking for plugins in C:/Program Files (x86)/Bazaar/plugins
>> 0.128  encoding stdout as sys.stdout encoding 'cp850'
>> 0.198  opening working tree 'D:/Data/Documents/..../trunk'
>> 0.237  preparing to commit
>> 0.405  ssh implementation is Putty's plink.
>> 1.315  Traceback (most recent call last):
>>   File "bzrlib\commands.pyc", line 846, in run_bzr_catch_errors
>>   File "bzrlib\commands.pyc", line 802, in run_bzr
>>   File "bzrlib\commands.pyc", line 504, in run_argv_aliases
>>   File "bzrlib\builtins.pyc", line 2381, in run
>>   File "bzrlib\decorators.pyc", line 165, in write_locked
>>   File "bzrlib\workingtree_4.pyc", line 246, in commit
>>   File "bzrlib\decorators.pyc", line 165, in write_locked
>>   File "bzrlib\mutabletree.pyc", line 190, in commit
>>   File "bzrlib\commit.pyc", line 292, in commit
>>   File "bzrlib\commit.pyc", line 447, in _check_bound_branch
>>   File "bzrlib\decorators.pyc", line 127, in read_locked
>>   File "bzrlib\branch.pyc", line 1795, in get_master_branch
>> BoundBranchConnectionFailure: Unable to connect to target of bound 
>> branch BzrBranch6('file:///D:/Data/Documents/..../trunk/') => 
>> sftp://ssh.blah.com/bzr/..../trunk/: Unable to connect to SSH host 
>> ssh.blah.com; EOF during negotiation
>>
>> 1.320  return code 3
>>
>> So I'm guessing it's plink, unless anyone knows better!
>>
>> Thanks.
>> Matt
> 
> Of course, the other thing I forgot to mention is that I'm running on 
> 64bit Vista, with putty and bzr running in 32bit mode.
> 
> Matt

-- 
________________

Matt Scarisbrick (matt_scarisbrick at cantab.net)