Hi, Attached is a bundle for the 0.90 branch that attempts to fix this issue. The commit message hopefully explains the issue and the fix quite well, but I am not sure it is the correct one, specifically is it now being too lenient, in that it will allow two URIs to match that refer to different ports? There is also another case that seems like it may also cause issues, namely _reuse_for in bzrlib/transport/__init__.py, as that compares self._port to the output of _split_url. If someone that understands the transport framework better than me could evaluate whether this could cause bugs that would be great. The reason the tests didn't get this bug in the first place is that the implementation tests use urls with a specific, non-default port, which doesn't trigger the issue, and the general tests didn't use bzr://. Thanks, James -- James Westby -- GPG Key ID: B577FE13 -- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256 # Bazaar merge directive format 2 (Bazaar 0.90) # revision_id: