[12:12] <Ubunter> hello
[12:31] <superm1> evand, i'm back around if you got a chance to look at my branch now
[10:06] <superm1> evand, i solved the page skipping problem tonight! i pushed it up to the ~mythbuntu branch.  would you be able to merge me and do a release with my set of changes?  We wanted to prepare our next disk for the next mythbuntu alpha release this coming weekend, so it'd be nice to be able to use the builds off ubuntu rather than a PPA/personal repo for it.
[01:42] <JD> cjwatson: I've rebuilt d-i, but it hasn't picked up the new module
[01:42] <cjwatson> check its build output to make sure it really used the one from localudebs rather than downloading
[01:43] <JD> okay
[01:43] <JD> is it looking for a particular version of the udebs?
[01:44] <cjwatson> no
[01:44] <cjwatson> might be looking for a particular kernel ABI though, so make sure yours matches
[01:44] <cjwatson> the 2.6.15-<number> part of the package name
[01:45] <JD> yeah, that's what I'm thinking
[01:46] <cjwatson> s/might be/is definitely/
[01:46] <JD> it's looking for -26. not sure what the kernel I built is
[01:47] <cjwatson> the version of d-i you're building should have come from the same place (dapper vs. dapper-proposed vs. dapper-updates) as the kernel source you based your work on
[01:48] <JD> -23
[01:48] <JD> so I think I've used the wrong one
[01:48] <JD> okay
[01:48] <cjwatson> but worst case, just grep for 2.6.15-23 in build/config/ and change all those to 2.6.15-<whatever you built>
[01:50] <JD> nah, my d-i was from dapper-proposed
[01:50] <JD> using the one from dapper should work
[01:54] <JD> w00t that worked. cheers
[03:32] <evand> superm1: looking over the changes now
[04:04] <saispo> hi
[04:05] <saispo> cjwatson: i try to generate a custom cd but i have an error with debootstrap, apparently, some packages in scratch/1.packages file are not present, such as bash or something else. Which program generate 1.packages for example ?
[04:06] <saispo> Missing debootstrap-required bash
[04:06] <saispo> Missing debootstrap-required bsdutils
[04:06] <saispo> for example
[04:07] <saispo> i have no problem when i try to generate a feisty cd
[04:12] <CIA-20> ubiquity: evand * r2197 ubiquity/ (31 files in 5 dirs): Merged with ubiquity.mythbuntu
[04:13] <evand> superm1: skip_pages scares me somewhat, but I can't think of a better solution right now, short of turning on --automatic, which is less than ideal.
[04:14] <evand> if we don't have any other changes by the end of the day, and there are no objections, I'll put out a new release tonight.
[04:17] <cjwatson> saispo: usually means the Priority fields in the Packages files in your archive are bust
[04:17] <evand> actually, hrm
[04:18] <saispo> cjwatson: i merge with your repos today...
[04:19] <saispo> my ubuntu repository is up2date too
[04:21] <cjwatson> I'm sorry, there is no reasonable way for me to debug your setup from here; it works for us
[04:21] <evand> superm1: if I have some free time I'm going to play around with this a bit.  I'm not seeing why you can't just handle everything in set_page, but I'm sure I'm missing something obvious.  I wont hold up the release though.  I'm assuming you've tested this, right?
[04:22] <saispo> Package: bash
[04:22] <saispo> Essential: yes
[04:22] <saispo> Priority: required
[04:23] <saispo> cjwatson: i generate the cd on the feisty for a gutsy, it may be this or not ?
[04:24] <cjwatson> no. we generate all our CDs on edgy at the moment.
[04:24] <cjwatson> I'm sorry but you're going to have to dig into this yourself
[04:25] <saispo> i will :)
[05:44] <superm1> evand, yes i've tested it within a virtual machien
[05:44] <superm1> i cant seem to handle this all in set_page because set_page has no idea of whether this is a forward or backward request