tseliotapw: hi, what's the "<!stage1>" field in control.stub.in?11:59
apwtseliot, a profile selector12:00
tseliotapw: a profile to do what? I'm trying to build locally12:00
apwtseliot, specifically in that case that the build dependancy is not required when building in profile stage112:00
tseliotand sbuild doesn't seem to like that12:00
apwwhich is bootstrapping a new architecture12:00
tseliotmaybe trusty doesn't recognise that field12:01
apwin your case you could rip them all out and it would be functionally the same12:01
tseliotok, I'll do that, thanks12:01
apwi thought we built all out will builds in trusty no problem12:01
apwwily builds12:01
tseliotI'm not sure what's going on12:02
apwbut for the kernel we only use them to drop deps for early bootstrap, so you would be find just ripping them12:02
apwtseliot, i guess the correct reply from me is: you should only be building packages in a chroot that matches the package12:04
apwtseliot, and in wily they will be grokked just fine12:04
tseliotapw: 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 easier12:05
apwoh i see, hrm12:05
apwtseliot, and does that imply the nightlies are no longer building ...12:05
tseliotdoes the PPA use trusty?12:05
tseliotno, they build fine12:06
apwkernel-ppa builds, i beleive they do yes12:06
apwoh but they maybe building -unstable and getting lucky12:06
tseliotdchroot -c trusty-amd6412:06
tseliot(from the log)12:06
apwtseliot, yes but that current == <xxx>-unstable12:07
apwso that means that we have not gotten those stage fixes into unstable yet, and we are just getting lucky12:07
apwalso that means it was built for trust, so ... can't you just use it?12:08
tseliotapw: ah, so the patches in that directory were not actually applied?12:08
tseliotand 0003-configs-based-on-Ubuntu-4.3.0-0.1.patch12:09
tseliotfrom http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/12:09
apwthey would have been as they are made by droppping them12:09
apwwith git format-patch12:09
tseliotalso I need to rebuild that kernel with a small change for testing12:09
tseliotright, and the stage thing came with those patches12:10
tseliotwhich I applied to the drm-intel-nightly tree (freedesktop)12:10
apwwell that is confusing, we we did build them in trusty12:10
apwso why didn't it explode12:10
tseliotthis is what I get in my chroot:12:11
tseliotdpkg-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
tseliotDummy package creation failed12:11
apwoh ... hmmm, welll12:13
apwok so that is the package that sbuild made to install the deps which is wrong12:13
apwwe do not use sbuild, we directly build them in an schroot, so dpkg-buildpckage clearly understands in trusty12:14
apwbut not schroot, ok, that we might be able to get fixed12:14
tseliotthat would be nice12:15
tseliotin the meantime I'll get rid of the stage stuff, or enter the chroot and build from there12:15
tseliotapw: 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 directory12:25
tseliot #include <openssl/bio.h>12:25
TJ-tseliot: The latest mainline added a new dependency for signing12:26
apwoh yuo need a new dep12:26
apwlibssl-dev or something12:26
tseliotoh, let's see12:26
bananapieI 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:29
apwbananapie, 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 way13:40
apwbananapie, otherwise you want to be building in a chroot for the series and with the linux build-deps installed, using dpkg-buildpackage -b13:41
bananapieI want to build it locally for a single machine for the sake of learning about the kernel.13:42
bananapieI 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
apwbananapie, yep, then you want to build a chroot, and use dpkg-buildpackage -b in that 13:45
bananapieok, 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:46
apwbananapie, here are some rough instructions: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel13:48
bananapieThank you.13:50
apwbananapie, i recommend using the git repos as they are more up to date13:51
bananapieOh! Building the kernel is quite similar to building non-kernel packages :o13:53
bananapieCool. Thanks for your help13:54
apwbananapie, it is identicle, it _is_ a debian package too13:54
bananapieok. 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:54
bananapieThanks :)13:55
ubot5A list of common questions about the Ubuntu Kernel can be found in http://wiki.ubuntu.com/Kernel/FAQ13:55
ubot5The core of Ubuntu is the Linux kernel: see https://help.ubuntu.com/community/Kernel - You shouldn't have to compile your own, and if you need to troubleshoot issues, you can try a !Mainline kernel instead, but if you insist, see https://help.ubuntu.com/community/Kernel/Compile (see also !Stages)13:55
ubot5The Ubuntu Kernel gets updated in stages.  If you have the updated kernel, but do not have the corresponding restricted modules, you may be leaving yourself with no X when you reboot.  If you have compiled binary versions of your video driver, eg from the nVidia site, you will need to recompile them for the new kernel.  This is normal, and not a bug.13:56
bananapieI thought the stages was about initrd, that's where I got stuck last time.13:56
apwbananapie, i was just looking myself indeed.  stick with the short one imo13:56
melodieI 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
melodieif the linux-image-xyz-lowlatency is installed, will the linux-image-generic get the newer versions when they come out?15:15
rtgmelodie, 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-lowlatency15:17
melodiehi rtg 15:17
melodiertg so it seems I can safely remove linux-image-generic and linux-headers-generic ?15:20
rtgmelodie, yes, though that won't remove the generic kernel packages. before you do that you'll likely want to install linux-lowlatency15:22
melodieI had installed the other lowlatency packages but not this one. I do now15:23
melodie(I had also rebooted to boot to it of course)15:23
rtgmelodie, linux-lowlatency is the meta package that will keep your lowlatency kernel install up to date.15:24
melodiegood! that was exactly what I was looking for, thanks!15:25
=== alai` is now known as adlai
=== adlai is now known as alai8
melodiegood night19:56
ttr_ppixwill it be possible (or advisable) to upgrade the 3.13 kernel in ubuntu 14.04 lts to the wily 4.2 kernel?21:42
jtaylorthere will be a lts-wily kernel21:48
jtaylorttr_ppix: there is already lts-vivid with 3.19 btw21:49
ttr_ppixjtaylor, 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-wily22:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!