[00:35] <MegaBrutal> Are there any plans at all to make kernel live patches automatic?
[05:29] <th3s3_3y3s> Is there a link used to browse the sourcecode from a web browser?
[05:40] <who_me> I'm trying to compile kernel 4.2.5-wily but getting this error" gcc: error: unrecognized command line option ‘-fstack-protector-strong’ . Is this because I'm using an older version of gcc on Trusty? Also, why are the regular mainline kernels failing to build 64bit packages?
[05:45] <who_me> Should rephrase that. Why are 64bit packages failing to build for the mainline kernels?
[05:56] <th3s3_3y3s> who_me, I haven't seen that they really know anything.
[05:57] <who_me> th3s3_3y3s, who's "they"
[05:58] <th3s3_3y3s> the channels
[05:59] <who_me> I got help here in the past when kernel package builds failed.
[06:00] <th3s3_3y3s> they know what they have setup
[06:00] <th3s3_3y3s> and if what they have setup doesn't work they don't really know what's going on
[06:01] <th3s3_3y3s> it looks like they are programs building fake code on an X server.
[06:03] <th3s3_3y3s> imaginary code
[06:03] <th3s3_3y3s> spinning on an Xserver
[06:04] <th3s3_3y3s> so the output does something completely different
[06:04] <th3s3_3y3s> than what the imaginary code specified
[06:05] <th3s3_3y3s> this is why I was asking about a text mode only switch for the gpu
[06:05] <th3s3_3y3s> they don't know about it
[06:05] <th3s3_3y3s> they keep compiling on some X server
[06:08] <th3s3_3y3s> the thought of being alone shivers me
[06:09] <th3s3_3y3s> the only light in complete darkness
[06:09] <th3s3_3y3s> it must be cold
[06:09] <th3s3_3y3s> inanimate cold still

[06:22] <th3s3_3y3s> so many illuminati
[06:22] <th3s3_3y3s> JEEEE EEEHHH SUS CHRIST SEW MY EYES SHUT
[06:22] <th3s3_3y3s> -- --
[06:22] <th3s3_3y3s> even the illuminati sing about Christ

[06:23] <th3s3_3y3s> eyes wide open
[06:25] <th3s3_3y3s> LocutusOfBorg1, Soul Survivor is the last temptation.
[06:26] <th3s3_3y3s> Winner takes ALL
[06:28] <th3s3_3y3s> infinity do you want to live forever?
[06:35] <th3s3_3y3s> You're all "Job" now.
[06:35] <th3s3_3y3s> Don't blink yet.
[06:41] <th3s3_3y3s> She'll carelessly cut you and laugh while you're bleeding.
[06:42] <th3s3_3y3s> Stay wide awake.
[07:12] <th3s3_3y3s> envision a world full of sparc servers
[07:13] <th3s3_3y3s> clusters of sparc servers
[07:14] <th3s3_3y3s> pure darkness and metal
[07:14] <th3s3_3y3s> inanimate glass encased in metal
[07:23] <th3s3_3y3s> the choice can only happen after knowing
[07:47] <LocutusOfBorg1> WTF?
[08:01] <th3s3_3y3s> LocutusOfBorg1, where does pi exist?
[08:02] <th3s3_3y3s> Do you want to enter the gate?
[08:06] <th3s3_3y3s> The New City.
[10:36] <sbeattie> who_me: it's fine to build with older gcc, you'll just need to adjust the CONFIG_CC_STACKPROTECTOR_REGULAR and CONFIG_CC_STACKPROTECTOR_STRONG options (set the former to y and unset the latter)
[10:37] <who_me> sbeattie, cool. thank you :)
[10:38] <who_me> I also figured how to build the mainline kernels to workaround the ZFS stuff (which makes builds fail). I use: fakeroot debian/rules do_mainline_build=true binary-headers binary-generic
[10:39] <who_me> sbeattie, what's the diff between mainline and "wily" kernels from that repository?
[10:48] <sbeattie> who_me: I don't know exactly what the disctinction is, I haven't really poked much at the mainline repo.
[13:19] <apw> who_me, yep, i added do_mainline_build support only in the last couple of days to make it possible to avoid the zfs issue
[13:19] <apw> who_me, if there are specific older builds you wanted they can be re-queued, but new ones _should_ be ok
[13:20] <apw> who_me, the -wily represents (now) where it was built
[13:42] <who_me> apw, thanks for the clarifications :)
[13:45] <apw> who_me, np
[13:53] <hallyn> apw: jjohansen: could one of you give an answer about fixing the bug in precise' kernel?  (whether it's something we'll do or not)
[13:53] <apw> "the bug" ?
[13:55] <apw> hallyn, ^
[13:56] <hallyn> sigh.  sorry, too many things at once,
[13:57] <hallyn> or, my clipboard just failed me actually.  bug 1504781
[13:58] <apw> hallyn, hmmm, i thought that was a profile issue and the lxc profile was updated
[13:59] <hallyn> apw: hm, i need to reread then.  i thought they wanted a kernel update to let the better lxc patch work
[13:59] <apw> hallyn, hrmm, well let me know if there si something outstanding ...
[14:00] <apw> hallyn, as yes, if it is broken we want to fix it if at all sensible
[14:01] <hallyn> apw: thanks, yes, will ping you if there is
[14:01] <apw> hallyn, as a data point the three uploads since that lxc update have passed testing at least
[14:10] <hallyn> apw: that's odd, they're acting like the world's on fire.
[14:10] <hallyn> but i think you're right, they want an lxc update, sorry, i'll handle it :)
[14:10] <apw> hallyn, no problem :)
[14:45] <adamian> hi guys
[14:46] <adamian> I'm wondering what happend with the amd64 builds in drm-intel-next and drm-intel-nightly
[14:47] <adamian> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2015-10-11-unstable/ has them
[14:47] <adamian> but they are missing in http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2015-10-24-unstable/
[14:48] <adamian> it's stopping at ZFS compilation, tries to rsync to an inexistent directory; and execute autogen.sh there afterwards
[14:53] <who_me> adamian, you can rebuild the kernels yourself or wait for the newer ones. For example, the problem seems fixed in v4.3-rc7-unstable
[14:54] <who_me> adamian, "<apw> who_me, yep, i added do_mainline_build support only in the last couple of days to make it possible to avoid the zfs issue"
[14:54] <adamian> yes, I've bypassed the problem myself, just wanted to know if it's known and tracked :)
[14:54] <adamian> thanks
[14:56] <who_me> adamian, had the same issue but I'm only after the latest LTS (4.1.x) and latest stable (4.2.x)
[15:05] <apw> adamian, in theory it is fixed, i've re-queued that build above, we shall see if it pops out happy
[15:29] <adamian> apw: thanks !