=== chiluk_away is now known as chiluk | ||
=== smb` is now known as smb | ||
infinity | henrix_: The quantal/armhf linux build failed with a SEGV (probably cosmic rays). I've retried it, but it won't be done for another ~8h. Just a heads-up. | 08:29 |
---|---|---|
=== yofel_ is now known as yofel | ||
=== henrix_ is now known as henrix | ||
henrix | infinity: ack, thanks. | 09:39 |
=== smb` is now known as smb | ||
=== cking_ is now known as cking | ||
BenC | So is the intent to go with 3.8 for raring? | 12:39 |
* henrix -> lunch | 12:52 | |
xnox | BenC: yes. As far as I remember that was announced by kernel team at the end of UDS. | 12:54 |
rtg | BenC, definitely | 13:06 |
rtg | cking, henrix: rebooting gomeisa for kernel update | 13:11 |
henrix | rtg: ack | 13:12 |
rtg | ppisati_, rebooting tangerine for kernel update | 13:15 |
ppisati_ | rtg: ack | 13:15 |
janimo | apw, anything I can do on the nexus7 kernel config syncup WI? | 14:14 |
janimo | no hurry, just to make sure we're still on the same page wrt the scripted headstart you can give it | 14:14 |
* ppisati_ goes out for a bit | 14:33 | |
=== kentb-out is now known as kentb | ||
* ogasawara back in 20 | 15:52 | |
* ppisati_ -> gym | 17:12 | |
=== kamal1 is now known as kamal | ||
=== kamal is now known as Guest1901 | ||
=== kamal2 is now known as kamal | ||
* rtg -> lunch | 18:28 | |
=== henrix is now known as henrix_ | ||
* rtg -> EOD | 20:47 | |
infinity | bjf / henrix: Is it an assumption in the bot, or human error, that prepare-package-signed was set to Invalid for a non-ABI bump kernel? | 22:33 |
bjf | infinity, probably an invalid assumption in the bot | 22:34 |
infinity | (For 3.5.0 in quantal and lts-quantal, no signed, which means they'll be out of sync) | 22:34 |
bjf | ugh | 22:34 |
infinity | If you'd like to whip up a pair of signed packages for me and throw them at the PPA, you can fix the bot later. :) | 22:35 |
bjf | infinity, will probably do that | 22:36 |
infinity | (Since I already promoted linux/quantal before noticing the error) | 22:36 |
bjf | infinity, i'm working on it | 22:40 |
infinity | bjf: Oh, wait. Were all the reverts in modules? | 22:40 |
bjf | infinity, looking, but i don't think so | 22:41 |
infinity | Actually, you know what? While what I was about to say was technically true, it's probably just confusing to make the distinction and branch the workflow. | 22:41 |
bjf | infinity, it's in the fs subsystem | 22:41 |
infinity | Much simpler to just say "if linux revs, linux-signed also must" than to say the more-true-but-more-error-prone "if linux revs, but the kernel image stays the same, linux-signed can be left alone". | 22:42 |
infinity | bjf: Yeah, check. We need a new -signed regardless, then. :P | 22:42 |
infinity | bjf: Either way, like I said, it's probably just confusing to bother making the distinction anyway. | 22:42 |
bjf | infinity, agreed, let's not try to optimize it | 22:43 |
bjf | infinity, they are building | 22:57 |
infinity | bjf: My hero. I'll fix up the bugs manually, if you want to make sure the bot gets this right next time. | 23:05 |
herton | infinity, bjf: it's fixed now. Our script to create tracking bugs was mistakenly marking it as invalid, as it did a substring check for 'prepare-package-', as previously we didn't have the -signed task, now it should behave properly | 23:06 |
infinity | herton: Oh, shiny. Thanks for the quick fix. | 23:08 |
maxb | Hi. https://help.ubuntu.com/community/AsusZenbookPrime suggests using the kernel parameter acpi_osi= to make backlight control keys work. How concerned should I be about this breaking other unrelated things? | 23:35 |
maxb | (I have enough understanding of what this does to know that it's causing the kernel to lie rather a lot to the ACPI stuff) | 23:37 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!