[08:31] <quicksilver> LeoNerd: you can unshelve and then partially reshelve
[19:57] <Eduard_Munteanu> Where can I find a definition of the 'lp' transport? I want to know if it uses a secure channel like https or ssh.
[20:02] <fullermd> Technically it's not a transport, it's a directory service.
[20:03] <fullermd> Pretty sure it resolves to http if you're not lp-login'd, and bzr+ssh if you are.
[20:04] <SamB> yeah
[20:05] <rozzin> Eduard_Munteanu: I think it's in the "launchpad" plugin.
[20:06] <rozzin> Eduard_Munteanu: On my Debian installation, this appears to be in /usr/lib/python2.7/dist-packages/bzrlib/plugins/launchpad.
[20:06] <Eduard_Munteanu> Thanks.
[20:07] <Eduard_Munteanu> I guess I should use the account and add the ssh key.
[20:14] <SamB> the plugin ships with bzr, though
[20:15] <Eduard_Munteanu> SamB: yes, but I don't want to fetch stuff over plain http or without some signature
[20:20] <SamB> it's odd, there's no mention of "http" anywhere in /usr/lib/python2.7/dist-packages/bzrlib/plugins/launchpad/lp_directory.py
[20:22] <SamB> Eduard_Munteanu: it looks rather as though launchpad itself resolves the lp: URLs in the non-SSH case ...
[20:32] <SamB> 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 ...
[20:32] <SamB> (because they don't have the needed CA certs installed/trusted)
[20:32] <Eduard_Munteanu> SamB: yeah... I ended up downloading a tarball through the web interface
[20:50] <rozzin> 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.
[20:51] <rozzin> 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.