[00:41] <CIA-4> debian-installer-utils: cjwatson * r672 ubuntu/ (7 files in 3 dirs): merge from Debian 1.67
[00:46] <CIA-4> debian-installer-utils: cjwatson * r673 ubuntu/list-devices: update list-devices usage message for mmc-partition
[00:48] <CIA-4> debian-installer-utils: cjwatson * r674 ubuntu/debian/changelog: releasing version 1.67ubuntu1
[02:13] <CIA-4> debian-installer: cjwatson * r1089 ubuntu/ (5 files in 2 dirs): Move mainline architectures to 2.6.30-1 kernels.
[02:16] <CIA-4> debian-installer: cjwatson * r1090 ubuntu/ (build/config/common debian/changelog debian/rules): Set default suite to karmic.
[02:18] <CIA-4> choose-mirror: cjwatson * r613 ubuntu/debian/ (changelog choose-mirror-bin.templates-in): Switch to karmic by default; drop gutsy from the list of suite choices.
[02:20] <CIA-4> choose-mirror: cjwatson * r614 ubuntu/debian/changelog: releasing version 2.28ubuntu2
[05:30] <maxagaz> In the preseed, at the line: "tasksel tasksel/first multiselect standard, ubuntu-desktop", where is ubuntu-desktop defined ?
[09:24] <cjwatson> maxagaz: tasksel
[11:00] <CIA-4> rootskel: cjwatson * r340 ubuntu/ (debian/changelog debian/rules src/init): merge from Debian 1.76
[12:22] <CIA-4> partman-auto: cjwatson * r291 ubuntu/ (90 files in 25 dirs):
[12:22] <CIA-4> partman-auto: Merge from Debian 85.
[12:22] <CIA-4> partman-auto: Drop relatime from autopartitioning recipes; it's the default in Linux 2.6.30.
[12:24] <CIA-4> partman-auto: cjwatson * r292 ubuntu/debian/po/ (ast.po kk.po): msgmerge new translations
[12:27] <CIA-4> partman-auto: cjwatson * r293 ubuntu/debian/changelog: releasing version 85ubuntu1
[13:37] <CIA-4> base-installer: cjwatson * r365 ubuntu/ (5 files in 4 dirs): Use -ia64 kernel across the board on ia64.
[16:03] <cybydude>  :) hi folks!
[16:07] <davmor2> Hello
[16:16] <cybydude> hi cjwatson
[16:16] <cybydude> greets tp all
[16:16] <cybydude> i mean greets to all
[16:16] <cybydude> basically, am trying to develop an integrated installer for a customised version of slax
[16:16] <cybydude> i found ubiquity sort of approach very ideal
[16:16] <cybydude> especially the partioning part
[16:17] <cybydude> so i was wondering, how do i go about compiling it
[16:17] <cybydude> and customising it
[16:19] <cjwatson> well, start by learning how to build Debian-format source packages in general
[16:20] <cjwatson> the debuild(1) tool in the devscripts package is a reasonable starting point
[16:20] <cjwatson> ubiquity is really really STRONGLY dependent on other things in Ubuntu though
[16:20] <cjwatson> so you may find it pretty difficult going if the underlying distribution differs much at all
[16:20] <cjwatson> there's a doc/README file in the ubiquity source package with some initial guidance
[16:21] <cybydude> thanks a lot for the information. i had gone through the the README and a couple of wiki articles.
[16:22] <cybydude> atleast to begin with, can u please tell me how to compile ubiquity from source in jaunty
[16:22] <cjwatson> I thought I just did
[16:22] <cjwatson> get the source package and use the debuild tool
[16:22] <cybydude> sorry. i tried ./configure and ended up with error
[16:22] <cjwatson> yeah, don't do that :)
[16:22] <cybydude> regarding pygtk2 not being found tha
[16:23] <cjwatson> 'sudo apt-get build-dep ubiquity' will help ... but (unfortunately) you still can't build ubiquity using the traditional ./configure && make approach, sorry. you have to use the Debian build system for it
[16:23] <cybydude> ok. i think i got it.
[16:23] <cjwatson> I realise it's confusing because it looks as though you can build it like that
[16:24] <cybydude> if u dont mind , can u briefly mention how do we go about using the debian build system - any link / pointer would do.
[16:24] <cjwatson> debuild
[16:24] <cybydude> ok.
[16:24] <cjwatson> it's in the devscripts package, and it has a manual page
[16:25] <cjwatson> you probably want to use 'debuild -b' to build just binaries, and to avoid
[16:25] <cjwatson> err, ignore "and to avoid"
[16:25] <cybydude> thanks a lot for your time. one last question - is it possible to only build a part of ubiquity - for eg just partioning
[16:25] <cjwatson> afraid not, it's pretty monolithic
[16:25] <cjwatson> it'd be a lot of work to split that out
[16:26] <cybydude> thanks.
[16:26] <cybydude> any other better way u can think of - for my probs (slax installer)?
[16:26] <cjwatson> ubiquity builds on "d-i", the Debian installer, which is very modular; but most of the UI is implemented in the ubiquity layer, and not in a modular way
[16:27] <cjwatson> distributions tend to build installers themselves, IME :-)
[16:27] <cjwatson> the reusability is mostly in things like libparted
[16:27] <cjwatson> I'm not sure this is the way it ought to be, but it seems to be the way it is at the moment
[16:27] <cybydude> thanks a lot cj.
[16:27] <cjwatson> sorry I can't help further
[16:27] <cybydude> very kind of you to have spared ur time.
[16:27] <cybydude> good day to you.
[16:36] <cjwatson> if you wanted to get ubiquity running exactly as-is, you'd probably have to start by getting a live CD working with casper or something extremely similar, and also get debconf ported
[16:37] <cjwatson> ubiquity kind of expects dpkg and apt at the moment, so you'd need to port from that if you're using a different package management system, and figure out how to get progress information and such through
[16:37] <cjwatson> the build system is inextricably wedded to debhelper
[16:38] <cjwatson> things like console keymap setup and the like would need to be ported to whatever your target uses - it might actually be easiest to keep on using console-setup in ubiquity and maybe just have it spit out different files on the target system if that's needed
[16:39] <cjwatson> the partitioner might actually be one of the easiest bits, although in order to use it you'd have to figure out how to port the rest
[16:39] <cjwatson> definitely a head-scratcher until you've made yourself very familiar with debconf though :-
[16:39] <cjwatson> :-)
[16:39] <cjwatson> cybydude: ^-
[16:44] <CIA-4> base-installer: cjwatson * r366 ubuntu/ (45 files in 8 dirs): merge from Debian 1.99
[16:50] <CIA-4> base-installer: cjwatson * r367 ubuntu/kernel/tests/armel/ (qemu-versatilepb.test sheevaplug.test): update new tests for Ubuntu
[16:54] <CIA-4> base-installer: cjwatson * r368 ubuntu/debian/changelog: releasing version 1.99ubuntu1
[17:14] <CIA-4> netcfg: cjwatson * r635 ubuntu/ (20 files in 3 dirs): merge from Debian 1.48
[19:20] <NCommander> cjwatson, I have a patch for libdebian-installer on SPARC (to resolve the FTBFS), although I'm not sure if I should also fix the fputs lines as well (they don't trigger a warning, but they look wrong to me unchecked)
[19:20] <NCommander> https://bugs.edge.launchpad.net/ubuntu/+source/libdebian-installer/+bug/369439
[19:20] <ubottu> Launchpad bug 369439 in libdebian-installer "Please merge SPARC FTBFS fixes onto libdebian-installer" [Undecided,New]
[19:49] <alex_joni> if I create a custom apt source list (located in /etc/apt/sources.list.d) on the LiveCD, does it get copied over on the installed CD?
[19:49] <alex_joni> (I found that it did, but can't quite locate where this happens. and since I have used a /usr/lib/ubiquity/apt-setup/generators/* custom generator, I ended up with twice the info)
[19:50] <alex_joni> should I just remove the generator I wrote, and trust that the file from sources.list.d/ gets copied over every time?
[22:20] <cjwatson> NCommander: no, please don't
[22:20] <NCommander> cjwatson, ?
[22:20] <cjwatson> NCommander: I intentionally removed the fwrite checks because (a) they're horribly ugly and (b) current glibc no longer needs them - the reason that libdebian-installer FTBFS on sparc is that glibc hasn't built on sparc for the last three revisions
[22:21] <NCommander> Oh
[22:21] <cjwatson> so the right thing to do is to fix glibc
[22:21] <cjwatson> alex_joni: if the file is in the live filesystem, it'll get copied along with everything else
[22:22] <NCommander> cjwatson, ew, sorry, I was unaware that glibc was FTBFSing :-/
[22:22] <cjwatson> NCommander: I mentioned it on IRC a few days ago and tried to highlight you, I think
[22:23] <NCommander> cjwatson, must have missed the ping :-/
[22:23] <cjwatson> NCommander: http://irclogs.ubuntu.com/2009/04/28/%23ubuntu-devel.html and search for glibc
[22:24] <NCommander> cjwatson, completely missed that ping
[22:35] <CIA-4> netcfg: cjwatson * r636 ubuntu/debian/changelog: releasing version 1.48ubuntu1
[22:47] <alex_joni> cjwatson: cool, thanks
[22:52] <cjwatson> alex_joni: of course if you don't want it to be copied then there are ways around it, but it sounds as if this is actually the best behaviour from your POV
[22:53] <alex_joni> yup, it is
[22:53] <alex_joni> around dapper I wasn't aware of the sources.list.d, so I added a apt-setup generator
[22:53] <alex_joni> and on hardy I did the same as for dapper :)
[23:36] <CIA-4> rootskel: cjwatson * r341 ubuntu/debian/changelog: releasing version 1.76ubuntu1
[23:51] <alex_joni> cjwatson: thanks again, I'll test the fresh CD tomorrow, but I bet it works as it should