[10:22] <ev> mpt: http://paste.ubuntu.com/550168/ - I'm sure there's an easier way, but that should tell you which theme packages aren't from maverick.
[10:25] <ev> ah, broken
[10:41] <ev> mpt: http://paste.ubuntu.com/550172/ - slight variation.  This wont tell you if a package isn't in maverick, but it will tell you which releases have the version of the package you have installed.  So look for a package that only has lucid for an option, I suppose.
[10:48] <mpt> usplash-theme-ubuntu |       0.27 |        karmic | source, amd64, i386
[10:48] <ev> ah, that'd do it :)
[10:48] <mpt> That's the only item in the output that doesn't have maverick as an option
[10:49] <mpt> oh, no it isn't
[10:49] <mpt> It's just in universe after karmic
[10:49] <mpt> and according to Synaptic it's not installed anyway
[10:49] <ev> ah, right, hm
[10:50] <mpt> I think the problem might be that the default theme was changed but the new default wasn't installed or the old default wasn't uninstalled
[10:52] <mpt> ev, http://paste.ubuntu.com/550176/
[11:31] <ev> ugh, this chroot with rapt thing on honeysuckle is proving to be quite the pain
[11:31] <ev> contemplating moving that bit into a PPA
[11:33] <ev> with some LP API black magic to figure out when a new version appears in the PPA
[11:34] <ev> that or trying to convince IS to let me have full access to pbuilder.
[14:11] <ScottK> cjwatson: rbelem was asking me if we could have btrfs for the kubuntu-mobile image on arm.
[14:12] <ScottK> rbelem: cjwatson's question was "Do we have a boot loader that can cope?"
[14:12] <rbelem> ScottK, yup
[14:12] <ScottK> cjwatson: So yes.
[14:12] <cjwatson> do you control your own kernel arguments for initial boot of the images?
[14:12] <cjwatson> or does that have to be done on the cdimage side?
[14:12] <rbelem> ScottK, currently we boot kubuntu-mobile on n900 via uboot with meego kernel
[14:13] <cjwatson> uboot doesn't read the kernel off the filesystem?
[14:13] <rbelem> cjwatson, i think it is builtin in kernel
[14:13] <cjwatson> whether btrfs is built into the kernel is beside the point
[14:14] <cjwatson> how does the boot loader load the kernel?
[14:14] <ScottK> cjwatson: We're in kind of a hybrid position at the moment using a meego kernel, but we've got a linaro variant that also works in git that we're trying to switch to.
[14:14] <rbelem> cjwatson, i mean the cmd line parameters
[14:15] <cjwatson> in that case I don't really have a good way to change the default fs for you.
[14:15] <rbelem> mpoirer and apachelogger reported that linaro kernel is already booting
[14:15] <cjwatson> the standard way I would do that kind of thing is by passing a boot parameter when booting the installer
[14:16] <cjwatson> furthermore, partman-btrfs would have to be changed to avoid its current warning if and only if you're using a boot loader which can cope
[14:16] <cjwatson> which means I really do need you to answer my question above: how does the boot loader load the kernel?
[14:16] <cjwatson> because I need to know how to decide which boot loader is going to be used - I need to know whether this is armel-wide, or subarchitecture-specific
[14:16] <rbelem> cjwatson, it uses a vfat boot partition, afaik
[14:16] <cjwatson> do you use a partman recipe?
[14:17] <rbelem> cjwatson, i'm just using the same meego partition scheme
[14:17] <cjwatson> that doesn't answer my question, sorry
[14:17] <rbelem> :-(
[14:17] <cjwatson> what installer do you use?
[14:18] <rbelem> cjwatson, for now we are dd'ing the image to the first partition
[14:18] <cjwatson> then I don't see why I'm being asked to change anything :-)
[14:18] <cjwatson> you aren't using either of the two installers I co-maintain
[14:19] <cjwatson> I don't really understand what change I'm being asked to make ...
[14:19] <rbelem> cjwatson, the fs from ext4 to btrfs
[14:19] <cjwatson> I don't know where that's set
[14:20] <cjwatson> (are you sure you don't mean ext3?  nothing in cdimage mentions ext4 at all)
[14:20] <rbelem> cjwatson, i think it is ext3, sorry
[14:20] <rbelem> :-)
[14:21] <cjwatson> ah, I think I see where that is set
[14:21] <ScottK> The preinstalled images are preinstalled into a particular file system?  (sorry, I've no idea how this part of the system works)
[14:21] <cjwatson> has somebody checked that livecd-rootfs is capable of producing btrfs images?
[14:21] <cjwatson> it doesn't appear to have relevant code
[14:22] <cjwatson> so I think you guys need to write that if you want it
[14:22] <rbelem> ScottK, i think it is, when i dd it the destination becomes ext3
[14:22] <cjwatson> I'm happy to flip the switch in cdimage after that's done
[14:22] <rbelem> cjwatson, cool
[14:23] <rbelem> cjwatson, np with that :-)
[14:23] <cjwatson> you want lp:~ubuntu-core-dev/livecd-rootfs/trunk - search for IMAGEFORMAT
[14:23] <rbelem> cjwatson, nice :-)
[14:24] <rbelem> cjwatson, i will ping you when it is ready
[14:24] <rbelem> thx cjwatson
[14:25] <cjwatson> sorry for my initial misunderstanding, I sometimes forget how radically different arm installation is from everything else
[14:28] <rbelem> cjwatson, np :-)
[14:28] <rbelem> cjwatson, another question...
[14:29] <rbelem> cjwatson, is it possible to add a default user to the image?
[14:32] <cjwatson> dunno, I don't handle any of the software in question
[14:32] <cjwatson> ogra might know
[14:43] <rbelem> cjwatson, oki
[14:43] <rbelem> thanks cjwatson :-)
[17:37] <ev> cjwatson: what are your thoughts on filtering out the C locale ('No localization') from the language list in ubiquity? mpt is arguing that it's not a language and thus no one would ever want to select it from that list.  I'm inclined to agree.
[17:37] <cjwatson> it should be preserved in d-i but I'm OK with filtering it out of ubiquity.  send any complaints about it to mpt. :-)
[17:37] <cjwatson> (it's popular for servers in particular.)
[17:41] <ev> hahaha, okay
[17:48] <superm1> actually it was already filtered out if only-installable-languages was picked too i think
[17:56] <cjwatson> probably, but that goes further ...
[18:01] <ev> cjwatson: do you recall why we don't jump straight into compiz (so nvidia and all that) on the live CD?  It's been raised in the office that the install experience and the installed system experience are moving quickly apart when the installer uses metacity and the installed system uses unity.
[18:03] <cjwatson> there was no specific reason, using metacity was just easier to get going
[18:03] <cjwatson> at the time
[18:03] <cjwatson> and of course 3D drivers were often not installed
[18:05] <ev> I'll file a bug (to use whatever black magic the desktop uses to gracefully fall back), since I'm already doings tons of that thanks to mpt running through a install
[18:15] <superm1> on the live cd you would have to build the nvidia kernel module during boot
[21:24] <superm1> cjwatson, how do you feel about different upstart jobs for debconf_ui and gtk/kde?  it seems the stopping rc RUNLEVEL[2345] is a little bit racy still and causes oem-config's X to not always spawn before gdm gets X up first
[21:25] <superm1> side effect would be that the different oem-config frontend packages would have to conflict one another though
[21:37] <cjwatson> I'm quite sure it's possible to fix it given --verbose logs of what upstart is doing in each case
[21:37] <cjwatson> I don't see why different jobs should be necessary