[11:20] <stokachu> lol @ stoken
[11:32] <davmor2> cjwatson: is this week a better one to discuss the secureboot issues on upgrading from raring to saucy?  did you want me to reinstall raring and try again? Was it just an unsigned kernel?  Is there some other issue?
[11:36] <cjwatson> Honestly, you might be better off asking kernel folks
[11:36] <cjwatson> But I suppose it's worth at least looking at the output of:  dpkg-query -W grub-efi-amd64\* linux-image\*
[11:36] <cjwatson> PS this is the wrong channel
[12:11] <davmor2> D'oh why did I think this was installer :( long day and it's only just begun
[14:41] <rtg_> infinity, I'm not groking the problem here, nor can I reproduce it in my local chroot: https://launchpadlibrarian.net/140308235/buildlog_ubuntu-saucy-i386.linux_3.9.0-2.7_FAILEDTOBUILD.txt.gz
[14:42] <infinity> rtg_: Probably has to do with the texlive mess Colin and I are currently unwinding.
[14:43] <rtg_> infinity, ah. shall I just restart that build once you're done ?
[14:43] <infinity> rtg_: Yeah.
[14:43] <infinity> rtg_: (And you could reproduce it if you had proposed enabled, surely)
[14:43] <rtg_> infinity, I thought proposed was bad news on saucy ?
[14:43] <cjwatson> It is for users.  Builds have to have it.
[14:44] <cjwatson> I can restart the build if you give me a pointer to the archive it's in.
[14:44] <rtg_> makes sense
[14:44] <infinity> rtg_: Running proposed is bad, building against it is somewhat necessary.
[14:44] <cjwatson> My build chroots all have -proposed enabled, since otherwise it's impossible to do anything with transitions.
[14:44] <infinity> cjwatson: https://launchpad.net/ubuntu/+source/linux/3.9.0-2.7
[14:44] <infinity> (ie: primary)
[14:45] <cjwatson> Aha
[14:45] <cjwatson> Fine - I have a batch of stuff to retry later
[14:51] <cjwatson> Right, well, I'm basically waiting for All The Builds now.  Time for a break.