[MERGE] Ensure failed operations leave remote transport in clean state

[Aaron Bentley]

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

Hi all,

Since transports are cached, it seems logical to me that failed
operations must never leave them in a bad state.  If failed operations
left a transport in a bad state, further operations could select that
transport from the cache, causing it to fail in bizarre ways when
perhaps it shouldn't fail at all.

This is not a theoretical issue.  I encountered it with multi-pull.

This patch corrects the behavior of smart transports so that if they
fail due to DNS resolution problems, they can still be reused (likely to
fail again, of course).

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

iD8DBQFG2GKD0F+nu1YWqI0RAnFqAJ9El5YUioJWdctAs5L2rHFn0vSJaACeLxDv
wicNWw+0h639W5QY6jEXXy0=
=6F7A
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bzr-mail-jIMzaZ.patch
Type: text/x-patch
Size: 5520 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070831/81552c2b/attachment.bin