|=== lifeless_ is now known as lifeless
|=== jml_ is now known as jml
|=== rvba` is now known as rvba
|=== wgrant_ is now known as wgrant
|=== gnuoy` is now known as gnuoy
|=== quicksil1er is now known as quicksilver
|LeoNerd: you can unshelve and then partially reshelve
|=== r0bby_ is now known as robbyoconnor
|=== dames is now known as thedac
|=== verterok` is now known as verterok
|=== LoganCloud_ is now known as LoganCloud
|=== LoganCloud is now known as Guest4645
|Where can I find a definition of the 'lp' transport? I want to know if it uses a secure channel like https or ssh.
|Technically it's not a transport, it's a directory service.
|Pretty sure it resolves to http if you're not lp-login'd, and bzr+ssh if you are.
|Eduard_Munteanu: I think it's in the "launchpad" plugin.
|Eduard_Munteanu: On my Debian installation, this appears to be in /usr/lib/python2.7/dist-packages/bzrlib/plugins/launchpad.
|I guess I should use the account and add the ssh key.
|the plugin ships with bzr, though
|SamB: yes, but I don't want to fetch stuff over plain http or without some signature
|it's odd, there's no mention of "http" anywhere in /usr/lib/python2.7/dist-packages/bzrlib/plugins/launchpad/lp_directory.py
|Eduard_Munteanu: it looks rather as though launchpad itself resolves the lp: URLs in the non-SSH case ...
|Eduard_Munteanu: I suppose there's not really much you can do besides that, realistically; launchpad could theoretically be changed to resolve that to https, but that might break existing deployments if they can't validate the SSL keys ...
|(because they don't have the needed CA certs installed/trusted)
|SamB: yeah... I ended up downloading a tarball through the web interface
|I do vaguely recall looking into how "lp:" URLs get resolved, at some point, and finding that there was some series of redirects from lauchpad.net.
|I remember being confused by it; I also remember it making slightly more sense after looking at how a user configures branches/series on the launchpad.net website.