=== cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-installer === joejaxx [i=joejaxx@alpha.joejaxx.net] has joined #ubuntu-installer === joejaxx [i=joejaxx@ubuntu/member/joejaxx] has left #ubuntu-installer [] === joejaxx [i=joejaxx@ubuntu/member/joejaxx] has joined #ubuntu-installer [11:02] hi [11:03] cjwatson: when i use apt-install it's possible to disable debconf question for some packages ? [11:03] sure, preseed them to the appropriate values [11:04] k thanks :) [11:04] debconf/priority ? [11:05] huh? [11:05] debconf/priority=critical no ? [11:06] please be more verbose [11:06] excuse me [11:07] i use apt-install at boot for installing a base ubuntu with a metapackage [11:07] but when he try to install libpam-ldap [11:07] (you should probably just use pkgsel/include instead) [11:07] i have an error... [11:07] but go on [11:07] because it needed sorme information [11:08] and i don't want this screen [11:08] just force the pkg install whitout question [11:09] debconf/priority=critical means "only present questions that are asked at priority critical" [11:09] libpam-ldap asks questions at priority critical, at least in some situations [11:09] this means that a decision MUST be taken on them [11:09] if you don't want them presented to the user interactively, the only thing you can do is preseed them [11:09] ok [11:09] thanks [11:10] will try with this === cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-installer [02:05] ubiquity: cjwatson * r1843 ubiquity/ubiquity/frontend/gtkui.py: typo: self.environ -> os.environ [02:09] ubiquity: cjwatson * r1844 ubiquity/ (d-i/manifest debian/changelog): [02:09] ubiquity: * Automatic update of included source packages: partman-partitioning [02:09] ubiquity: 45ubuntu1. [02:14] ubiquity: cjwatson * r1845 ubiquity/debian/changelog: minor changelog fix [02:15] cjwatson: so if I preseed partman-auto/method=lvm I need to specify the disk as before? [02:15] that's how it works now [02:17] if there's more than one disk on the system, yes [02:17] # If there's only one disk, then preseeding partman-auto/disk is unnecessary [02:17] if [ "$method" ] && [ -z "$disks" ] ; then [02:17] DEVS="$(get_auto_disks)" [02:17] if [ "$(echo "$DEVS" | wc -l)" -eq 1 ] ; then [02:17] disks="${DEVS%$TAB*}" [02:17] fi [02:17] fi [02:18] ok, somethings wrong then [02:24] 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. [02:25] nice, thanks [02:28] ubiquity: cjwatson * r1846 ubiquity/debian/changelog: releasing version 1.3.18 [04:50] can gfxboot be disabled when booting from the live cd? [04:51] hold down shift [05:56] ugh, is there any way of resolving a undefined Py_InitModule4 symbol, other than using a newer daily CD? [05:57] um, no idea, not heard of that [05:59] It keeps happening to me in various Python packages in Feisty. Unfortunately it's happening with emap.so in Ubiquity using trunk. [06:00] have you updated since building emap.so? [06:00] it's not checked in, so ... [06:05] Sorry, I don't follow. Updated what? [06:13] I just commented out the tzmap stuff for now as I'm just trying to test an install. [06:16] updated as in upgraded anything [06:17] or did it just fail as soon as you built it? [06:18] I think it started to fail when I built it. [06:20] When it happened to me with democracyplayer it eventually went away after a few upgrades. [06:32] truly bizarre; I don't call Py_InitModule4 directly, only Py_InitModule [06:32] perhaps doko can help [06:33] eh, no worries. I'm sure it will resolve itself. [06:37] if it happens on a live CD, that would really be odd [06:38] 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. [06:42] that's *really* weird, because I often build ubiquity locally on the running live CD and it works fine [06:42] did you build it in the live session, or externally and copy it in? [06:42] externally and copy [06:43] ah, so could still be a broken build system === jharr [n=jharr@137.48.138.204] has joined #ubuntu-installer [06:48] is this the right chan for help with automated installers? [06:48] *installs [06:50] yes [06:51] 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. [06:51] thanks [06:55] I've been trying to get automated pxe installs (feisty,amd64,20061102ubuntu13 netboot.tgz installer). [06:55] 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. [06:56] but I've done what several tutorials have said, and it's not really working that well. [06:58] 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://192.168.0.200/preseed/feisty-amd64-server --' [06:58] '/proc/cmdline shows those arguments in tact. [06:59] however I still have to answer all the language questions before it grabs the preseed/url file. [06:59] any ideas? [07:00] 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. [07:01] looks like your information is outdated [07:01] change preseed/locale to debian-installer/locale; change kbd-chooser/method to console-setup/layoutcode [07:01] otherwise your assumption is correct [07:01] s/assumption is/assumptions are/ [07:01] where did you get that information? it may just legitimately date from dapper or before, but otherwise I'd like to get it corrected [07:02] it was for dapper [07:02] http://halisway.blogspot.com/2006/06/ubuntu-dapper-pxe-network-install.html [07:02] got it from there [07:03] ok, stuff has changed since then [07:03] cool. [07:03] https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/preseed-contents.html is (almost) up to date for edgy [07:03] up to date in this respect, anyway [07:03] has much changed when going into feisty? [07:04] 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 [07:04] otherwise not much preseeding-wise [07:04] ahh, cool. [07:04] 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. [07:05] sensible [07:05] yeah, it's a pretty big project because of the way things were done for a long time. [07:05] It's mostly going to be getting everyone to work that way. [07:05] Believe it or not, the way they did things before hand was to do raw installs for every client. [07:06] oh, I can believe it [07:06] and some of the software required makefile patches & such. [07:06] I convinced them to use systemimager after my boss asked me to install 20 new nodes. [07:06] is there a way to get the installer to spit out the choices you made into a preseed file? [07:07] I remember debian doing something like that, that left a couple of files in /root. [07:58] jharr: see right at the bottom of the URL I gave above [07:58] it will certainly preseed more than you need, though [08:06] 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. [08:06] debconf-get-selections I guess [08:06] but you really have too much things preseeded [08:07] yeah, but I mean it would be nice to have the results of the install spit out just the stuff you answered. [08:07] It'd make it a lot easier for OEMs to setup their own custom installs that way. [08:09] I think it was removed when debconf-get-selections --installer was implemented, because at that point it was trivial to generate [08:09] oh, you're talking about the old /root/dbootstrap_settings perhaps [08:09] that definitely predates d-i and preseeding [08:10] you can probably filter the cdebconf database for stuff with the seen flag set [08:11] interestingly, the debconf db on my system does not appear to have very much at all with the seen flag set. Curious [08:11] shall have to investigate that at some point [08:16] oh, nice, I <3 text based DBs :D [08:59] hrmm [09:02] When I'm doing an install, how can I tell what the preseed directive is for the current prompt? [09:02] partitioning in Feisty has changed apparently and I'm looking around for the preseed options that are equivalent to edgy's === jeckers [i=hexum@tejava.dreamhost.com] has joined #ubuntu-installer === mark [i=mark@tilia.nedworks.org] has joined #ubuntu-installer === Quadrispro [n=1040FF65@ip-2-168.sn1.eutelia.it] has joined #ubuntu-installer === Quadrispro [n=1040FF65@ip-2-168.sn1.eutelia.it] has left #ubuntu-installer [] [11:46] 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 [11:46] it may not be entirely up to date at every point due to buffering [11:46] jharr: the partman-auto/method thing I mentioned should be the only relevant change