#ubuntu-installer 2007-03-01 <CIA-4> ubiquity: jriddell * r1908 trunk/configure: ./autogen.sh for new version number <cjwatson> looks ok <evand> cjwatson: I see 89009 and the problem appears obvious, but I'm not going to have adequate time to handle it until midnight EST. I will fix it then though. <cjwatson> evand: thanks #ubuntu-installer 2007-03-02 <secureboot> cjwatson: did you have any ideas on the partman error that says "can't have a partition outside of disk" <secureboot_> anyone know how to preseed with the first hard disk available? <secureboot_> i mean, make partman use the first hard disk available <secureboot_> the examples that do that are from dapper, and don't work <secureboot_> d-i partman-auto/disk string /dev/sda will work if i have an sda disk, hda works for hda, but i want something that works for both <secureboot_> any ideas? <secureboot_> i've begun to think there's a bug in partman for PATA disks <secureboot_> the same recipes that work for hdas, don't work for sdas when you have PATA disks <secureboot_> I get "no root filesystem" when I try the same recipes <secureboot_> whereas they work fine on hdas (QEMU, for instance) <cjwatson> first hard disk available> not possible in edgy; use dapper or feisty <cjwatson> well, only possible with grungy scripting <cjwatson> or you could use Kickstart, which should be fine in edgy. See the documentation for clearpart <cjwatson> if you're getting "no root file system" then your recipe is buggy in some subtle way; I'm pretty confident that partman couldn't care less whether it's hda or sda (and much less whether it's PATA) at that level <secureboot_> cjwatson: hmm - i use exactly the same recipe <secureboot_> cjwatson: you were mentioning something 2 days ago about this maybe being related to an error someone found <cjwatson> you were talking about "can't have a partition outside of the disk" which is surely different? <secureboot_> cjwatson: yes, that's true <secureboot_> cjwatson: you also said that recipe looked correct, however <secureboot_> cjwatson: i was wondering if there was just a whole class of problems on PATA disks <secureboot_> http://pastebin.ca/378772 is what i'm using now <cjwatson> providing the disk is big enough, of course <secureboot_> cjwatson: it is <cjwatson> did I already ask you for a DEBCONF_DEBUG=5 log? it would probably also help to add 'set -x' to /bin/autopartition and /bin/perform_recipe <cjwatson> takes quite a while to debug this sort of thing unfortunately <secureboot_> cjwatson: huh - i'll try to do that - how do i add to /bin/autopartition? where is that /bin? <cjwatson> you have to edit it from tty2 with nano <cjwatson> I would suggest leaving the hostname unpreseeded, and then you'll be able to edit it while the installer is waiting for the answer to that question <cjwatson> then extract /var/log/syslog and /var/log/partman <cjwatson> (after the failure, obviously) <secureboot_> cjwatson: oh - neat. I'll try to do that then <cjwatson> fairly standard approach to this sort of probblem <cjwatson> it's quite data-intensive and you need the code as a reference to work out what it means <cjwatson> it's definitely useful to add DEBCONF_DEBUG=5 to the kernel boot parameters so that you get a debconf protocol trace in there too <secureboot_> i didn't evne know /var/log/partman existed - i'll be happy to look at that <CIA-4> migration-assistant: evand * r38 migration-assistant/ (10 files in 2 dirs): Fixes for non-English systems. #ubuntu-installer 2007-03-03 <mptech> Hello <mptech> I was trying to install feisty with its minimal install disk, and the install hangs at trying to detect hardware (after retrieving installer components) <mptech> Is this a known issue? <mptech> is it possible to use newer versions of the feisty installer to install edgy? <mptech> is it possible to install ubuntu with qemu (run the livecd in qemu and use the physical HD as the HD) and then boot into it natively? #ubuntu-installer 2007-03-04 <CIA-4> ubiquity: evand * r1479 ma/ (178 files in 13 dirs): Merging with trunk. <CIA-4> ubiquity: evand * r1480 ma/ (4 files in 4 dirs): Added support for spaces in usernames in migration-assistant. <CIA-4> ubiquity: evand * r1481 ma/ (debian/changelog ubiquity/frontend/gtkui.py): Fixed list movement bugs on the m-a page. Selecting an item now selects the user as well. <joejaxx> Hello All :) <evand> hello joejaxx <joejaxx> hello evand how have you been? <evand> joejaxx: not too bad, how's fluxbuntu going? <joejaxx> it is going well <evand> awesome <joejaxx> the first release is in April <evand> ready for UDS Spain? <evand> nice <joejaxx> yeah <joejaxx> it will be interesting to see how the release goes <evand> how so? <joejaxx> i am planning to release it on the same day as ubuntu <joejaxx> evand: alot of people are using it now <joejaxx> but more are waiting for the final <evand> ahh <joejaxx> yeah main things right now is to get it polished for the final release and build the alternative discs <evand> are you following the same freeze rules as Feisty? <joejaxx> no not exactly <joejaxx> since this is the first release <evand> ah, indeed <CIA-4> ubiquity: evand * r1482 ma/ (3 files in 2 dirs): The migration now auto-fills the username box. #ubuntu-installer 2007-03-05 * netjoined: irc.freenode.net -> anthony.freenode.net <jake333> how do i install darwin streaming server onto ubuntu <evand> jake333: This is not the channel to ask that in. /join #ubuntu <CIA-4> ubiquity: evand * r1483 ma/ (debian/changelog ubiquity/frontend/gtkui.py): Stopped the username auto-fill from clobbering the m-a username selection. <CIA-4> migration-assistant: evand * r39 migration-assistant/ (6 files in 2 dirs): Better i18n support, detection fixes, support for spaces in usernames. <CIA-4> migration-assistant: evand * r40 migration-assistant/debian/changelog: Releasing 0.4.1. * Starting logfile irclogs/ubuntu-installer.log <evand> cjwatson: can you upload m-a 0.4.1 (r40) and merge with my Ubiquity branch (r1483)? The latter is dependent on the changes in the former. Thank you. <xt> why does the "kickstart installer" download package-list from dapper-security, and not my local mirror? <cjwatson> xt: file a bug on kickseed with your kickstart file (minus any passwords) attached. It's an awkward corner case because we don't want people to miss out on security patches without realising it <cjwatson> evand: bazaar.launchpad.net only seems to have r39 <xt> cjwatson: well, I only selected url --url http://x.x.x.x/ubuntu/, but it says my repository is broken because the package index doesnt match the dapper default server install <xt> because it download the package index from ubuntu-security <cjwatson> xt: bug please :-) <xt> argh! :) <xt> Is kickstart fundamentally different from preseed? <evand> cjwatson: arr, I'll fix that in a bit. Class now. Sorry about that. <cjwatson> xt: kickstart is implemented on top of preseed, and you can actually mix them if you want <cjwatson> (our kickstart has a 'preseed' command extension) <xt> k, I think i'll be better of making a good preseed <evand> cjwatson: fixed * Starting logfile irclogs/ubuntu-installer.log <CIA-4> ubiquity: cjwatson * r1909 ubiquity/ (5 files in 4 dirs): merge from Evan <evand> thanks! <cjwatson> just minor tweaks in the merge, d-i/manifest and debian/changelog <cjwatson> (I tend to only update d-i/manifest right before an upload) <evand> ah, I had originally left the updated packages bit in tact as subtle hint that it depended on the new m-a <evand> but I'll remember that for future merges <cjwatson> evand: uploaded migration-assistant earlier, which you may have noticed <cjwatson> ah, noted <evand> indeed, just waiting on a few builds <evand> spac and amd64 <evand> sparc* <cjwatson> just trying to decide what else is urgent <evand> eh? Are we approaching a cut off? <cjwatson> well, there's the beta in <2 weeks <evand> ah, indeed <cjwatson> evand: bug 89821? <evand> cjwatson: it sounds like the spaces in the username bug. <evand> but I wont know for sure until I see the logs <cjwatson> ok <evand> The only other major issue I'm working around right now is that m-a does a bad job of detecting which users of Windows XP it should actually care about, that and handling /home on a different partition. Both of those should be relatively easy to fix and will do so for .2 <evand> err 0.4.2 #ubuntu-installer 2007-03-06 <evand> I forgot to note that I'm still working on the IOError stuff, but I'm trying to get these last bugs in m-a smoothed out first. <saispo> hi <saispo> how germinate know DIST values ? because i need to build feisty custom CD but he want to use edgy... <cjwatson> try germinate --help <saispo> hi cjwatson :) <saispo> i think, it's a shell script before which send edgy... <cjwatson> shell scripts are easy to read; I recommend reading it ;-) <saispo> =) <saispo> yep, i read, i adapt, i fix, it's very interesting ;-) <saispo> it's about restricted now... <saispo> cjwatson: you use xfce ? <cjwatson> no <saispo> k <saispo> cjwatson: it's possible to grab seeds file of feisty ? <cjwatson> yes, usual place <saispo> http://people.ubuntu.com/~cjwatson/seeds/ <saispo> i found... before i search under bzr :) <CIA-4> ubiquity: cjwatson * r1910 ubiquity/ (debian/changelog ubiquity/frontend/gtkui.py): <CIA-4> ubiquity: * GTK frontend: Don't reset partition_edit_mount_combo's cell renderer; <CIA-4> ubiquity: doing so causes GTK warnings. <CIA-4> ubiquity: cjwatson * r1911 ubiquity/ (3 files in 2 dirs): * New partitioner: Allow changing the mount point for NTFS. * cjwatson tries to work out how to figure out which partitions need to be unmounted before committing partitioning changes <cjwatson> guess it needs a parted_server extension <saispo> cjwatson: the syntac of automatic partitioning in preseed file is the same for feisty, or some changes occur ? <saispo> s/syntac/syntax/ <cjwatson> you need to add 'd-i partman-auto/method string regular' if you're preseeding partman-auto/disk <saispo> ok <saispo> thks <saispo> d-i partman-auto/method string regular <saispo> d-i partman-auto/disk string /dev/discs/disc0/disc <saispo> d-i partman-auto/expert_recipe string root 33ec:265c:71fe:e26d:2682:4ec2:aaa1:99ab \ 500 10000 1000000000 ext3 method{ format } format{ } \ use_filesystem{ } filesystem{ ext3 } mountpoint{ / } . \ 64 512 300% linux-swap method{ swap } format{ } . <saispo> d-i partman/confirm_write_new_label boolean true <saispo> d-i partman/choose_partition select \ Finish partitioning and write changes to disk <saispo> d-i partman/confirm boolean true <saispo> you think it's good ? <cjwatson> /dev/discs/disc0/disc won't work in edgy or later. you need to use /dev/hda or /dev/sda as appropriate. <saispo> erf <cjwatson> In feisty, if you only have one disk, you can just leave out partman-auto/disk <cjwatson> (that won't work in edgy) <saispo> ok <saispo> i want an automatic partition on the first disk (hda or sda) but i don't know before <cjwatson> use feisty with partman-auto/method but without partman-auto/disk then <saispo> ok :) <saispo> i use feisty at this time :) <saispo> i leave the ubuntu partitioner for my product under edgy #ubuntu-installer 2007-03-07 <evand> cjwatson: Hrm, migration-assistant doesn't currently report the size of things it's going to import to the installer. I could implement this over next week (Spring Break here) for most items. <evand> Unless of course you think it's too risky so close to release, in which case I would recommend modifying the warning in the new partitioner to say, "at least 2GB and enough space for any data you have chosen to import from your previous OS" or something to that effect. <joejaxx> cjwatson: do you have any links to the documentation on the debian install cd building process? other than the debian wiki <john> what do I need to add to my /etc/apt/sources.list to be able to install streamripper with apt-get? <cjwatson> evand: do we import data yet, or just settings? <cjwatson> joejaxx: no, that and the documentation in debian-cd itself are all I know of <cjwatson> john: no idea - this channel's for full OS installation rather than figuring out how to install particular packages <CIA-4> ubiquity: cjwatson * r1912 ubiquity/debian/ (changelog control): * Add XS-Vcs-Bzr field to debian/control. <CIA-4> ubiquity: cjwatson * r1913 ubiquity/debian/changelog: reorg <CIA-4> ubiquity: cjwatson * r1914 ubiquity/ (debian/changelog ubiquity/frontend/gtkui.py): - Add more space around text in question dialogs. <CIA-4> ubiquity: cjwatson * r1915 ubiquity/ (configure configure.ac): bump to 1.3.25 <CIA-4> ubiquity: cjwatson * r1916 ubiquity/ (82 files in 4 dirs): <CIA-4> ubiquity: * Automatically unmount mounted partitions if they are on a changed <CIA-4> ubiquity: partition table or they are to be mounted somewhere other than /media/*. <CIA-4> ubiquity: Display an error and allow the user to try to unmount them manually if <CIA-4> ubiquity: automatic unmounting fails (LP: #89605). <evand> cjwatson: My Documents, My Pictures, and My Music, so yes, we import data as well. <cjwatson> evand: ok, so perhaps report the size (shove it in the debconf db somewhere) but don't change the partitioner yet? That should obviously be minimally safe, means the partitioner can be changed independently, and that warning needs to be reimplemented properly for the new partitioner anyway ... <evand> cjwatson: ok, will do <evand> thanks <CIA-4> ubiquity: cjwatson * r1917 ubiquity/debian/changelog: note fix for LP: #90276 <CIA-4> ubiquity: cjwatson * r1918 ubiquity/ (4 files in 3 dirs): <CIA-4> ubiquity: * Work around datetime misbehaviour if the system clock is set before the <CIA-4> ubiquity: Unix epoch (LP: #57952). <CIA-4> ubiquity: cjwatson * r1919 ubiquity/ (d-i/manifest debian/changelog): <CIA-4> ubiquity: * Automatic update of included source packages: console-setup 1.13ubuntu7, <CIA-4> ubiquity: localechooser 1.37ubuntu1, migration-assistant 0.4.1, partman-auto <CIA-4> ubiquity: 62ubuntu6, partman-base 100ubuntu6, partman-efi 11ubuntu3. <CIA-4> ubiquity: cjwatson * r1920 ubiquity/d-i/get-sources: make sure to remove d-i/source/console-setup/.svn <CIA-4> ubiquity: cjwatson * r1921 ubiquity/ (d-i/manifest debian/changelog): * Automatic update of included source packages: partman-base 100ubuntu7. <CIA-4> ubiquity: cjwatson * r1922 ubiquity/debian/changelog: releasing version 1.3.25 <CIA-4> ubiquity: cjwatson * r1923 ubiquity/ (configure configure.ac): bump to 1.3.26 <joejaxx> cjwatson: alright thanks <CIA-4> ubiquity: cjwatson * r1924 ubiquity/ (bin/ubiquity debian/changelog): * Make acquire_lock properly atomic (LP: #90391). <CIA-4> ubiquity: cjwatson * r1925 ubiquity/ubiquity/frontend/ubiquity.glade: open/save in glade-3 <CIA-4> ubiquity: cjwatson * r1926 ubiquity/ (3 files in 2 dirs): <CIA-4> ubiquity: * GTK frontend: Remove the disk bar placeholder for the new partitioner; <CIA-4> ubiquity: we'll probably have to do without the disk bar for Feisty at this point. #ubuntu-installer 2007-03-08 <CIA-4> ubiquity: cjwatson * r1927 ubiquity/ (debian/changelog ubiquity/frontend/kde-ui.py): <CIA-4> ubiquity: * KDE frontend: Fix disk selection handling in automatic partitioner so <CIA-4> ubiquity: that we stop always selecting the last disk no matter what (LP: #83010). <CIA-4> ubiquity: cjwatson * r1928 ubiquity/ (3 files in 2 dirs): remove disk bar placeholder from KDE frontend too <CIA-4> ubiquity: cjwatson * r1929 ubiquity/ (bin/ubiquity debian/changelog): <CIA-4> ubiquity: * Reluctantly print error messages from main program to stdout rather than <CIA-4> ubiquity: stderr, as gksudo swallows them otherwise. <CIA-4> ubiquity: cjwatson * r1930 ubiquity/ (5 files in 3 dirs): <CIA-4> ubiquity: * Drop dependencies on gparted and qtparted. Instead, print a helpful <CIA-4> ubiquity: error message if --old-partitioner is used but these programs are not <CIA-4> ubiquity: installed. <CIA-4> ubiquity: cjwatson * r1931 ubiquity/ (d-i/manifest debian/changelog): * Automatic update of included source packages: partconf 1.19build1. <CIA-4> ubiquity: cjwatson * r1932 ubiquity/debian/changelog: releasing version 1.3.26 <CIA-4> oem-config: cjwatson * r258 timezone/lib/ (frontend/gtk-ui.py tz.py): timezone fixes from ubiquity <CIA-4> oem-config: cjwatson * r254 oem-config/.bzrignore: ignore debian/oem-config-kde <CIA-4> oem-config: cjwatson * r259 timezone/.bzrignore: update ignores <saispo> hi <joejaxx> hello <saispo> anyone know how can i create a repository with alphabetical order such as ubuntu repository ? mini-dinstall can do it or i must use other things ? <cjwatson> saispo: off-topic for this channel. <CIA-4> ubiquity: cjwatson * r1933 ubiquity/ (configure configure.ac): bump to 1.3.27 <joejaxx> cjwatson: is the udeb.list in the debian-installer image directory in the repos a collective on for all the d-i make targets? netboot, hd, cdrom_isolinux <joejaxx> s/in/one/g <joejaxx> on* <cjwatson> IIRC it's for everything <cjwatson> MANIFEST.udebs has a more detailed breakdown <joejaxx> ah ok i just wanted to make sure <joejaxx> thanks #ubuntu-installer 2007-03-09 <bdmurray> anybody around? <bdmurray> there is an interesting bug 90173 that is probably "installer" related <bdmurray> where xfsprogs isn't installed if you format a partition as xfs <evand> bdmurray: cjwatson would be the person to ask for that and he's on GMT. <joejaxx> evand: i got an iso built and it boots but it is broken :P <evand> broken? <joejaxx> yeah <joejaxx> the d-i is not on it <joejaxx> it only has memtest86+ :P <joejaxx> so i wonder what happened <bdmurray> evand: cool thanks <joejaxx> the weird thing is though <joejaxx> is that it is in the tmp work area that is created when the disc images are built <evand> heh <joejaxx> yeah <evand> joejaxx: I'd love to help you, but my experience with building cds is limited to adding udebs to d-i currently. <joejaxx> evand: it is quite alright :) <joejaxx> hopefully after april i will have time to dive into the d-i source more <evand> joejaxx: are you in University? <evand> s/U/u <joejaxx> not this semester <joejaxx> i will be back in next semester again <evand> ah, I thought that date might coincide with your spring break <joejaxx> nope it coincides with post-feisty release <joejaxx> :P <evand> wow, you'd figure I'd pick up on that, but apparently not <joejaxx> yours was a valid one <joejaxx> :) <cjwatson> bdmurray: I'll look at that when LP comes back, but I suspect that that's one of the problems that's gone away for free with the new partitioner <cjwatson> bdmurray: (because now we naturally use partman-xfs which calls apt-install xfsprogs which ensures that ubiquity doesn't remove xfsprogs after copying the filesystem over) <joejaxx> cjwatson: do you know why when building with debian-cd a situation would arise when it does not build discs with the d-i but the d-i imagesets are in the build work directory during the build process? <cjwatson> sounds like one of its directories is configured wrongly in CONF.sh <cjwatson> but otherwise, no, not really, this is the sort of thing that's incredibly hard to debug remotely ... <joejaxx> oh ok <joejaxx> i will try and look again <cjwatson> if by build work directory you mean BDIR or TDIR or whatever it is <joejaxx> yes TDIR <joejaxx> i will look again perhaps i overlooked something <CIA-4> oem-config: cjwatson * r255 oem-config/d-i/get-sources: make sure to remove d-i/source/console-setup/.svn <CIA-4> oem-config: cjwatson * r260 timezone/ (15 files in 6 dirs): <CIA-4> oem-config: * Update language and timezone handling code from ubiquity. <CIA-4> oem-config: * Move the timezone step before the keyboard step. <CIA-4> oem-config: * Apply language and timezone changes at the end of oem-config rather than <CIA-4> oem-config: on the fly. <CIA-4> oem-config: cjwatson * r261 timezone/ (.bzrignore d-i/get-sources debian/changelog debian/rules): merge from mainline <CIA-4> oem-config: cjwatson * r262 timezone/lib/frontend/gtk-ui.py: finish reordering keyboard and timezone steps <CIA-4> oem-config: cjwatson * r256 oem-config/d-i/sources.list: bump to feisty <CIA-4> oem-config: cjwatson * r257 oem-config/ (d-i/Makefile debian/changelog debian/rules): <CIA-4> oem-config: * Add a 'debian/rules update-local' target to allow updating d-i/source/ <CIA-4> oem-config: without updating debian/changelog, which is sometimes convenient for <CIA-4> oem-config: local hacking. <CIA-4> ubiquity: cjwatson * r1934 ubiquity/ (d-i/Makefile debian/changelog debian/rules): <CIA-4> ubiquity: * Add a 'debian/rules update-local' target to allow updating d-i/source/ <CIA-4> ubiquity: without updating debian/changelog, which is sometimes convenient for <CIA-4> ubiquity: local hacking. <CIA-4> oem-config: cjwatson * r258 oem-config/.bzrignore: ignore lib/frontend/*.bak <CIA-4> oem-config: cjwatson * r263 timezone/debian/ (changelog control rules): <CIA-4> oem-config: * Depend on a version of console-setup at least as new as the one in our <CIA-4> oem-config: source tree. <bdmurray> cjwatson: It's this bug - https://launchpad.net/ubuntu/+bug/90173 <cjwatson> oh, server? odd <cjwatson> ah, maybe incorrect seeds <cjwatson> yeah, seed bug. I'll fix it in feisty, thanks <cjwatson> problem was that xfsprogs wasn't on the server CD at all <bdmurray> sure, no problem <bdmurray> I also ran into an NTFS resize bug in Herd 5 last night <cjwatson> what kind? <CIA-4> oem-config: cjwatson * r264 timezone/lib/frontend/gtk-ui.py: no i18n here yet <CIA-4> oem-config: cjwatson * r265 timezone/ (5 files in 3 dirs): merge from mainline <CIA-4> oem-config: cjwatson * r266 timezone/ (12 files in 5 dirs): <CIA-4> oem-config: * Update keyboard handling code from ubiquity. <CIA-4> oem-config: * Apply keyboard changes at the end of oem-config rather than on the fly. <CIA-4> oem-config: * Track console-setup 1.13ubuntu4 changes by generating and using <CIA-4> oem-config: MyKeyboardNames.pl based on xkb-data, which is more up to date than <CIA-4> oem-config: KeyboardNames.pl. <cjwatson> this branch is getting hairy <CIA-4> oem-config: cjwatson * r267 timezone/ (debian/changelog lib/frontend/oem-config.glade): <CIA-4> oem-config: * Stop the user page spreading out in an ugly manner now that the pages <CIA-4> oem-config: are bigger. This does result in an unpleasant amount of empty space; the <CIA-4> oem-config: page needs a redesign to cope with this. <CIA-4> oem-config: cjwatson * r268 timezone/scripts/ (console-setup-apply localechooser-apply): executability <CIA-4> oem-config: cjwatson * r269 timezone/lib/frontend/gtk-ui.py: fix filter startup <CIA-4> oem-config: cjwatson * r270 timezone/debian/rules: fix tzsetup post-base-installer script not to use /target <CIA-4> oem-config: cjwatson * r271 timezone/ (debian/changelog lib/frontend/oem-config.glade): <CIA-4> oem-config: * Activate the Forward button when Enter is pressed in any entry field on <CIA-4> oem-config: the user page. <CIA-4> oem-config: cjwatson * r272 timezone/ (debian/changelog lib/frontend/gtk-ui.py): <CIA-4> oem-config: * Leave the UI up until we've finished applying changes; we now have to <CIA-4> oem-config: regenerate the initramfs (due to console-setup changes) and it takes a <CIA-4> oem-config: while. <CIA-4> ubiquity: cjwatson * r1935 ubiquity/ (80 files in 3 dirs): <CIA-4> ubiquity: * New partitioner: Add validation for system partitions being formatted <CIA-4> ubiquity: (LP: #89461). <CIA-4> ubiquity: cjwatson * r1936 ubiquity/debian/ (changelog rules): <CIA-4> ubiquity: * Really use MyKeyboardNames.pl (based on xkb-data) rather than <CIA-4> ubiquity: KeyboardNames.pl. <joejaxx> cjwatson: i think i need to change something in feisty/boot-i386 #ubuntu-installer 2007-03-12 <CIA-4> ubiquity: evand * r1484 ma/ (97 files in 10 dirs): Merged with trunk. <CIA-4> ubiquity: evand * r1485 ma/ (debian/changelog scripts/install.py): When m-a is disabled, don't try to run its apply script. <CIA-4> ubiquity: cjwatson * r1937 ubiquity/ (d-i/manifest debian/changelog): * Automatic update of included source packages: console-setup 1.13ubuntu8. <CIA-4> ubiquity: cjwatson * r1938 ubiquity/debian/changelog: releasing version 1.3.27 <CIA-4> oem-config: cjwatson * r273 timezone/lib/components/timezone.py: Timezone should import locale <CIA-4> oem-config: cjwatson * r259 oem-config/ (debian/changelog oem-config): <CIA-4> oem-config: * Make OEM_CONFIG_DEBUG=1 imply DEBCONF_DEBUG='developer|filter' for ease <CIA-4> oem-config: of debugging. <CIA-4> oem-config: cjwatson * r260 oem-config/ (debian/changelog oem-config): * Add a --debug option, equivalent to setting OEM_CONFIG_DEBUG=1. <CIA-4> ubiquity: cjwatson * r1939 ubiquity/ (configure configure.ac): bump to 1.3.28 <CIA-4> ubiquity: cjwatson * r1940 ubiquity/ (80 files in 3 dirs): <CIA-4> ubiquity: * Use just one progress message for all target-config hooks, to avoid <CIA-4> ubiquity: uglinesses like "Running 32gnome_power_manager". <CIA-4> ubiquity: cjwatson * r1941 ubiquity/ (debian/changelog ubiquity/frontend/kde-ui.py): <CIA-4> ubiquity: * KDE frontend: In the partition create dialog, set the maximum partition <CIA-4> ubiquity: size before setting the value to avoid the value being incorrectly <CIA-4> ubiquity: clipped. #ubuntu-installer 2007-03-13 <CIA-4> oem-config: cjwatson * r274 timezone/ (d-i/update-control debian/control): build-depend on libxml-parser-perl for console-setup bits <CIA-4> oem-config: cjwatson * r275 timezone/lib/frontend/ (gtk-ui.py kde-ui.py): remove redo_step callback, no longer used <CIA-4> oem-config: cjwatson * r276 timezone/scripts/console-setup-apply: send output of update-initramfs to stderr to avoid confusing debconf <CIA-4> oem-config: cjwatson * r277 timezone/ (debian/changelog oem-config-dm): <CIA-4> oem-config: * Send SIGKILL to the window manager if it fails to exit within a second <CIA-4> oem-config: of receiving SIGTERM. * pkt is away: . <cjwatson> pkt: please turn off public away <pkt> cjwatson: sorry :-) <cjwatson> thanks <CIA-4> oem-config: cjwatson * r278 timezone/ (6 files in 2 dirs): merge from Anirudh <CIA-4> oem-config: cjwatson * r279 timezone/lib/frontend/kde-ui.py: fix exception when step not recognised <CIA-4> oem-config: cjwatson * r280 timezone/lib/frontend/kde-ui.py: remove redo_step again <CIA-4> oem-config: cjwatson * r281 timezone/ (3 files in 2 dirs): rename SysConf.ui back to lower case <CIA-4> oem-config: cjwatson * r282 timezone/lib/frontend/kde-ui.py: remove stray import <CIA-4> oem-config: cjwatson * r283 timezone/lib/frontend/kde-ui.py: whitespace <CIA-4> oem-config: cjwatson * r284 timezone/ (debian/changelog oem-config): merge from mainline <CIA-4> oem-config: cjwatson * r261 oem-config/ (70 files in 13 dirs): merge from timezone branch #ubuntu-installer 2007-03-14 <evand> cjwatson: Is it too late to add a string to the migration-assistant page that explains what the user has to do a little better than it currently does? <evand> I believe it is as we're past string freeze, but I wanted to run it by you before I put it on the Feisty+1 agenda. <saispo> hi <saispo> cjwatson: have you an example of a preseed file with lvm automatic partitioning and expert_recipe ? <cjwatson> evand: go ahead and put it in now <cjwatson> saispo: sorry, don't have time at the moment <saispo> ok <saispo> no problem <saispo> thanks for your answer <evand> cjwatson: will do <cjwatson> evand: feisty translations aren't quite really up and running yet anyway <evand> great! (for me, anyway) <CIA-4> migration-assistant: evand * r41 migration-assistant/ (7 files in 2 dirs): Prompt the user to umount partitions that are in use. Mount /home when necessary. <CIA-4> ubiquity: evand * r1486 ma/ (debian/changelog ubiquity/components/migrationassistant.py): Dont crash Ubiquity when m-a is disabled. <CIA-4> ubiquity: evand * r1487 ma/ (85 files in 6 dirs): Merged with trunk. <evand> cjwatson: is translating strings that aren't Gtk widgets something that's going to be dealt with in Feisty+1? <evand> I investigated doing it for the "there are no OSes to import" message and noticed that the Install button does not get translated. Or at least it appears that way in gtkui.py <cjwatson> there are random TODO comments littered around for the ones that aren't translated <evand> indeed <evand> Can I get a second set of eyes on this? Does this look ok? http://evalicious.com/ma.png <CIA-4> migration-assistant: evand * r42 migration-assistant/debian/changelog: Releasing migration-assistant 0.4.2 <cjwatson> evand: avoid "into Ubuntu" <cjwatson> we have derivatives both inside and outside the archive, and modifying translated strings for that is hassle <evand> cjwatson: ah, point taken. I'll change that now. <cjwatson> evand: instead of "press next", use something like "go to the next page" - note how the button is actually "Forward", and you don't want to have to stay in sync <cjwatson> evand: otherwise looks fine <evand> cjwatson: great, thanks for the tips. I'm just making sure everything still works, I'll add those changes now and then let you know when it's ready to merge. <cjwatson> righto <CIA-4> oem-config: cjwatson * r262 oem-config/ (d-i/manifest debian/changelog): <CIA-4> oem-config: * Automatic update of included source packages: console-setup 1.13ubuntu8, <CIA-4> oem-config: localechooser 1.37ubuntu1, tzsetup 1:0.14, user-setup 1.8ubuntu1. <CIA-4> oem-config: cjwatson * r263 oem-config/debian/changelog: releasing version 1.9 <CIA-4> oem-config: cjwatson * r264 oem-config/ (configure configure.ac): bump to 1.10 <CIA-4> oem-config: cjwatson * r265 oem-config/debian/ (changelog control): * Make oem-config-kde depend on python-qt4, not python-kde3. <CIA-4> oem-config: cjwatson * r266 oem-config/ (debian/changelog src/Makefile.am src/Makefile.in): <CIA-4> oem-config: * Don't install e-map.defs; it's not all that important and it causes a <CIA-4> oem-config: conflict with ubiquity-frontend-gtk. <CIA-4> oem-config: cjwatson * r267 oem-config/debian/changelog: releasing version 1.10 <CIA-4> ubiquity: cjwatson * r1942 ubiquity/debian/ (changelog rules): * Disable the intro message for beta. <CIA-4> ubiquity: evand * r1488 ma/ (debian/changelog ubiquity/frontend/ubiquity.glade): Added more descriptive text to the Migrate page. <evand> cjwatson: m-a at r42, williamsmith@example.net. Ready to merge and upload. <cjwatson> great, thanks, will do shortly <evand> cjwatson: thank you <cjwatson> evand: m-a uploaded; wanna close the bugs? <cjwatson> I've got another major item to do before upload <cjwatson> (of ubiquity) <CIA-4> ubiquity: cjwatson * r1943 ubiquity/ (4 files in 4 dirs): merge from Evan <saispo> juste a little question, when preseeding partition, it's possible to set flags ? for example quota and acl on ext3 ? <cr3> is there a way to have the alternate install drop to busybox at some point during the installation? <cjwatson> cr3: alt-f2 to get a shell <cjwatson> cr3: or do you mean in an automated way? <cr3> cjwatson: in an automated way. I tried specifying break=premount in the kernel parameters but that didn't seem to work over a netinstall <cjwatson> no, that's an initramfs-tools instruction and not applicable <cr3> cjwatson: aha! thanks for the explanation, makes sense now <cjwatson> BOOT_DEBUG=3 will give you shells at various points in the boot process <cjwatson> can be useful in figuring out why the installer doesn't boot on a given machine <cjwatson> that's the nearest equivalent to break=premount <cr3> cjwatson: the problem I'm actually trying to solve is that I'd like to netboot, mostly using files from the alternate cd, and perform the following actions once booted into a minimal system: wget latest.iso; mount latest.iso /mnt; cp -a /mnt /root; reboot from /root <cr3> some of those commands are pseudo shell, just to give an idea of the actions I'd like to perform <cjwatson> isn't that more or less what ubiquity does? <cjwatson> sounds like you want a noninteractive ubiquity frontend :) #ubuntu-installer 2007-03-15 <cjwatson> anyway, one approach to doing that with d-i would be to preseed the first few steps of the installer (locale/keyboard/network) and put the stuff you actually want to do in preseed/early_command <cjwatson> maybe terminate it with reboot <cr3> cjwatson: and that can be performed over the net somehow. the purpose for this is to be able to boot the desktop install without having to burn a cd <cr3> cjwatson: if I add a custom d-i, somewhere after network has been detected and drives detected, could I somehow overwrite the installation process altogether, perform those actions I need and then reboot? <cjwatson> that would be the procedure I described above <cjwatson> well, you might have to force a hardware detection run but in practice disks should have been detected by that pointt <cjwatson> point <cjwatson> ultimately I'd like to be able to do boot-iso-from-hard-disk using grub2, but note that partitioning gets very difficult when you're relying on an image on the hard disk <cr3> cjwatson: very cool! I can most certainly run all the shell commands I need in that early_command section, thanks! <cjwatson> just a warning, I am unlikely to be able to support partitioning problems you run into by this method <cr3> cjwatson: how so? for now, since grub doesn't seem to support iso9660, I'm simply using cp -a into a 800Mb partition at the beginning of the drive <cjwatson> the disk is busy and therefore it is not possible to get Linux to re-read the partition table, so new partitions you create won't be usable <cjwatson> (until a reboot) <cjwatson> this is why both d-i and ubiquity try to avoid having anything mounted on the hard disk <cr3> cjwatson: the new partitions will not be usable to the currently running install, but the d-i script should be able to cp -a onto a partition and then reboot from that partition, right? <cjwatson> the device node won't appear until Linux has re-read the partition table <cjwatson> so no, not unless the partition existed before you booted <cjwatson> or unless you're using a separate hard disk to store the CD image from the one which you're partitioning <cr3> I wonder what tools I could use from the installer to grab the files from an internal server without having to grab the iso locally <cr3> wget -r might work, but I'm not sure if there are symlinks on the installation media and if that would work with wget <cr3> I guess iso9660 is rather limited in feature set so wget -r could potentially work just fine <cr3> I'm not sure if the -r option is supported by the version of wget on busybox <cjwatson> it's not <cjwatson> honestly, this isn't sounding like a test which will very accurately reproduce a normal installation <cjwatson> lifeless did figure out how to NFS-boot the desktop CD; talk to him if you like <cr3> ultimately, the original CD will be extracted integrally onto a partition from which the system will be installed. how is that different from a normal installation? <cjwatson> Because the partition table on that disk will be *immutable* while a filesystem is mounted from it. <cjwatson> Totally different. The installation really doesn't like unrereadable partition tables. <cjwatson> Well, not immutable, but changes won't be reflected until you reboot. <cjwatson> this is why e.g. the partitioner has to disable swap before committing partitioning changes <cjwatson> but if the partitioner is running off a partition on the hard disk, it won't be able to do that <cr3> doesn't the partitionner run from memory during the installation process? <cjwatson> no <cjwatson> it's read into memory in order to execute it obviously, but you can't just go unmounting its root filesystem under it! <cr3> there's something I don't understand, I thoutht the root filesystem was an initramfs? <cjwatson> if you're booting (a version of) the desktop CD, then the ISO is mounted, a squashfs is loopback-mounted from that, and the eventual root filesystem is a unionfs of that squashfs and a tmpfs <cjwatson> the root filesystem is an initramfs in d-i, but that's a very different environment <cjwatson> doing the desktop CD with an initramfs / would have vastly increased memory requirements over the existing solution <cjwatson> you'd have to unpack the entire CD (effectively) into memory before you could get started <cr3> just in case there's misunderstanding, when I intend the desktop installation to proceed from a partition on the hard drive, I intend it to install onto the rest of the drive and not touch the partition containing the installation media <cjwatson> I understand that, but it still won't work. <cjwatson> Not unless you use a *separate* drive. <cjwatson> A separate partition won't do because it's still inside a partition table which is going to be locked. <cr3> I'm starting to understand the problem now, darn ;( <cr3> cjwatson, I really appreciate you have taken the time to explain this to me, it would've taken me quite a while to figure it out on my own through trial and error <cr3> mostly error :) <cjwatson> not a problem, it's not an uncommon line of thought and it's not obvious at first glance why it doesn't work <cr3> I'm gone. g'night and thanks a million! <evand> cjwatson: Sorry about that, I left right after my message. I'll close the bugs, but is there any paticular reason why I should instead of waiting and letting LP do it for me? <evand> Just curious <cjwatson> evand: because LP won't do it for you yet ... <cjwatson> evand: the distro side of changelog-closes-bugs is implemented, but not the LP side <evand> cjwatson: Really? I could've sworn it's been closing them. Weird. Ok, will do. <cjwatson> I've closed some following your uploads - you may have interpreted that as something automatic <cjwatson> s/your uploads/uploads I've done on your behalf/ <cjwatson> I tend to just paste the changelog into the bug so it's not terribly distinguishable from something automatic <evand> ahhh, sorry about that. I thought that was LP working its magic. I'll take care of that in the future. <evand> Being now :) <cjwatson> evand: # FIXME: we'll probably need to check if /etc is its own part as well. <cjwatson> evand: /etc has to be on the same partition as / in pretty much all Unix systems I know of - can't do much else without /etc/fstab <evand> hahaha, point taken. I wrote much of that very early in the AM after much frustration with UUIDs <evand> I'll remove the comment <CIA-5> ubiquity: cjwatson * r1947 ubiquity/debian/changelog: releasing version 1.4.0 <CIA-5> ubiquity: cjwatson * r1948 ubiquity/ (configure configure.ac): bump to 1.4.1 <CIA-5> ubiquity: cjwatson * r1949 ubiquity/ (debian/changelog ubiquity/tz.py): * Make the timezone database a singleton, saving about 2MB of memory. <CIA-5> ubiquity: cjwatson * r1950 ubiquity/ (debian/changelog ubiquity/tz.py): <CIA-5> ubiquity: * Avoid storing temporary variables as members of the (long-lived) <CIA-5> ubiquity: SystemTzInfo class. <cyp_taf> hello <cyp_taf> I have some questions about ubiquity : is it the good chan ? <CIA-5> oem-config: cjwatson * r268 oem-config/ (debian/changelog oem-config): * Add missing 'import os' to oem-config. <CIA-5> oem-config: cjwatson * r269 oem-config/ (debian/changelog debian/control oem-config-dm): <CIA-5> oem-config: * Stop using xsetroot in oem-config-dm for KDE, as the KDE frontend now <CIA-5> oem-config: sets its own wallpaper. <CIA-5> oem-config: cjwatson * r270 oem-config/ (configure configure.ac): bump to 1.11 <CIA-5> oem-config: cjwatson * r271 oem-config/ (d-i/manifest debian/changelog): * Automatic update of included source packages: user-setup 1.8ubuntu2. <cjwatson> cyp_taf: yes <CIA-5> oem-config: cjwatson * r272 oem-config/debian/changelog: releasing version 1.11 <cyp_taf> cjwatson: great <cyp_taf> there a website or someting like for know how modify ubiquity <cjwatson> no <cyp_taf> or a page decribing the internal comportment of ubiquity ? <cjwatson> aside from the live CD customization howto somewhere on help.ubuntu.com/community/ <cjwatson> there's doc/README in the source package <cyp_taf> ok <cyp_taf> I have some trouble for use lvm with partman <cjwatson> not supported in ubiquity yet. <cyp_taf> partman see lvm intruction but dont apply them <cjwatson> don't bother trying in ubiquity; it's still a good deal of work. use d-i instead <cyp_taf> in facts, my boss ask to me to adapt ubiquity for our custom debian distribution so I can't use d-i directly ... <cjwatson> I'm afraid LVM support just isn't there yet <cyp_taf> :( <cjwatson> it shouldn't be *too* bad to do in the new partitioner, but hooking up the pieces will still be a reasonable amount of code <cjwatson> certainly a lot more tractable than in the old partitioner <cyp_taf> ok <Tux-Rox> While installing Ubuntu in Parallels Desktop on a MacBook, it hangs as the install is finishing, while trying to insmod an IDE controller driver. It never gets to the grub install and even though I can chroot into the file system in the Virtual Machine, grub-install does not see (hd0). Any ideas or command switches that might help? <cjwatson> sounds like something that should be fixed in the kernel <cjwatson> modprobe hanging => kernel bug <Tux-Rox> cjwatson: Makes sense, except that I have tried not only herd-5and the daily build from the 8th of March, but also herd-1 and 6.10 as well. They all hang at the same spot. It is really odd. I am running ubiquity with the debug switch now to see what happens. <Tux-Rox> I feel it might be a Parallels bug, as I once had 6.10 working in an older beta version. I just wanted to get feedback from the installer developers first in case they may have an idea. <Tux-Rox> cjwatson: The exact point at which it freezes the installer is at "Loading module 'aec62xx' for 'IDE chipset support'..." Still seem like a kernel bug? <Tux-Rox> Last line in the debug log states: debconf (developer): --> 1 Loading module 'aec62xx' for 'IDE chipset support'... Mar 15 07:45:28 debconf (filter): --> 1 OK <Tux-Rox> Last two lines it seems. <cr3> cjwatson: thanks again for the help yesterday, I managed to get the live cd booting over nfs this morning and only two small patches were needed: 1. initramfs-tools to support netboot= option; 2. casper to enable the network for mountroot to work over nfs. <cr3> the patches have already been submitted to Mithrandir and lifeless <cr3> now, I have yet another question: how could I hook into the live cd to run some script once the installer has reached the desktop? <cr3> I could probably modify the squashfs or somesuch, but I really want to have as little impact as possible on the original media <cjwatson> Tux-Rox: yes, still seems like a kernel bug <cjwatson> ubiquity --debug probably won't help a lot <cjwatson> Tux-Rox: I bet if you reboot and run 'sudo modprobe aec62xx' from a shell it'll hang too <cjwatson> cr3: tweak casper to dump an appropriate script into /etc/init.d, make it executable, run update-rc.d on it so that it runs late in the boot process? <Tux-Rox> cjwatson: I quit out of the installer and first tried insmod. The response was that the module was already loaded. I tried to rmmod and it said that the module was in use by [permanent] , which I expected. I then tried modprobe, and sure enough I had to eventually ctrl-c.... :-( <cjwatson> right, that's a sure sign that the kernel has a problem <Tux-Rox> I am going to try installing 6.10 once again. <cjwatson> mind you I'm surprised you could even ctrl-c <cjwatson> Tux-Rox: hang on a sec, there's a workaround at least <Tux-Rox> Cool! That is what I was hoping. <cjwatson> Tux-Rox: edit /bin/hw-detect as root on the running live CD and look for get_ide_chipset_info <cjwatson> Tux-Rox: should be a line that looks like: if [ "$baseidemod" != hpt366 ] ; then <cjwatson> Tux-Rox: change that to: if [ "$baseidemod" != hpt366 ] && [ "$baseidemod" != aec62xx ] ; then <cjwatson> Tux-Rox: you may have to repeat if other modules hang, and probably reboot after each failure, so I expect it'll be a slow process <cjwatson> Tux-Rox: or you could gamble and search for the second instance of get_ide_chipset_info in that file (in the get_manual_hw_info function) and just comment it out by putting a # at the front of the line) <Tux-Rox> cjwatson: :-) Thanks! I'll give it a go. <cjwatson> thinking about it your disk is probably detected already anyway so commenting that out should be harmless <cjwatson> maybe I should just kill off that chunk of code <Tux-Rox> It is assumed then that the live-cd puts the /etc scripts in ramdisk? <cjwatson> Tux-Rox: I don't understand the question? <Tux-Rox> Nevermind, I just typed something random that popped into my head. A bit of a brain fart is all... :-) <cjwatson> the whole / on the live session is a unionfs of the squashfs on the CD and a tmpfs <cjwatson> so you can write to all of it <Tux-Rox> I figured as much, it just took a second after typing the above cryptic question to realize it... :-) <cr3> cjwatson: I discovered that if I just dropped a squashfs in the casper directory, it could automatically be unionfs mounted for me. so, by not having to modify casper scripts, I wouldn't have to rebuild the initrd.gz <cr3> what would be nice is being able to nfs export the union of the live cd iso image and a directory containing my squashfs file, but nfs is broken in regards to unionfs :( <CIA-5> ubiquity: cjwatson * r1951 ubiquity/ubiquity/tz.py: minor neatness <CIA-5> ubiquity: cjwatson * r1952 ubiquity/ (debian/changelog scripts/install.py): * Fix broken call to kboot-installer. <CIA-5> ubiquity: cjwatson * r1953 ubiquity/debian/changelog: releasing version 1.4.1 <cr3> aha! when exporting a filesystem over nfs, it assumes that it is located on a block device. otherwise, you must specify the fsid in the exports file. as simple as that! <thom> cjwatson: do you happen to know what happens if i call pkgsel multiple times? <thom> um, pkgsel/include <thom> in preseed installs <cjwatson> you mean specify that preseed more than once? <cjwatson> preseeding isn't procedural, it's declarative. The last one will win <thom> damnation :/ <cjwatson> why not just comma-separate multiple package names? <thom> i have some common packages and some class specific ones <cjwatson> you'll need to generate the preseed file in a way that can add to a given line, then <cjwatson> or else perhaps use preseed/late_command if you just need to blat in a load of shell <thom> yeah, i'm using apt-install in late_command currently, was hoping for a cleaner way <thom> guess i'll either stay with that or just have a bunch of more or less duplicated pkgsel/includes in the class configs <cjwatson> sounds like it's worth having a smarter generator :) <thom> s/smarter// ;-) <cjwatson> heh <thom> d-i preseed/include_command string case $(debconf-get netcfg/get_hostname) in *-foo) echo foo.cfg ;; etc :-) <cjwatson> ah yes <joejaxx> cjwatson: is deboostrap-udeb downloaded along with the rest of the udebs that are pulled when you compile the d-i? <cjwatson> joejaxx: it's downloaded at run-time by d-i, not when you build the initrd (unless you're building monolithic) <joejaxx> hmm <joejaxx> because the debootstrap extract script is looking for it <cjwatson> could you give more detail? <joejaxx> on the Package.gz <joejaxx> in* <cjwatson> what debootstrap extract script? <joejaxx> cjwatson: the extract-debootstrap script <cjwatson> sure, it needs to be on your mirror <cjwatson> it doesn't need to be in the d-i initrd <cjwatson> extract-debootstrap is just there because debian-cd needs it later on for internal checking purposes <cjwatson> (which actually isn't all *that* useful with debootstrap 0.3, but anyway) <joejaxx> yeah because debian-cd is not putting the udebs on the cd archive <joejaxx> or atleast when it goes to do scanpackages during the build process it comes up with <joejaxx> dists/feisty/main/binary-i386/: New 877kB 611 files 237MB 4m22s <joejaxx> dists/feisty/main/debian-installer/binary-i386/: New 20B 0 files 0B 0s <cjwatson> check the stuff in tasks/blah/installer in the scratch directory <cjwatson> see if it actually lists any udebs <cjwatson> if not, one possibility might be that the mirror you're germinating from doesn't have a proper udeb mirror, or it could be something else weirder <cjwatson> e.g. if you're germinating off an incompletely debmirrored site, that would do it <joejaxx> oh ok #ubuntu-installer 2007-03-16 <CIA-5> ubiquity: evand * r1489 ma/ (10 files in 7 dirs): Merged with trunk. <CIA-5> ubiquity: evand * r1490 ma/debian/ubiquity.templates: I forgot to update debian/ubiquity.templates. <evand> cjwatson: See above. Sorry. <evand> I probably should've attempted the remote administration option as upon inspecting scripts/install.py it looks like it would've taken a matter of minutes to code up. Feisty+1, I suppose. <cjwatson> evand: ok - hmm, did you push that? <cjwatson> $ bzr pull <cjwatson> Using saved location: http://bazaar.launchpad.net/~evand/ubiquity/ma/ <cjwatson> No revisions to pull. <evand> whoops <evand> sorry, it's early <evand> one sec, I'll push <evand> done <cjwatson> what timezone are you on? 33ec:265c:71fe:e26d:2682:4ec2:aaa1:99ab) <cjwatson> :) <evand> cjwatson: EDT, whatever that is now <evand> 4:24AM <cjwatson> ah, that sort of early then <evand> indeed! <evand> Are there any areas of Ubiquity that need help? With everything in freeze I'm looking for something to do. <cjwatson> there are still a few bits to iron out in the new partitioner <cjwatson> somebody should sort out the timezone page rework from https://wiki.ubuntu.com/Ubiquity/FeistyReview <cjwatson> um, there's probably a bunch of other stuff but 8:30am is not my best time either <evand> heh <evand> If you think of anything else, just let me know. I'm eager to get involved in more than just m-a where possible. <evand> I'll take a look at what you've already listed later today. <cjwatson> there's https://wiki.ubuntu.com/InstallerDevelopment/ToDo <CIA-5> ubiquity: cjwatson * r1954 ubiquity/debian/ (changelog ubiquity.templates): merge from Evan <cjwatson> need to keep that better updated <cjwatson> * recover more gracefully from errors, particularly boot loader installation problems <cjwatson> sorting out that item would be fantastic; maybe some kind of retry option <evand> cjwatson: should I start up a new branch or are these things that can still go into Feisty? <cjwatson> I think they're probably feistyable, although you probably want a new branch anyway <evand> ok <CIA-5> ubiquity: cjwatson * r1955 ubiquity/debian/po/ (77 files): debconf-updatepo <evand> oh, that's something that's confusing me <evand> I noticed that the data in ubiquity.templates isn't getting put in the po files. Was there any reason for this? I thought maybe it had something to do with a new translation approach. <cjwatson> you need to run debconf-updatepo when changing .templates <cjwatson> the d-i project has a cron job that runs over svn and does that, so developers don't need to <cjwatson> we don't though <evand> Is that why things like partman-failed-mount were not in the po files? <cjwatson> partman-failed-unmount? it's there <cjwatson> #. Type: boolean <cjwatson> #. Description <cjwatson> #: ../ubiquity.templates:91001 <cjwatson> msgid "Failed to unmount partitions" <cjwatson> msgstr "" <evand> yeah whoops <evand> I was grepping for the title, which obviously doesn't work <evand> ok, noted <cjwatson> some of the templates aren't translatable - the ones with Description rather than _Description <evand> indeed <cjwatson> oh, other thing that needs attention, memory use <cjwatson> I found an easy 2MB savings the other day, but I'm sure there's lots more <evand> yeah, I noticed you started doing that <cjwatson> and fitting the UI into 640x480, for similar reasons <evand> mind if I ask how you're profiling? Or is it just a combination of the running app and top? <cjwatson> I haven't figured out a great way of doing it yet <cjwatson> I was using python-dbg and PYTHONDUMPREFS=1 <cjwatson> it's not really quite what I want <cjwatson> or maybe I'm just not good at reading the output yet <evand> hrm <cjwatson> there are some speed/memory tradeoffs in ubiquity <cjwatson> the most significant is the way I read a bunch of translations into memory because extracting them from debconf is slow <cjwatson> maybe that should become simple temporary files or something like that, which could be mmaped <cjwatson> or just opened each time <cjwatson> though of course temporary files use up memory on the live session too, so that doesn't help * cjwatson wakes up <evand> via cow, right? <cjwatson> right <cjwatson> should probably finish the work I started on making cdebconf mmap its databases, and then switch ubiquity to cdebconf <cjwatson> trying to make debconf lowmem-friendly is a bit of a dead end <evand> you're going to switch to cdebconf for Feisty? <cjwatson> no <cjwatson> I thought about it, but it doesn't really buy anything without the db mmap work <cjwatson> doesn't seem significantly faster <evand> didn't cdebconf not have some issues that debconf does? I seem to recall something about metaget not working quite right, though I could be way off. <evand> or perhaps I'm thinking of a different problem entirely <cjwatson> there have been various issues where one is better than the other <cjwatson> cdebconf doesn't have escape capb support yet, which would be a requirement to switch <cjwatson> I started writing that but got bored <evand> hahaha <CIA-5> ubiquity: cjwatson * r1956 ubiquity/ (configure configure.ac): bump to 1.4.2 <saispo> cjwatsohi all <saispo> oups <saispo> hi all :) <saispo> cjwatson: if i change my gpg keys for creating a custom cd, i must rebuild ubuntu_keyrings ? <saispo> hi cr3 <cr3> saispo: ahoy! <saispo> if no kernel found, it's due to ubuntu-keyring ? <saispo> anyone can give me some tips
{'channel': 'ubuntu-installer', 'month': 3}