[07:53] <_ruben> are there any plans yet on supporting ipv6 in the installer?
[09:27] <bigon> is it "normal" that there is no iwlagn driver on the alternate cd?
[10:06] <cjwatson> bigon: sounds like a bug in linux (the kernel decides which drivers to deliver to the installer)
[10:06] <cjwatson> _ruben: I'd like to, but I can't justify much of a high priority on it
[10:06] <_ruben> cjwatson: fair enough
[10:07] <_ruben> was mainly curious if it was on anyone's radar at all :)
[10:49] <CIA-17> ubiquity: cjwatson * r3623 lucid/debian/ (changelog intro-alpha.txt rules): Add an intro message noting that we're alpha again.
[10:53] <davmor2> cjwatson: d-i keyboard selection is it worth droping the yes no question for automatic detection?
[10:54] <cjwatson> replaced by what behaviour?
[10:54] <cjwatson> reason I kept it was that the automatic detection is actually a bit tedious if you just want the default keyboard
[10:55] <cjwatson> but I still wanted some easy way to get at it
[10:56] <davmor2> cjwatson: yes so if your used to the ubiquity install then you're used to the default selector way of choosing your keyboard.  So I'm thinking why not make that the default method and just lose the automatic detection aspect, /me hopes that makes sense
[11:08] <cjwatson> mm, except I know there are people who like the automatic detection thing, and we've had requests to add it as an option to ubiquity (which we haven't got round to yet)
[11:22] <davmor2> meh okay just an idea :)
[11:24] <CIA-17> ubiquity: cjwatson * r3624 lucid/ubiquity/filteredcommand.py: [pychecker] avoid using keyword args to __import__, which pychecker doesn't like
[11:25] <CIA-17> ubiquity: cjwatson * r3625 lucid/ubiquity/ (2 files in 2 dirs): [pychecker] note unused arguments
[11:26] <CIA-17> ubiquity: cjwatson * r3626 lucid/ubiquity/frontend/kde_components/Timezone.py: [pychecker] remove unused local variables, confirmed by Roman
[11:27] <davmor2> cjwatson: raid install is only available on alt correct?  also is it built though manual partitioning?
[11:29] <cjwatson> yes to both
[11:32] <davmor2> cool compiling a list of every install case I can think of :)
[14:27] <Omahn> cjwatson: I managed to resolve the issue I had yesterday with chain loading of preseeds. The originally loaded preseed had proxy configuration inside it so the machine was making the request for the second preseed file through our proxy (which does not have access rights to the build server).
[14:31] <cjwatson> Omahn: ah, right
[14:33] <Omahn> cjwatson: I've removed the proxy settings from the initial preseed and I now plan on 'including' a proxy.cfg at the very end of the setup so that the actual install itself still goes via proxy.
[14:33] <Omahn> cjwatson: Still a local issue, not d-i. Just thought I would let you know. In case you had trouble sleeping last night with worry. ;-)
[14:38] <cjwatson> I slept very well last night ;-)
[14:39] <Omahn> Likewise. :-)
[14:39] <davmor2> cjwatson: so did I when I got back home eventually
[14:40] <davmor2> cjwatson: admittedly that was like 01:30-ish
[15:04] <CIA-17> ubiquity: cjwatson * r3627 lucid/ubiquity/ (frontend/noninteractive.py segmented_bar.py): [pychecker] revert unused_ prefixes on keyword arguments, as those cause an interface change
[15:35] <davmor2> All karmiced up :)
[16:50] <CIA-17> ubiquity: cjwatson * r3628 auto-update/ (scripts/install.py ubiquity/frontend/gtk_ui.py): initial merge of Michael Vogt's auto-update branch from years back
[16:50] <CIA-17> ubiquity: cjwatson * r3629 auto-update/ubiquity/frontend/gtk_ui.py: whitespace and general style
[16:51] <CIA-17> ubiquity: cjwatson * r3630 auto-update/ (debian/ubiquity.templates ubiquity/frontend/gtk_ui.py): use debconf progress information
[16:52] <CIA-17> ubiquity: cjwatson * r3631 auto-update/ubiquity/frontend/gtk_ui.py: update package list
[16:52] <CIA-17> ubiquity: cjwatson * r3632 auto-update/gui/ (gtk/stepLanguage.ui qt/stepLanguage.ui): add "Update this installer" button to language page
[16:53] <CIA-17> ubiquity: cjwatson * r3633 auto-update/ubiquity/ (auto_update.py frontend/gtk_ui.py): move auto-update code from GTK frontend to a common file
[16:54] <CIA-17> ubiquity: cjwatson * r3634 auto-update/ubiquity/ (components/ubi-language.py frontend/gtk_ui.py): componentise the auto-update code; adds KDE frontend support
[16:55] <CIA-17> ubiquity: cjwatson * r3635 auto-update/ubiquity/frontend/gtk_ui.py: remove stray blank line
[16:56] <CIA-17> ubiquity: cjwatson * r3636 auto-update/ubiquity/ (auto_update.py components/ubi-language.py): hide auto-update button if already updated
[16:56] <CIA-17> ubiquity: cjwatson * r3637 auto-update/debian/changelog: add changelog entry
[16:59] <CIA-17> ubiquity: cjwatson * r3638 auto-update/ubiquity/auto_update.py: use self.parent.refresh instead of direct gtk calls
[17:02] <CIA-17> ubiquity: cjwatson * r3639 auto-update/ubiquity/auto_update.py: fix check_for_updates arguments
[17:05] <CIA-17> ubiquity: cjwatson * r3640 auto-update/ubiquity/auto_update.py: fix exec call
[17:11] <CIA-17> ubiquity: cjwatson * r3641 auto-update/ubiquity/auto_update.py: unused variables
[19:18] <JanC> hm, where does the installer put its logs during installation?
[20:47] <cjwatson> JanC: which installer?
[20:47] <cjwatson> (don't say "the Ubuntu installer" :-) )
[20:51] <JanC> good point, was ubiquity
[20:52] <JanC> cjwatson: somebody's install hung at the point of installing grub
[20:52] <JanC>  Oct 30 19:03:21 ubuntu grub-installer: info: Installing grub on ''
[20:53] <JanC> that's wrong I suppose...
[20:55] <cjwatson> normally, although I think that can be correct in the case of dmraid
[20:55] <JanC> it was on an external disk
[20:55] <cjwatson> I recommend against reading installation logs in isolation - they often have to be read alongside the code
[20:55] <cjwatson> (I'm not going to debug it now, though, it's Friday evening and it's been a long week)
[20:56] <JanC> right, I was looking at the code a bit, then he had to go before he could give more info (was somebody asking on #ubuntu-nl)
[20:58] <cjwatson> 'ubuntu-bug ubiquity' is the thing to tell him to do
[20:58] <JanC> well, his install didn't finish
[20:58] <cjwatson> so? :)
[20:58] <cjwatson> you can run that from the live CD environment, and it'll attach the logs
[20:59] <JanC> and he wasn't in the live environment, and not somebody I want to play in the console  ;)
[21:00] <JanC> I made him read the log files with the firefox that he could open from the presentation or something  :P
[21:02] <JanC> (didn't know that was possible, until he said he had firefox open)