[10:17] <apw> balerion (N,BFTL), you probabally should be more specific as your issue, as that allows someone 4 hours later to work out if they are the right person to reply; plus you should file a bug
[11:29] <Technetium191> Hi forum, I've had to install an rc Ubuntu Mainline Kernel to overcome a bug with vsftpd in 14.04 - can anyone explain if and how the generic kernel in Trusty will ever be updated to this rc, or am I stuck with using a mainline kernel forever?
[11:34] <smb> Technetium191, Upstream stable changes will be carried back to the generic kernel. Usually about every three weeks. And if it is the problem of running vsftp in EC2, that is queued for the next updates round
[11:46] <Technetium191> Thanks smb, yes that's the bug. So I can keep running the mainline rc kernel for a few weeks and when the next generic update comes along change over to it? So if 3.13.0-27-generic is the latest kernel I guess I'm waiting for 3.13.0-28-generic? 
[11:48] <smb> Technetium191, There has been a bit of riple effect from some "urgent" things. So the next one currently pending is 3.13.0-29.52
[11:48] <smb> Give me a sec to check whether that patch is in there
[11:53] <smb> Technetium191, Ok, sorry, that one (-29) is still without that patch. So -30 supposedly contains the fix
[11:55] <Technetium191> smb, where can I find that kind of information, release schedules, included patches etc?
[11:59] <smb> http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=summary branches with the queues (the longterm repos we support), otherwise the ubuntu-trusty tree on the same site contains the current version in release in master and master-next is staging. 
[12:01] <smb> For the schedule... maybe https://wiki.ubuntu.com/Kernel/StableReleaseCadence not sure. I never can find things again in wikis...
[12:18] <Technetium191> so if Trusty is an LTS release is it correct that there won't a major kernel update for it (eg to 3.15 series), only patches to the 3.13 (3.14 ?) series?
[12:20] <smb> Technetium191, So not sure there is a real schedule. But things from the longterm queue go into the longterm release and from there into master-next of the release and then into master when the next update is prepared. 
[12:21] <smb> The upload first goes into -proposed and then to -updates (which maybe can be seen best on https://launchpad.net/ubuntu/+source/linux)
[12:22] <smb> Technetium191, There will be lts backports of newer kernel as part of hardware enablement, but you have to specifically install those. Except when installing from newer point release isos which may have newer kernels
[12:27] <smb> Technetium191, That might be helpful: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[12:37] <Technetium191> smb, many thanks, that explains a lot, much appreciated!
[13:05] <jpds> apw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325260 - verified.
[13:32] <apw> jpds, i am impressed at your remote fingers 
[13:33] <jpds> apw: Got someone in the office to install things.
[13:36] <apw> jpds, ok that is great, it looks like this has been applied to all the stables but 3.13 and i assume that is just timing
[15:03] <jsalisbury> **
[15:03] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:03] <jsalisbury> **
[15:12] <jhenke> hi folks, out of curiosity: what is the meaning of the "kernel-key" tag? Just asking as it got removed from bug 1315921 I reported.
[15:13] <jsalisbury> jhenke, That key is used for reports that the kernel team views.
[15:15] <jhenke> jsalisbury thanks for the answer
[15:15] <jsalisbury> np
[16:56] <jsalisbury> ##
[16:56] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:56] <jsalisbury> ##
[17:34] <infinity> zequence: Also, while I'm annoying you today, you have new lowlatency tracking bugs again.  At least no more quantal now.
[17:41] <zequence> infinity: Thanks
[17:45] <infinity> zequence: I think you might have already jumped the gun and done saucy, but probably worth double-checking that it's still correct and matches their upload (maybe an artificial build version bump and including the right tracking bug would bring some sanity to the situation)
[17:46] <zequence> infinity: ok
[17:47] <infinity> zequence: By which I mean, keep the changelog intact, and just edit the second half of the version to increment it, and put in the right tracking bug.
[17:48] <infinity> zequence: (After making sure the rebase doesn't pull in any new bits, etc)