[01:46] <CIA-4> ubiquity: cjwatson * r1894 ubiquity/ (4 files in 3 dirs):
[01:46] <CIA-4> ubiquity: - partman-* updates add validation support (LP: #82768); also add
[01:46] <CIA-4> ubiquity:  XFS-on-/boot validation.
[02:03] <CIA-4> ubiquity: cjwatson * r1895 ubiquity/ (debian/changelog ubiquity/components/partman.py): - Break out of setting the mountpoint if it's invalid (LP: #84543).
[02:27] <CIA-4> ubiquity: cjwatson * r1896 ubiquity/ (configure configure.ac debian/changelog): * configure.ac: Bump required GTK version to 2.10.0.
[02:34] <CIA-4> ubiquity: cjwatson * r1897 ubiquity/debian/changelog: clarify
[02:37] <evand> cjwatson: quite the late night
[02:44] <cjwatson> can't sleep due to bunged-up respiratory system
[02:44] <cjwatson> about to try again
[02:56] <evand> ouch, feel better
[02:20] <secureboot_> when i try to build_monolithic, i get errors about elilo-installer not being installable since firmware-modules can't be installed - why is this happening, and what can I do to fix it?  Is it just the case that no one else is building CDs?  It doesn't seem to be related to anything I'm doing...
[02:33] <secureboot_> actually, i added elilo-installer - to the exclude file of monolithic, with good results
[02:33] <secureboot_> so far
[02:33] <secureboot_> the README should reflect that the minus sign must go in the exclude file, not places like pkg-list/standard-udebs
[02:54] <secureboot_> well, it worked, but the install kernel has no modules - i think that i removed -generic from the build targets in the kernel, and 386 is what was used in the installer - the mismatch resulted in nothing usable
[02:54] <secureboot_> consequently, i'm starting again from scratch, doing nothing different
[02:54] <secureboot_> different than normal, that is
[02:55] <secureboot_> the one piece of advice I'd really like, however, is how to avoid building so many targets in the dpkg-buildpackage when building an ubuntu kernel from source
[02:55] <cjwatson> monolithic could easily be broken; it's not used for normal CD builds
[02:55] <cjwatson> kernel targets> #ubuntu-kernel not here
[02:58] <secureboot_> ah, thanks
[02:58] <secureboot_> just FYI - putting elilo-installer in exclude built
[02:59] <secureboot_> is there some other way, other than monolithic, of easily building a CD?  I tried netboot, but got openoffice dependancy problems instead
[04:19] <cjwatson> easiest way's to customise an existing CD and use the cdrom target if you need to rebuild the initrd - but otherwise start with http://people.ubuntu.com/~cjwatson/bzr/cdimage/mainline/ (and check out the subsidiary bits in configs/devel) for the full scary CD-building kit which is really hard to set up
[05:00] <saispo> hi
[05:00] <saispo> cjwatson: your exact Name is Colin Watson ?
[05:01] <cjwatson> yes (use /whois)
[05:01] <saispo> ok, thanks
[05:01] <saispo> because i write a doc about the work i made, and i need your Name for it :)
[05:42] <secureboot_> cjwatson: i've already done the customization - i just need to replace the kernel and initrd on the iso, as well as the kernel-module udebs
[05:42] <secureboot_> cjwatson: does that require the debian-cd approach?
[05:48] <cjwatson> secureboot_: no, see the customization howto somewhere on help.ubuntu.com/community which I believe describes this
[05:49] <secureboot_> cjwatson: hmmm - i've seen, used, digested, and understood the InstallCDCustomization page - it mentions nothing about replacing the kernel debs, udebs
[05:49] <secureboot_> cjwatson: did you mean something else?
[05:50] <secureboot_> https://help.ubuntu.com/community/InstallCDCustomization
[05:50] <cjwatson> it's just the same as replacing any other package ...
[05:50] <secureboot_> that's the one I think i fully understand...
[05:50] <cjwatson> it tells you how to regenerate the Packages and Release files, which is the hard bit
[05:50] <secureboot_> cjwatson: okay - you at least have to replace vmlinuz and initrd on the cd
[05:50] <cjwatson> yeah, that's trivial though, just shove the new files in place
[05:50] <secureboot_> cjwatson: in addition to what's on that page
[05:51] <secureboot_> cjwatson: okay - i'll see if i can figure out where to put the new udebs
[05:51] <secureboot_> cjwatson: or are they necessary?
[05:51] <cjwatson> yes
[05:51] <secureboot_> cjwatson: what are they used for, exactly?  Just to let the installer load modules?
[05:52] <secureboot_> cjwatson: huh - they have to go in the appropriate places in pool/, huh?
[05:52] <secureboot_> cjwatson: i suppose that makes sense...
[05:53] <secureboot_> cjwatson: so - to sum up - build custom kernel (not covered here), take resulting udebs/debs, shove them in the right place in the pool, replace vmlinuz/initrd, make CD as normal?
[05:53] <secureboot_> this regenerates packages/releases via apt-ftparchive...
[06:19] <cjwatson> secureboot_: the kernel udebs provide kernel modules in ways that the installer can use
[08:00] <secureboot_> hmmm, 4 hours later i'm still compiling...
[08:00] <secureboot_> just the kernel though - wish I could find some docs about that