[08:36] <mvo> hey, is there a way to get more details from LP if it tells me (for a git merge proposal): "lp:~mvo/+git/cnf-extractor-charm is not mergeable into this repository." - context is that I try to create a PR from https://code.launchpad.net/%7Emvo/+git/cnf-extractor-charm/+ref/master/+register-merge to ~canonical-sysadmins/+git/cnf-extractor-charm - when I do this using the git cli it seems to be just fine
[08:38] <cjwatson> mvo: No personal-namespace (i.e. ~owner/+git/name) repositories are ever mergeable into any other ones
[08:38] <cjwatson> As far as LP is concerned
[08:38] <cjwatson> Somebody in ~canonical-sysadmins needs to move that to a different location if they want to be able to accept MPs
[08:39] <cjwatson> Yes, they're mergeable at the git level, but that isn't enough because we need to be able to do things like efficiently scan for merged MPs when pushes happen
[08:44] <mvo> cjwatson: thank you! so the right way is to create a proper LP project for the cnf-extractor-charm and use that for the PRs I assume
[08:47] <cjwatson> Yeah, that would be best
[08:49]  * mvo nods
[10:11] <rbasak> cjwatson: you mentioned there was something you wanted to check before we attempt to switch the default VCS for the LP "ubuntu" project over to git, IIRC. Does that still need looking at, or are you happy for a TB member to make the API call when ready?
[10:17] <cjwatson> rbasak: It was kind of inchoate memories of possible unimplemented bits.  I can't find anything specific (other than that we don't have push permissions for uploaders set up, which we knew about already), but somebody should really try it out on qastaging first and see what happens there.
[10:17] <rbasak> OK, thanks. slangasek (not here) agreed to make the change on behalf of the TB. I'll ask him to try qastaging first.
[13:08] <coreycb> this comment looks malicious, figured i'd report it: https://bugs.launchpad.net/neutron/+bug/1057558/comments/15
[13:08] <cjwatson> coreycb: Thanks, dealing with it.
[13:09] <coreycb> thanks cjwatson
[13:10] <cjwatson> It's gone.
[20:02] <teward> what SSH key encodings are supported?  I know RSA and ECDSA, I wasn't sure if there were any other key types that were supported?
[20:03] <teward> s/encodings/'types'/
[20:09] <cjwatson> teward: It's documented on https://launchpad.net/~/+editsshkeys.
[20:09] <cjwatson> RSA, DSA, and ECDSA.
[20:10] <teward> cjwatson: not sure where exactly you're looking... but no, that isn't actually listed anywhere
[20:10] <teward> oh wait I see, it only lists the "usually" paths
[20:10] <cjwatson> "Insert the contents of your public key (usually ~/.ssh/id_rsa.pub, ~/.ssh/id_dsa.pub, or ~/.ssh/id_ecdsa.pub)."
[20:10] <teward> that's where the confusion is
[20:10] <cjwatson> Yeah, could be clearer I suppose.
[20:10] <teward> cjwatson: indeed, just realized that I'm a bit blind there :P
[20:10] <teward> side effect of tired too
[20:11] <teward> but if it were a tad clearer that'd be easier.  But also if it were documented in the help docs as well
[20:11] <teward> about importing keys (so that it explicitly states the supported types)
[20:11] <teward> but no matter :)
[20:11] <teward> thanks.
[20:11] <teward> *goes back to updating his SSH keys*
[20:12] <cjwatson> teward: I've documented it in https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair#Creating_the_key
[20:15] <cjwatson> (Personally I'm sticking with RSA until we manage to get Ed25519 support going.)
[20:21] <teward> cjwatson: indeed.
[20:22] <teward> i have keys of each good type - rsa ecdsa and ed25519, i'm just a little annoyed that ed25519 isn't supported yet heh
[20:22] <teward> i'm also insane, it seems - I just generated 8k and 16k bitlength keys
[20:22] <teward> so maybe I should be put in the "Overkill" loony bin for a short while :p
[20:23] <teward> (I'm not a fan of DSA as much...)
[20:23] <cjwatson> That is basically ridiculous, yes.
[20:23] <cjwatson> As it happens I was working on pushing Ed25519 a bit further up the hill this evening.
[20:23] <teward> heh, so, coincidence then :p
[20:24] <cjwatson> But it's still going to need an as-yet-unlanded patch to cryptography before I can get anything into Twisted, and the cryptography branch I'm looking at seems to be buggy ...
[20:24] <cjwatson> Also I have a prerequisite branch in Twisted that's still in review
[20:24] <cjwatson> Yaks, yaks everywhere
[20:26] <teward> cjwatson: ouchies.  well, I wish you luck :)
[20:27] <cjwatson> Oh, and then we need OpenSSL 1.1.1 everywhere relevant, which is kind of a pain
[20:28] <teward> indeed, i've heard some evil rumors about it
[20:29] <cjwatson> Specifically 1.1.1, which is newer than bionic.
[20:29] <teward> mhm.
[20:29] <cjwatson> Not even the general 1.1 issues.
[20:31] <teward> cjwatson: help.launchpad.net finally loaded, thanks for making the edit under "Creating the key" to document the types there :)
[20:31] <teward> should help be a little more clear :)
[20:32] <cjwatson> np