#ubuntu-installer 2007-02-01 <CIA-4> ubiquity: cjwatson * r1827 herd-3/ (debian/changelog ubiquity/components/partman.py): <CIA-4> ubiquity: * New partitioner: Fix a crash if the edit dialog is OKed with neither <CIA-4> ubiquity: method nor mountpoint changed. <CIA-4> ubiquity: cjwatson * r1828 herd-3/ (debian/changelog ubiquity/frontend/gtkui.py): <CIA-4> ubiquity: * GTK frontend: Fix re-raising of exceptions to (a) work and (b) interact <CIA-4> ubiquity: properly with apport's Python hook. <CIA-4> ubiquity: cjwatson * r1829 herd-3/debian/ (changelog rules): <CIA-4> ubiquity: * Quick hack to avoid updating the initramfs when calling <CIA-4> ubiquity: console-setup.postinst from within ubiquity. <CIA-4> ubiquity: cjwatson * r1831 herd-3/debian/changelog: releasing version 1.3.16 <CIA-4> ubiquity: cjwatson * r1829 ubiquity/ (6 files in 4 dirs): merge from herd-3 branch <CIA-4> ubiquity: cjwatson * r1830 ubiquity/ (configure configure.ac): bump to 1.3.17 <poningru> does the new partitioning tool have a name? <poningru> cjwatson: ^^^ <poningru> need info for the herd 3 release notes <poningru> no one? <cjwatson> poningru: no; but you don't need to write anything about that, I'll fill it in provided you're doing it on the wiki <cjwatson> poningru: (hint: I'm on London time so don't expect answers at 3:30am) <poningru> ooh k copying to wiki now <poningru> ah sorry :) <poningru> thanks <poningru> ok <poningru> https://wiki.ubuntu.com/FeistyFawn/Herd3 <cjwatson> ta <poningru> its under Installation btw <poningru> cjwatson: thanks soo much btw I do appreciate this <CIA-4> ubiquity: cjwatson * r1832 herd-3/debian/ (changelog rules): * Fix build failure due to console-setup fix. <CIA-4> ubiquity: cjwatson * r1833 herd-3/ (configure configure.ac): bump to 1.3.17 <tepsipakki> I have a number of packages complaining about "Depends: foo but it is not going to be installed" when trying to netboot Herd3 <cjwatson> can you put a syslog somewhere? <tepsipakki> and all of those depend on X <tepsipakki> maybe <tepsipakki> does busybox have a "reverse-wget" or something?-) <cjwatson> nc <cjwatson> or you can anna-install openssh-client-udeb and use scp <tepsipakki> ah, of course <tepsipakki> cjwatson: btw, your comments before the cancelled TB meeting two weeks ago did the trick on Tuesday ;) <cjwatson> good to hear it <cjwatson> I was on a train on Tuesday evening <tepsipakki> yeah, so mdz dug the logs and found your comments <tepsipakki> ok I have the syslog now, but I'll read it myself to be sure it's not my fault <CIA-4> ubiquity: cjwatson * r1834 herd-3/debian/changelog: releasing version 1.3.17 <CIA-4> ubiquity: cjwatson * r1831 ubiquity/debian/ (changelog rules): merge from herd-3 branch <CIA-4> ubiquity: cjwatson * r1832 ubiquity/ (configure configure.ac): bump to 1.3.18 <tepsipakki> cjwatson: ok, I can't see any obvious error in it http://users.tkk.fi/~tjaalton/d-i/syslog <tepsipakki> I can try running apt-install and see where it fails <cjwatson> tepsipakki: looks like you're trying to install both Ubuntu and Kubuntu desktops? maybe they conflict just enough to break tasksel <tepsipakki> yes, been doing that for a while :) <cjwatson> actually it looks like you're trying to install a whole raft of stuff :) <tepsipakki> it's quite a lot yes <cjwatson> you'll have to simulate on a normal system and use apt-get -o Debug33ec:265c:71fe:e26d:2682:4ec2:aaa1:99abpkgProblemResolver=true or something <cjwatson> which will produce a massive slew of output and be quite hard to read, but ... <tepsipakki> ok, I'll look into that <tepsipakki> found the error.. libgd2-{no,}xpm conflict <tepsipakki> pdl depends on libgd2-xpm, and -noxpm is already installed <tepsipakki> nope, can't be that <tepsipakki> argh, it was our own dear xv <tepsipakki> I wonder why x11-common conflicts with xv which isn't even distributable :) <tepsipakki> anyway, I just need to bump the version <cjwatson> because the older version of xv used obsolete paths which would break current x11-common <cjwatson> xorg (1:7.0.21) unstable; urgency=low <cjwatson> [ Josh Triplett ] <cjwatson> * Add conflicts on the old non-free package xv, no longer in Debian, <cjwatson> which broke upgrading on at least one system. <tepsipakki> oh, I see <cjwatson> * Have x11-common conflict with packages installing binaries to <cjwatson> /usr/X11R6/bin. We need to remove them in order to install a proper <cjwatson> symlink at this location to /usr/bin. Packages will still be able to <cjwatson> install to /usr/X11R6/bin, but they need to be removed from the system <cjwatson> first so that we can set up the symlink and not drop them out of the path. <cjwatson> Thanks Steve Langasek. (closes: #362524, #362200) <cjwatson> make your xv package install to /usr/bin when you bump the version to make sure there won't be a problem <tepsipakki> yes, it already does <tepsipakki> PREFIX=/usr <tepsipakki> not that we use upgrade, but still <tepsipakki> xli seems to be the only one we have installed on dapper that still installs in /usr/X11R6 <tepsipakki> xli (1.17.0-22) unstable; urgency=low <tepsipakki> * Install to /usr, instead of /usr/X11R6. (closes: #362311) <tepsipakki> -- Graham Wilson <acolon@example.com> Sat, 22 Apr 2006 05:14:56 +0000 <tepsipakki> that didn't make it in dapper :) <mpt_> Wow, I remember xv <mpt_> Its error alerts had buttons like "Drat" and "Bother" instead of "OK" <tepsipakki> heh <tepsipakki> some people still want to use it <cjwatson> ok, port of gparted's visual partition widget to Python working <cjwatson> now to figure out how to unify its visual disk widget; at the moment it involves massive code duplication <saispo> hi <saispo> cjwatson: i use base-configapt-setup/security-updates boolean false in my preseed file but in the sources.list i have security update and i don't want :/ <saispo> other things to do ? <cjwatson> where did you get that instruction? <cjwatson> the correct way to disable security updates is 'd-i apt-setup/security_host string', as documented in the installation guide (https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/preseed-contents.html) <saispo> i get it on ubuntu-fr docs :/ <saispo> it's possible to bypass the error in a preseed/late_command ? <saispo> or automaticaly answer Y ? <cjwatson> ubuntu-fr docs are wrong. see the guide <cjwatson> and let the ubuntu-fr people know that they need to update <saispo> ok <saispo> thks cjwatson, all work now, just find how bypass a readline question in my preseed_latecommand foir a metapackage i install... <saispo> an idea ? #ubuntu-installer 2007-02-02 * netjoined: irc.freenode.net -> brown.freenode.net <CIA-4> ubiquity: cjwatson * r1833 ubiquity/ (4 files in 3 dirs): <CIA-4> ubiquity: * New partitioner: Handle partman/exception_handler and <CIA-4> ubiquity: partman/exception_handler_note (LP: #82848). <CIA-4> ubiquity: cjwatson * r1834 ubiquity/ubiquity/components/partman.py: tell debconffilter to catch partman/exception_handler and partman/exception_handler_note * cjwatson attempts to implement resizing in new-partitioner <cjwatson> I seem to have forgotten about that up to now <evand> heh <CIA-4> ubiquity: cjwatson * r1835 ubiquity/ (debian/changelog ubiquity/frontend/ubiquity.glade): <CIA-4> ubiquity: * New partitioner: Note that unadorned sizes are assumed to be in <CIA-4> ubiquity: megabytes (LP: #82848). <cjwatson> components/partman.py | 77 ++++++++++++++++++++++++++++++++++++++++++++++-- <cjwatson> frontend/gtkui.py | 36 +++++++++++++++++++--- <cjwatson> frontend/ubiquity.glade | 58 +++++++++++++++++++----------------- <cjwatson> 3 files changed, 139 insertions(+), 32 deletions(-) <cjwatson> easier than I thought, but I wonder how many bugs there are in that ... <evand> I'd wager none in that last file <cjwatson> I hope not, otherwise I'm slipping <cjwatson> what's the usual rate, one bug per 20 lines of code? <evand> haha <cjwatson> evand: how's m-a mergeability looking? feature freeze is Thursday ... <evand> cjwatson: I still have to take a look at that old partitioner issue, but I intend to get a new release of m-a out the door this weekend. So it should be mergeable after that, provided you're willing to let it in while I try to fix the old partitioner in advanced mode + m-a issue. <cjwatson> I'm happy to merge without the old partitioner <cjwatson> I can just disable m-a for the old partitioner. no problem <evand> great! <evand> The Ubiquity code is complete (except for that one issue), it just depends on the unreleased version of m-a, to which I want to add one or two more features before releasing. <evand> I'll make sure I have m-a stable by the end of this weekend so a version can be uploaded and then anything I add after that (provided it's far enough before the freeze that it can be uploaded) is uploaded in a new version. <evand> cjwatson: I'm assuming I have to fill out a main inclusion request when the time comes. <cjwatson> yeah <cjwatson> argh, fucked up the Partman state machine in some non-intuitive way AGAIN * cjwatson rolls up his metaphorical sleeves <cjwatson> ahh, backing up from partman-partitioning/new_size jumps back to choose_partition rather than stepping back to active_partition, for some reason * cjwatson apologises for thinking out loud but sometimes it can be helpful <evand> not a problem, it livens this place up a bit <cjwatson> my thought too <cjwatson> one benefit of all this, it's certainly making partman's control flow in d-i more regular <cjwatson> particularly as regards backup <cjwatson> because the ubiquity component works by stepping into all of the partitions and lots of the options for each partition, and backing up rather than actually doing anything <cjwatson> if backup behaves oddly, you really notice <evand> I can imagine <evand> That reminds me, at some point m-a needs to support that capability, not that it's needed in Ubiquity. <evand> But for d-i <cjwatson> backup's fairly easy once you get the hang of it, as long as your code is a state machine already <evand> that's the problem, we actually briefly discussed this at UDS <evand> basically, it has an inner loop or two <evand> and that's hard to roll into a state machine in bash without some somewhat ugly code, afaik <evand> but I'm sure I'll figure it out, there are just more pressing issues <cjwatson> oh yes, we did <cjwatson> you can do it, it's just fiddly :) <cjwatson> actually, I'm not sure why it's really harder with nested loops than without <cjwatson> the only wart with nested loops is that you need to propagate backup when you back up off the start of an inner loop, and therefore keep track of how to back up in each loop independently <evand> I meant ash, but I'm sure you knew that <evand> indeed <evand> yeah, that doesn't sound too bad, I think I was just having a hard time conceptualizing it when I first tackled it <cjwatson> I tend to think of it as "busybox sh" to avoid confusion with the shells available in the normal system <CIA-4> ubiquity: cjwatson * r1836 ubiquity/ (4 files in 3 dirs): <CIA-4> ubiquity: * New partitioner: Implement resizing. Ask for the size using a spinbutton <CIA-4> ubiquity: (in megabytes) rather than a text entry field. #ubuntu-installer 2007-02-03 <dabaR> Hey. I just saw that mailing to the list by Aaron Fay. I am wondering whether he tried using both the alternate and desktop CDs. <dabaR> And would it make a difference. I will send a mail to the list to ask him. <kro> reposting from ubuntu-devel. just found out about this chat room. <kro> Should the netboot version of debian installer located at <kro> http://archive.ubuntu.com/ubuntu/dists/feisty/main/installer-i386/current/images/netboot/ubuntu-installer/i386/ <kro> work? <kro> I just tried the daily alternate installer cdimage and is bombing out for me as well <kro> doh, I think I spoke to soon. investigating. <kro> in the alt-f4 console it does keep spitting out kernel: not found repeatedly. <kro> and it seems to either hang, or be moving really slow. <kro> it starts spitting out the kernel: not found message after the "Detecting hardware to find cd-roms" window closes. <tepsipakki> kro: known kernel bug <tepsipakki> https://launchpad.net/bugs/76341 <kro> tepsipakki: thanks. I'll try the workaround listed in the comments <kro> tepsipakki: w00t! thanks. <tepsipakki> kro: glad it worked for you ;) <CIA-4> ubiquity: cjwatson * r1837 ubiquity/ (debian/changelog doc/README): <CIA-4> ubiquity: * doc/README: Add comment about language pack installation following a <CIA-4> ubiquity: query from Telmo Baa. <cjwatson> dabaR: it's hard to tell without the logs, but the relevant autopartitioning code is common to both <cjwatson> dabaR: I've followed up <tepsipakki> cjwatson: what package is responsible for displaying foreign character sets in alternate installer, newt-something? <cjwatson> a chain of stuff <cjwatson> cdebconf, newt, bogl <cjwatson> bogl's the underlying terminal; newt does form layout; cdebconf's newt frontend mediates between installer code and newt <cjwatson> and there's also the font, bterm-unifont <cjwatson> if characters are missing from it, it might be the build system's fault, debian-installer <cjwatson> sometimes it's best just to file bugs on debian-installer and sort out exactly who's to blame later ... :-) <tepsipakki> ok, cool <dabaR> cjwatson: Yes, I saw. Thanks. #ubuntu-installer 2007-02-04 <pradalover> hello <CIA-4> ubiquity: cjwatson * r1838 ubiquity/debian/changelog: reorganise changelog <CIA-4> ubiquity: cjwatson * r1839 ubiquity/ (debian/changelog ubiquity/components/partman.py): <CIA-4> ubiquity: - Offer 'fat16' and 'fat32' filesystem types for new partitions rather <CIA-4> ubiquity: than the non-existent 'fat' (LP: #83211). <CIA-4> ubiquity: cjwatson * r1840 ubiquity/ (debian/changelog ubiquity/frontend/gtkui.py): - Fix crash when backing up to automatic partitioning page (LP: #83230). <CIA-4> ubiquity: cjwatson * r1841 ubiquity/ (debian/changelog scripts/install.py): <CIA-4> ubiquity: * Fix crash due to underqualification of debconf.DebconfError (thanks, <CIA-4> ubiquity: Joel Bryan Juliano; LP: #83008). <cjwatson> I really, really love ubiquity bug reports from apport. They take about a tenth of the time to wade through, partly because I can assume that they already contain all the necessary information without having to think about it. <CIA-4> ubiquity: cjwatson * r1842 ubiquity/ (debian/changelog ubiquity/frontend/gtkui.py): - Display current partition sizes in megabytes (part of LP: #83166). <evand> Is that ever going to be automated? I can imagine that creating quite a flood of bug reports. <cjwatson> is which ever going to be automated, sorry? <evand> apport. Right now, at least when I've used it, you have to create the bug report yourself and attach the apport report. I was curious if the plan was to auto-submit that information to launchpad. <evand> err malone <cjwatson> try a more recent version of apport :-) <evand> hah, I thought I was only a few days out of sync, but I guess that's all it takes <cjwatson> as of very recently, pressing the button in apport-gtk submits everything to Launchpad, gets a token back for the submission, and pops up a browser to let you describe the problem; when you submit that it ties it together with the stuff it submitted earlier <cjwatson> so not totally automatic but much closer than before <cjwatson> that was basically what I was waiting for before switching ubiquity over <cjwatson> I don't mind a flood of bug reports as long as they're good, detailed bug reports :-) <evand> Nice, but does it mark similar apport reports as duplicates? <evand> hah, indeed <cjwatson> the problem with the earlier flood was that they tended not to be detailed - it will be much harder for people to screw that up now <cjwatson> it tries to use a semi-descriptive title so that Launchpad's attempts to detect duplicates on filing have a better chance of working <evand> Yeah, I did see a lot of "the installer crashes, here's the pop-up dialog message" in my inbox. <evand> nice <cjwatson> it's not perfect - if several different code paths lead to the same exception on the same line of code, it'll false-positive <cjwatson> but that's probably fairly rare <cjwatson> well, apart from stuff like grub-installer failing <cjwatson> but to be honest I have so many reports of that now that I don't mind losing a few ;-) <evand> haha <cjwatson> I thought the bit in bug 83166 about swap was bogus until I went and read the code - apparently partman *can* choose not to format swap <cjwatson> will need to look at that this week <evand> ouch <kro> I'm having problems preseeding with the fiesty installer. the old preseed I used to use to do automatic partitioning of the hard drive without asking isn't working. tracing through the choices, it seems like the selection is specific to the machine. I need something more generic that I can apply to machines with different hard drives. Did something change? <cjwatson> kro: you mean partman-auto/disk and /dev/hda / /dev/sda rather than /dev/discs/disc0/disc? <cjwatson> that was a change in edgy <cjwatson> kro: in feisty, preseed partman-auto/method to regular and just leave partman-auto/disk unset and it'll automatically use the first disk <cjwatson> kro: oh, preseeding partman-auto/method to regular is a new requirement in feisty anyway, so you may just have been being bitten by that. Regardless, leaving partman-auto/disk unpreseeded is probably what you want now if you just have one disk <cjwatson> the partman-auto/method stuff is part of a batch of changes that will eventually produce better preseeding of stuff like LVM and RAI <cjwatson> D <cjwatson> and crypto <kro> cjwatson: thanks. I hadn't touched d-i since dapper. * cjwatson -> bed #ubuntu-installer 2007-02-05 <saispo> hi <saispo> cjwatson: when i use apt-install it's possible to disable debconf question for some packages ? <cjwatson> sure, preseed them to the appropriate values <saispo> k thanks :) <saispo> debconf/priority ? <cjwatson> huh? <saispo> debconf/priority=critical no ? <cjwatson> please be more verbose <saispo> excuse me <saispo> i use apt-install at boot for installing a base ubuntu with a metapackage <saispo> but when he try to install libpam-ldap <cjwatson> (you should probably just use pkgsel/include instead) <saispo> i have an error... <cjwatson> but go on <saispo> because it needed sorme information <saispo> and i don't want this screen <saispo> just force the pkg install whitout question <cjwatson> debconf/priority=critical means "only present questions that are asked at priority critical" <cjwatson> libpam-ldap asks questions at priority critical, at least in some situations <cjwatson> this means that a decision MUST be taken on them <cjwatson> if you don't want them presented to the user interactively, the only thing you can do is preseed them <saispo> ok <saispo> thanks <saispo> will try with this <CIA-4> ubiquity: cjwatson * r1843 ubiquity/ubiquity/frontend/gtkui.py: typo: self.environ -> os.environ <CIA-4> ubiquity: cjwatson * r1844 ubiquity/ (d-i/manifest debian/changelog): <CIA-4> ubiquity: * Automatic update of included source packages: partman-partitioning <CIA-4> ubiquity: 45ubuntu1. <CIA-4> ubiquity: cjwatson * r1845 ubiquity/debian/changelog: minor changelog fix <tepsipakki> cjwatson: so if I preseed partman-auto/method=lvm I need to specify the disk as before? <tepsipakki> that's how it works now <cjwatson> if there's more than one disk on the system, yes <cjwatson> # If there's only one disk, then preseeding partman-auto/disk is unnecessary <cjwatson> if [ "$method" ] && [ -z "$disks" ] ; then <cjwatson> DEVS="$(get_auto_disks)" <cjwatson> if [ "$(echo "$DEVS" | wc -l)" -eq 1 ] ; then <cjwatson> disks="${DEVS%$TAB*}" <cjwatson> fi <cjwatson> fi <tepsipakki> ok, somethings wrong then <evand> cjwatson: m-a should be ready to merge today, I just have to test it in the installer after class to make sure everything still works. <cjwatson> nice, thanks <CIA-4> ubiquity: cjwatson * r1846 ubiquity/debian/changelog: releasing version 1.3.18 <cr3> can gfxboot be disabled when booting from the live cd? <cjwatson> hold down shift <evand> ugh, is there any way of resolving a undefined Py_InitModule4 symbol, other than using a newer daily CD? <cjwatson> um, no idea, not heard of that <evand> It keeps happening to me in various Python packages in Feisty. Unfortunately it's happening with emap.so in Ubiquity using trunk. <cjwatson> have you updated since building emap.so? <cjwatson> it's not checked in, so ... <evand> Sorry, I don't follow. Updated what? <evand> I just commented out the tzmap stuff for now as I'm just trying to test an install. <cjwatson> updated as in upgraded anything <cjwatson> or did it just fail as soon as you built it? <evand> I think it started to fail when I built it. <evand> When it happened to me with democracyplayer it eventually went away after a few upgrades. <cjwatson> truly bizarre; I don't call Py_InitModule4 directly, only Py_InitModule <cjwatson> perhaps doko can help <evand> eh, no worries. I'm sure it will resolve itself. <cjwatson> if it happens on a live CD, that would really be odd <evand> Well it did, but it was with the copy of Ubiquity that I built. It didn't happen with the version that was previously on the CD though. <cjwatson> that's *really* weird, because I often build ubiquity locally on the running live CD and it works fine <cjwatson> did you build it in the live session, or externally and copy it in? <evand> externally and copy <cjwatson> ah, so could still be a broken build system <jharr> is this the right chan for help with automated installers? <jharr> *installs <cjwatson> yes <evand> cjwatson: it's crashing somewhere in ma_apply. I have a few things to take care of then I'll take a look at it a little later. I just wanted to keep you posted. <cjwatson> thanks <jharr> I've been trying to get automated pxe installs (feisty,amd64,20061102ubuntu13 netboot.tgz installer). <jharr> I have a preseed file going, however, since I'm hosting that on an http server (for dev purposes), I'm assuming that all the language questions have to be answered by the 'append' option. <jharr> but I've done what several tutorials have said, and it's not really working that well. <jharr> I've been using 'append vga=normal initrd=ubuntu-installer/amd64/initrd.gz preseed/locale=en_US kbd-chooser/method=us netcfg/choose_interface=eth0 netcfg/get_hostname= preseed/url=http://+1-473-444-0812/preseed/feisty-amd64-server --' <jharr> '/proc/cmdline shows those arguments in tact. <jharr> however I still have to answer all the language questions before it grabs the preseed/url file. <jharr> any ideas? <jharr> I know the preseed/url is making it to debconf, because it does download the preseed file (visible on VC4) when it gets the network up and running. <cjwatson> looks like your information is outdated <cjwatson> change preseed/locale to debian-installer/locale; change kbd-chooser/method to console-setup/layoutcode <cjwatson> otherwise your assumption is correct <cjwatson> s/assumption is/assumptions are/ <cjwatson> where did you get that information? it may just legitimately date from dapper or before, but otherwise I'd like to get it corrected <jharr> it was for dapper <jharr> http://halisway.blogspot.com/2006/06/ubuntu-dapper-pxe-network-install.html <jharr> got it from there <cjwatson> ok, stuff has changed since then <jharr> cool. <cjwatson> https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/preseed-contents.html is (almost) up to date for edgy <cjwatson> up to date in this respect, anyway <jharr> has much changed when going into feisty? <cjwatson> if you're using partman-auto/disk to preseed partitioning of a single disk, then you need to add 'd-i partman-auto/method string regular' to make it use regular partitioning rather than LVM or RAID or what-have-you <cjwatson> otherwise not much preseeding-wise <jharr> ahh, cool. <jharr> I'm working on a cluster here, and I want to start sticking everything we have into debian packages and just do clean installs every time. <cjwatson> sensible <jharr> yeah, it's a pretty big project because of the way things were done for a long time. <jharr> It's mostly going to be getting everyone to work that way. <jharr> Believe it or not, the way they did things before hand was to do raw installs for every client. <cjwatson> oh, I can believe it <jharr> and some of the software required makefile patches & such. <jharr> I convinced them to use systemimager after my boss asked me to install 20 new nodes. <jharr> is there a way to get the installer to spit out the choices you made into a preseed file? <jharr> I remember debian doing something like that, that left a couple of files in /root. <cjwatson> jharr: see right at the bottom of the URL I gave above <cjwatson> it will certainly preseed more than you need, though <jharr> cjwatson: yeah, that's what I was thinking. I thought the original debian installer put just the choices you made in a file, so you'd automatically have a skeliton preseed. <stgraber> debconf-get-selections I guess <stgraber> but you really have too much things preseeded <jharr> yeah, but I mean it would be nice to have the results of the install spit out just the stuff you answered. <jharr> It'd make it a lot easier for OEMs to setup their own custom installs that way. <cjwatson> I think it was removed when debconf-get-selections --installer was implemented, because at that point it was trivial to generate <cjwatson> oh, you're talking about the old /root/dbootstrap_settings perhaps <cjwatson> that definitely predates d-i and preseeding <cjwatson> you can probably filter the cdebconf database for stuff with the seen flag set <cjwatson> interestingly, the debconf db on my system does not appear to have very much at all with the seen flag set. Curious <cjwatson> shall have to investigate that at some point <jharr> oh, nice, I <3 text based DBs :D <jharr> hrmm <jharr> When I'm doing an install, how can I tell what the preseed directive is for the current prompt? <jharr> partitioning in Feisty has changed apparently and I'm looking around for the preseed options that are equivalent to edgy's <cjwatson> jharr: boot with DEBCONF_DEBUG=5 and you'll get a trace of what debconf's doing in /var/log/syslog - look for INPUT commands <cjwatson> it may not be entirely up to date at every point due to buffering <cjwatson> jharr: the partman-auto/method thing I mentioned should be the only relevant change #ubuntu-installer 2007-02-06 <evand> cjwatson: It's ready :-) <evand> I've tagged migration-assistant 0.3 in r29 <evand> And the latest revision of my Ubiquity branch is also ready. <evand> As I am not a MOTU, can you push m-a to Universe and then I'll get started on a Main Inclusion Report? <cjwatson> evand: working on it now <cjwatson> sorry, was a bit distracted for a while with trying to recover the karate club's old website <cjwatson> yay for WWW33ec:265c:71fe:e26d:2682:4ec2:aaa1:99abMechanize + web.archive.org, though <evand> not a problem <evand> so, should I start filling out a Main Inclusion Report? <cjwatson> uploaded <cjwatson> yeah <evand> awesome, thanks <evand> ok, done. Does libxml2-udeb need a report? Libxml2 is already in main. <cjwatson> no <cjwatson> extra binary packages from sources already in main are fine <evand> ok <jharr> can I setup partman-lvm to create a VG from two drives? <Peek> Hi!, The live CD 6.10 says that cannot mount cdrom/ on root/cdrom/ <Peek> this is the first line of the casper.log <Peek> and after that nothing works <Peek> knows anyone whats happening? <Peek> its the same with all the debian dists #ubuntu-installer 2007-02-07 <evand> cjwatson: I'm a bit confused by this main promotion process. The wiki page says that I should hold any necessary discussion on -devel (presumably -devel-discuss now) but SeedManagement seems to imply this has to be done. Should I do this? <evand> MainInclusionProcess also says that I should add it to a seed (presumably the installer seed), but I believe I'd need to be a core dev to do this, so am I safe in assuming that you will take care of that part? <evand> hrm, I probably could've asked that in -devel <cjwatson> jharr: I don't know it well enough, unfortunately :( <cjwatson> evand: that's only if a reviewer comes back to you with queries <cjwatson> (pitti and iwj are the two reviewers for this at present) <cjwatson> evand: yeah, I'll take care of seeding it; in fact I'll do that now <cjwatson> evand: seeded (sorry for delay, mornings tend to have so much incoming stuff for me that I usually thrash for a bit) <evand> ok <evand> thanks <evand> cjwatson: sorry about posting it to -discuss then. I did end up asking in -devel last night and they suggested that it couldn't hurt to post it. <cjwatson> yeah, it's ok <CIA-4> ubiquity: cjwatson * r1847 ubiquity/ (debian/changelog ubiquity/frontend/gtkui.py): <CIA-4> ubiquity: * New partitioner: Don't allow creating a disk label or creating, editing, <CIA-4> ubiquity: or deleting a partition while other similar operations are in progress. <jharr> I think I spotted an installer bug with lvm2. <jharr> My preseed stuff was working last night <jharr> but today it busted. <jharr> http://+1-473-444-0812/~jharr/motu/ <jharr> I gotta run, but if anyone is interested, check those out. #ubuntu-installer 2007-02-08 <jeckers`> hey all i've submitted a patch to a bug in partman-auto <jeckers`> https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/83897 <jeckers`> should be a quick one somebody can bang out in a minute <cjwatson> I'm not convincd <cjwatson> convinced, even <jeckers`> $dev is the directory <jeckers`> e.g. =dev=hda <cjwatson> I know, but your patch is in the wrong place <cjwatson> I think it's the code calling get_auto_disks which is incorrect <cjwatson> get_auto_disks is called from more than one place and your patch would break the other callers, AFAICS <jeckers`> perhaps, although i ran through the install ok after applying that <cjwatson> specifically select_auto_disk <cjwatson> you'd need a >1-disk system without preseeding to see the breakage <jeckers`> ah i see <jeckers`> and just when i thought i was being clever. doh. <jeckers`> well then auto.d/initial_auto must need to do some massaging then? <cjwatson> jeckers`: try the patch I just posted to your bug? <jeckers`> will do <cjwatson> jeckers`: thanks for the report, though, this was the first I'd realised that was broken <cjwatson> jeckers`: and don't be put off, partman is a hairy piece of code to try to work on; good effort for getting as far as you did :-) <jeckers`> i spent the better part of 3 hours trying to figure out what the heck it was doing :) <cjwatson> my fault for not testing the fix in the first place - I was in Oslo and nowhere near any of my test rigs <jeckers> yup your patch did the trick <jeckers> thanks a lot <jeckers> you'll probably be seeing more of me in the coming months <jeckers> i'm going to be following along with feisty closely as it develops <jeckers> hopefully i'll catch a few more good ones along the way :) <cjwatson> great, look forward to more installer manpower :) <cjwatson> will upload that patch now <jeckers> cool thanks <jeckers> and i'd be glad to give more installer manpower :) <cjwatson> feel free to ping me here for help <jeckers> and my partner in crime has arrived <saispo> hi all <CIA-4> ubiquity: cjwatson * r1848 ubiquity/ (83 files in 3 dirs): <CIA-4> ubiquity: * Display a warning message next to the password entry box if running in <CIA-4> ubiquity: debug mode, since the password will then end up in the log file via <CIA-4> ubiquity: debconf debugging. <CIA-4> ubiquity: cjwatson * r1849 ubiquity/ (debian/changelog ubiquity/components/console_setup.py): * Don't crash if /etc/X11/xorg.conf is unaccountably missing (LP: #83927). <CIA-4> ubiquity: cjwatson * r1850 ubiquity/ (configure configure.ac): bump to 1.3.19 <saispo> cjwatson: it's possible for me to backport this fix on edgy ? (https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/83897) <cjwatson> saispo: yes, but only on top of the change in feisty that it was fixing ... <saispo> ok <saispo> it may fix the error with /dev/disc/disc0 things... <cjwatson> well, you can't use /dev/discs/disc0/disc any more either way, but yes, it could make that situation easier <saispo> because today i use a script but don't work on installer... <saispo> if [ cat /sys/block/hda/devices/media = "cdrom" ] ; then echo part-auto-sda.cfg; else echo part-auto-hda.cfg; fi <saispo> if it != cdrom he don't get the other file... <cjwatson> well, that's just bogus shell syntax <cjwatson> if that's literally what your script says <cjwatson> correct would be if [ "$(cat /sys/block/hda/devices/media)" = cdrom ] ; then echo part-auto-sda.cfg; else echo part-auto-hda.cfg; fi <saispo> ok, thanks <evand> cjwatson: Are you shooting for an FF exception for the new partitioner work? <evand> s/an/a/ <cjwatson> yeah <evand> cjwatson: how comfortable would you be with me attempting one on say, Saturday morning, for Opera bookmarks importing and email account information importing? I've basically got the former done. <evand> Or should I let it wait for Feisty+1? <cjwatson> well, can we land the ubiquity m-a work today? :) <cjwatson> if so extra little bits don't count for FF IMO <evand> really? That's amazing. <evand> But yeah, it's there for you to merge <evand> I figured you were waiting for m-a main promotion <cjwatson> oh, I need to hassle about that, yes <cjwatson> brb, preparing meeting agenda for today and then lunch <evand> lazy core devs :-) <evand> ok <saispo> how can i debug why a package for a local repository i make on the cd is installing in the base installer without any apt-install command or other ? <saispo> s/for/from/ <saispo> cjwatson: where i can find docs about seeds structure files ? <cjwatson> http://wiki.ubuntu.com/SeedManagement <cjwatson> oh you mean the STRUCTURE file? <saispo> nono <saispo> description of a seeds <saispo> with = or == <cjwatson> you mean the text bits at the top of the seed files? <cjwatson> they're ignored - the only reason they have that format is that the seeds used to be stored in a wiki <saispo> ok <saispo> no difference between = or == ? <cjwatson> in the wiki two years ago, they were different heading levels <cjwatson> it makes no difference whatsoever now <cjwatson> germinate ignores all lines that don't start with " * " <saispo> k <saispo> i have a problem which i don't understand... <saispo> when i include a package in my seeds file wich is in my local repository on the cd, the base installer install it <saispo> and i don't want... <saispo> Dependency problem ? <saispo> Germinate Problem ? <saispo> i have no clue... <cjwatson> you probably gave it a Priority: of required, important, or standard <saispo> in the packaging ? <saispo> Priority: optional <cjwatson> or else something depends on it in the base system <saispo> maybe..., how can i see germinate output ? <cjwatson> or you put it in the minimal seed and cdimage inflated the priority for you <cjwatson> sudo apt-get install germinate <cjwatson> man germinate <saispo> k :) <saispo> thanks for your help, will search in this road <CIA-4> ubiquity: cjwatson * r1851 ubiquity/ (73 files in 4 dirs): <CIA-4> ubiquity: * Import translations for Cancel, Back, Forward etc. buttons from gtk+2.0 <CIA-4> ubiquity: 2.10.9-0ubuntu1 (LP: #43915). <cjwatson> blink, this is a fun merge * cjwatson attempts the m-a merge the other way round to see if that's any easier <evand> Really? I thought I was fairly up to date. <evand> The only issue should be glade, but that's as easy as just cutting the MA section out and pasting it into the most recent copy. <evand> Did I do something wrong in bzr? <secureboot_> is there any way to do encrypted partitions from the installer in feisty? any plans to enable this? <secureboot_> if not, is there any way to use etch's partman when building your own custom installer? <cjwatson> evand: I just made a bunch of changes ... <cjwatson> ow, merging .po files is so insanely painful <cjwatson> I'll just msgmerge it <cjwatson> evand: could you set your editor to never use tabs in Python code? space-indentation is usually considered better there <evand> cjwatson: I thought I was, but sure thing. <cjwatson> looks like maybe you did part-way through the project <evand> ah <cjwatson> anyway, not *right* now, mid-merge :-) <cjwatson> just setting up the test rig <evand> heh <cjwatson> note that there was a diff in bin/ubiquity which I dropped (@VERSION@ -> 1.3.8, looked accidental) and an extra change in gtkui.py where it looked like you missed a new-partitioner bug fix (it was an "if 'UBIQUITY_NEW_PARTITIONER' not in os.environ:" around gparted_loop()) <cjwatson> hmm, dinnertime <cjwatson> will return afterwards and hopefully commit <evand> ah, I probably did that recently, in the last merge <cjwatson> secureboot_: don't think the pieces are in place; if cryptsetup is ever moved to main it may be possible to assemble them from Debian <cjwatson> secureboot_: not unless you're a d-i god <cjwatson> (etch's partman) <evand> cjwatson: thanks again, hopefully this will be much easier going forward. <cjwatson> yeah, I expect so <secureboot_> cjwatson: sad. <cjwatson> evand: I think you get to write the changelog entry, too. Any suggestions? <evand> cjwatson: uh, "Merged in migration-assistant work, moved the user-setup page to after migration-assistant..." <evand> here be dragons? <evand> everything is pretty high level as this is going in all at once <evand> those two things were obviously the main focus <evand> oh, and made user-setup able to use users from m-a <evand> if you want me to describe the feature set in the commit, let me know and I'll give you a run down <CIA-4> ubiquity: cjwatson * r1852 ubiquity/ (92 files in 8 dirs): merge migration-assistant branch from Evan <cjwatson> blam <cjwatson> [ Evan Dandrea ] <cjwatson> * Merged in migration-assistant work. Moved the user-setup page to after <cjwatson> migration-assistant (and thus also after the partitioner, since <cjwatson> migration-assistant needs to know which partitions are to be left <cjwatson> evand: let me know if that's inaccurate <cjwatson> intact). Made user-setup able to make use of users from <cjwatson> migration-assistant. <evand> looks good <evand> cjwatson: thanks * evand crosses fingers and hopes everything works as well as it did in his testing <CIA-4> ubiquity: cjwatson * r1853 ubiquity/ (4 files in 3 dirs): indentation, minor style nits <cjwatson> (easier to do it straight away, I think) <evand> et in vim will do it, right? <cjwatson> yeah <cjwatson> augroup myauto <cjwatson> au! <cjwatson> [blah] <cjwatson> au FileType python setlocal tabstop=8 softtabstop=4 shiftwidth=4 expandtab <cjwatson> augroup END <cjwatson> is what I have <evand> thanks <cjwatson> but my .vimrc has all sorts of stuff in it and some of it's global; I have autoindent on for everything <cjwatson> oh, and let python_highlight_all = 1 is handy too <evand> I have the habit of just doing a :syn on <cjwatson> I'm not sure it necessarily highlights everything by default <evand> hrm, I'll have to play around with it then <cjwatson> ooh, there's a changelog plugin * cjwatson makes the productivity error of reading vim's help files <CIA-4> ubiquity: cjwatson * r1854 ubiquity/ubiquity/frontend/gtkui.py: iter -> iterator (avoid shadowing builtins) <evand> whoops <cjwatson> r1854 is one that python_highlight_all is handy for catching <cjwatson> it highlights builtins in cyan (here, anyway) <evand> ah, indeed it does. Very nice. <cjwatson> evand: I think UBIQUITY_MIGRATION_ASSISTANT is implemented slightly dubiously - doesn't it need to fix up the page numbers too after removing a page? <cjwatson> as it is the page numbers skip if you're running without --migration-assistant <cjwatson> these are all nits though, it's looking pretty good <cjwatson> of course I've not run it on a system that actually has anything to migrate ;-) <cjwatson> evand: btw, might be fun for you to set up bzr-cia and have your commits logged here too <evand> cjwatson: definitely to cia <evand> cjwatson: It's skipping pages? <cjwatson> evand: mkdir -p ~/.bazaar/plugins; cd ~/.bazaar/plugins; bzr get http://bazaar.launchpad.net/~jelmer/bzr-cia/main/ cia <evand> thanks <cjwatson> then 'bzr cia-project ubiquity' in your branch and make sure the bzr nick is right <evand> ok <cjwatson> in ~/.bazaar/bazaar.conf, 'cia_user = evand' or whatever you're comfortable with and 'cia_send_revno = true' <cjwatson> at least that's what I prefer <evand> ok <evand> when you say page numbers, do you mean it's skipping actual pages or just the numbers on the labels? <cjwatson> and finally, 'bzr submit-cia' after each commit, or put 'post_commit = bzrlib.plugins.cia.post_commit' in the appropriate bit of ~/.bazaar/locations.conf <cjwatson> evand: just the numbers, the "Step N of M" bit <evand> ahh, I actually kind of completely forgot about that <cjwatson> it goes up to "Step 8 of 8" now even if m-a is disabled <cjwatson> like I say, a nit <evand> ok, so I'm assuming the workflow you'd prefer is what we've been doing? I'll pull trunk, make some changes and then when I fix a bug you'll merge again. Or would you prefer plain old patches or something else? <evand> I'd imagine not the latter. <cjwatson> the former, definitely <evand> I figured :) <cjwatson> ideally you should be in core-dev eventually and maintain it directly, of course <evand> Yeah, I really need to get on the getting work into REVU so I can first get into MOTU <cjwatson> in retrospect maybe I should have made it writable by ubuntu-installer <cjwatson> but never mind now <evand> eh, it's something I've been aiming for anyway, so this is just more incentive. <CIA-4> ubiquity: cjwatson * r1855 ubiquity/ (d-i/manifest debian/changelog): <CIA-4> ubiquity: * Automatic update of included source packages: apt-setup 1:0.16ubuntu3, <CIA-4> ubiquity: migration-assistant 0.3.1, partman-auto 62ubuntu4, <CIA-4> ubiquity: partman-basicfilesystems 51ubuntu1. <evand> ok, I should be all set up for CIA <evand> Should I do it on both m-a and my ubiquity branch or would you prefer just one of them? <cjwatson> why not both, and I'll tell the CIA bot to mention those commits here <CIA-4> ubiquity: cjwatson * r1856 ubiquity/debian/changelog: releasing version 1.3.19 <evand> ok, great. Already done <cjwatson> what's the project name (cia-project)? <evand> hrmm, where do I set that? <evand> I have the post commit hooks <cjwatson> bzr cia-project <blah> in the branch <evand> oh, right! <cjwatson> it knows about the project name and the branch name - the branch name comes from 'bzr nick' <cjwatson> the bot only needs to be told about project names though <cjwatson> there you go, ubiquity 1.3.19 uploaded, just under the feature freeze wire. :-) <evand> ok I did a bzr cia-project migration-assistant in m-a <evand> haha, awesome! Thanks again for all of your help. <cjwatson> all right, the bot'll know about that now <evand> and bzr cia-project ubiquity.ma <evand> creative, I know <cjwatson> no, that should be bzr cia-project ubiquity and bzr nick ma <evand> oh crap <cjwatson> otherwise it won't link it up properly <cjwatson> it's ok, you can change it easily <evand> ok, just did <evand> do I need to do anything else, like add these to my projects list on cia.navi.cx? <cjwatson> I think it should do that magically when you commit <evand> great <cjwatson> oh, I forgot to note in the changelog how to invoke it <cjwatson> maybe you could post to ubuntu-devel@ about that? <cjwatson> I left a note in the spec status whiteboard about it <evand> will do <evand> I was planning on doing a planet post as well <cjwatson> good plan <CIA-4> migration-assistant: evand * r33 migration-assistant/ (firefox-import.c firefox-import.h import.c): Added Opera support. <evand> neat! #ubuntu-installer 2007-02-09 <CIA-4> ubiquity: cjwatson * r1857 ubiquity/ (debian/changelog ubiquity/frontend/kde-ui.py): * KDE frontend: Add apport integration to crash handler. * cjwatson documents CIA setup on https://wiki.ubuntu.com/InstallerDevelopment <CIA-4> ubiquity: cjwatson * r1858 ubiquity/ (debian/changelog ubiquity/frontend/kde-ui.py): back out r1857 for now as adept_notifier isn't ready yet <CIA-4> ubiquity: cjwatson * r1859 ubiquity/ (3 files in 2 dirs): * KDE frontend: Remove now-unused kde-distro-logo.png. <saispo> hi <saispo> cjwatson: i get an error about ubuntu-keyring with my custom cd, i have rebuild one with my gnupg key i used for my package building, but when a try a minimal install, i get an error wich says : can't install ubuntu-minimal because ubuntu-keyring package not installed <saispo> you know this ? <saispo> maybe because ubuntu-keyring is not in the main Packages ? just in my local Packages ? <saispo> i found why... <cjwatson> saispo: not sure how well stuff works with multiple repositories as I haven't tested that for a while - you may have some bugs to fix <saispo> yep... <saispo> if ubunutu-keyring is not in man Packages file, don't work... <saispo> s/man/main/ <cjwatson> I think debootstrap can only use one repository <cjwatson> well <cjwatson> it can use one repository but multiple components <cjwatson> saispo: are you using /dists/feisty/local or similar? <saispo> no i use other... <saispo> i use dists/local <cjwatson> oh, don't do that <cjwatson> make it a component of feisty (or whatever) <cjwatson> saispo: then make sure that /.disk/base_components on the CD has 'local' in i <cjwatson> it <cjwatson> then it should work <saispo> k <saispo> i don't create this at the first time, i reuse some things which is made by other, and must adapt... <saispo> % cat base_components [0.15 0.42 - 46% 1%] <saispo> main <saispo> restricted <saispo> how can i add universe and local ? <saispo> ok... <saispo> with scripts scanpackages ? <cjwatson> I don't recall and I have several phone calls to make, sorry - if this is debian-cd, search through the Makefile <saispo> ok <saispo> thanks <saispo> no problem, i understand <CIA-4> ubiquity: cjwatson * r1861 ubiquity/debian/ (ubiquity-frontend-gtk.links ubiquity-frontend-kde.links): fix package-hooks symlinks as well <CIA-4> ubiquity: cjwatson * r1862 ubiquity/debian/changelog: aargh dch <CIA-4> ubiquity: cjwatson * r1863 ubiquity/ (configure configure.ac): bump to 1.3.20 <CIA-4> ubiquity: cjwatson * r1864 ubiquity/debian/changelog: releasing version 1.3.20 <jeckers> anybody know an easy way to force eject a CD from within d-i <jeckers> since there's no eject command :) <jeckers> and this imac refuses to give me my cd back <jeckers> nevermind <jeckers> eject-udeb :D <cjwatson> right, apt-install that ... <cjwatson> holding down the eject button on the keyboard (or F12 if you don't have one) at boot time sometimes does it too <cjwatson> or ctrl-cmd-o-f at boot to get to the Open Firmware prompt, and type 'eject cd' <jeckers> yea once it gets into the installer the keyboard eject quits working though <jeckers> im using the netboot mini iso <jeckers> so i just need it to load the kernel/ramdisk and then give me the cd back <cjwatson> *nod* <jeckers> but all is well now <jeckers> although i rolled the eject-udeb up in the ramdisk and set preseed/early_command=eject and that didn't work as i expected <jeckers> but it worked when i ran it from the terminal, so im cool with that for now <jeckers> this is on dapper by the way #ubuntu-installer 2007-02-10 <mark> I seem to have caught into some endless loop in the installer <mark> in the software RAID setup <mark> it's in a loop of redrawing an empty blue screen <mark> which is great fun to watch on 9600bps :) #ubuntu-installer 2007-02-11 <CIA-4> migration-assistant: evand * r34 migration-assistant/ (10 files in 2 dirs): Initial support for importing from Outlook Express and Evolution. Only supports IMAP in OE currently. <evand> I have not forgotten about the existing bugs or the m-a announcement. Those will be taken care of later today. #ubuntu-installer 2007-02-12 <allmanj> hey - i'm continually forgetting this so this time i'll make a note. If i want to stop an install from rebooting after it finishes, there's a kernel option i can pass, right? <cjwatson> just don't preseed prebaseconfig/reboot_in_progress or finish-install/reboot_in_progress (as applicable); it doesn't reboot noninteractively unless you preseed that <allmanj> on a dapper system? <allmanj> actually, i have preboot_in_progress set <allmanj> i'll try switching that off - thanks! <cjwatson> prebaseconfig/reboot_in_progress on dapper IIRC <allmanj> seems to be the one all right. type note? is that right? (seems odd) <allmanj> running an install now to see if that'll stop it <cjwatson> yes, it's a note template <cjwatson> preseeding it has the effect of indicating that you've already "seen" the note and thus it shouldn't be displayed again <allmanj> gotcha, but i thought that was normall done with seen? anyway - it worked a charm! <cjwatson> you can do it with seen too, but it doesn't make any difference with notes because there's no relevant value involved <cjwatson> the ability to preseed just the seen flag postdates ordinary value+seen preseeding <cjwatson> and it's mostly just used for preseeding something but then setting the seen flag to false again * allmanj nods slowly <cjwatson> (i.e. set a default) <allmanj> yes, i think i follow that <allmanj> that's what i've been using it for <allmanj> didn't really see the distinction but i think i get you now <cjwatson> preseeding does have the (arguable) flaw that it makes a lot more sense if you're familiar with debconf <cjwatson> it was designed by the author of debconf, and it shows :) it's a low-level facility in some ways <allmanj> yeah, it's not always obvious - but it does appear to work nicely when it works! <evand> I posted an announcement for m-a to -discuss. Hopefully the mailman admins will get my drop request before it's posted there too. * evand awaits a flood of bug reports <cjwatson> evand: neat, thanks #ubuntu-installer 2007-02-13 <chrisj> cjwatson: ping <cjwatson> chrisj: pong <chrisj> I'm very familiar with creating bzr branches. How would I create one for the partitioner work? Can it be hosted on launchpad? <chrisj> I mean Im not familiar <chrisj> cjwatson: I've made a fair bit of progress so far on the horizontal bar widget. You can add multiple partitions and small partitions have a minimum width. <cjwatson> first, check out the mainline branch <cjwatson> bzr get http://bazaar.launchpad.net/~ubuntu-core-dev/ubiquity/trunk/ <cjwatson> then branch your own copy (actually technically you've already done this by virtue of bzr get, but you probably want to keep a copy of mainline anyway) <cjwatson> bzr get trunk name-of-your-branch <cjwatson> then in your branch, bzr push sftp://bazaar.launchpad.net/~tortoise/ubiquity/name-of-your-branch <chrisj> ok, thanks <cjwatson> you'll need to bzr push after each commit <cjwatson> there's a way to set up a "checkout" which doesn't require you to push after each commit, if you like, but you don't have to <saispo> hi all <chrisj> cjwatson: ok, done. I wasn't sure where to put it, the code is in frontend/partbar.py for now <cjwatson> it's easy to move it around later <cjwatson> thanks, I'll have a look <cjwatson> chrisj: not to be overly picky or anything, but could you make that be four-space indents and no tabs, please? :-) <chrisj> cjwatson: yeah, sure <chrisj> sorry, the code is a bit sketchy at the moment. I was just trying to get something working first. <cjwatson> no worries <cjwatson> oh, I owe you an e-mail ... <cjwatson> ok, you have mail which I hope isn't too late <chrisj> cjwatson: um...are you sure you sent that email? <cjwatson> chrisj: yes, Message-ID: <acolon@example.com> <cjwatson> To: Chris Jones <acolon@example.com> <chrisj> grrr dodgy uni email. Could you try acolon@example.com? thanks <saispo> hi <saispo> cjwatson: how can i force this "E: Packages need to be removed but remove is disabled" with apt-install ? <saispo> --force-yes not working... <cjwatson> chrisj: bounced <cjwatson> saispo: um - arrange for packages not to need to be removed <cjwatson> saispo: apt-install isn't meant to do that <saispo> cjwatson: exim4 conflicts with ssmtp :/ <cjwatson> saispo: if you absolutely can't arrange that, then remove --no-remove or whatever it is from apt-install <cjwatson> saispo: what's apt-installing either of those? <saispo> uucp <saispo> mailx <cjwatson> no, I mean what installer component <saispo>
{'channel': 'ubuntu-installer', 'month': 2}