#ubuntu-installer 2007-04-01 <CIA-16> ubiquity: cjwatson * r1999 ubiquity/ (configure configure.ac): bump to 1.4.6 <CIA-16> ubiquity: cjwatson * r2000 ubiquity/ (debian/changelog ubiquity/frontend/kde-ui.py): <CIA-16> ubiquity: * KDE frontend: Fetch locale from frontend object rather than partition <CIA-16> ubiquity: tree item, fixing a crash rendering unusable partitions (LP: #99660). <xivulon> Hi all #ubuntu-installer 2007-04-02 <CIA-16> ubiquity: cjwatson * r2001 ubiquity/ (d-i/manifest debian/changelog): <CIA-16> ubiquity: * Automatic update of included source packages: console-setup <CIA-16> ubiquity: 1.13ubuntu10. <CIA-16> ubiquity: cjwatson * r2002 ubiquity/debian/changelog: releasing version 1.4.6 <jetsaredim> evand: pign <jetsaredim> *ping <jetsaredim> can't seem to get a new hbox into the notebook that has all of the steps in it <evand> jetsaredim: what Ubuntu release's Ubiquity are you working with? Edgy? Feisty? <evand> cjwatson: is #100013 something you'd like to see in Feisty+1? If so I'll assign it to myself and take care of it. <evand> I believe it was mentioned by you previously as part of the m-a defaults preseeing at UDSMTV <evand> jetsaredim: what I usually do is open up the glade xml file in an editor, copy the page I want from id="stepWhatever" on to its closing tag (vim's % key press is good for this) and paste it above the id="stepWhatever" or above the next id="stepSomething" <evand> then you can open the file back up in glade and modify from there <evand> the benefit of doing it this way is that you stay consistent with the spacing between elements used in the rest of the installer. <jetsaredim> evand: sry I missed ya <jetsaredim> when I dupe the page, I can't seem to bring it up in glade to be able to add new components <jetsaredim> like if I click on the various different step h/vboxes that have different layouts the layout in glade doesn't change <cjwatson> jetsaredim: go to the 'steps' element (the notebook) and edit the Page number there <cjwatson> I have a bug open in glade asking for this to be easier, iirc <jetsaredim> so how do I add elements to the step "page" <cjwatson> delete all the existing ones and then use glade as normal ... I don't think this is the best place for glade user help :) <jetsaredim> hm <jetsaredim> good point <jetsaredim> not exactly the most straightforward <jetsaredim> where would one go for that? <jetsaredim> is this just because of the way the glade is structured <cjwatson> there's #glade3 on irc.gnome.org although I'm not sure whether it's a user channel or not <jetsaredim> i mean - like why can't I see the differences between the various step pages in glade? <cjwatson> you know the absolute basics, that you add elements by clicking on them in the palette and then clicking on an empty space in the page, right? <cjwatson> er, what are you doing to change page? <jetsaredim> just select it, I suppose <jetsaredim> i mean - i can see the default page, but it just has 2 little pages with red "X"s on them <jetsaredim> like I can get the window component to show up with the three buttons <jetsaredim> but the contents of that window never change <cjwatson> live_installer -> wizard -> hbox36 -> vbox50 -> steps in the inspector <cjwatson> change the "Page" attribute <cjwatson> crap UI, but it works <cjwatson> remember to change it back to 0 before saving (or just revert that bit of the diff later) <cjwatson> the glade guys have bugs about all this <jetsaredim> ah <jetsaredim> thanks <jetsaredim> didn't even notice that field <CIA-16> ubiquity: cjwatson * r2003 ubiquity/ (configure configure.ac): bump to 1.4.7 <cjwatson> evand: if it's reasonably easy and non-intrusive ... <evand> Ok, I'll just write it down as something to investigate for djennings@example.org. #ubuntu-installer 2007-04-03 <CIA-16> migration-assistant: evand * r48 migration-assistant/ (5 files in 2 dirs): <CIA-16> migration-assistant: * Grab the location of Documents and Settings from the registry. <CIA-16> migration-assistant: (LP: #95152) <CIA-16> ubiquity: evand * r1494 ma/ (167 files in 10 dirs): Merged with trunk. <CIA-16> ubiquity: cjwatson * r2004 ubiquity/ (debian/changelog ubiquity/components/partman_commit.py): <CIA-16> ubiquity: * Set PARTMAN_ALREADY_CHECKED when committing changes from the new <CIA-16> ubiquity: advanced partitioner, to avoid duplicate warnings (LP: #100009). <CIA-16> ubiquity: cjwatson * r2005 ubiquity/ (3 files in 3 dirs): <CIA-16> ubiquity: * Use debconf escape capability to simplify migration-assistant summary <CIA-16> ubiquity: handling. <cjwatson> evand: ^-- resolves one of your TODOs - seems to work OK for me <evand> cjwatson: thanks! I'll have to take a djennings@example.org. <CIA-16> ubiquity: jriddell * r2004 trunk/ (debian/changelog ubiquity/frontend/kde-ui.py): <CIA-16> ubiquity: + * KDE frontend: disable all widgets in autopartition subchoices <CIA-16> ubiquity: + when selecting another parent choice <CIA-16> ubiquity: evand * r1495 ma/ (debian/changelog ubiquity/components/migrationassistant.py): <CIA-16> ubiquity: * Catch exceptions in migration-assistant to avoid bringing down the <CIA-16> ubiquity: entire installer. <CIA-16> ubiquity: jriddell * r2005 trunk/ (debian/changelog ubiquity/frontend/liveinstaller.ui): Fix misplaced widgets on user details page, closes https://launchpad.net/bugs/86175 <CIA-16> ubiquity: jriddell * r2006 trunk/ (debian/changelog ubiquity/frontend/kde-ui.py): Hide error messages from user info at start of each evaluation <CIA-16> ubiquity: jriddell * r2007 trunk/ubiquity/frontend/liveinstaller.ui: set minimum size for user info error labels <cjwatson> Riddell: ooh. let me know when you want a merge <Riddell> cjwatson: merge to what? <cjwatson> main ubiquity trunk <Riddell> cjwatson: I was just doing pushes when I felt happy <cjwatson> 14:48 <CIA-16> ubiquity: cjwatson * r2005 ubiquity/ (3 files in 3 dirs): <cjwatson> 14:55 <CIA-16> ubiquity: jriddell * r2004 trunk/ (debian/changelog ubiquity/frontend/kde-ui.py): <cjwatson> ok, I thought you were off on a separate branch since you're not up to date. Fair enough, just merge yourself and push when you're done then .. <CIA-16> ubiquity: jriddell * r2008 trunk/ubiquity/frontend/ (kde-ui.py liveinstaller.ui): <CIA-16> ubiquity: Add images to error image labels <CIA-16> ubiquity: Add horizontal spacers back to user info layout <CIA-16> ubiquity: Always hide user info error labels <CIA-16> ubiquity: jriddell * r2009 trunk/ (4 files in 3 dirs): Merge with trunk <CIA-16> ubiquity: jriddell * r2010 trunk/ (debian/changelog ubiquity/frontend/kde-ui.py): Use Apport as crash handler when available <saispo> hi <saispo> cjwatson: it's germinate which create $MIRROR/cdimage/scratch/PROJECT/daily/tasks/$DIST/* files ? #ubuntu-installer 2007-04-04 <cjwatson> saispo: germinate works out what should go in those files, but it's cdimage/bin/germinate-to-tasks that actually puts stuff there <CIA-16> ubiquity: evand * r1496 ma/ (6 files in 4 dirs): Merged with trunk. <evand> cjwatson_: Please merge that whenever you get a chance. It wraps m-a in a try-except to prevent the installer from completely failing if any more issues are found in m-a after the final release. * Starting logfile irclogs/ubuntu-installer.log <saispo> hi cjwatson <saispo> ok, thanks :) <CIA-16> ubiquity: cjwatson * r2011 ubiquity/debian/changelog: standard LP bug closing format <CIA-16> ubiquity: cjwatson * r2012 ubiquity/ (debian/changelog ubiquity/components/migrationassistant.py): merge from Evan <cjwatson> evand: done, thanks <CIA-16> ubiquity: cjwatson * r2013 ubiquity/ (debian/changelog ubiquity/components/console_setup.py): <CIA-16> ubiquity: * Update Japanese keyboard layout handling to match console-setup <CIA-16> ubiquity: 1.7ubuntu18, which uses jp(latin),jp by default (LP: #63915). <CIA-16> ubiquity: jriddell * r2011 trunk/ubiquity/frontend/ (PartitionsBar.py kde-ui.py liveinstaller.ui): Add a partition bar widget <CIA-16> ubiquity: jriddell * r2012 trunk/ (3 files in 2 dirs): tidy up debugging, add changelog <CIA-16> ubiquity: jriddell * r2013 trunk/ (3 files in 2 dirs): Merge with trunk <Riddell> groovy, partition bar widget pushed, testers welcome <Riddell> cjwatson: seems that with apport a lot of problems don't get caught, they just get swallowed into the main loop <Riddell> I wonder if that's a pyqt thing <cjwatson> exceptions from sub-mainloops maybe <cjwatson> whoa. how did you hook up the partition bar widget? <cjwatson> I didn't think all the core bits were there yet :) <cjwatson> also could you call it something less generic than PartitionsBar.py since I'm sure it's qt/kde-specific? <CIA-16> ubiquity: jriddell * r2014 trunk/ubiquity/frontend/ (PartitionsBarKde.py kde-ui.py): 'ubiquity/frontend/PartitionsBar.py' => 'ubiquity/frontend/PartitionsBarKde.py' <Riddell> what core bits are needed? it just shows the disks and the relative size of the partitions <cjwatson> a way to know whether a partition is virtual, possibly <cjwatson> FWIW I'm a little worried about adding this so late. Can it be disabled easily? <cjwatson> (by me, I mean) <Riddell> sure <CIA-16> migration-assistant: evand * r49 migration-assistant/ma-search-users.c: Cleanup <CIA-16> migration-assistant: evand * r50 migration-assistant/debian/changelog: releasing version 0.4.4 <evand> cjwatson: can you push that out whenever you have a chance? <evand> thanks! <cjwatson> evand: OK, will do tomorrow morning (just back from London, tired now) #ubuntu-installer 2007-04-05 <evand> cjwatson: Definitely ok, I probably have to do another version anyway as apparently 99004 is not fixed, so I'll need to take care of that tonight <CIA-16> migration-assistant: evand * r51 migration-assistant/ (debian/changelog ma-script-utils): * Proper grep for mounted devices. (LP: #99004) <CIA-16> migration-assistant: evand * r52 migration-assistant/debian/changelog: releasing version 0.4.5 <evand> And done. Bed. <cjwatson> evand: uploaded both <CIA-16> ubiquity: cjwatson * r2015 ubiquity/ (3 files in 2 dirs): * Display an error dialog if a subsidiary process fails (LP: #92442). <CIA-16> oem-config: cjwatson * r277 oem-config/ (4 files in 3 dirs): * Display error dialogs on user-setup errors (LP: #94913). <CIA-16> oem-config: cjwatson * r278 oem-config/ (configure configure.ac): bump to 1.13 <CIA-16> oem-config: cjwatson * r279 oem-config/lib/components/user.py: fix super call <CIA-16> oem-config: cjwatson * r280 oem-config/debian/changelog: releasing version 1.13 <CIA-16> oem-config: cjwatson * r281 oem-config/ (configure configure.ac): bump to 1.14 <CIA-16> oem-config: cjwatson * r282 oem-config/ (6 files in 2 dirs): * Add an apport hook to attach /var/log/oem-config.log. <CIA-16> oem-config: cjwatson * r283 oem-config/debian/ (changelog rules): * Strip binaries. <CIA-16> ubiquity: cjwatson * r2016 ubiquity/ (d-i/manifest debian/changelog): <CIA-16> ubiquity: * Automatic update of included source packages: console-setup <CIA-16> ubiquity: 1.13ubuntu12, migration-assistant 0.4.5, partman-base 105ubuntu3. <CIA-16> ubiquity: cjwatson * r2017 ubiquity/debian/ (79 files in 2 dirs): * Update translations from Rosetta. <CIA-16> ubiquity: cjwatson * r2018 ubiquity/debian/changelog: releasing version 1.4.7 <evand> cjwatson: thanks #ubuntu-installer 2007-04-06 <CIA-16> ubiquity: jriddell * r2015 trunk/ (83 files in 4 dirs): <CIA-16> ubiquity: Merge with trunk <CIA-16> ubiquity: install partitionsbar in ubiquity-frontend-kde.install <CIA-16> ubiquity: jriddell * r2016 trunk/ (debian/changelog ubiquity/frontend/kde-ui.py): Only translate QWidgets (LP: #103575) <CIA-16> ubiquity: evand * r1497 ma/ (88 files in 6 dirs): Merged with trunk. <cjwatson> Riddell: can you not push your trunk over the top of my trunk in future? if you've had to do a merge, it's not the same branch <cjwatson> makes revision numbers very confusing when you do that <cjwatson> either pull and then push over the top, or merge and then push to somewhere else * cjwatson wonders if there's any way for him to recover the old branch state <cjwatson> also don't merge and make real new changes in the same commit <Riddell> yes, that was a mistake <cjwatson> I don't think I can get my old branch back :( <Riddell> erk, sorry <Riddell> I'll stop working in a local branch anyway, just do a checkout should avoid such problems <cjwatson> yes, that would be better #ubuntu-installer 2007-04-07 <joejaxx> cjwatson: would you happen to know what would cause the d-i not to find any "installable kernel in the apt sources" everything is up to date d-i, udebs, debs and the kernel images are in fact on the cd repository <CIA-16> ubiquity: cjwatson * r2019 ubiquity/ (5 files in 3 dirs): merge from Jonathan <cjwatson> hah, got it back ;-) <cjwatson> hmm, not entirely <cjwatson> well, revision numbers look in sequence now, so it'll do <mark> does feisty have any new installer features interesting for autoinstalls/servers? #ubuntu-installer 2007-04-09 <xivulon> Hi evand #ubuntu-installer 2007-04-10 <evand> arg, missed him <CIA-16> ubiquity: cjwatson * r2020 ubiquity/ (configure configure.ac): bump to 1.4.9 <CIA-16> ubiquity: cjwatson * r2021 ubiquity/ubiquity/components/partman.py: use separate variables for separate tasks <CIA-16> ubiquity: cjwatson * r2022 ubiquity/ (3 files in 2 dirs): <CIA-16> ubiquity: * Suppress error dialog if the user quits while a debconffiltered process <CIA-16> ubiquity: is running. * Starting logfile irclogs/ubuntu-installer.log * Starting logfile irclogs/ubuntu-installer.log <mgalvin> quick question... what tool does d-i use to install packages? is there a different minimalistic apt like tool it uses (i though i read that somewhere but can't seem to find that info again)? <cjwatson> do you mean the packages that make up d-i itself? <cjwatson> (udebs) <CIA-16> ubiquity: cjwatson * r2023 ubiquity/ (debian/changelog ubiquity/components/partman.py): <CIA-16> ubiquity: * New partitioner: If the user tries to change multiple attributes of a <CIA-16> ubiquity: partition at once, look each item up in the partman menu in sequence <CIA-16> ubiquity: rather than looking them all up at the start. This makes it possible <CIA-16> ubiquity: e.g. to change the method from one that doesn't support a mountpoint to <CIA-16> ubiquity: one that does and set a mountpoint at the same time. <mgalvin> cjwatson: no... how does d-i install each package such as xorg, gedit, etc... does d-i call apt or apititude or does this happen some other way? <cjwatson> it calls tasksel which calls aptitude <cjwatson> actually, no, apt-get these days <mgalvin> ah, thats what i was looking for <mgalvin> dapper uses the method you just mentioned correct? <mgalvin> tasksel <mgalvin> cjwatson: thanks! <cjwatson> no, dapper called aptitude directly <mgalvin> hm, ok cool <mgalvin> thanks <CIA-16> ubiquity: cjwatson * r2024 ubiquity/ (17 files in 3 dirs): * Update translations from Rosetta. <CIA-16> ubiquity: cjwatson * r2025 ubiquity/ (d-i/manifest debian/changelog): <CIA-16> ubiquity: * Automatic update of included source packages: console-setup <CIA-16> ubiquity: 1.13ubuntu13, partman-auto 62ubuntu10. <CIA-16> ubiquity: cjwatson * r2026 ubiquity/debian/changelog: releasing version 1.4.9 #ubuntu-installer 2007-04-11 <joejaxx> hmm <CIA-16> migration-assistant: evand * r53 migration-assistant/ (debian/changelog ma-script-utils): * Handle more than one installed copy of Windows (LP: #97081). <tepsipakki> lvcreate in d-i is for some reason quite slow <tepsipakki> now <tepsipakki> it was much faster before <tepsipakki> I'll take a look at the logs once the machine has installed <tepsipakki> cjwatson: would it be possible to copy casper.log to /var/log/installer after ubiquity has done it's business? It would help debugging X problems <tepsipakki> now they need to boot the session again to get that log <saispo> hi all <saispo> cjwatson: when i boot on a feisty custom cd i have an error wich say me thats no kernel module loaded, have you an idea ? <saispo> i think i have the solution... <saispo> no, same error :/ <saispo> anna[4466] : WARNING **: no packages for kernel in archive <saispo> http://djennings@example.org/msg01803.html <saispo> cjwatson: http://people.ubuntu.com/~ubuntu-archive/seeds/ubuntu.feisty/installer <saispo> is not up2date :/ <cjwatson> hmm, I wonder why <saispo> 2.6.20-13 in installer and not 2.6.20-14 <saispo> (installer seeds file) <cjwatson> yes I know <saispo> :) <saispo> thanks for fixing them :) <saispo> cjwatson: have you an idea how can i upgrade debian-cd, germinate and britney without broking all things i have modified ? <cjwatson> bzr has perfectly good merge tools <cjwatson> if you make modifications it's your responsibility to deal with merging them <cjwatson> I will not and cannot help you <cjwatson> saispo: seeds fixed now, thanks for the heads-up <saispo> no problem <saispo> i work on ubuntu everydays too :) <saispo> preseeding lvm automatic partition is very long... <saispo> tepsipakki: same problem here <cjwatson> tepsipakki: yeah, file a bug on casper about it? <CIA-16> ubiquity: cjwatson * r2027 ubiquity/ (4 files in 2 dirs): <CIA-16> ubiquity: * Improve the layout of the language page resulting from the release-notes <CIA-16> ubiquity: link (LP: #105470). <CIA-16> ubiquity: cjwatson * r2028 ubiquity/ (configure configure.ac): bump to 1.4.10 <CIA-16> ubiquity: cjwatson * r2029 ubiquity/ (d-i/manifest debian/changelog): * Automatic update of included source packages: hw-detect 1.45ubuntu4. <CIA-16> ubiquity: cjwatson * r2030 ubiquity/debian/changelog: releasing version 1.4.10 <tepsipakki> cjwatson: or on ubiquity? <cjwatson> no <cjwatson> casper generates the ubiquity-casper binary package and this belongs there <tepsipakki> ah, ok <penta> hi, can anyone help me with activating lvm at the feisty installer? <cjwatson> make sure all the PVs are marked as "Use as: physical volume for LVM", and then select "configure the logical volume manager" in the partitioner <penta> ?? where do i find configure the lvm (feisty beta) <penta> i use the alternate cd and was expecting something like activate LVMs (like dapper and edgy had) <penta> i chose 'text mode install' and when loading partition programm there are three guided and one manual partitioning available <penta> the lvm i want to install into is configured and in use (i want to install feisty besides edgy and etch) <cjwatson> use manual partitioning and then do as I said above <CIA-16> ubiquity: evand * r1498 ma/ (25 files in 7 dirs): Merged with trunk. <CIA-16> ubiquity: evand * r1499 ma/ (debian/changelog ubiquity/frontend/gtkui.py): <CIA-16> ubiquity: * Prevent mounted volumes icons from appearing on the desktop. (LP: <CIA-16> ubiquity: #105531) <evand> cjwatson: not sure if you want that one, but I got a bug report about it and I saw that mdz mentioned it in -devel. I would've split it out into its own function but that seemed like a waste. #ubuntu-installer 2007-04-12 <saispo> hi all <saispo> anyone know why i get this error in log file when i generate a dapper CD : Missing debootstrap-required hfsplus ? <saispo> tepsipakki: have you open the bug report about casper and lvm preseed partitionning ? <cjwatson> evand: thanks, but I think post-feisty at this point <saispo> hi cjwatson :) * Fujitsu wonders what the chance of getting partman-crypto integrated into Ubiquity for gutsy would be. <saispo> :) <saispo> hi cr3 <cjwatson> Fujitsu: fair - it's on the UDS schedule <cjwatson> the only reason it didn't happen for feisty was that cryptsetup and usplash didn't play nice together <cjwatson> saispo: what does casper have to do with LVM preseeding? <saispo> oups, not casper <saispo> about partman-lvm <Fujitsu> cjwatson: Great! <saispo> cjwatson: you have an idea why ? it's not hurry... but for final release it may be good <saispo> with latest updates i haven't got this <cjwatson> saispo: I have no idea what you're talking about <cjwatson> oh, the hfsplus thing? <cjwatson> that means that your archive has hfsplus at Priority: important or required, but it isn't in your minimal seed <saispo> no hfsplug, i correct this things <saispo> cjwatson: about lvm preseeding automatic, it's so slow... <saispo> before i haven't got this things <cjwatson> oh that's known, nothing to do with preseeding <cjwatson> too late to fix for feisty though <cjwatson> bug 105623 <cjwatson> it'll just have to go in the release notes, and maybe be point-release material <saispo> ok :/ <saispo> thanks :) <cjwatson> evand: let me know when you're around? I need to talk to you about weirdness in the m-a component <cjwatson> evand: specifically bug 105861 <cjwatson> evand: panic over, decided it wasn't release-critical <evand> here now <evand> hrm, yikes <cjwatson> I don't think it's quite as weird as I initially thought, but it's weird <cjwatson> why does ma-ask need to be called from ok_handler? <evand> checking <cjwatson> dropping back into a UI loop from cleanup is freaky, but probably just about OK - it's the call of run_command from ok_handler that really makes me blink <evand> I'm still looking it over, but the general overview is that it calls ma-ask the first time to figure out what all the options are to populate the interface, it then calls ma-ask again to see if there were any errors in the options that the user selected. If that pops up an error question, then it drops back to the interface and sets up an error, otherwise it proceeds to the next page <cjwatson> Hmm. In that case I think it would be best to refactor it so that you can avoid exiting ma-ask in between <cjwatson> (not feisty, but) <cjwatson> if that doesn't fit with the d-i control flow, something I've been known to do is create a wrapper script in scripts/ that does something extra that's ubiquity-specific <evand> Ah, that would make much more sense. I tried to avoid making ma-ask ubquity specific, but I'm sure that can still be avoided <evand> ah, ok <cjwatson> which might for instance include a spurious db_input/db_go just to give you something to block on <cjwatson> - mount $device $mountpoint <cjwatson> + mount $device $mountpoint || error "failed to mount $device" <cjwatson> evand: doing that to ma-script-utils would be good - I have a partition on my test system here where mount fails because it's an LVM PV <cjwatson> which was the root cause of 105861 <cjwatson> took me ages to find where the 32 was coming from :) turns out it's EX_FAIL from mount <evand> whoops, I thought I did check that mount succeeded, but apparently not <evand> ah, just in windows <evand> hilarious <cjwatson> and /home <evand> indeed <cjwatson> wah, escaping in summary is broken <evand> right! <evand> I forgot to mention that to you <cjwatson> fuck <evand> I noticed it as well <evand> heh <cjwatson> sadly not release-critical either, I think ... <cjwatson> trivial to fix <evand> I've got to bolt, I have work in less than an hour. If you happen to cross any more crazyness in m-a, just let me know in here and I'll try to get back to you ASAP. <evand> I assigned that bug to myself. I'll refactor for Gutsy. <cjwatson> thanks <cjwatson> yeah, it seems to be largely working ok, just some minor glitches <cjwatson> sorry for panicking :) <evand> no worries, I understand completely. I can see from -devel that things are quite hectic right now for the release team. <cjwatson> just a bit <CIA-16> ubiquity: cjwatson * r2031 ubiquity/ (configure configure.ac): bump to 1.4.11 <CIA-16> ubiquity: cjwatson * r2032 ubiquity/ (debian/changelog scripts/summary): * Fix escaping of migration-assistant summary. <CIA-16> ubiquity: cjwatson * r2033 ubiquity/ (debian/changelog scripts/summary): <CIA-16> ubiquity: * Only display partitions with scheduled migrations in the summary, and <CIA-16> ubiquity: improve the formatting slightly. <CIA-16> ubiquity: cjwatson * r2034 ubiquity/ (debian/changelog scripts/summary): * Remove another stray newline from the migration-assistant summary. <CIA-16> ubiquity: cjwatson * r2035 ubiquity/ (configure configure.ac debian/changelog): bump to 1.5.0; this is all post-feisty <cjwatson> (whee) <CIA-16> ubiquity: cjwatson * r2036 ubiquity/ (debian/changelog ubiquity/frontend/ubiquity.glade): <CIA-16> ubiquity: * GTK frontend: Pressing Enter in the migration-assistant user/password <CIA-16> ubiquity: entry boxes activates the Forward button. <cjwatson> 15 files changed, 285 insertions(+), 2167 deletions(-) <cjwatson> monkey like * cjwatson is deleting the old partitioner ... <CIA-16> ubiquity: cjwatson * r2032 feisty/debian/ (changelog po/fr.po po/tr.po): <CIA-16> ubiquity: * Fix broken French and Turkish translations of "Go Back" and "Continue" <CIA-16> ubiquity: (LP: #105903). <CIA-16> ubiquity: cjwatson * r2033 feisty/debian/changelog: releasing version 1.4.11 <penta> hi <penta> i have some problems with installing feisty on an existing lvm partition #ubuntu-installer 2007-04-13 <CIA-16> ubiquity: cjwatson * r2038 ubiquity/debian/ (changelog po/fr.po po/tr.po): merge from feisty branch <CIA-16> ubiquity: cjwatson * r2037 ubiquity/ (98 files in 7 dirs): * Remove the old advanced partitioner. <CIA-16> ubiquity: cjwatson * r2039 ubiquity/ubiquity/components/partman_commit.py: use new question_type helper method <CIA-16> oem-config: cjwatson * r284 oem-config/ (debian/changelog oem-config): <CIA-16> oem-config: * Print usage message and exit if any non-option arguments are supplied to <CIA-16> oem-config: oem-config; suggest oem-config-prepare (LP: #105940). <TodoInTX> Hello, I've got an IBM Thinkpad T43. I'm trying to install 7.04 and the installer freezes 3% into "Loading Kernel" I don't think I've got a JMicron controller and the symptom is a bit different from that bug report. <TodoInTX> The laptop is currently running 6.10 just fine <penta> hi, i have some problems with activating lvm in the installer <CIA-16> ubiquity: cjwatson * r2040 ubiquity/ubiquity/components/migrationassistant.py: typo <saispo> hi <saispo> cjwatson: debian-cd, ubuntu-cd, britney and germinate are up2date on people.ubuntu.com/~cjwatson/ ? <cjwatson> yes <saispo> ok, thanks :) <saispo> cjwatson: merge working find, w00t :) <saispo> but i don't know why now he want to add +openoffice.org-help-gl on the cd.. <CIA-16> ubiquity: cjwatson * r2041 ubiquity/debian/changelog: reorg <CIA-16> ubiquity: cjwatson * r2042 ubiquity/ (debian/changelog desktop/ubiquity-gtkui.desktop.in): <CIA-16> ubiquity: - Drop X-Ubuntu-Gettext-Domain=ubiquity in the .desktop file for now, to <CIA-16> ubiquity: work around a bug somewhere that causes the translations in the <CIA-16> ubiquity: .desktop file to be ignored in that case. #ubuntu-installer 2007-04-14 <geo_> Can somone tell me what the difference is between the CD version, and the DVD version? Like what extra stuff is on the DVD #ubuntu-installer 2007-04-15 <czr> does anyone know whether it's possible to disable usplash via d-i/preseed directives? Installing ubuntu/kubuntu 6.10 via preseeds (desktops) and seems that usplash doesn't switch VT (or something weird). end effect is that usplash progress bar is almost full, but display manager isn't seen. without 'splash' in kernel command line it works just fine. <czr> (and yes, I know it's sunday) <cjwatson> there's a slightly cheating way, by preseeding debian-installer/framebuffer=false. That'll have other effects but if your install is entirely automatic then they may not matter all that much. <cjwatson> failing that you can just sed /target/boot/grub/menu.lst from a preseed/late_command <cjwatson> other way is to just not install usplash at all, but that's probably difficult since it's (currently) a dependency of ubuntu-desktop et al <cjwatson> other effects> i.e. d-i won't use a framebuffer for its own display so the display may well be pretty wonky <czr> cjwatson, thanks. fb=false doesn't disable usplash though <czr> the installer runs without fb, but usplash will still be installed :-) <czr> and sed is what I'm trying now :--) <cjwatson> it's installed, but it should take 'splash' out of menu.lst <czr> but I'm wondering whether /target/boot/grub/menu.lst exists at the point where late_command is executed (will find out soon enough) <czr> hmm. I'll try that too then <cjwatson> if ! db_get debian-installer/framebuffer || [ "$RET" = false ] ; then <cjwatson> # No framebuffer, so disable the splash screen. <cjwatson> sed -i '/^# defoptions=/ { s/ *splash//g; s/=splash\( *\|$\)/=/; }' \ <cjwatson> $ROOT/boot/grub/$menu_file <cjwatson> need_update_grub=1 <cjwatson> fi <cjwatson> late_command> yes <czr> thanks a bunch <cjwatson> no problem <cjwatson> you'd need to do something slightly different from the sed above if you were doing it in late_command <cjwatson> that's expecting update-grub to be run later so it only has to change defoptions <czr> I have sed -i s/splash/nosplash/ /target/boot/grub/menu.lst (yes, I'm cheating ;-) <cjwatson> I guess that's one option <czr> I've used the nosplash before because of the defoptions thing <czr> well, it's installing grub now * cjwatson goes back to bed. Was up in the middle of the night frobbing kernel uploads <czr> must be close to 60 installs now ;-) <czr> oh, night night, thanks a lot again :-) <czr> the sed thing works quite nicely, I'll try the proper way next <czr> cjwatson, noticed that you're back :-). any hints on how to go to implement a partitioning scheme which uses LVM and partitions max 20G of the first disk like that and works with sata, scsi, usb and ide? :-) <czr> using d-i/preseeds #ubuntu-installer 2007-04-16 <wowow> hey guys <wowow> installing dapper on intel chipset systems is a problem, screen goes all black 3/4'rs of the way through <wowow> and not sure how to push the install through <wowow> has anyone seen this before or knows of tips to help rectify the issue? <wowow> note: all terminals have gone black with one ... white character pixel in the middle of the screen <wowow> i've only noticed this ONLY on intel chipset mobos <wowow> anyone? <cjwatson> wowow: xresprobe problem IIRC rather than an installer problem as such. Wait half an hour or so to make sure, and then hit Enter and it'll probably boot. <wowow> oh really? <wowow> you know what? <wowow> that worked exactly once ... didn't realize it was half hour <wowow> damn installing feisty right now ... hmm <wowow> cjwatson, thanks for the heads up! <wowow> any hint on wha tmight be going on with xres? <cjwatson> there's a bug about it somewhere (well, at least ten), but it's not my field of knowledge <cjwatson> half an hour is probably an exaggeration, but ... <snoops> evand hi - I'm wondering what your plan for the migration-assistant is? What do you envisage it becoming/doing etc? <evand> snoops: Well, I haven't written the spec for Gutsy yet, and we still need to discuss things at UDS, however there are a few things that stand out... <evand> KDE support is critical. <evand> Vista support is something I'd like to cover, which shouldn't be too hard as the registry format hasn't changed... <evand> OS X support should be feasible, but I'm willing to let that one slide if I don't find enough time for it <evand> the main thing is adding targets for Windows XP/Vista <evand> it doesn't import the actual email yet, and it doesn't import from Thunderbird <evand> there are more things that can be imported from IE, Firefox, and Opera <snoops> importing from outlook (not express) would be great - except for the silly format it uses <evand> indeed, that's a big one <snoops> I would like to try and add support for different im clients - googletalk, msn <evand> that would be great <evand> the biggest problem there has been figuring out where the password is stored and how to decode it <evand> as you can imagine, the IM clients aren't very forthcoming with that information <evand> and it's kind of sucky that it doesn't import the passwords now, as I can imagine people easily forgetting their AIM password <snoops> hehe...I can imagine <evand> GoogleTalk is something I completely forgot about <snoops> one thing I think would be great is importing your history - for instance msn saves history in xml files and applies and xslt stylesheet for viewing <evand> That would be pretty easy to pull in as the only major dependency that m-a has right now is libxml2 <evand> which makes reading such files trivial <snoops> excellent - and with that format to gaim/kopete etc <evand> I try to avoid pulling in major libraries as I'd like to see Debian use this in d-i (hopefully with the polishing for that getting done this development cycle) <evand> indeed <snoops> skype is another one <evand> definitely <evand> some people have suggested installing it as well, but I believe that's bloat. <evand> I'm willing to discuss such an idea if someoene brings it up at UDS or on the VoIP like during the m-a spec meeting at UDS <evand> s/like/line/ <snoops> perhaps making an install.sh file on the desktop to install those proprietary apps - skype, opera <evand> oh! One really big thing I forgot to mention... <evand> migration-assistant merges things <snoops> oh? <evand> so for IM clients it looks in the Gaim accounts file, sees if the account is there, if not, it puts it in <evand> it doesn't just copy things 1-to-1 <evand> which can be difficult, but really increases the things we can do with it <snoops> yep I agree with that <evand> I'd prefer actually installing the packages over a script that does it, but I'm still quite weary of that. <snoops> what's the gui for it like (sorry I haven't tried feisty yet)? Are there a bunch of tick boxes for what you want to import? <snoops> or is it just - try to import everything <evand> http://evalicious.com/migration-assistant.png <snoops> superb <evand> it looks slightly different now <evand> there's an explanation that those boxes on the bottom are for the account you're importing into <snoops> oh, itunes importing would be a valuable one, as well as winamp <evand> you can import multiple accounts from multiple operating systems into a single account or as many accounts as you'd like <snoops> the winamp one would be good, since you can read the playlist file for all the locations of files <evand> it actually already imports from iTunes in that iTunes puts all your music in My Music and it copies that <evand> I'll look into what winamp does though <snoops> I'd really like to help out with this - migration is something I personally believe can be improved a lot <snoops> how about things like network settings <evand> you're more than welcome to branch off of trunk and develop from there, then let me know the url so I can merge it into trunk where necessary <evand> network settings is definitely on the list <evand> whether to stop at wireless settings or do something crazier like windows domain membership remains to be seen <snoops> is the list in your head or is there a a todo list? <evand> I have a tomboy note for it, which I'll pretty soon convert into a spec for Gutsy <evand> or at least the draft for one <evand> I don't know if you're familiar with the Ubuntu release process, but basically there's a developer summit in Spain starting on the 6th, where we'll gather and write up specs for the features that should be in Gutsy <evand> for those that cannot make it to spain, there's VoIP lines for each spec meeting <snoops> what do you think about the install.sh idea for apps like opera/skype? That could be extended a bit more for things like vlc etc <snoops> I'm in New Zealand, doubt I'll be able to make it to spain..voip would be cool though :) <evand> once the specs are finalized, then we do feature development for a few months, then things get locked down for bug fixing <evand> yes, you should definitely call in. The information for that will be posted as we get closer to the event. <evand> I'm not keen on an install.sh script. The proper way to do it would be to have the installer actually install said packages, but I'm not sure if that's a good idea. It's definitely something we can discuss further at the summit, when there's more than just the two of us talking about it. <evand> In my head it comes down to is that within the scope of migration-assistant, but we shall see <snoops> yep, cool <snoops> I'll mull away at a few things - like a im-history-import <snoops> and take a look at googletalk <evand> awesome, let me know if you need any guidence or explanation of the code <snoops> I don't think this is directly in the migration scope, but one thing I had trouble with when first getting into linux was what application replaces the one I used in windows.. Do you see any potential after looking at a hdd (and the list of programs) for a list suggesting.. "for outlook, outlook express use evolution", "for photoshop, mspaint, paint.net try the gimp, or gimpshop" etc <evand> I see that as more of a documentation and naming issue <snoops> yep, cool. <evand> the ubiquity-slideshow spec sort of covers this, but I don't think the intention was to explain what applications are used as replacements, but rather what exciting features are in this release <snoops> Over the next couple weeks when I get time I'll try to start chipping away at various settings - skype, network settings, msn, gtalk <evand> great! keep me posted <snoops> thanks - and I must say, I really appreciate being able to talk to the person who's made this, to get some insight. It's been very helpful <evand> anytime, thanks for your interest <saispo> hi <saispo> if i use apt-install or apt-get install in a preinst or postinst file with debconf, it's possible to get a progress bar ? <cjwatson> err, a preinst or postinst where? <saispo> in a meta package <cjwatson> preinsts aren't allowed in d-i and neither preinsts nor postinsts of regular (non-udeb) packages are allowed to install other packages <cjwatson> metapackages should just depend on other packages, not do crazy things like trying to apt-get install them <saispo> cjwatson: yes, i understand <saispo> but when i preseed an installation of a metapackage in d-i, the progress bar stop... <cjwatson> the packaging system isn't re-entrant - you can't call it recursively <cjwatson> if you try, stuff will break <saispo> cjwatson: ok, not possible ? <cjwatson> nope <saispo> hmmm <cjwatson> when you get a hang, check syslog <cjwatson> but in general, don't try to call dpkg/apt/etc. from maintainer scripts. :) <saispo> no hang :) it install the package but the progress bar stop on "preseeding application..." <saispo> cjwatson: ok :) <cjwatson> "preseeding application" isn't a string in the installer - this must be your code <saispo> cjwatson: i don't think it's the real phrase i have :) <cjwatson> you must never paraphrase messages <saispo> the progress bar hangs when i use preseed_latecommande="apt-install eole --force-yes" for example <cjwatson> that's (a) full of typos (b) not legal apt-install syntax <cjwatson> apt-install != apt-get install <saispo> --force-yes it's not comptible with apt-install ? <cjwatson> no <saispo> i just want to enhance the d-i for my project :) just this, if it's not possible, it's not possible :) <cjwatson> sure, but don't make up options and expect them to work ;) <saispo> :) <cjwatson> there is no reason it should not be possible to install extra packages, as long as those packages don't do abnormal things in their maintainer scripts <saispo> cjwatson: and if i create a metapackage which includes three metapackages and i use debconf-apt-progress in a preseed_latecommand, it's not possible too ? :) <cjwatson> it is possible with very careful use of in-target, but it is not easy to get right and I would recommend you keep it simple <saispo> yep <saispo> i think it's more safe :) <cjwatson> I would advise just using apt-install and not worrying about the progress bar <saispo> i will must switch to ubiquity ;-) <cjwatson> or preseeding pkgsel to install your packages, in which case you will get a progress bar <saispo> if i use pkgsel, i must modify pkgsel-data packages no ? <cjwatson> this is documented in the preseeding appendix of the installation guide <cjwatson> under "Package selection" <saispo> ok, will see this <saispo> i don't understand how to create pkgsel-data... will read :) thanks <cjwatson> "pkgsel-data" does not exist <saispo> k <saispo> #d-i pkgsel/include string openssh-server build-essential if i change openssh-server with my metapackage, i will get a progress bar you think ? <cjwatson> it will be included in the pkgsel stage of the installer which has a progress bar <saispo> ok, thanks <saispo> will test this :) <saispo> but i can use preseed_latecommand="pkgsel eole" at the prompt boot cd ? <saispo> or i must write it in the preseed file ? <cjwatson> that is completely garbled - please read the documentation! <cjwatson> it is release time, I cannot possibly read the manual for you at this point, I'm sorry <saispo> i understand, no problem <saispo> i have some difficult to understand the difference between pkgsel and tasksel... <cjwatson> you do not need to; read the documentation <saispo> k <saispo> thanks Colin :) <cjwatson> I'm afraid you must enter things precisely as documented rather than guessing - there is no indication anywhere in the manual that "pkgsel" might be valid as a command inside preseed/late_command (not preseed_latecommand, which is mentioned nowhere) <saispo> you're right :) <saispo> because i have to problem, and i try to resolve the two problems with one solution, and it's not the good solutionn <saispo> the second problem is to have a choice in d-i for a preseed schema partion or manually do it... <saispo> cjwatson: pkgsel work fine, thanks :) <cjwatson> good <poningru> hmm anyone here familiar with the sparc installer? <cjwatson> only in broad terms <poningru> we need someone for the 7.04 final 'tour' <poningru> https://wiki.ubuntu.com/FeistyFawn/RC <poningru> specifically https://wiki.ubuntu.com/FeistyFawn/RC?action=show&redirect=Ubuntu704Features#head-97f528cdec6aa0524271cdcc137149e6fbc950ab <poningru> cjwatson: just a feature writeup is what we need <poningru> and if you have any suggestions to add to that would wonderfull too <cjwatson> ask fabbione <CIA-16> oem-config: cjwatson * r285 oem-config/ (debian/changelog lib/components/console_setup.py): <CIA-16> oem-config: * Update Japanese keyboard layout handling to match console-setup <CIA-16> oem-config: 1.7ubuntu18, which uses jp(latin),jp by default (LP: #63915). #ubuntu-installer 2007-04-17 <tepsipakki> I guess this won't be too much offtopic here :) http://apcmag.com/5862/intel_shows_pc_booting_windows_with_uefi_firmware <tepsipakki> forget the windows part <cjwatson> tepsipakki: I do dearly hope that we can forget the DOS partition table format in time <cjwatson> tepsipakki: though I'm worried that we still need the VGA BIOS to initialise many graphics cards for us; wonder if these PCs are any different in that regard than the Intel Macs <tepsipakki> remains to be seen.. bios-compatibility needs to be around for some time :/ <tepsipakki> what would be the replacement for DOS partition table? <tepsipakki> I hear that AIX systems have a flexible format <cjwatson> tepsipakki: GPT <tepsipakki> ah, reading -> <cjwatson> ia64 systems and Intel Macs already use it <cjwatson> though for Intel Macs we still have to mirror it to DOS-style ("MBR") partition tables in a slightly crazy way <tepsipakki> hum, the AIX scheme is practically just LVM using the drives as PV:s.. bleh <tepsipakki> so nothing special there <cjwatson> I must admit that AIX's filesystem management is a dream to se <cjwatson> use <cjwatson> it's the only nice thing I ever saw about AIX <tepsipakki> heh <tepsipakki> I like AdvFS of Tru64 <tepsipakki> filesets are nice <cjwatson> I didn't know Tru64 had the LVM-like fs grow/shrink stuff <cjwatson> I mean in AIX it's "please give this fs another 10GB" "OK" <tepsipakki> in Tru64 the layering is a bit confusing, since AdvFS has some of the features of LSM <cjwatson> ah <tepsipakki> but you could have partitioned root (root_domain), swap, and the rest (usr_domain, usually). Then create multiple filesets to the domains as needed. They still share the same storage space, but can have quotas <tepsipakki> like, in usr_domain we have var- and tmp-filesets, which have quotas <cjwatson> oh, ok, that's neat <cjwatson> quotas are the main reason to bother with partitioning on a server ... <tepsipakki> true.. <tepsipakki> I still have the habit of using multiple partitions on my desktops, but on the most recent installation it only has root, var and home :P <tepsipakki> and a spare one for testing <jetsaredim> evand: ing <jetsaredim> *ping <jetsaredim> or cjwatson if you're around too <jetsaredim> I'm finally getting a chance to go over those notes that evand gave me a few weeks ago <jetsaredim> and I had a quick question <jetsaredim> actually just more questions in general <evand> jetsaredi1: pong <evand> sure thing <evand> though Tuesdays and Thursdays are quite busy, so if I don't respond right away, rest assured I'll respond later in the day <spheard> hi, Ive had my MBR wiped out by bloody vista, Im trying to use $sudo grub-install to reinstate it but its asking for a device sda0 and sda1 dont do it. Im using edgy <cjwatson> 'sudo grub-install hd0' is normally what you want to install on the first drive <cjwatson> or 'sudo grub-install /dev/sda' <cjwatson> (assuming your disk really is sda) <spheard> sata <cjwatson> hd0 is the grub syntax. /dev/sda is the Linux syntax. Either should work <spheard> then grub-install will search all the partitions and list them <spheard> ? <cjwatson> no <spheard> oh <spheard> then I have to put in each line? <cjwatson> what? <cjwatson> just use either of the commands I suggested <spheard> I take it then I will have to tell grub where all my operating systems are <cjwatson> no, your old /boot/grub/menu.lst will still be there <cjwatson> it's not stored in the MBR <cjwatson> grub-install will just switch it back on <spheard> oh of course <spheard> sweet <spheard> so $grub-install /dev/sda should make it all good then <spheard> although the partition with grub on is is sda5 <spheard> thnks, Im going to give it a go <wienczny_> Hi I heard that there a plans for a new automatic installer for feisty+1 but I did not find a spec yet. Does a spec already exist? <cjwatson> I think that's overstating the case slightly <cjwatson> you're probably thinking of https://blueprints.launchpad.net/ubuntu/+spec/ubiquity-automation <cjwatson> which is basically adjusting ubiquity to make automation a bit easier <cjwatson> I suspect many people doing automated installs will still want to use d-i though <mark> is there anything new in that respect in feisty? <cjwatson> the main use cases for ubiquity automation are (IMO) people who are already doing customised live CDs and automatic testing <cjwatson> mark: very little, just minor tweaks <mark> ok <cjwatson> partman-auto/disk is optional now if you have only one disk and have partman-auto/method preseeded to regular <cjwatson> that's about the only significant thing <cjwatson> it's been a slow cycle because Debian's been frozen <mark> hmm oh well <mark> at least I won't have many problems adapting to feisty ;) <wienczny_> There are no plans beyond that? <cjwatson> wienczny_: do you have specific requests? <mark> automated LVM/raid would be really nice <cjwatson> right, but that's for d-i <cjwatson> and being worked on in Debian already <mark> ok <wienczny_> Its just that I wrote my own small scripted-installer for debian and ubuntu and I'd like to see a better solution in the distro <cjwatson> wienczny_: what did you find you couldn't do with the existing d-i preseeding facilities? <cjwatson> or with Kickstart in the case of Ubuntu <wienczny_> Installing software-raid. lvm. etc. <cjwatson> ok, then what I said to mark <mark> heh <cjwatson> ubiquity-automation isn't going to help with that <cjwatson> and you don't want a "new automatic installer", you want extensions to the existing one :-) <cjwatson> no point reinventing a perfectly good whell <cjwatson> wheel <mark> no, d-i seems pretty good <wienczny_> I want an installer that is easier to use that can do raid and lvm ;-) <cjwatson> ubiquity doesn't do lvm or raid yet, although it's on a sort of tenuous long-term roadmap <mark> d-i raid/lvm works ok once you learn about its quirks <cjwatson> a lot of the point of doing the new ubiquity advanced partitioner in feisty was to make it more practical to fit advanced partitioning methods like lvm and raid into it in the future <mark> it's a REAL pain on 9600 bps though ;-) <cjwatson> this was basically not practical with gparted/qtparted <cjwatson> once those are fitted into ubiquity and ubiquity-automation is done, it'll be possible to use exactly the same preseeding as becomes available in d-i for LVM and RAID <cjwatson> </vision> * cjwatson likes symmetry <cjwatson> however, there's enough stuff backed up from previous cycles for ubiquity that I'm not sure when lvm and raid will happen <wienczny_> Will it possible to use ubiquity for automatic network installation? <cjwatson> ubiquity's very much designed for live CDs at the moment, although the LCA2007 guys did work out a hack to get it to install over the network <cjwatson> it would probably be a smallish patch from someone interested <mark> is this for some automated desktop deployment thing? :) <cjwatson> make sure casper's support for netbooting works properly, and teach ubiquity where to get its source filesystem <mark> because if you were installing servers like me, you wouldn't care about ubiquity probably ;) <wienczny_> mmh. My point is this: Ubuntu tries to be a server-distribution (some sort of that). If you've got a look at SuSE or Redhat you will see that its a lot easier to do a unattended automatic installation of complete networks. This is still missing in ubuntu <mark> why would you want ubiquity for servers? <cjwatson> for unattended installations ... what mark said <cjwatson> we already implement compatibility with RH's Kickstart tool <cjwatson> the main pain is that the underlying preseeding facilities for LVM and RAID aren't quite there, but when they are, we can extend that to them <czr> do ks lvm/raid setups work in feisty d-i? <cjwatson> and then I think it's merely a documentation problem <mark> I imagine it hard to explain ;) <cjwatson> czr: no, due to the problem I just mentioned <wienczny_> ^^ Kickstart would be great if I could just take the redhat kickstart docu and do whats documented there ;-( <cjwatson> it's documented as an omission in the installation guide <cjwatson> wienczny_: aside from LVM and RAID, is there anything you can't do? <czr> cjwatson, I thought so, was suprised by your "we already implement compatibility"-thingy. nm :-) <cjwatson> Our installation guide includes errata of what we don't implement relative to RH <czr> are pre and post-scripts supported? <cjwatson> yes <wienczny_> I'm need to doing initial configuration that goes beyond the di <czr> cool. x setups? <cjwatson> they may only be shell scripts <mark> wienczny_: like what? <czr> they mostly are anyway, shell restriction is not a problem <cjwatson> czr: to some extent, yes, though the need for that is gradually going out the window as X gets smarter <cjwatson> we translate xconfig options into xserver-xorg/blah preseeds <wienczny_> deploying exchanging cfengine-keys <cjwatson> wienczny_: post scripts should let you do all of that I'd've thought <mark> that's hardly a d-i thing is it ;) <mark> yeah <wienczny_> You need to get it over a secured channel... <czr> cjwatson, well, I normally only set the resolution through ks, and let it decide and autodetect the rest automatically <mark> I never understand what "secured" means on a newly installing box <czr> haven't really figured out how to do that with d-i yet (worked with edgy though) <cjwatson> xconfig --resolution is translated into xserver-xorg/config/display/modes <wienczny_> Well, I'm currently copying all of those files using ssl and a kerberos-ticket. <cjwatson> in a slightly hackish way although I think the original is hackish to begin wish <cjwatson> with <cjwatson> wienczny_: if you install the relevant packages in %packages, you should be able to do just the same thing with a chrooted %post script * czr nods at cjwatson <czr> I'll take a stab at creating lvm stuff with d-i next week maybe when I have the time. I need a setup which will install on any hard disk (not depending on the device name). <wienczny_> cjwatson: do you run tests on automatic installtions of complete desktops? I ran into great problems doing that. <czr> and will be testing with feisty, so I guess I'll be counting the installs again. took 82 installs to get edgy in the way I wanted :-) <mark> sounds familiar ;)
{'channel': 'ubuntu-installer', 'month': 4}