[11:55] <saispo> anyone can give me some help for building live cd ?
[11:55] <saispo> i have this error :
[11:55] <saispo> No filesystem for i386!
[11:55] <saispo> ln: accessing `/home/eole/mirror/cdimage/scratch/eolefeisty/daily-live/live/i386.manifest': No such file or directory
[11:55] <saispo> ln: accessing `/home/eole/mirror/cdimage/scratch/eolefeisty/daily-live/live/i386.manifest-desktop': No such file or directory
[11:56] <saispo> mv: cannot stat `/home/eole/mirror/cdimage/scratch/eolefeisty/daily-live/tmp/feisty-i386/CD1/casper/filesystem.kernel-generic': No such file or directory
[11:56] <saispo> make: *** [/home/eole/mirror/cdimage/scratch/eolefeisty/daily-live/tmp/feisty-i386/bootable-stamp]  Error 1
[11:56] <saispo> ERROR WHILE BUILDING OFFICIAL IMAGES !!
[11:56] <saispo> thanks
[02:01] <cjwatson> saispo: you have to put the filesystem and auxiliary files somewhere appropriate; it would be easiest to read the source, really (grep for the tails of some of the files mentioned in your error messages)
[02:02] <cjwatson> evand: if you haven't noticed, gutsy live CDs are up
[02:02] <cjwatson> I'm grabbing one now to see how broken ubiquity is
[02:02] <saispo> cjwatson: ok thanks, i try to build a livecd
[02:02] <saispo> i will test this
[02:03] <evand> cjwatson: just got up, so I hadn't noticed :).  Downloading now.
[02:04] <cjwatson> saispo: have you read the customisation howto on help.ubuntu.com/community?
[02:04] <cjwatson> we haven't published the live filesystem build script yet (although we will soon), so presumably you're customising rather than building-from-scratch at some level anyway
[02:04] <saispo> not at this time, i just launch the command i already launch to build my custom alternate cd
[02:04] <cjwatson> ok, I suggest reading the customisation howto
[02:05] <cjwatson> we are not yet in a position where cdimage can build a whole live CD for you from scratch.
[02:07] <saispo> will read, will try to adapt
[02:07] <saispo> you think ubiquity is more appropriate ?
[02:08] <tepsipakki> cjwatson: was the gtk-frontend functional yet?
[02:08] <tepsipakki> for the alternative installer
[02:12] <cjwatson> saispo: err - that's not relevant
[02:12] <cjwatson> tepsipakki: functional (in Debian, at any rate), but not pretty
[02:12] <cjwatson> saispo: ubiquity has nothing much to do with actually building the live filesystem/CD, aside from being one of the components that goes into it
[02:13] <saispo> k
[02:14] <saispo> i will investigate how to build a live-cd from debian-cd
[02:14] <saispo> thanks
[02:15] <cjwatson> you cannot
[02:15] <saispo> ok
[02:15] <cjwatson> the code to build the live filesystem is not there
[02:15] <saispo> ok, will wait about you ? :)
[02:15] <tepsipakki> cjwatson: ok, but not in gutsy?
[02:15] <cjwatson> as I said above, we're still in the process of publishing the code we use (sorry)
[02:16] <cjwatson> there are other tools like live-helper or the gnewsense builder which may be able to do it with a bit of tweaking
[02:16] <cjwatson> tepsipakki: no, I was going to but it would have taken quite a few main inclusion reports and I didn't have the energy or time at that point
[02:19] <tepsipakki> cjwatson: ah, ok :)
[02:22] <saispo> cjwatson: i will wait your script, i prefer
[02:40] <evand> cjwatson: still failing to find the loop device for me
[02:40] <evand> the daily-live, that is
[02:42] <cjwatson> evand: hmm, hadn't heard of that problem
[02:43] <cjwatson> fancy digging into casper?
[02:43] <evand> heh, I shall give it a shot, but I'm not sure how to test that, short of remastering the cd
[02:43] <cjwatson> that's about all you can do
[02:44] <cjwatson> oh, well
[02:44] <cjwatson> if it's a simple-ish change, you can boot with break=top and edit the script on the fly
[02:44] <evand> neat, ok
[02:44] <cjwatson> you might have to edit it with sed; the initramfs isn't exactly set up for decent editing
[02:49] <evand> oh and fyi, it's bug 118561
[02:54] <cjwatson> "//filesystem.squashfs" is suspicious; that should be /casper/filesystem.squashfs
[02:58] <cjwatson> ah no, red herring
[03:01] <cjwatson> pretty odd, looks like the loop module isn't being loaded properly or something
[03:02] <evand> hrm
[03:03] <cjwatson> or maybe some kind of race condition
[05:13] <CIA-19> ubiquity: cjwatson * r2072 ubiquity/ (3 files in 2 dirs): * Remove stray references to ubiquity.settings.
[05:14] <saispo> cjwatson: i read the "builder" of gnewsense, it's based on dapper
[05:17] <CIA-19> ubiquity: cjwatson * r2073 ubiquity/ (bin/ubiquity debian/changelog):
[05:17] <CIA-19> ubiquity: * Restore distribution() function used by bin/ubiquity, previously in
[05:17] <CIA-19> ubiquity:  ubiquity.misc.
[05:18] <cjwatson> saispo: yes
[05:23] <CIA-19> ubiquity: cjwatson * r2074 ubiquity/ (bin/ubiquity debian/changelog):
[05:23] <CIA-19> ubiquity: * Clean up some breakage from ubiquity.misc.ex -> ubiquity.misc.execute
[05:23] <CIA-19> ubiquity:  renaming.
[05:31] <CIA-19> ubiquity: cjwatson * r2075 ubiquity/ (d-i/manifest debian/changelog):
[05:31] <CIA-19> ubiquity: * Automatic update of included source packages: console-setup 1.16ubuntu2,
[05:31] <CIA-19> ubiquity:  partman-partitioning 50ubuntu1, silo-installer 1.10ubuntu2.
[05:37] <CIA-19> ubiquity: cjwatson * r2076 ubiquity/debian/changelog: releasing version 1.5.1
[06:51] <CIA-19> ubiquity: evand * r1501 ma/ (debian/changelog ubiquity/components/summary.py): * Make sure the summary question regex gets split properly.
[06:51] <evand> there's more
[07:26] <CIA-19> ubiquity: evand * r1502 ma/ (debian/changelog ubiquity/frontend/base.py): * Fix typo in base frontend get_summary_device stub.
[07:40] <evand> hrm, /etc/default/console-setup has disappeared.
[08:39] <jetsaredim> cjwatson: ping
[08:39] <jetsaredim> have some questions about how my changes should be setup
[08:44] <jetsaredim> basically, I have about 5 pages to add to the installer for mythtv-related installations
[08:46] <jetsaredim> the first page is something like: "would you like the typical mythtv install or custom"
[08:49] <jetsaredim> and I'd like to be able to have the installer skip the rest of the pages if the user selects the default install
[08:50] <jetsaredim> the other thing is that there are already meta-packages for the different types of installs
[08:54] <evand> as soon as I can figure out what's causing that console-setup bug we'll have a fully functional installer (I skipped over it and the rest of the install completed just fine)
[09:33] <CIA-19> ubiquity: evand * r1503 ma/ (7 files in 5 dirs): Forgot to merge with trunk.
[11:13] <cjwatson_> jetsaredim: have on_next_clicked go to the page you want, and conversely on_back_clicked
[11:13] <jetsaredim> yep got it
[11:13] <jetsaredim> actually
[11:13] <cjwatson> sorry, weird network glitch
[11:13] <jetsaredim> i asked all of these questions and someone else on the mythbuntu team had already done most of it
[11:13] <jetsaredim> anyway
[11:14] <jetsaredim> i asked evand to take a look at the changes, but you're more than welcome to as well
[11:53] <cjwatson> evand: I think I might see the console-setup bug
[11:53] <cjwatson> <cjwatson@cairhien ~/src/ubuntu/console-setup>$ tail -n1 console-setup-1.13ubuntu14/debian/config.proto
[11:53] <cjwatson> fi
[11:53] <cjwatson> <cjwatson@cairhien ~/src/ubuntu/console-setup>$ tail -n1 console-setup-1.16ubuntu2/debian/config.proto
[11:53] <cjwatson> exit 0
[11:53] <cjwatson> 'exit 0' there is bad - it exits the postinst too
[11:53] <cjwatson> evand: yep, hack that off the end of /var/lib/dpkg/info/console-setup.config and it should work fine
[11:55] <cjwatson> fixed in console-setup 1.16ubuntu3
[11:55] <cjwatson> evand: push your branch and I can merge from it if you like