[00:28] <tsimonq2> why does xenial only have -16 when wily has -17? ()
[00:28] <tsimonq2> *(kernel)
[01:03] <Daekdroom> tsimonq2, Xenial was synced before -17 was released, most likely.
[01:03] <Daekdroom> This is not something unusual to happen during development. Firefox stays behind every development cycle...
[01:04] <tsimonq2> Daekdroom: when will it be fixed? and why aren't you updating Xenail and THEN backporting to wily?
[01:04] <tsimonq2> *xenial
[01:04] <Daekdroom> I don't know why I'm doing anything. I'm not an Ubuntu developer.
[01:04] <Daekdroom> besides, Wily is the released version. It's the one that needs all security fixes asap.
[01:05] <Daekdroom> xenial isn't supposed to be used in production systems in the first place.
[01:05] <Daekdroom> I'm just saying this is not the first time I see something like this happen.
[01:06] <tsimonq2> Daekdroom: when will it happen where Xenial gets it first? or does someone have to do that
[01:07] <Daekdroom> tsimonq2, actually, -17 isn't even released for wily
[01:07] <Daekdroom> It's in -proposed
[01:07] <Daekdroom> Both have 4.2.0-16 kernels...
[01:08] <tsimonq2> Daekdroom: but it isn't in Xenial proposed
[01:08] <tsimonq2> why is that?
[01:09] <Daekdroom> Not sure. That's something up to Canonical Kernel Team, I think. Probably not a priority.
[01:09] <Daekdroom> I mean, Xenial doesn't even have daily builds yet.
[01:10] <tsimonq2> Daekdroom: yes it does
[01:11] <Daekdroom> Huh. /topic needs to be updated, then.
[01:11] <tsimonq2> http://cdimage.ubuntu.com/lubuntu/daily/current/
[01:11] <tsimonq2> at least for Lubuntu :P
[01:11] <tsimonq2> and Ubuntu http://cdimage.ubuntu.com/ubuntu/daily-live/current/
[01:12] <tsimonq2> Daekdroom: so is this versioning situation only with the kernel, or with other packages as well?
[01:12] <Daekdroom> tsimonq2, like I said, I've seen it happen before with Firefox.
[01:13] <Daekdroom> But why even bother about a bugfix release of a kernel? It's not like Xenial will end up using 4.2
[01:14] <tsimonq2> but regardless, who makes the decision on that? why does wily get something before xenial?
[01:16] <tsimonq2> Daekdroom: or is it package-by-package?
[01:16] <tsimonq2> Daekdroom: and regardless, doesn't somebody make that decision with Debian imports?
[01:18] <Daekdroom> I believe it's package by package.
[01:21] <Daekdroom> Packages imported from Debian are synced atleast once per development cycle, up to the DebianImportFreeze point
[01:21] <Daekdroom> https://wiki.ubuntu.com/DebianImportFreeze
[01:21] <Daekdroom> (Kernel is not treated as that, though)
[08:15] <Fudge> yesterdays xenial image fails at live boot drops to a busybox prompt. is that still the case?
[08:17] <Fudge> actually the current one
[11:05] <BluesKaj> Hiyas all