[11:59] <tseliot> apw: hi, what's the "<!stage1>" field in control.stub.in?
[12:00] <apw> tseliot, a profile selector
[12:00] <tseliot> apw: a profile to do what? I'm trying to build locally
[12:00] <apw> tseliot, specifically in that case that the build dependancy is not required when building in profile stage1
[12:00] <tseliot> and sbuild doesn't seem to like that
[12:00] <apw> which is bootstrapping a new architecture
[12:00] <tseliot> oh
[12:01] <tseliot> maybe trusty doesn't recognise that field
[12:01] <apw> in your case you could rip them all out and it would be functionally the same
[12:01] <tseliot> ok, I'll do that, thanks
[12:01] <apw> i thought we built all out will builds in trusty no problem
[12:01] <apw> wily builds
[12:02] <tseliot> I'm not sure what's going on
[12:02] <apw> but for the kernel we only use them to drop deps for early bootstrap, so you would be find just ripping them
[12:03] <tseliot> right
[12:04] <apw> tseliot, i guess the correct reply from me is: you should only be building packages in a chroot that matches the package
[12:04] <apw> tseliot, and in wily they will be grokked just fine
[12:05] <tseliot> apw: I'm trying to build drm-intel-nightly on trusty since the system I need to test the packages on is trusty. Maybe building on wily would be easier
[12:05] <apw> oh i see, hrm
[12:05] <apw> tseliot, and does that imply the nightlies are no longer building ...
[12:05] <tseliot> does the PPA use trusty?
[12:06] <tseliot> no, they build fine
[12:06] <apw> kernel-ppa builds, i beleive they do yes
[12:06] <apw> oh but they maybe building -unstable and getting lucky
[12:06] <tseliot> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/
[12:06] <tseliot> dchroot -c trusty-amd64
[12:06] <tseliot> (from the log)
[12:07] <tseliot> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/BUILD.LOG.amd64
[12:07] <apw> tseliot, yes but that current == <xxx>-unstable
[12:07] <apw> so that means that we have not gotten those stage fixes into unstable yet, and we are just getting lucky
[12:08] <apw> also that means it was built for trust, so ... can't you just use it?
[12:08] <tseliot> apw: ah, so the patches in that directory were not actually applied?
[12:08] <apw> ?
[12:08] <tseliot> 0001-base-packaging.patch
[12:09] <tseliot> 0002-debian-changelog.patch
[12:09] <tseliot> and 0003-configs-based-on-Ubuntu-4.3.0-0.1.patch
[12:09] <tseliot> from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/
[12:09] <apw> they would have been as they are made by droppping them
[12:09] <apw> with git format-patch
[12:09] <tseliot> also I need to rebuild that kernel with a small change for testing
[12:10] <tseliot> right, and the stage thing came with those patches
[12:10] <tseliot> which I applied to the drm-intel-nightly tree (freedesktop)
[12:10] <apw> well that is confusing, we we did build them in trusty
[12:10] <apw> so why didn't it explode
[12:11] <tseliot> this is what I get in my chroot:
[12:11] <tseliot> dpkg-deb: error: parsing file '/«BUILDDIR»/resolver-tOYP3O/sbuild-build-depends-linux-dummy/DEBIAN/control' near line 4 package 'sbuild-build-depends-linux-dummy':
[12:11] <tseliot>  `Depends' field, syntax error after reference to package `kmod'
[12:11] <tseliot> Dummy package creation failed
[12:13] <apw> oh ... hmmm, welll
[12:13] <apw> ok so that is the package that sbuild made to install the deps which is wrong
[12:14] <tseliot> right
[12:14] <apw> we do not use sbuild, we directly build them in an schroot, so dpkg-buildpckage clearly understands in trusty
[12:14] <apw> but not schroot, ok, that we might be able to get fixed
[12:15] <tseliot> that would be nice
[12:15] <tseliot> in the meantime I'll get rid of the stage stuff, or enter the chroot and build from there
[12:25] <tseliot> apw: ok, I think the build scripts simply hate me: /«PKGBUILDDIR»/scripts/sign-file.c:23:25: fatal error: openssl/bio.h: No such file or directory
[12:25] <tseliot>  #include <openssl/bio.h>
[12:26] <TJ-> tseliot: The latest mainline added a new dependency for signing
[12:26] <apw> oh yuo need a new dep
[12:26] <apw> libssl-dev or something
[12:26] <tseliot> oh, let's see
[13:27] <bananapie> Hello,
[13:29] <bananapie> I am looking to learn about the Linux Kernel on my computer, I know a bit about compiling ( I used Gentoo back in 2006-2007 ). I am wondering what is the "right" way to compile a kernel on Ubuntu? Which doc should I use to reproduce the kernel exactly as it appears in the binary packages in Ubuntu?
[13:40] <apw> bananapie, depends if you want to build it locally, or if a ppa would do, if a ppa would do then that always builds the corerct way
[13:41] <apw> bananapie, otherwise you want to be building in a chroot for the series and with the linux build-deps installed, using dpkg-buildpackage -b
[13:42] <bananapie> I want to build it locally for a single machine for the sake of learning about the kernel.
[13:45] <bananapie> I want to start from the same config as the kernel ( back in gentoo, we'd copy .config from /boot ) and have it functional, after that I can try different options and learn :)
[13:45] <apw> bananapie, yep, then you want to build a chroot, and use dpkg-buildpackage -b in that 
[13:46] <bananapie> ok, do I do apt-get source linux-image-3.19.0-15-generic, or is there a better way to get the source codes?
[13:48] <apw> bananapie, here are some rough instructions: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[13:50] <bananapie> Thank you.
[13:51] <apw> bananapie, i recommend using the git repos as they are more up to date
[13:53] <bananapie> Oh! Building the kernel is quite similar to building non-kernel packages :o
[13:54] <bananapie> Cool. Thanks for your help
[13:54] <apw> bananapie, it is identicle, it _is_ a debian package too
[13:54] <bananapie> ok. Last time I tried this, I found multiple 'tutorials' each with a different method to compiling the kernel. It was frustrating and I never got it working.
[13:55] <bananapie> Thanks :)
[13:55] <apw> np
[13:55] <apw> !kernel-faq
[13:55] <apw> !kernel
[13:56] <bananapie> !Stages
[13:56] <bananapie> I thought the stages was about initrd, that's where I got stuck last time.
[13:56] <apw> bananapie, i was just looking myself indeed.  stick with the short one imo
[15:14] <melodie> hi
[15:15] <melodie> I would like an information about the lowlatency kernels under Trusty. It seems there is no "linux-image-generic" for it, or do I miss something? 
[15:15] <melodie> if the linux-image-xyz-lowlatency is installed, will the linux-image-generic get the newer versions when they come out?
[15:17] <rtg> melodie, yup, but I'm not sure which kernel will be the default boot option. likely the last one you installed by hand, e.g., linux-image-lowlatency
[15:17] <melodie> hi rtg 
[15:20] <melodie> rtg so it seems I can safely remove linux-image-generic and linux-headers-generic ?
[15:22] <rtg> melodie, yes, though that won't remove the generic kernel packages. before you do that you'll likely want to install linux-lowlatency
[15:23] <melodie> I had installed the other lowlatency packages but not this one. I do now
[15:23] <melodie> (I had also rebooted to boot to it of course)
[15:24] <rtg> melodie, linux-lowlatency is the meta package that will keep your lowlatency kernel install up to date.
[15:25] <melodie> good! that was exactly what I was looking for, thanks!
[19:56] <melodie> good night
[21:42] <ttr_ppix> will it be possible (or advisable) to upgrade the 3.13 kernel in ubuntu 14.04 lts to the wily 4.2 kernel?
[21:48] <jtaylor> there will be a lts-wily kernel
[21:49] <jtaylor> ttr_ppix: there is already lts-vivid with 3.19 btw
[22:01] <ttr_ppix> jtaylor, thank you for the response, i was hoping to go from 3.13->current at some point soon, sounds like i should just wait for lts-wily