possible bug with locks

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew King wrote:
> Using bzr+ssh:// transport, I just had a problem where something had
> caused an invalid lock on a server, but I was not told that bzr was
> waiting for a lock when using this transport. When I changed to
> sftp://, it informed me it was waiting on a lock. I think this is a
> bug with the bzr+ssh transport. If people agree, I will file a bug
> report.
> 
> Cheers,
> Andrew.
> 

My guess is that it was a command that was trying to open the lock on
the far side, rather than locally. Which caused the waiting + message to
happen on the remote side.

It certainly seems like something that should be investigated.

John
=;->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGux0sJdeBCYSNAAMRAuR+AJ9YnHvftzPhytapSha+R8qVR/VtEQCeKye2
ltp8Q/t60QZemqzbUosQJkM=
=vX3C
-----END PGP SIGNATURE-----