[00:18] <infinity> tjaalton: You missed video-intel's build-dep on libxcb-util-dev, which isn't in trusty.
[00:23] <wxl> infinity: so how long before we're testing the 4.4 kernel?
[00:24] <infinity> wxl: You could be testing it today from rtg's PPA, if you're brave.
[00:24]  * tsimonq2 compiles it straight from Linus' git repo, believe me, it's not system-breaking :D
[00:25] <infinity> tsimonq2: No, but it's missing features, and any form of support.
[00:25] <tsimonq2> "features"? like what?
[00:25] <infinity> Like aufs, zfs, other bits and bobs.  overlayfs before that got merged upstream recently.
[00:26] <infinity> apparmor
[00:26] <tsimonq2> but isn't that in the regular kernel?
[00:26] <infinity> No.
[00:26] <tsimonq2> if not, why isn't it upstream?!
[00:26] <infinity> Upstreaming large features sucks (see how many years it took to get overlayfs upstream), such is life.
[00:29] <tsimonq2> hmm :/
[00:30] <infinity> tsimonq2: Anyhow, it's the same tradeoff you get with any package.  Compile from upstream, lose distro support and (potentially) distro improvements/fixes/integration.
[00:30] <infinity> tsimonq2: Personally, I got over my version fetishism a long time ago and decided to trust maintainers, but I used to be you and had to live on tip, so I get it.
[00:31] <tsimonq2> infinity: yeah...but I am doing http://eudyptula-challenge.org/ and so I need Linus' kernel
[00:31] <tsimonq2> infinity: I have a really good computer and an older computer. The good one has Linus' and the old one has the Ubuntu kernel, which I am on now.
[00:31] <tsimonq2> infinity: so they both have pros/cons
[00:33] <infinity> tsimonq2: Sure.  The biggest issue is moving the support commitment to, well, yourself.  Which is fine if you know that.  But it's also why I don't recommend it to others.
[00:33] <infinity> tsimonq2: All too often, someone will build their own and run it for 6 months, 5 of those 6 months involving a known remote hole.
[00:34] <tsimonq2> infinity: aaand this wouldn't be a problem if this was all done upstream :P
[00:35] <infinity> tsimonq2: Eh?  No, it's a problem that humans how have to compiler their own kernel over and over.
[00:35] <infinity> tsimonq2: Nothing to do with upstream, but people who pull a bunch of upstream sources are less likely to check for updates/vulns in every one every day, while they're likely to run apt-get update occasionally.
[00:35] <tsimonq2> infinity: let's agree to disagree :)
[00:35] <tsimonq2> or rather me not wanting to continue
[00:35] <tsimonq2> :)
[00:36] <infinity> tsimonq2: Sure, I don't care what you *do* on your own machines, I care what you recommend to other users in Ubuntu channels.  Not every user is you.
[00:37] <tsimonq2> infinity: ok, I am sorry :)
[00:37] <tsimonq2> infinity: and I know wxl, so it's all cool :)
[00:38] <tsimonq2> infinity: and so I am not recommending it, I was just pointing it out. Probably shoudn't have done so. :)
[00:38] <tsimonq2> infinity: thanks either way
[00:44] <wxl> tsimonq2: hah! you assume infinity and i are "cool" XD
[00:45] <wxl> all seriousness aside though (heheh), how soon before it starts popping out on dailies?
[00:45] <tsimonq2> wxl: no, I am assuming that WE are "cool", I said nothing about infinity :P
[00:45] <infinity> wxl: I'm so hip, I can't see over my own pelvis.
[00:45] <tsimonq2> XD
[00:45] <infinity> wxl: As for when it lands in the archive (and, thus, dailies), no exact date, but "soon".
[00:45]  * wxl nods
[00:45] <infinity> wxl: But if you have a machine you want to play on with rtg's packages and tell him why they suck, the PPA is https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
[00:46] <wxl> infinity: would it be too much to request a nudge to ubuntu-devel-announce when they're in the archive?
[00:46] <infinity> wxl: Mostly, I think we're just cleaning up the long tail of DKMS failures right now, the kernel seems decent.
[00:46] <infinity> wxl: We don't tend to announce when new versions of things land in the archive.
[00:46]  * tsimonq2 is gonna put that on his older computer XD
[00:47] <wxl> yeah, normally it's not something i would ask normally
[00:47] <wxl> i'll just keep watching teh arhive :)
[00:49] <wxl> plars: how does one add to loco.ubuntu.com and/or planet.ubuntu-us.org?
[00:50] <wxl> i didn't even know about the latter one O_O
[00:51] <wxl> looks like we contact plars :)
[00:51] <wxl> ugh wrong channel
[00:51]  * wxl facepalms
[09:36] <doko> any idea what to do about https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1534779 ? vivid is EOL ...
[09:36] <ubot5> Launchpad bug 1534779 in gccgo-4.9 (Ubuntu) "Trusty has higher release than Vivid - breaks upgrading" [Undecided,New]
[09:38] <lordievader> Oeh, that is a nasty bug. Is recommending people to wait for Xenial an option?
[10:41] <cjwatson> doko: hmm?  vivid's not EOL, that happens in two months ish
[10:52] <doko> cjwatson, Feb 04, but ok. so what I can do is at least build a gcc-4.9 in the ubuntu-toolchain-r/ppa PPA for now
[13:46] <jdstrand> tsimonq2 (and infinity): apparmor actually is upstream, but not all of the features Ubuntu uses
[13:47] <jdstrand> (yet)
[13:49] <tsimonq2> hmm ok
[18:08] <infinity> jdstrand: Tomayto, tomahto.
[19:51] <tumbleweed> what's the procedure for unsticking packages from proposed, when when they're stuck because of obsolete reverse-deps?
[19:51] <tumbleweed> e.g. pypy + pyzmq
[19:52] <tumbleweed> pyzmq autopkgtests used to fail. now they pass, with a new upstream release (although these tests are non-deterministic, so bleh)
[19:52] <tumbleweed> but pypy is still stuck because of the old failure
[19:56] <cjwatson> tumbleweed: I'll re-run those with an up-to-date trigger
[19:57] <tumbleweed> if it fails, I'll just push them through probably - those tests are rather dodgy :(
[19:57] <tumbleweed> cjwatson: thanks
[19:58] <cjwatson> queued
[20:23] <tumbleweed> cjwatson: argh, it looks like the armhf binary hadn't published yet
[21:22] <tumbleweed> \o/ it migrated