=== maclin1 is now known as maclin === ahasenac` is now known as ahasenack === ahasenack is now known as Guest12330 [16:13] wondering if something is wrong with Launchpad: I have registered, enabled SSH access, and cannot 'push', it simply hangs after SSH login. [16:13] also if I try 'bzr branch lp:bzr' SSH hangs the same way. [16:22] Walex: Can you run 'ssh -vvv bazaar.launchpad.net', put the output on paste.ubuntu.com, and give us the resulting link? [16:23] (I'm expecting that to fail, since bazaar.launchpad.net doesn't support ordinary shells, but exactly how it fails should be informative.) [16:39] looking [16:40] ha! [16:41] (my bet is mismatched local/remote usernames which you'll need to configure) [16:41] https://paste.ubuntu.com/26307329/ [16:42] looks like 'ed25519' [16:43] it hangs after offering that key. [16:43] which however is accepted when registering it... [16:44] I'll try again with RSA key [16:46] Walex: We don't support ed25519 yet [16:46] (I thought it was rejected on registration too; evidently not) [16:46] https://bugs.launchpad.net/launchpad/+bug/1282220 said it was rejected [16:46] Launchpad bug 907675 in Launchpad itself "duplicate for #1282220 Add support for ECDSA and Ed25519 SSH keys" [Low,Triaged] [16:46] https://bugs.launchpad.net/launchpad/+bug/907675 suggests it too [16:47] Launchpad bug 907675 in Launchpad itself "Add support for ECDSA and Ed25519 SSH keys" [Low,Triaged] [16:47] anyway, that last bug has the full story [16:47] ahhhhhhhh [16:48] oh welll. [16:48] cjwatson: thanks for the pointers [16:50] np. the situation is unfortunate but tough to make much progress on ... [16:51] Ahhh it gets funnier. I added the RSA key... and now my profile has instead of the ED25519 and RSA keys two RSA keys with the same content. [16:51] Ah no I am describing things incorrectly... [16:56] As long as there is an ED25519 key available (from 'ssh-agent') the connection hangs. [16:57] even if there is no ED25519 key registered for my user. [16:57] Walex: Right, you'll need to use IdentitiesOnly and IdentityFile in ~/.ssh/config for that host [16:58] Might as well do it for all of bazaar.launchpad.net git.launchpad.net upload.ubuntu.com ppa.launchpad.net [16:58] cjwatson: yes[Cm, it is a bit sad :-) [17:04] yes, created a "stanza" with those names and just the RSA key and that works file. Oh well. [17:09] I should be able to get the Twisted 16.5.0 upgrade done relatively soon, but as noted in that bug there's still upstream work to do. [17:10] which suffix to use for Markdown files? [17:13] this file for example gets colored as C++ (probably) not as Markdown or rendered: http://bazaar.launchpad.net/~ubuntuone-pqm-team/markdown/stable/view/head:/README.md [17:17] cjwatson: dependencies, packages, transitions, ... all my day goes into that. :-) [17:17] yeah, quite [17:18] it is possible loggerhead is too ancient to understand markdown properly [17:18] though it's pygments, it shouldn't be that terrible [17:19] system administration: not just wild parties in exotic locations, loose women and fast cars, sometimes one had to deal with packages, versions, updgrades :-) [17:20] oh, hmm, conceivably we need to specifically install a lexer [17:20] could you file a bug? .md is common enough that we really ought to just get it right [17:21] cjwatson: about to do two: one to put a warn about 'ed25519' keys for the time being, the other about markdown. [17:24] looks like we just need to upgrade pygments [17:30] https://bugs.launchpad.net/launchpad/+bug/1740899 [17:30] Launchpad bug 1740899 in Launchpad itself "Launchpad hangs if presented an 'ed25519' key" [Undecided,New] [17:33] https://bugs.launchpad.net/launchpad/+bug/1740903 [17:33] Launchpad bug 1740903 in Launchpad itself "Launchpad does not colorise or render Markdown source files as Markdown but as C++" [Undecided,New] === necrose99_ is now known as necrose99 [17:44] man thanks for the assistance. [19:50] Hi! Sorry this must've been discussed before, but is there some problems with amd64 builders of Launchpad? All have been "Cleaning" for multiple hours and doesn't take new builds. amd64 queue is now 18655 (20 hours) [20:04] hemu: That queue is mostly just the test rebuild, but we're working on the issue that showed up about an hour ago. [20:06] wgrant: is that the x86 builders being borked? sorry, I just switched to a machine with no IRC backlog available [20:06] acheronuk: Yep [20:07] cool. thanks for being on it :) [20:15] thanks for the information :) [21:56] The x86 (non-rebuild) backlog has just about cleared. [22:16] wgrant: thank you :)