=== Noskcaj_ is now known as Noskcaj === andyrock_ is now known as andyrock === Peng__ is now known as Peng === Riking is now known as Guest82018 === Guest82018 is now known as Riking === Riking is now known as Guest86934 === Guest86934 is now known as Riking === ePierre__ is now known as ePierre [13:35] I reported a bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759920) about a kernel/microcode issue that affects both Artful and Xenial and trying to add Xenial to the "also affects" list results in an "Oops", would someone else mind giving it a try and see if I'm doing something wrong? [13:35] Ubuntu bug 1759920 in linux (Ubuntu Artful) "intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux-image-4.13.0-37-generic)" [High,Confirmed] [14:30] cjwatson, any chance you have the power to retry this upload for me? https://code.launchpad.net/~sergiusens/+snap/snapcraft/+build/177313 [16:41] ehoover: best thing is to quote the oops id that you're given, since its purpose is to communicate information to developers [16:42] kyrofa: not super-convinced that that error is transient, but I've retried anyway [16:43] cjwatson, thank you, if it fails again we'll survive [16:43] kyrofa: seems to have succeeded, so what do I know [16:43] Hey! Alright, nice [20:23] Hey, can someone tell me why git-commit is not expanding in my recipe? according to this https://help.launchpad.net/Packaging/SourceBuilds/Recipes#Specifying_revisions git-commit is a valid variable [20:24] but what it doesn't say is whether that's valid for version 0.3, is there a new recipe version I should be using instead? [20:24] oh... nevermind, 0.4 for git [20:24] I see it now, it was lost in the text... [20:24] bladernr: :) [20:24] bladernr: was just about to say [20:46] cjwatson: my oops id is OOPS-8493dcf8b62ec1587896280d33c4aa71 , who should I send this to? [20:46] https://oops.canonical.com/?oopsid=OOPS-8493dcf8b62ec1587896280d33c4aa71 [20:48] ehoover: Ah, so you can't use "Also affects" to do this, you need to use "Nominate to series" or "Target to series" depending on your privileges. Do you have either of those? [20:49] ehoover: (It's a bug that it OOPSes; feel free to file that on https://bugs.launchpad.net/launchpad, quoting the OOPS ID. But at best it would just refuse more gracefully.) [20:53] cjwatson: ah, okay - I thought I was allowed to do that since I made the bug [20:54] cjwatson: and no, I do not have nominate or target options - oh well, I'm sure the person responding will do it if it matters :) [20:57] thanks for the help though, I'll go ahead and file a launchpad bug once I get a chance so that others do not get confused :) [20:58] ehoover: I've targeted it to xenial for you now [20:59] cjwatson: awesome, thanks - hopefully we can figure this out before it affects too many people :) [21:10] eh... so still having trouble with a recipe... sigh... [21:10] So I have a project that was originally bzr based, and was moved to git, but the bzr trees are still there. [21:10] If I go to the git tree: https://code.launchpad.net/~hardware-certification/maas-cert-server/+git/maas-cert-server/+ref/master and create a new recipe [21:11] once I save the recipe, the recipe is instead linked to the old bzr trunk and lp changes git-build-recipe in my recipe to bzr-builder [21:11] what's a guy need to do to build a PPA recipe for a git tree? [21:11] (or more accurately, what the heck have I screwed up :/ ) [21:13] bladernr: See https://bugs.launchpad.net/launchpad/+bug/1623924, which has a workaround [21:13] Ubuntu bug 1623924 in Launchpad itself "Source package recipes prefer Bazaar when lp:$foo alias is VCS-ambiguous" [High,Triaged] [21:17] cjwatson, thanks, I've been running around in circles with that for the last half-hour or so. The workaround did indeed fix it.