[10:13] I have a suggestion for Ubiquity [10:13] Though I am quite impressed by the one found in UNE 10.04, I can see a small, and probably simple chance for improving it [10:14] When choosing keyboard-layout, there are three options. [10:14] I was quite intrigued by the "Guess"-option [10:14] It asks to press any of a handful of characters [10:15] When pressing, say "+", I am asked if the character "æ" is on my keyboard [10:15] Here, Ubiquity expects the user to say yes or no [10:16] My suggestion is to let the user just press this key [10:17] Because as it is now, one first has to say "yes", and then answer "no" to the question "Is this key (ä) on your keyboard?", and then press "æ" [11:19] Jonta: sounds like a useful suggestion to me - could you file a bug about that? perhaps on the cdebconf-keystep package in Ubuntu, although ev might pop up and say it should be somewhere else [11:20] cjwatson: Hm, directions on that? Never done this before.. [11:21] Launchpad? [11:21] cdebconf-keystep is a good place to start. It will have to be rewritten for ubiquity as the two components only share the decision tree used by both. [11:21] Jonta: http://launchpad.net/ubuntu/+source/cdebconf-keystep/+filebug [11:21] Thanks [11:22] What short description to give though.. [11:23] up to you [11:23] I'm sure we'll work it out [11:25] Found one. Reporting... [11:43] wow, screw kvm-autotest. Sikuli is made of some serious awesome. [11:44] not being tied to KVM, it means we can do graphical testing across both KVM and real hardware without any changes. [11:44] Not really. [11:45] no? [11:45] Unless something changed, of course. [11:45] How would you hook up Sikuli to the installer? [11:45] I'd do lots of black magic in an early_command [11:46] Yeah, but Sikuli doesn't know how to look at a virtual framebuffer, as I understand it. [11:46] It takes screenshots from an X server. [11:46] this would be running it from within the kvm instance [11:47] Ah, so you'd use Sikuli to interact with the SDL window from kvm? [11:49] ahh, I think I see your point. We can't use it for server tests. kvm-autotest is still the best option for that. [11:51] Maybe. I hadn't thought of using Sikuli to talk to kvm's SDL window. It'd be an interesting experiment. [11:51] ..but for testing gui stuff, Sikuli is very likely the best bet. [11:52] Don't get me wrong, I still see lots of value in kvm-autotest :) [11:53] Yeah, it's quite nice if you have time to hold its hand. Some sort of computer vision magic like Sikuli would certainly make it less painful to maintain. [11:54] * soren adds that experiment to his TODO list [12:02] base-installer: cjwatson * r401 ubuntu/ (42 files in 8 dirs): merge from Debian 1.107 [12:39] base-installer: cjwatson * r402 ubuntu/debian/changelog: releasing version 1.107ubuntu1 === JanC_ is now known as JanC === saispo is now known as StEdward [17:25] for network installs, how do i get to point to installation media available by HTTP? i'm looking at the pxelinux.cfg/default file === bladernr_ is now known as bladernr-afk === bladernr-afk is now known as bladernr_