[09:03] <ev> persia: thanks for the heads up, I'll keep an eye on that thread
[09:05] <ev> michaelforrest: do you have a few minutes today to clarify exactly what you need in terms of the size of the installer window in Lucid?  I'm in the office, for what it's worth.
[09:05] <ev> I've managed to shrink the window down quite a bit, but there are a few caveats
[09:06] <michaelforrest> ev: absolutely
[09:06] <michaelforrest> come and find me whenever
[09:07] <ev> good deal
[09:09] <persia> ev: You might just want to catch Anzenketh in #ubuntu-bugs to plan the best strategy, depending.  Threads have a way of solidifying :)
[09:30] <ev> persia: good call :)
[09:31] <ev> persia: while I have you here, what's the smallest resolution that you guys need ubiquity to work on?
[09:32] <persia> Um, hrm.
[09:32] <persia> I don't have a good answer.
[09:32] <persia> I'd personally like 640x480, but that's not realistic.
[09:33] <persia> There are still some 800x480 devices being manufactured, and I'd say that's a more reasonable absolute smallest.
[09:34] <persia> But there's 4.8" 1024x600 screens available, so I'd like to hope that smaller stuff becomes less common, or more specialised.
[09:35] <persia> To sum up:
[09:35] <persia> If you'd like to enable running ubiquity on the N900 (or similar devices), we need 800x480.
[09:35] <ev> okay, big thanks for clearing that up
[09:36] <persia> If you want to run on the new generation of handhelds, 1024x600 is probably sufficiently low res.
[09:36] <persia> (unless manufacturers go for "cheap" over "useful" again)
[09:40] <ev> michaelforrest: is now a good time to swing by?
[09:57] <michaelforrest> ev sure
[10:00] <ev> ncdjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjkkkjkjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
[10:00] <ev> whhops
[10:00] <ev> whoops*
[10:30] <ev> cjwatson: given that we're going with the "boot straight into ubiquity and let it deal with creating a try/install page" for lucid+1, is the greeter stuff (specifically the design and artwork for it) still a priority for you?
[10:30] <cjwatson> no
[10:30] <ev> it came up in discussion with michaelforrest
[10:30] <ev> okay cool
[10:30] <cjwatson> I actually want to do this for lucid if possible
[10:30] <cjwatson> and am still tracking it in the release meetings and such
[10:30] <cjwatson> if nothing else because Mark announced it for lucid :P
[10:31] <michaelforrest> cjwatson: oh god. what ?
[10:31] <cjwatson> I have been enormously clear about this in e-mail
[10:31] <cjwatson> I cannot believe that it is a surprise
[10:32] <cjwatson> I also don't think it matters to you guys since we have the bits we need to do it now :)
[10:32] <michaelforrest> I didn't know Mark had announced something
[10:33] <michaelforrest> I thought it was still a 'nice-to-have'
[10:33] <cjwatson> at the platform briefing at UDS
[10:33] <cjwatson> it was practically the very first thing in his presentation
[10:33] <cjwatson> there's a reason this spec is Essential ...
[10:34] <cjwatson> and why I've been desperately trying to get styling information from people for months
[11:23] <CIA-3> ubiquity: evand * r3853 ubiquity/ (5 files in 4 dirs): (log message trimmed)
[11:23] <CIA-3> ubiquity: * The timezone is perfectly usable at half its width and height, so
[11:23] <CIA-3> ubiquity:  only request that. This also means we're not trying to guess how
[11:23] <CIA-3> ubiquity:  much space we can reasonably take up with the map, but rather
[11:23] <CIA-3> ubiquity:  letting the rest of the interface determine the width and height of
[11:23] <CIA-3> ubiquity:  the installer window.
[11:23] <CIA-3> ubiquity: * If the screen resolution is particularly low (< 600px height), allow
[11:28] <persia> \o/
[11:31] <ev> still more work to do there on the partitioner so it works reasonably well at 640x480
[11:32] <persia> Is it a horizontal issue, or a vertical issue?
[11:32] <ev> cjwatson: http://people.canonical.com/~evand/tmp/try_or_install2.png <- about to implement that for lucid, per michaelforrest's request, and with the workflow we've discussed.  Any massive objections? :)
[11:32] <ev> persia: vertical
[11:32]  * ev shakes his fist at the segmentedbars
[11:33] <ev> fixable though
[11:35] <cjwatson> ev: gosh, you beat me to it, I thought I was going to end up doing that :)
[11:36] <cjwatson> ev: slight UI glitch in the "release notes" link, but overall looks fine to me - can we make sure that this workflow only appears when you're booting with maybe-ubiquity (or some similar switch) though?
[11:37] <cjwatson> it would be weird for it to appear if (for example) you use the icon on the live CD desktop
[11:38] <ev> cjwatson: indeed, that's the plan :)
[11:40] <ev> just awaiting sign off from boss^3
[11:40] <ogra> hugo ? :)
[12:40] <ogra> hmm, oem-config still doesnt remove itself on my rootstock install
[12:42] <ogra> seems it exits with:
[12:42] <ogra> debconf (developer): <-- PROGRESS INFO ubiquity/install/hardware
[12:42] <ogra> Can't call method "info" on an undefined value at /usr/share/perl5/Debconf/FrontEnd.pm line 142, <GEN0> line 315.
[12:43] <persia> Does ubiquity/install/hardware appear in your debconf db?
[12:50] <ogra> persia, i dont touch the debconf db at all
[12:50] <ogra> mainly what i do is run debootstrap and install oem-config in that
[12:50] <persia> Understood.  And it ought be there if ubiquity is installed.  I'm just curious if it's present in your local environment when you encounter the issue.
[12:50] <ogra> touch /var/lib/oem-config/run and that it
[12:50] <ogra> *thats
[12:56] <CIA-3> ubiquity: cjwatson * r3854 ubiquity/ (debian/changelog ubiquity/components/ubi-partman.py):
[12:56] <CIA-3> ubiquity: Fix choose_partition thawing to handle free space at the end of
[12:56] <CIA-3> ubiquity: update_partitions (LP: #527848).
[12:58] <ogra> well, i see it in the ubiquity template file
[12:59] <ogra> so i would assume its there
[13:01]  * persia grabs trunk ubiquity thinking that this may solve the partman-uboot bug that has been confusing for the past few days
[13:01] <ogra> root@osiris:/# echo get ubiquity/install/hardware | debconf-communicate
[13:01] <ogra> 0
[13:01] <persia> Can you call INFO on it?
[13:02] <ogra> root@osiris:/# echo info ubiquity/install/hardware | debconf-communicate
[13:02] <ogra> 0
[13:03] <persia> Hrm.  Nothing else comes to mind offhand.  Logs might help (or maybe someone who knows more has an idea).
[13:04] <ogra> well, the above is all thet is in the logs
[13:04] <ogra> *that
[13:04] <ogra> the rest looks normal
[13:06] <ogra> i wonder if its caused by hw-detect
[13:07] <cjwatson> err - INFO != PROGRESS INFO
[13:07] <cjwatson> (and you won't be able to call PROGRESS INFO on its own via d-c anyway ...)
[13:08] <cjwatson> persia: what's up with partman-uboot?
[13:08] <ogra> hmm, i see in syslog that it tries to install usbutils
[13:08] <ogra> which it cant because there is no network setup
[13:08] <cjwatson> this all sounds pretty unrelated
[13:09] <cjwatson> ogra: can I see the debug log?
[13:09] <ogra> yeah, i just noticed it has the same timestamp ...
[13:09] <ogra> yup, one sec
[13:09] <ogra> http://people.canonical.com/~ogra/oem-config.log
[13:09] <persia> cjwatson: It keeps selecting "dummy__________dummy" as the preferred partition, causing error 141 with choose_partition//do_option
[13:09] <michaelforrest> ev - we are go on the installer first screen - mark just wants to make the "If you have internet access…" bit only show if there's network. Reworded as "You may wish to…".
[13:10] <cjwatson> persia: could I see the full logs, please?
[13:10] <persia> cjwatson: So I'm guessing that it was a space (which may be why I had trouble tracking), and want to test your most recent fix.
[13:10] <ogra> and http://people.canonical.com/~ogra/syslog
[13:10] <cjwatson> persia: it's certainly in the category that *might* have been fixed, but I could tell you for sure given a debug log
[13:11] <cjwatson> ogra: ok, so the problem is that nested progress bars don't work outside debconffilter
[13:12] <persia> cjwatson: I'd have to construct one (rebooted over the weekend, and scrapped the virtual machine).  Do you especially want it, or do you see a reason I shouldn't pull trunk to keep debugging?
[13:12] <ogra> wow
[13:12] <cjwatson> it has nothing to do with that particular template name
[13:12] <ogra> what does indicate that ?
[13:12] <cjwatson> persia: if you don't have it conveniently to hand, you might as well use trunk, sure
[13:12]  * persia would otherwise merge patches to ubiquity, and start installs again tomorrow.
[13:12] <cjwatson> ogra: PROGRESS STOP followed by PROGRESS <anything> failing
[13:12] <ogra> ah
[13:13] <cjwatson> ogra: this is complicated to fix - could you file a bug, please?
[13:13] <ogra> yep, do you want both logs ?
[13:13] <cjwatson> sure
[13:13] <ogra> ok
[13:18] <ogra> bug 530027
[13:20] <ev> michaelforrest: AWESOME
[13:20] <ev> working on it now
[13:36] <ev> michaelforrest: http://people.canonical.com/~evand/tmp/thinner-partition-bars.png - does that look okay?
[14:10] <cjwatson> 14:06 <cjwatson> didrocks: the point of casper's ubiquity-hooks is specifically to reproduce things that are done by casper at live CD boot time, and need to be repeated after installation
[14:10] <cjwatson> 14:08 <cjwatson> didrocks: accessibility is there because casper does accessibility stuff at boot time
[14:10] <cjwatson> 14:07 <cjwatson> it isn't meant to be a grab-bag of post-install scripts
[14:10] <cjwatson> 14:08 <didrocks> cjwatson: there is already some hooks like that like accessibility, etc. ev told me to put the first version there (which works in live mode)
[14:10] <cjwatson> 14:08 <cjwatson> didrocks: I don't think things should go in casper's ubiquity-hooks unless they're also done at boot time in casper
[14:10] <cjwatson> 14:09 <cjwatson> otherwise the result is that we end up with code spread around between casper and ubiquity when it doesn't need to be
[14:10] <cjwatson> 14:09 <cjwatson> you could install a ubiquity-hooks file in gnome-desktop if you want, but it might be better to just have it in ubiquity
[14:10] <cjwatson> (from #ubuntu-devel)
[14:25] <ev> ugh, I didn't tell him to put it in casper
[14:25] <ev> I told him to look at the hooks in casper as examples
[14:33] <cjwatson> heh, ok
[14:34] <cjwatson> I said I was OK with either ubiquity or a hook in gnome-desktop
[14:34] <cjwatson> if you have a strong preference for the latter, you should join #u-d and say :)
[15:01] <ev> nope, I just agree that casper is the wrong place
[16:29] <superm1> ev, michaelforrest  re http://people.canonical.com/~evand/tmp/try_or_install2.png, should you really still be referring to it as from CD as a lot of people install from USB media these days instead?
[16:31] <michaelforrest> I was hoping you'd make that dynamic actually ev
[16:31] <michaelforrest> not that I said that!
[16:37] <ev> will do
[17:20] <ev> michaelforrest: just to clarify, you want the labels beneath the bars in the partitioner left-aligned rather than their present center-alignment, correct?
[17:27] <michaelforrest> hm
[17:28] <michaelforrest> can you show me?
[17:28] <michaelforrest> ev^
[17:29] <ev> yup, heading over
[17:30] <CIA-3> netcfg: cjwatson * r640 ubuntu/debian/changelog: Rebuild against libiw30.
[17:40] <CIA-3> ubiquity: evand * r3855 ubiquity/ (debian/changelog ubiquity/segmented_bar.py):
[17:40] <CIA-3> ubiquity: * Left-align the labels on the segmented_bars.
[17:40] <CIA-3> ubiquity: * Make the segmented_bars narrower.
[20:10] <cr3> is it just me or does the casper.log generated on lucid no longer seem to contain: Found label '...' containing the disk image information?
[20:11] <cr3> I'm quite sure I recall that information existing before
[20:12] <cr3> there's now /var/log/installer/media-info though
[21:41] <CIA-3> netcfg: cjwatson * r641 ubuntu/debian/changelog: releasing version 1.51ubuntu2
[21:48] <ev> hrm, are "USB" and "CD" universally accepted acronyms, or should they be translated to something?  Google is entirely unhelpful for such a query.
[21:57] <cjwatson> ev: they get transliterated in at least (random sample) Chinese
[21:57] <cjwatson> ev: see the cdrom-detect translations, for example
[22:24] <ev> ah, damn, okay
[22:24] <ev> thanks
[23:23] <ev> so far: http://people.canonical.com/~evand/tmp/ubiquity-greeter.png - just need to fix one glaring bug.
[23:24] <superm1> are you parsing the OS from .disk/info to populate that, so Kubuntu, Xubuntu etc will automatically have their text set properly?
[23:24] <cjwatson> cool
[23:25] <cjwatson> does that dialog expand if you have a reasonable amount of screen space available?
[23:27] <ev> as in the space between the try section and the install section?
[23:27] <ev> or in some other way?
[23:28] <cjwatson> the whole window, it's smaller than it was, presumably due to your timezone changes
[23:28] <cjwatson> I'm just making sure that it uses more screen space if you have it, otherwise it'll feel cramped
[23:29] <cjwatson> while being smaller when there isn't so much space available
[23:37] <ev> cjwatson: ah, a mistake in my previous commit.  Fixing now.
[23:42] <CIA-3> ubiquity: evand * r3856 ubiquity/ (gui/gtk/stepUserInfo.ui ubiquity/components/ubi-usersetup.py): Fix r3853. Only use scrollbars on the user setup page when needed.
[23:42] <ev> ^ fixed, thanks