[01:12] <infinity> stgraber: You around?
[01:14] <infinity> stgraber: If you have a reproducer the for ipv6 bug that's better than "wait 48 hours and see if my machine is still up", I'd love to have you test the kernels in the PPA quick-like, so we can turn them around ASAP.
[01:15] <stgraber> infinity: I wish I did but no, the bug usually triggers within 24h of boot here. Even knowing the fix, hitting the actual codepath is kinda hard.
[01:15] <stgraber> I can boot the kernel from the PPA now to at least confirm it's not any worse
[01:16] <infinity> stgraber: Sure.  Given that we're 99.9% sure that 2-line revert is the right fix, I'd rather push it out quickly than wait for a long test cycle.
[01:16] <infinity> bjf: You haz opinions on that?
[01:16] <stgraber> yeah, I can certainly agree with that
[01:17] <bjf> infinity, take a deep breath and push
[01:17] <infinity> bjf: Good, we all agree, that means I'm only going to claim 33% of the blame when it goes wrong.
[01:18] <bjf> infinity, i just blame sconklin
[01:18] <infinity> bjf: But please do find suckers to do install/reboot smoketests of amd64/i386 for both trusty and lts-trusty before I push.
[01:18] <infinity> bjf: They're all built (just waiting on lts-trusty/armhf)
[01:18] <stgraber> I'm installing amd64 now
[01:24] <stgraber> Linux athos 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[01:24] <stgraber> so it boots fine at least
[01:25] <infinity> stgraber: Shiny.  Was that trusty?
[01:25] <stgraber> it was, yes
[01:25] <infinity> stgraber: Mind snagging lts-trusty and just installing it with dpkg and rebooting that too?
[01:26] <infinity> stgraber: Assuming its deps are satisfied in trusty, but I think they should be.
[01:31] <stgraber> booting now
[01:34] <stgraber> Linux athos 3.13.0-46-generic #77~precise1-Ubuntu SMP Mon Mar 2 23:24:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[01:34] <infinity> \o/
[01:36] <infinity> stgraber: Thanks for that.  Releasing trusty now, lts-t when it's done building.
[15:40] <jsalisbury> ##
[15:40] <jsalisbury> ## Kernel team meeting today @ 17:00 UTC
[15:40] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
[20:45] <cmagina> it appears that the utopic kernel did not get the fix for bug 1426043, so as of right now utopic will also not boot on arm64 boards
[20:48] <cmagina> vivid is the only one that already had the fix
[20:48] <cmagina> well, not right now, but when the last sru kernel was released
[20:59] <sforshee> cmagina: utopic will getting the fix from upstream stable in the sru cycle which starts this week
[21:00] <cmagina> sforshee: ok, so when does that kernel release?
[21:00] <sforshee> cmagina: in 3 weeks, give or take
[21:01] <cmagina> sforshee: is that kernel available in proposed already?
[21:02] <sforshee> cmagina: no, it will get uploaded tomorrow, then it will get copied to proposed when it finishes building
[21:03] <cmagina> sforshee: one last question, is vivid-proposed using the 3.19 kernel?
[21:04] <apw> cmagina, v3.q
[21:04] <apw> cmagina, v3.19 is already in vivid release pocket
[21:05] <cmagina> apw: ok, cool, thanks. just wanted to be sure that was not my problem with booting it on an arm64 board. must be something else then