[12:09] <Erick> hi need some help with installing from HD (NOT CDROM). Is this the right channel?
[12:09] <Erick> to discuss?
[06:26] <tepsipakki> cjwatson: yay, gfxboot works now?
[08:23] <superm1> cjwatson, I wrote a patch for https://bugs.launchpad.net/mythbuntu/+bug/130445 in my branch at https://code.launchpad.net/~mythbuntu/ubiquity/mythbuntu-ubiquity if you would be able to look at it and possibly merge
[08:26] <tepsipakki> cjwatson: so it seems.. sleep well :)
[10:02] <cjwatson> tepsipakki: yeah. please check whether new gfxboot patches change APIs all over the place in future :)
[10:06] <cjwatson> it had interesting knock-on effects all the way into the theme font and stuff
[10:15] <cjwatson> superm1: looks great to me, more or less exactly how I'd have done it
[10:16] <CIA-20> ubiquity: cjwatson * r2169 ubiquity/ (9 files in 6 dirs): merge from Mario
[10:46] <tepsipakki> cjwatson: I'll be very careful even when thinking of starting to merge syslinux/gfxboot in the future :)
[04:24] <tepsipakki> cjwatson: by the way, dapper installation with the new debconf worked just fine
[04:25] <cjwatson> great
[05:28] <CIA-20> ubiquity: cjwatson * r2170 ubiquity/ (debian/changelog scripts/install.py):
[05:28] <CIA-20> ubiquity: * Run apt's DoInstall() method with stdin redirected from /dev/null, to
[05:28] <CIA-20> ubiquity:  stop it hijacking the debconf protocol (LP: #130843).
[06:17] <CIA-20> ubiquity: cjwatson * r2161 tribe-4/ (debian/changelog scripts/install.py): cherry-pick r2170 from trunk
[06:24] <CIA-20> ubiquity: cjwatson * r2162 ubiquity/ (d-i/manifest debian/changelog):
[06:24] <CIA-20> ubiquity: * Automatic update of included source packages: apt-setup 1:0.21ubuntu2,
[06:24] <CIA-20> ubiquity:  base-installer 1.81ubuntu1, partman-auto 69ubuntu5.
[06:25] <cjwatson> (that was really the tribe-4 branch)
[06:28] <CIA-20> ubiquity: cjwatson * r2163 tribe-4/debian/changelog: releasing version 1.5.7
[06:41] <CIA-20> ubiquity: cjwatson * r2171 ubiquity/ (d-i/manifest debian/changelog): merge tribe-4 branch
[06:43] <superm1> i'm a bit confused, was this tribe-4 branch just made for doing the tribe 4 release?
[06:47] <evand> superm1: yes, there were changes to ubiquity that were in bzr but were not released as a version.  As they were somewhat large, it was decided they should not be included for tribe-4.
[06:47] <evand> At least that's what my understanding was
[06:47] <superm1> i see
[06:47] <superm1> well that's sensible
[07:07] <cjwatson> correct
[07:07] <cjwatson> pitti told me to do it. :)
[08:05] <superm1> cjwatson, so is the plan to do some incremental testing releases with the bigger changes right after tribe-4 but before tribe-5 in the form of dailies?
[08:07] <evand> superm1: Can you clairfy that?  Daily CD images are always built.  Do you mean daily images tagged with specific features and announced to the community?
[08:07] <superm1> evand, i mean incremental testing releases of ubiquity in the dailies
[08:08] <superm1> for testing/showing those "bigger" changes to ubiquity
[08:10] <evand> I'm sorry, I'm having a really hard time understanding people today.  If you mean additional releases of Ubiquity between now and Tribe-5 that include the changes that didn't make it into Tribe-4 as well as changes that have occurred since then, then yes, we will do that.
[08:10] <superm1> yea that's what i had meant :)
[11:41] <superm1> cjwatson, in the tribe 4 release, were any of the mythbuntu frontend changes added in?
[11:46] <cjwatson> no, I'm afraid not
[11:46] <cjwatson> I explicitly branched to avoid all the churn that hadn't been uploaded yet
[11:46] <cjwatson> they'll go in in the next upload, which will be well before tribe-4
[11:46] <cjwatson> err
[11:46] <cjwatson> well before tribe-5
[11:47] <superm1> oh ok.  well i'll make sure to upload to our 3rd party repo then until then
[11:48] <superm1> we're  lagging behind by about 2-3 weeks on our alphas anyhow, so that will work out well