[13:40] <Madkiss> hi folks
[13:40] <Madkiss> sforshee: are you online? :)
[13:40] <Madkiss> sforshee: i'm looking for the header packages for http://people.canonical.com/~sforshee/lp1505948/
[13:41] <sforshee> Madkiss: let me see if I still have them
[13:41] <Madkiss> that'd be superawesome :)
[13:46] <sforshee> Madkiss: I have the _amd64.deb package but I never actually built the _all.deb package
[13:47] <sforshee> anyway, I copied what I have to that same location
[13:47] <Madkiss> Okay. I've tried to apply the two patches to 4.4.5, but the second one fails.
[13:47] <Madkiss> patching file fs/fuse/fuse_i.h
[13:47] <Madkiss> Hunk #1 FAILED at 24.
[13:50] <sforshee> Madkiss: mine was based on our xenial tree, I think 4.4.4 was the latest we had applied but we also have extra patches that could maybe account for the differences
[13:50] <Madkiss> most likely. I also tried to apply against 4.2-wily and that failed for the same reason. Is there a way I can get the source you used for your build?
[13:52] <sforshee> definitely. It's at https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial, my build was based on the Ubuntu-4.4.0-11.26 tag
[13:54] <Madkiss> thanks
[14:01] <Madkiss> IOCB patch. ahum.
[14:15] <Madkiss> sforshee: you don't happen to have the source tree still available, right?
[14:18] <mamarley> Hmm, 4.4.0-12.28 seems to have disappeared from Proposed in Xenial.
[14:21] <sforshee> Madkiss: I still have the source, yes
[14:21] <Madkiss> fakeroot debian/rules binary-headers <= should give us the debs we're looking for, no
[14:21] <Madkiss> ?
[14:22] <apw> mamarley, its prolly on its way to -release, it dissappears in launchpad's view for a bit during that though it is always published in the archive proper in one or the other at all times
[14:22] <Madkiss> apw: we fixed the fuse bug ;)
[14:22] <Madkiss> or rather, Robert Doebbelin did.
[14:22] <apw> Madkiss, nice ... do you have a pointer to the fix ?
[14:22] <apw> rtg, ^ we might want to consider this for your -13
[14:23] <mamarley> apw: Ah, OK.  Thanks!  I was wondering if it might have something to do with 4.4.5 that had just been released.
[14:23] <Madkiss> apw: sforshee already has it
[14:23] <Madkiss> http://people.canonical.com/~sforshee/lp1505948/
[14:23] <sforshee> Madkiss: I'll build the header package for you, I'll let you know when it's done
[14:25] <Madkiss> sforshee: thanks a bunch
[14:25] <apw> sforshee, are those ready for primetime, or is testing still on going ?
[14:26] <sforshee> apw: depends on how aggressive you want to be. I was going to send them upstream today after I test build on 4.5.
[14:26] <apw> sforshee, ok sounds good, rtg ignore me
[14:51] <sforshee> Madkiss: both the header packages are there now
[14:51] <Madkiss> excellent, thanks!
[15:00] <Madkiss> Okay. It looks like these do not work OOTB on Trusty systems with DKMS-enabled modules (because gcc 4.9 is required)
[15:01] <apw> Madkiss, that is a xenial kernel, so yeah the dkms issues have not yet been worked out
[15:01] <Madkiss> What's the correct way to get these patches into the lts kernel for trusty?
[15:02] <apw> into the lts-xenial kernel ?  that will occur naturally, if you mena another one, then we need to get that info added to the bug (if not there already) so we remeber to do that
[15:04] <Madkiss> linux-signed-image-generic-lts-wily in 14.04 is the one I mean
[15:04] <apw> right so you want it in the wily family, so sforshee needs to submit those for sru once they are safe enough to get into xenial
[15:08]  * Madkiss starts crying
[15:11] <apw> Madkiss, heh, grinding out patches takes time ... though i am sure sforshee could make you an lts-wily with them applied too
[15:11] <apw> for testin
[15:11] <Madkiss> i'm already on it
[15:13] <Madkiss> arrr