=== cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk]  has joined #ubuntu-installer
=== superm1 [n=superm1@ubuntu/member/superm1]  has joined #ubuntu-installer
=== cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk]  has joined #ubuntu-installer
[12:10] <tepsipakki> cjwatson, evand: I noticed that if universe/multiverse are enabled, the generated sources.list does not contain an -updates entry for them
[12:10] <tepsipakki> I'll make a patch for apt-setup to fix that
[12:13] <cjwatson> tepsipakki: I noticed the discussion in #ubuntu-devel and already fixed it in my tree
[12:13] <cjwatson> tepsipakki: did you file a bug?
[12:13] <tepsipakki> cjwatson: heh, no :)
[12:13] <tepsipakki> thanks
[12:13] <cjwatson> ok, sorry, beat you to it then ;)
[12:14] <cjwatson> (will leave it to you next time)
[12:14] <tepsipakki> haha
[12:14] <tepsipakki> the result is what matters ;)
[02:21] <glledo> uops, I've got ubiquity to install with partman-crypto, but obviously doesn't boot :P
[02:26] <cjwatson> if it needs to install tools not in the live filesystem then you need to make sure they're at least in the apt archive on the CD
[02:28] <glledo> Im checking that now
[02:29] <glledo> I think dmsetup is removed at the end of the installation, for instance
[02:30] <cjwatson> quite possible unless something apt-installs it
[02:31] <cjwatson> (apt-install is a d-i command to have packages installed in the target system; in ubiquity, there's a shim to have it arrange to keep packages from the live filesystem installed even if they aren't in desktop, or install them if they weren't in the live filesystem)
[02:31] <glledo> anyway, ill try now to chroot to the system, install the needed stuff and see if it can boot
[02:32] <glledo> ok, thanks for the info
=== cr3_ [n=marc@modemcable178.77-70-69.static.videotron.ca]  has joined #ubuntu-installer
[03:39] <tepsipakki> hmm, gutsy install fails with gnupg-doc claiming "can't read doc-base file 'gnu-privacy-handbook'"
[03:40] <cjwatson> silly gnupg-doc.
=== avoine [n=avoine@69.70.0.36]  has joined #ubuntu-installer
[03:59] <tepsipakki> so there's a bug in gnupg-doc postinst?
[04:04] <tepsipakki> or in doc-base
[04:05] <cjwatson> sounds like it, but haven't looked
[04:06] <tepsipakki> yep, debian bug 425351
[04:08] <tepsipakki> seems like the files should generally have full paths now
[04:14] <tepsipakki> mind if I upload a new version?
[04:15] <tepsipakki> doesn't seem like it's going to be fixed in debian anytime soon :)
[04:21] <tepsipakki> uploaded
=== cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk]  has joined #ubuntu-installer
[04:42] <cr3> when making build_monolithic in the gutsy debian installer, I get a bunch of missing *-modules packages
[04:52] <cjwatson> if you're building against any set of kernel images other than gutsy, that's expected
[04:52] <cjwatson> the kernel udebs get rearranged every so often and I can only track whatever's current
[04:56] <cr3> cjwatson: I'm building against 2.6.22-9-generic
[04:57] <cr3> cjwatson: I suspect this is the directory where the packages should be retrieved from and *-modules aren't there: http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.22/
[04:58] <cr3> cjwatson: evand mentionned that the *-modules might've been replaced by fs-core-modules
[04:58] <cr3> however, the partman-basicfilesystems package depends on ext2-modules which can't seem to be found anywhere
[05:01] <cjwatson> Provides
[05:01] <cjwatson> though you're right, it's not provided by anything right now, that's a bug
[05:02] <cjwatson> I'll send a patch for the next kernel release
[05:06] <cr3> cheers, I'll be using feisty in the meanwhile which has the same problem but which I hopefully fixed by creating my own partman-basicfilesystems udeb which depends on fs-core-modules
[05:07] <cjwatson> should be fine
[05:07] <cjwatson> rescue-mode too if monolithic uses that
[05:07] <cjwatson> (this is just one of the many reasons I recommend against monolithic though
[05:07] <cjwatson> )
[05:16] <cr3> you'll now have to modulo fabbione and me on monolithic :)
[05:17] <cjwatson> anyway https://lists.ubuntu.com/archives/kernel-team/2007-August/001617.html should fix it when it gets applied
[05:17] <cjwatson> but only for filesystem modules; if there's anything else that's breaking then maybe d-i needs to be fixed
=== superm1 [n=superm1@ubuntu/member/superm1]  has left #ubuntu-installer ["Leaving"] 
[06:36] <cr3> that's weird, I just modified the preseed file of the installer and now I'm getting 'cdrom-detect' failed. maybe a faulty burn
[06:40] <cr3> yep, faulty burn. hate it when that happens :(
[06:46] <cr3> I'm getting "No root file system is defined" for feisty even though I have this line in my preseed: d-i partman-auto/choose_recipe select All files in one partition (recommended for new users)
[06:47] <cr3> might a potential reason be that I don't have the right modules to format the partition since I removed partman-ext* packages to install fs-core-modules instead?
[07:09] <cr3> hm, I removed preseeding of the partitioning and manually selecting "All files in one partition" worked. something seems to be wrong with the preseed on feisty
=== blackskad [n=blackska@d54C4A53D.access.telenet.be]  has joined #ubuntu-installer
[08:51] <evand> argh
[08:53] <evand> Disabiling m-a for the time being when using --automatic wont work as m-a mucks with FilteredCommand.cleanup() and that doesn't work with the graceful page skipping code.
[08:53] <evand> I'll start working on fixing m-a in a bit.  I want to finish that Vietnamese bug first.
[09:24] <cr3> evand: do you happen to run debian-installer against gutsy repositories sometimes?
[09:24] <evand> cr3: what do you mean?  I use the Gutsy alternate CD images often.
[09:24] <evand> which is d-i
[09:33] <cr3> evand: heh, nevermind, I'm confused in my own little world :)
[09:34] <evand> haha
[09:34] <cr3> turns out I was encountering problems building the install initrd.gz and vmlinuz because of the corruption in the gutsy repository
[09:34] <cr3> but the problem was that my apt-cacher was corrupted
[09:35] <cr3> I suspect the problem might be that the operations of apt-cacher aren't atomic so interrupting the process corrupts the cache
[09:36] <cr3> instead of wgeting directly to the cache, it might be safer to wget in a temporary directory and the mv to the cache
[09:36] <evand> hrm
[09:36] <cr3> I should contribute to the project just to get back into perl after a few years of deprivity
[09:41] <cr3> developing against gutsy is a pain :(
[09:44] <evand> nah, you just have to dogfood it.
[09:45] <cr3> fucking hell, the repository is consistently broken
[09:46] <cr3> ... and I don't have the bandwidth to make my own non-broken repository. this is insane, I'll have to work over the weekend
[09:53] <evand> yikes
[09:55] <cr3> W: http://192.168.2.60/apt-cacher?/ubuntu-archive/dists/gutsy/main/binary-i386/Packages.gz was corrupt
[09:57] <cr3> and, a few minutes ago, the problem was with universe. so if it's not one archive, it's another. I'm reverting to feisty in the hope I'll get some work done
[09:57] <cr3> and in the hope the intel xorg driver and mesa library backports are sufficiently stable
=== cr3 apologizes for this venting
[09:58] <evand> no worries, it's amusing :)
[10:00] <cr3> evand: heh, makes me feel better there's a positive side to it :) thanks
[10:01] <cr3> evand: I'm actually running the build process for gutsy in parallel and I'm being amused myself at the different parts of the repository that spontaneously fail :)
[10:01] <evand> heh
=== SunRaycer [n=rgb@sound.tricolour.net]  has joined #ubuntu-installer
=== avoine [n=avoine@69.70.0.36]  has left #ubuntu-installer [] 
=== superm1 [i=malimonc@ubuntu/member/superm1]  has joined #ubuntu-installer
=== xivulon [n=ago@87-194-85-156.bethere.co.uk]  has joined #ubuntu-installer
=== xivulon [n=ago@87-194-85-156.bethere.co.uk]  has left #ubuntu-installer []