[12:44] <superm1> cjwatson, sure i'd be glad to, how do i revert the revision?
[12:56] <CIA-18> ubiquity: superm1 * r2256 ubiquity/ (4 files in 4 dirs): revert non critical changes from r2255 until after beta
[08:57] <spam> hi there....
[09:01] <spam> i have using ubuntu installer ..and doing some study on this.Can anybody tell me how does it check internally the distribution name and version name so that if proper repository address has not given it shows error.."invalid repo link" or "release file missing'
[09:02] <spam> during mirror selection stage at the installation process
[09:09] <spam> is there anybody...
[09:36] <cjwatson> spam: could you tell me the exact message, please? Don't paraphrase
[09:36] <cjwatson> spam: at any rate, it looks in the Release file on the mirror
[09:37] <cjwatson> which has various metadata like that
[10:33] <spam> cjwatson..:"the specified ubuntu archive mirror is either not available,or doesnot have a valid Release file on it.Please try a different mirror"
[10:36] <spam> Cjwatson: r u there..? i was out of system....but i want to know what udeb does this checking during mirror selection stage.I checked one udeb is there"choose-mirror" is it the only mirror which checks the release file on the mirror?
[10:48] <cjwatson> spam: yes, choose-mirror (and choose-mirror-bin, which comes from the same source package) is the one you're looking for
[10:49] <cjwatson> spam: please don't do the "are you there" thing, by the way - I'm extremely busy this morning and it may take me a while to respond
[10:52] <spam> cjwatson:actually my problem is some what different. I have created one local repository and from there i am installting my softwares..no problem i am facing but i have given my version name."my-ver".So when installer is checking for version /code name the error is coming.
[10:54] <spam> so where i need to change exactly..as i changed the string name mentioned in "choose-mirror" pkg source code and after successful comilation i have included that one in the installer and compile it successfully,...no problem came but the same problem persist for choosing mirror.
[10:54] <cjwatson> do you have dists/*/Release files on your mirror?
[10:55] <spam> yah...and exactly in the same order.only the string is different
[10:55] <cjwatson> exactly where is your Release file? what directory?
[11:01] <spam> is it ok/
[11:02] <spam> /my-distro///dists//my-ver//Release
[11:02] <spam> same what debian repository follows...
[11:04] <spam> and when it fails i went to shell prompt and from there i tried to connect the specified location using wget ..and i got success
[11:04] <cjwatson> did you preseed mirror/suite=my-ver?
[11:04] <cjwatson> or otherwise change the installer's default suite to retrieve
[11:05] <cjwatson> (e.g. by changing /etc/lsb-release in the initrd)
[11:05] <spam> the first few line r like..
[11:05] <spam> Architectures: i386
[11:05] <spam> Codename: anant
[11:05] <spam> Components: main
[11:05] <spam> Date: Wed, 29 Aug 2007 10:24:05 UTC
[11:05] <spam> Description: BOSS Anant Repository
[11:05] <spam> Label: anant
[11:05] <spam> Origin: boss
[11:05] <spam> Suite: unstable
[11:05] <spam> Version: 2.0
[11:05] <spam> MD5Sum:
[11:05] <cjwatson> that Suite: is bogus
[11:05] <cjwatson> it should match the subdirectory of dists/
[11:06] <spam> that means in this case it should be anant ??
[11:06] <cjwatson> if that file is in dists/anant/Release, yes
[11:06] <cjwatson> you also need to change the installer to look there; it can't guess that it needs to retrieve dists/anant/Release by magic
[11:06] <cjwatson> changing /etc/lsb-release in the initrd is the easiest way
[11:07] <cjwatson> I suggest reverting whatever changes you made to choose-mirror, as that shouldn't be necessary
[11:07] <spam> yah..thats it..
[11:08] <spam> ok..but when i am choosing "enter manually.." option for mirror selection then also do i need to modify the d-i?
[11:09] <cjwatson> "enter information manually" lets you choose the hostname and directory, not usually the suite
[11:09] <cjwatson> you can avoid modifying the initrd by putting mirror/suite=anant on the kernel command line, if you prefer
[11:12] <spam> will it be ok for my case if other parameters are same as in debian in my local mirror?
[11:14] <spam> can i set "mirror/suite=anant" inside default file for PXE net booting installation/
[11:16] <spam> default file is in "ubuntu-installer/i386/pxelinux.cfg/default" which is the default configuration file...
[11:16] <spam> or i am missing something?
[11:16] <cjwatson> parameters> that's too general a question so I can't be sure. Try it :-)
[11:18] <cjwatson> yes, you can set it on the appropriate 'append' line in pxelinux.cfg
[11:18] <spam> yes .i got it.
[11:19] <spam> thanks..for your help.let me try this one
[11:29] <xivulon> cjwatson, evand, had little time this w/e and almost no internet connection, would like to catch up briefly on any progress you have made
[11:29] <xivulon> tonight I'll download and test the new image
[11:30] <cjwatson> aside from what I told you about Friday's work, I have almost entirely been panicking about other things
[11:32] <CIA-18> ubiquity: cjwatson * r2257 ubiquity/ (configure configure.ac): bump to 1.5.18
[11:35] <xivulon> cjwatson, is grub safe in loopinstallations?
[11:35] <xivulon> I'd like to start having more people involved in the testing process, it does not matter if they do not end up with ubuntu installed, but at least the should not find their MBR overwritten
[11:36] <xivulon> Did not go that far in the installation process myselef on friday, but noticed that "install grub in hd0" was selected when I got stack at the "ready to install" page
[11:40] <cjwatson> I haven't got that far in my testing
[11:41] <xivulon> np will give it another go tonight
[11:41] <cjwatson> oh, no, it isn't yet
[11:41] <cjwatson> it needs a wubi change
[11:41] <cjwatson> I'll commit that shortly
[11:41] <cjwatson> I added a preseeding facility which should make it safe, but wubi needs to use it
[11:42] <xivulon> are you goint to merge into wubi branch? I can only do that tonight
[11:42] <xivulon> To build wubi, remove the nsis fodler, and run "make clean; make prerequisites; make all"
[11:43] <xivulon> You only need "make all" once if plugins are cleaned/modified, to rebuild wubi itself, make is enough
[11:46] <xivulon> The other question which we left pending was whether Ubiquity can simply skip mounted devices/partitions (except when loopinstalling)
[11:46] <cjwatson> I've committed it straight to the wubi branch
[11:46] <xivulon> thanks
[11:47] <cjwatson> I'm not going to attempt to build it though, I'm not convinced enough that I can do that correctly
[11:47] <cjwatson> skip mounted devices/partitions> sorry, I don't know what you mean
[11:47] <xivulon> I assume that ubiquity at some stage prepares a list of partitions (and devices)...
[11:48] <xivulon> If some of those was already mounted, and we are not in a loopinstallation, would it be possible to skip it?
[11:49] <xivulon> I am not sure whether this is already current behaviour
[11:49] <cjwatson> I still don't quite understand what problem you're trying to solve
[11:50] <xivulon> The issue is to go around wubi read-only mode, but would also help when a LiveCD user had the windows partition mounted and then run Ubiquity targeting that partition
[11:50] <cjwatson> but what is the problem?
[11:51] <xivulon> If a partition is mounted it cannot be resized online
[11:51] <cjwatson> that is, what undesirable thing happens that you want not to happen?
[11:51] <cjwatson> oh, you mean in the manual partitioning UI?
[11:51] <xivulon> So for instance in read-only mode you have /isodevice mounted. I'd still want users to run ubiquity to be able to install on a different partition
[11:52] <cjwatson> I imagine the partitioner will simply not allow that. I don't think removing it from the manual partitioning UI is a good idea though; it would be very confusing to have only part of the disk listed
[11:52] <cjwatson> in any event, that's post-beta
[11:52] <xivulon> cjwatson "simply not allow that" is more than good enough
[11:53] <cjwatson> one problem is that it might allow resizing other partitions
[11:53] <cjwatson> on the same disk
[11:53] <cjwatson> or creating/deleting partitions
[11:53] <cjwatson> none of that will work if a partition is mounted
[11:54] <xivulon> Is modifying other partitions a problem? (change in partition table are not well digested maybe)?
[11:54] <cjwatson> it is not possible to make any changes to the partition table when the disk is locked, which will be the case if anything is mounted from that disk
[11:55] <cjwatson> well, you can change the partition table, but the kernel will refuse to reread it until you reboot
[11:56] <xivulon> Makes sense, even in this case though, Ubiquity has still a use though if the user pre-partitions the drives or already has a (non-mounted) partition to be overwritten.
[11:56] <xivulon> Or if the target partition is on a different device
[11:56] <CIA-18> ubiquity: cjwatson * r2258 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[11:56] <CIA-18> ubiquity: * GTK frontend:
[11:56] <CIA-18> ubiquity:  - Make release notes button work again (LP: #138365).
[11:56] <cjwatson> right, it isn't useless, but it does need to be made clear in the UI
[12:00] <xivulon> I'd do so that if a device is mounted the user can only pick free/space or an existing partition to install into
[12:00] <xivulon> Anyway don't what to distract you too much with that
[12:02] <cjwatson> free space won't work either
[12:02] <cjwatson> unless it's on another disk
[12:12] <xivulon> Just a list of available (non-mounted) partitions then (but I guess that splitting root and swap would be a problem).
[12:13] <xivulon> What about doing the partitioning and then forcing a reboot?
[12:20] <cjwatson> too horrible for words
[12:25] <xivulon> ahah
[12:25] <xivulon> I agree
[12:45] <xivulon> cjwatson, last try: partprobe
[12:45] <cjwatson> ?
[12:46] <xivulon> http://www.cyberciti.biz/tips/re-read-the-partition-table-without-rebooting-linux-system.html
[12:53] <cjwatson> xivulon: partprobe isn't magic; it's just a userspace program (and the same libparted calls are already made by the installer). That article is incomplete
[12:54] <cjwatson> xivulon: if the kernel refuses to reread the partition table because the disk is locked, no userspace program can possibly help
[12:59] <xivulon> makes sense
[01:08] <xivulon> http://lkml.org/lkml/2006/9/8/46 and http://www.gelato.unsw.edu.au/lxr/source/include/linux/blkpg.h
[01:08] <xivulon> could it be that there is some in-kernel support which is simply tapped by userspace toos?
[01:09] <cjwatson> not as far as I can see
[01:09] <cjwatson> I would rather you tried it than that you pasted URLs here :-)
[01:10] <xivulon> I wish, but have to use a windows machine during the day
[01:10] <cjwatson> it may be true that you can get away with BLKPG_ADD_PARTITION (which libparted already uses) if that specific partition isn't in use
[01:11] <cjwatson> it's risky for a partitioner to rely on the exact details though
[01:11] <cjwatson> particularly if any kind of resizing or insertion of partitions is involved
[03:12] <evand> weird, I could have sworn that the linkbutton issue was a GTK+ bug.
[03:13] <evand> but I suppose I was just not setting it up correctly.
[03:13] <cjwatson> I think the code fell out during the automation rearrangements; it was there originally
[03:13] <evand> yikes, sorry
[03:13] <cjwatson> no worries, caught it
[05:18] <superm1> yeah i had thought it was a GTK+ bug too, i had another pyGTK app that it randomly showed up in too.  i guess i'll have to take a look at your fix for it
[05:19] <cjwatson> you just need to do gtk.link_button_set_uri_hook(some_function)
[05:19] <cjwatson> gtk.LinkButton doesn't know how to launch a browser itself because that's pretty system-specific
[05:19] <superm1> so it doesn't by default call /usr/bin/sensible-browser then?
[05:19] <cjwatson> no
[05:20] <cjwatson> there's some argument that it should but then your application would still break on other systems ...
[05:27] <CIA-18> ubiquity: evand * r2259 ubiquity/ (debian/changelog ubiquity/osextras.py): * Fix typo in realpath_recurse (LP: #144460).
[05:28] <evand> Launchpad Janitor angers me.
[05:29] <evand> Though I suppose this can be fixed with a capital D
[05:45] <evand> cjwatson: now that we have ubiquity-dm, should we make that an option in isolinux in Hardy or document it as a kernel cmdline option?
[05:46] <cjwatson> something like that in hardy, yeah, though in that case it needs to not use --automatic
[05:46] <evand> indeed
[06:01] <evand> Is there some magic I can do to get past the partman crash with the latest daily cd and wubi?
[06:02] <cjwatson> which partman crash?
[06:03] <xivulon> ?
[06:03] <evand> reproducing...
[06:15] <xivulon> cjwatson, evand, if it may help with development, at this stage you can copy the ubuntu folder into a VM (ext3) drive and set the VM bootloader use the configfile in ubuntu/install
[06:19] <cjwatson> personally I don't have time to do anything other than get the standard installation flow working
[06:21] <evand> "The filesystem ntfs cannot be mounted on /, because it is not a fully-functional Unix file system."
[06:21] <evand> Clearly I must be doing something wrong
[06:21] <evand> that only started to appear after I canceled and ran ubiquity manually using -d and --automatic.
[06:21] <cjwatson> hmm
[06:22] <cjwatson> what build?
[06:22] <evand> wubi: the one from friday, ubiquity 1.5.17
[06:22] <cjwatson> hmm, that was supposed to be fixed in .17
[06:22] <cjwatson> why is it trying to mount an ntfs filesystem on / ?
[06:23] <cjwatson> oh, unless ...
[06:23] <cjwatson> evand: can you get ps ax output from when that happens and see if autopartition-loop is there?
[06:25] <evand> will do
[06:27] <evand> doesn't appear to be
[06:27] <cjwatson> hm
[06:27] <cjwatson> ok, not what I thought then
[06:28] <cjwatson> can you see what the innermost running partman script is?
[06:28] <cjwatson> ps axf may help
[06:30] <evand>  check.d/08mountpoint_fat
[06:31] <cjwatson> evand: ls /var/lib/partman/devices/*/*/mountpoint
[06:31] <cjwatson> err, maybe not quite that
[06:31] <cjwatson> grep -H '^/$' /var/lib/partman/devices/*/*/mountpoint
[06:32] <evand>  /
[06:32] <cjwatson> I'm looking for filenames under /var/lib/partman/devices
[06:32] <evand> well, /var/lib/partman/devices/=dev=sda/32256-17873533439/mountpoint;/
[06:33] <cjwatson> no others?
[06:33] <evand> nope
[06:33] <cjwatson> are you following what I'm looking for here? it may be easier for you to take it from here
[06:34] <evand> no, sorry I don't follow
[06:34] <cjwatson> partman-auto-loop 0ubuntu9 (included in ubiquity 1.5.17) added 'rm -f $partition_id/mountpoint' because the host NTFS filesystem shouldn't really be mounted on /
[06:35] <cjwatson> partman-auto-loop temporarily tells partman that that filesystem is mounted on / in order that it can use the mount.d scripts to mount it
[06:35] <cjwatson> but it's supposed to clean up after itself
[06:35] <cjwatson> the real / in a wubi install ought to be a loop-mounted filesystem
[06:35] <evand> I think this is my fault.
[06:35] <cjwatson> i.e. =dev=loop2 or something not =dev=sda
[06:35] <cjwatson> oh, it could be that you didn't clean up all the way after cancelling, maybe?
[06:35] <evand> I ran the install, partman crashed, and I hit cancel instead of continue.  This brought me back to the desktop.
[06:35] <evand> Exactly
[06:36] <cjwatson> (remember my comments from Friday where I was doing losetup and stuff)
[06:36] <evand> indeed, I just realized I should have ran that
[06:36] <evand> taking care of that now
[06:37] <evand> sorry for the false alarm
[06:37] <cjwatson> it's certainly harder to clean up than it ought to be
[06:37] <cjwatson> I think that is a bug, it's just awkward to fix
[06:42] <evand> cjwatson: have you gotten through a full install yet?
[06:50] <cjwatson> no :-(
[06:50] <CIA-18> ubiquity: cjwatson * r2260 ubiquity/ubiquity/osextras.py: fix realpath_root a bit more so that it really returns something prefixed with root
[06:50] <evand> I got close
[06:51] <evand> at least to the formatting stage
[06:51] <evand> but then it decided it had enough of life and hard locked
[06:51] <cjwatson> sigh
[06:51] <cjwatson> memory?
[06:51] <evand> are you asking how much I was giving it?  about 768MB
[06:52] <cjwatson> huh
[06:52] <evand> I'm going to try again with htop running in the background
[06:52] <cjwatson> I guess it's unionfs then
[06:52] <evand> ah
[06:52] <evand> any updates from pkl?
[06:52] <cjwatson> he's off ill
[06:52] <cjwatson> I've asked Ben to take over
[06:52] <evand> uh oh
[06:52] <evand> oh, ok
[06:53] <evand> I was unaware that ben knew the unionfs internals, but I suppose that doesn't matter when you're king kernel hacker
[06:53] <cjwatson> I don't think he does much
[06:53] <cjwatson> but pkl gave a relatively detailed description of what he was doing the other day
[06:54] <evand> ah, good
[07:09] <evand> ugh, I think you're right about the hard lock being unionfs
[08:05] <cjwatson> meh, wubi was broken by our CD designation switching from Alpha to Beta
[08:05] <cjwatson> how fragile
[08:10] <cjwatson> evand: when xivulon returns, would you ask him to rebuild wubi urgently, and when that's done rebuild the live CDs?
[08:10] <cjwatson> I've committed the relevant fix
[08:12] <cjwatson> I'm off for a few hours now
[08:13] <evand> cjwatson: will do
[08:13] <cjwatson> thanks
[08:13] <evand> no problem
[08:28] <evand> cjwatson: I'
[08:28] <evand> whoops
[08:29] <evand> cjwatson: I'm not a RM by any means, but at what point does the beta release get pushed back on account of these unionfs bugs
[08:29] <evand> or can we go down to the 11th hour on that one
[09:45] <evand> cjwatson: I have a fix for checking to see if we're running in automatic mode.  Basically, m-a.py sets a flag when it gets handed a question and if that flag is not set when it gets to the point where it would normally dive into the gtk loop, then it doesn't have any questions to ask, so it returns self.succeeded.
[09:45] <evand> It's pretty much the same thing as checking for automatic, but arguably slightly cleaner
[09:51] <evand> though that's basically duplicating what filteredcommand is doing, arr
[09:51] <evand> xivulon:
[09:51] <evand> 14:10:31 < cjwatson> evand: when xivulon returns, would you ask him to rebuild  wubi urgently, and when that's done rebuild the live CDs?
[09:52] <evand> 14:10:38 < cjwatson> I've committed the relevant fix
[09:53] <superm1_> evand, have you been seeing any weird oddities of the installer stopping at random places on the latest dailies (after the unionfs fix)?  I've had random stops at apt configuration, configuring hardware, and configuring packages that have gotten installed.  Nothing tangible in the logs though, so I was going to hold off reporting it until I found something in /var/log/syslog or /var/log/installer or dmesg
[09:53] <evand> superm1_: unionfs is still an issue
[09:53] <superm1_> evand, okay so that is likely where its sitting then
[09:54] <evand> most likely
[09:54] <evand> for some reason I wasn't experiencing it for a brief period of time
[09:54] <evand> but it's definitely back
[09:54] <evand> the kernel team is on it
[09:54] <superm1_> i'm almost wondering if they are better off rolling back to the older (functional) unionfs release rather than debug these issues with the beta looming so close
[09:54] <evand> they can't, though I do not recall why
[09:55] <superm1_> ah i see
[09:55] <xivulon> evand wubi rev 301 should be up
[09:55] <evand> xivulon: thanks!
[09:56] <xivulon> I'll explain how to rebuild yourself
[09:56] <xivulon> It's fairly straightforward
[09:56] <xivulon> 1 remove any nsis folder you may have
[09:56] <xivulon> 2 make clean
[09:56] <xivulon> 3 make prerequisites
[09:56] <xivulon> 4 make all
[09:57] <evand> <- 64-bit, no WINE atm.
[09:57] <xivulon> hmm
[09:57] <evand> but continue, I'll save it for reference
[09:57] <xivulon> that's it, if you then edit nsis you only need to run "make"
[09:57] <evand> neat, thanks
[09:57] <xivulon> make all also updates grub4dos, the plugins, and translations
[09:58] <xivulon> Which do not need to be rebuilt every time unless you change them or run make clean
[10:00] <evand> ok
[10:00] <xivulon> downloading the iso
[10:00] <evand> I haven't built a new one yet
[10:01] <evand> waiting to see if any other changes need to go in from elsewhere in the distro
[10:04] <xivulon> Hmm I am only interested in wubi/lupin relevant changes
[10:04] <xivulon> Are they in?
[10:21] <evand> xivulon: if I understand the release manager correctly, he wants to see ubiquity 1.5.18 on the next CD, so I'm uploading that, letting it build, then triggering a new CD build
[10:21] <evand> should be a few hours
[10:21] <xivulon> What is/isn't in there?
[10:23] <xivulon> It looks that rev 2258 are not in, anything relevant there?
[10:24] <evand> as far as wubi is concerned, no
[10:25] <xivulon> ok I am gonna test the iso I have. logging off now
[10:25] <evand> best of luck -- unionfs is still an issue, so beware
[10:25] <xivulon> I'll report back any issue
[10:25] <evand> thanks
[11:21] <michael_e_brown> cjwatson, ping
[11:48] <xivulon> cjwatson, I noticed that autopartition-loop does not include changes to make it skip mount.d scripts for mounted partitions
[11:49] <xivulon> You mentioned that a few days ago, so I am not really surprised, just pointing out
[11:54] <michael_e_brown> anybody here who can answer questions about ubiquity and preseed?
[11:54] <michael_e_brown> for gutsy?
[11:55] <xivulon> what question?
[11:57] <michael_e_brown> so... I am trying to automate gutsy install.
[11:57] <michael_e_brown> using live cd as the base.
[11:57] <michael_e_brown> and I dont see much documentation on it.
[11:57] <michael_e_brown> basically what I have is /dev/sda1 is a Dell Utility partition
[11:58] <michael_e_brown> /dev/sda2 has a copy of the live CD copied to it
[11:58] <michael_e_brown> and has grub installed to it is bootable
[11:58] <michael_e_brown> and that boots and works just fine.
[11:58] <michael_e_brown> I can go through the graphical installer and repartition the rest of the disk and everything is wonderful
[11:58] <michael_e_brown> but now, I need to totally automate that.
[11:58] <evand> michael_e_brown: yes
[11:59] <michael_e_brown> I tried starting with a preseed, but cant seem to make it do anything.
[11:59] <evand> the reason that it's not documented very well yet is that it was just developed in this release cycle.
[11:59] <evand> michael_e_brown: you want to run ubiquity with the --automatic flag
[11:59] <cjwatson> evand: unionfs> not sure yet, hoping not to have to decide
[11:59] <michael_e_brown> ok, how to pass that?
[11:59] <cjwatson> evand: m-a.py/automatic> let's stick with what we have for beta if it works, and roll that in afterwards
[11:59] <michael_e_brown> I have preseed=... on the kernel command line
[12:00] <cjwatson> superm1_: rolling back unionfs involves backing out lots of apparmor stuff too
[12:00] <evand> cjwatson: agreed, that's why it's not checked in
[12:00] <superm1_> cjwatson, ah that's a bit unfortunate
[12:00] <cjwatson> michael_e_brown: booting with automatic-ubiquity (and a very current image) should suffice
[12:00] <evand> I just bzr shelved it
[12:00] <cjwatson> (as in, 'automatic-ubiquity' on the command line)
[12:00] <michael_e_brown> I have daily gutsy from today
[12:01] <michael_e_brown> so, just add that to the kernel command line?
[12:01] <evand> cjwatson: the wubi.exe bug was not reproduceable.  Do you want me to trigger a CD build now or wait for ubiquity to make its way into the archive?
[12:02] <cjwatson> michael_e_brown: yeah
[12:02] <michael_e_brown> booting now..
[12:02] <xivulon> michael_e_brown if the preseed is on hard disk you can use find_preseed=/path/to/preseed
[12:02] <michael_e_brown> have that.
[12:02] <cjwatson> evand: which image were you using?
[12:02] <xivulon> cjwatson: rev231
[12:02] <michael_e_brown> I have preseed=/cdrom/preseed/dell.seed
[12:02] <cjwatson> michael_e_brown: use file=
[12:02] <xivulon> then you do not find_preseed
[12:03] <cjwatson> (or preseed/file=, equivalent)
[12:03] <michael_e_brown> sweet. Ok. 'automatic-ubiquity' worked. now?
[12:03] <xivulon> cjwatson, first time I run wubi I had a crush, but was not able to reproduce that again
[12:03] <cjwatson> xivulon: I meant which CD image version, not which wubi version
[12:03] <cjwatson> xivulon: I committed a fix to wubi to make it expect Beta rather than Alpha
[12:03] <michael_e_brown> Right now, I have 'preseed=/cdrom/preseed/dell.seed', I need "preseed/file=..." ?
[12:03] <cjwatson> that was the rebuild I wanted
[12:03] <xivulon> that went in fine
[12:04] <cjwatson> xivulon: you've told us several times how to rebuild wubi ourselves, which is great, but for beta I want to stick with the current build process
[12:04] <xivulon> I used the beta CD with wubi looking for beta
[12:04] <cjwatson> three days before beta is no time to be switching which machine is doing the build
[12:04] <xivulon> sure
[12:04] <evand> cjwatson: that went in fine, but pitti was in the process of building the CD and xivulon found that crash in wubi.exe so I held off on running the build, while at the same time pushing a new ubiquity out as it seemed like pitti wanted that asap
[12:05] <xivulon> cjwatson all other times I tried wubi went well, unfortunately I did not have --debug tracing the first time around
[12:06] <xivulon> I am writing from latest wubi boot indeed
[12:06] <evand> 1.5.18 is stuck waiting for approval
[12:06] <evand> should I just trigger a new cd build instead of waiting?
[12:07] <xivulon> evand can you quickly test wubi?
[12:07] <xivulon> I do not see any code change that could have triggered that though
[12:08] <evand> xivulon: yes, what am I looking for
[12:10] <xivulon> hmm any time I do tab completion in /var/log/ the shell freezes
[12:10] <michael_e_brown> ok, so ubiquity is coming up automatically, but doesnt appear to have read the preseed.
[12:10] <michael_e_brown> just a sec...
[12:12] <evand> xivulon: you seem to have broken CD rom detection