=== ebel_ is now known as ebel === ebel_ is now known as ebel === cjwatson_ is now known as cjwatson === cjwatson_ is now known as cjwatson [06:12] evand: uploaded base-installer, with just a couple of really minor tweaks (s/Bzr-Svn/Vcs-Bzr/ and s/ubuntu-archive-keyring-udeb/ubuntu-keyring-udeb/); looks like you got all the hard stuff right though [10:11] hi [10:11] hello [12:34] hrm, does partman-auto support mountoptions{ }? I assume so, but I'm lost in a maze of twisty directories [12:34] :) [14:06] ah, thanks === cjwatson1 is now known as cjwatson [14:31] evand: I'm dropping the bug references from the top entry in the partman-crypto changelog; I think it's generally best to leave out the bug numbers there since they can result in duplicate bug closures [14:32] ah, I had thought it knew to skip those. I'll make a note of that for the future. [14:33] I think it will normally skip them but if the bug was reopened due to not having really been fixed then this could lead to it accidentally being closed again [14:34] ah, good point [14:35] uploaded, pushing branch to usual place [14:36] fantastic, thanks [14:36] I think I'm up to date on your sponsorships now, let me know if not [14:36] you are [14:37] good stuff [16:31] cjwatson: worth it to update ubiquity to hardy components, or should it block on the new apt-setup? [16:33] I'd say do it now, it can be reuploaded later [16:34] ok [16:38] ubiquity: evand * r2363 ubiquity/d-i/sources.list: gutsy->hardy [16:46] ubiquity: evand * r2364 ubiquity/ (d-i/manifest debian/changelog debian/control): (log message trimmed) [16:46] ubiquity: * Automatic update of included source packages: base-installer [16:46] ubiquity: 1.85ubuntu2, choose-mirror 2.19ubuntu1, clock-setup 0.92ubuntu1, [16:46] ubiquity: console-setup 1.19ubuntu1, debian-installer-utils 1.49ubuntu1, grub- [16:46] ubiquity: installer 1.27ubuntu1, hw-detect 1.58ubuntu1, kboot-installer [16:46] ubiquity: 0.0.1ubuntu6, localechooser 1.42ubuntu1, partconf 1.24, partman-auto [16:46] ubiquity: 70ubuntu1, partman-base 111ubuntu1, partman-basicfilesystems [16:53] and here I was hoping to get CIA-4 kicked for excess flood. It seems he's smarter than that. [16:55] ubiquity: evand * r2365 ubiquity/debian/po/ (79 files): debconf-updatepo [17:09] apparently old ubiquity actually installs fine (#ubuntu-devel) [17:09] wasn't expecting that [17:10] yeah, it did for me as well [17:10] though I didn't check the sources.list [17:10] as I was just doing it to make sure it didn't explode when I updated the d-i components [17:10] erm, to make sure it worked before I did that step, that is [17:20] ubiquity: evand * r2366 ubiquity/debian/changelog: releasing version 1.7.0 [17:22] cjwatson: Whenever you have a moment, please sponsor http://people.ubuntu.com/~evand/upload/ubiquity_1.7.0.dsc [17:33] bah, guess partman-auto doesn't cope with mountoptions :( [17:34] thom: it does, the syntax is different though [17:34] I think you have to do mountoptions/noatime{ } [17:34] etc. [17:35] hmm, no, not quite that [17:35] options/noatime{ } I think [17:36] ubiquity uploaded [17:36] thanks [17:36] thom: sorry, I'd missed your question earlier [17:36] cjwatson: no worries [17:36] thanks [17:37] that's remarkably odd syntax :) [17:38] recipe syntax exactly mirrors the structure of /var/lib/partman/devices/ [17:38] hence the oddness [17:38] ahah! [17:38] thanks [18:02] uh oh [18:02] ? [18:03] /usr/lib/ubiquity/clock-setup/clock-setup: 35: tzsetup not found [18:04] whoops [18:08] yeah, tzsetup no longer provides a menu item and clock-setup calls it instead [18:09] hrm [18:09] that's, err, sort of tricky [18:09] maybe for now sed clock-setup.postinst to comment out the tzsetup call and figure it out later? [18:10] yeah, I noticed [18:10] we have scripts/tzsetup [18:10] I think it needs some thought about what order to do everything in, since we call tzsetup way earlier [18:10] right [18:10] if it's calling tzsetup at all, it should be sedded to call that [18:10] you could try making it call that and see if it works? [18:10] will do [18:10] so s,tzsetup,/usr/share/ubiquity/tzsetup, [18:11] probably won't work well though, since that resets the timezone [18:11] so doing that from clock-setup will lose the timezone configured earlier, unless you stash it in the component and shove it back in [18:12] might work better without calling tzsetup from clock-setup at all [18:13] ok, I'll try both [18:13] well [18:13] I'll do it without calling tzsetup first [18:52] cjwatson: http://pastebin.ubuntu.com/2362/ - look ok to you? [18:52] I've already tested it. [18:52] looks correct for what it does, if it works, go for it [18:52] fantastic [18:54] ubiquity: evand * r2367 ubiquity/ (configure configure.ac): bump to 1.7.1 [18:58] ubiquity: evand * r2368 ubiquity/debian/ (changelog rules): [18:58] ubiquity: * clock-setup in d-i now explicitly calls tzsetup, but we handle tzsetup [18:58] ubiquity: earlier on, so remove the tzsetup call in clock-setup. [19:08] ubiquity: evand * r2369 ubiquity/debian/changelog: releasing version 1.7.1 [19:11] cjwatson: http://people.ubuntu.com/~evand/upload/ubiquity_1.7.1.dsc whenever you have a moment. [19:16] uploading, thanks [19:16] thank you