xivulonevand, slanga required some testing for 217348 if possible (requires vm with multiple hd)11:47
xivulonalso would it be possible to update wubi on the iso?11:48
CIA-48installation-guide: cjwatson * r424 ubuntu/ (13 files in 2 dirs): Bump kernelversion to 2.6.26 (main architectures) and 2.6.25 (ports).13:08
CIA-48installation-guide: cjwatson * r425 ubuntu/ (debian/changelog en/welcome/what-is-ubuntu.xml): Bump GNOME version to 2.24.13:09
CIA-48installation-guide: cjwatson * r426 ubuntu/ (build/entities/common.ent debian/changelog): Bump release version and names for Intrepid.13:11
CIA-48installation-guide: cjwatson * r427 ubuntu/debian/changelog: releasing version 20080520ubuntu113:16
evandxivulon: I'm pulling down the latest ISO to test wubi now, then I'll fill out a SRU for it and ping slangasek when his core hours start.14:28
xivulonevand, great14:31
davmor2xivulon: what logs do you need?14:32
xivulondavmor2: if the error is on first reboot after windows, I need /casper.log14:33
davmor2cool np's I'll paste in a second along with menu.lst14:34
xivulonif it is a post-install boot issue you have to boot with the "debug" option and check the log in /tmp14:34
xivulonas mentioned on testing, please use paste.ubuntu.com for the time being as I cannot access gmail14:34
davmor2xivulon: http://paste.ubuntu.com/22345/ for menu.lst14:54
davmor2having issues finding the other log files though :(  not under /var/log/14:55
davmor2no casper and no installer and nothing under /dist-upgrade14:56
davmor2xivulon: I'm going to delete the install and try again15:05
xivulondavmor2: menu.lst looks good15:07
xivulonas mentioned in a normal installation you have to boot with "debug" then a log will appear under /tmp15:07
xivulonps shouldn't debug be a default option in recovery mode? that is certainly handy15:08
xivulondavmor2: boot with the following kernel line in menu.lst15:09
davmor2xivulon: need to re-install first15:10
xivulonno that shouldn't be required15:10
xivulongood to have a broken setup15:10
xivulon /boot/vmlinuz-2.6.24-19-generic root=UUID=78983F43983EFEE6 loop=/ubuntu/disks/root.disk15:10
xivulon /boot/vmlinuz-2.6.24-19-generic root=UUID=78983F43983EFEE6 loop=/ubuntu/disks/root.disk debug15:10
davmor2no I deleted the install so I need to reinstall first 2 ticks15:10
xivulon^ see the kernel line in menu.lst to get a log under /tmp15:11
davmor2can I run wubi with --debug?15:12
xivulonno, that will only stop the frontend every 2 secs15:12
xivulonit only helps to debug windows side issues, and nowdays does not add much over the wubi log15:12
davmor2okay np's15:13
xivulonyou seem to have a post-installation issue, so I need the initramfs logs15:13
xivulonand those are produced if you have debug as one of the kernel boot args15:13
davmor2xivulon: ha ha I shall add the C:ubuntuinstallation-logs.zip to my website the install fails15:38
evandargh, wubi install failed.15:39
evandhttp://evalicious.com/tmp/wubi-20080623-syslog.txt for the curious15:44
xivulondavmor2 do you get the same error as evand?15:48
xivulonalso your previous log indicates that installation was completed15:48
xivulonevand, that is a puls error, can you check why that fails?15:48
davmor2could be15:49
xivulondavmor2, so first try the installation went through up to reboot and second try it stopped, did you do anything different?15:49
xivulonlike installing of an ISO as opposed of installing of a CD15:50
davmor2no the first time it must of failed but not flagged the fact15:50
evandxivulon: the error isn't in ubiquity, it just bubbles up to it.15:51
evandlooks like grub-installer and, if I had to guess, the lack of a root device.15:52
evandI could be wrong about the latter.15:52
davmor2evand: xivulon: they're my logs knock yourselves out :)15:55
xivulonis this using a CD or ISO, i.e. do you have a directory /ubuntu/install/cdrom?16:01
xivulonthe issue seems to be the same as evand16:02
davmor2xivulon: cd16:07
xivulonevand can you run grub-installer with set -x?16:14
xivulondavmor2: can your un on an ISO?16:14
davmor2I'm just going to try the cd incase it's actually the cd at fault but I can try after that if you want16:15
xivulondavmor2: unlikely since evand has the same issue16:15
evandxivulon: already working on it.  The problem appears to be in is_removable.16:15
xivulonremovabledevice="$(mount | grep "on $ROOT${1%/} " | cut -d' ' -f1)"16:16
xivulonremovabledevice="$(mount | grep "on $ROOT${1%/} " | cut -d' ' -f1)"16:16
xivulonprobably needs head as well...16:16
xivulontry to add | head -n 116:16
xivulonin my vm test I killed it at copying files and did not get that far... arg...16:17
xivulondavmor2: please try with an ISO, as I think this is due to grub-installer being confused in the presence of bindmounts16:20
xivulonand bindmounts are only used when installing from CD16:20
xivulonevand if I am right findfs and findfstype are also affected16:21
evandhrm, actually I stand corrected, it might not be there after all.16:21
evandone moment, I'm going to try an install again with set -x in grub-installer.16:22
xivulonhmm it might be, see the fix in partman-auto-loop16:22
xivulonthis looks very similar issue16:22
xivulonsee how many lines we get for: mount | grep "on $ROOT${1%/} "16:23
xivulonhmm nope16:27
xivulonwe are grepping for the mountpoint here and not for the device16:28
* xivulon waits for set -x16:29
CIA-48debian-installer-utils: cjwatson * r657 ubuntu/ (17 files in 4 dirs): merge from Debian 1.5817:53
xivulonevand, any progress?17:59
CIA-48debian-installer-utils: cjwatson * r658 ubuntu/debian/ (changelog rules): merge from Debian 1.5918:02
evandxivulon: ah, there you are.  I might be very wrong about grub-installer: http://evalicious.com/tmp/wubi-20080623-syslog-2.txt18:03
evandI'm looking into it.18:03
CIA-48debian-installer-utils: cjwatson * r659 ubuntu/debian/changelog: releasing version 1.59ubuntu118:04
xivulonhmm, davmor2 did you try with an ISO by any chance?18:04
xivulonISO worked for me since I did a full test, but in CD mode I only stopped at file copying...18:05
xivulonso I would tend to think it is related to the bindmount of /cdrom18:06
xivulonwhich is the main difference between the 2 setups18:06
davmor2shall test shortly just had some other stuff to do :)18:21
hardwirecompbrain: hows life?18:23
* hardwire notes that the latest hardy kernels support openvz sans bugs, finally.18:24
evandhrm, the install succeeded that time.18:49
davmor2xivulon: installing sp3 I thought all the updates had finished :(18:59
xivulonevand ? did it work? anything different?19:04
xivulondid you use ISO or CD?19:05
evandit worked that time, I had enabled debugging and added some print statements.  Running another install in just debug mode to see if that's enough to get it to succeed.19:05
evandI'm wondering if it's an apt bug.19:06
davmor2xivulon: evand: would you believe it xp seems to have a bug ;) It's downloading SP3 and the dl bar vanished :)19:12
stgraberdavmor2: not a problem, last time I gave it a try I never saw a progress bar during the whole install process :)19:18
stgraberand it actually downloads it when "Preparing for download" ...19:18
davmor2still a bug ;)19:19
stgraberreport it :)19:20
davmor2I don't like windows enough to want to improve it ;)19:22
evandxivulon: very odd, it's not the use of --debug (still reproduceable, not sure why it worked the second time), and it's not an issue in regular installs as far as I can tell.19:32
xivulonevand could it be that you used an ISO in the second case?19:35
xivulonas opposed to using a CD? (wubi will eject the CD whether virtual or not)19:36
evandnope, this is all in vmware19:36
evandusing an emulated CD device19:36
xivulondo we know we chunk of code generates it?19:37
xivulonI'll be home in a couple of hours and start playing with it19:37
evandbut as far as what ubiquity code, scripts/install.py19:37
xivulonis it when chrooting?19:38
xivulonI'd guess so, since I imagine apt runs in chroot, I mean is the chrooting operation per se' or is it the command run in chroot mode19:39
evandI don't follow what you're asking.  We tell apt that the root is /target.  I haven't stared at the python-apt code long enough to if it is in fact chrooting.  I don't believe it does though.19:43
evanda grep for chroot in the source tree seems to prove that.19:44
xivulonignore that, have no code under my nose, just blind guesses, I seemed to remember that apt on the target was working in chroot, probably wrong19:48
evandoh fun, as soon as I try to print self.percent in pulse() the problem disappears.21:06
=== joejaxx_ is now known as joejaxx
davmor2xivulon: is there a specific folder that the iso needs to be in?21:10
davmor2evand: does the iso need to be in a specific diretory do you know?21:24
evandaccording to the wiki it needs to be in the same folder as the executable.21:28
davmor2evand: ta :)21:30
cjwatsonapt doesn't actually chroot itself. (Proof: grep for chroot in apt's source code; no matches.) We do tell apt to tell dpkg to chroot, using --root=/target, and we point apt's administrative file locations at /target (though may have missed some).21:33
cjwatsonah, I see Evan already did the grep proof21:33
davmor2xivulon: iso has gone further than the cd install current 94% should finish shortly21:46
davmor2xivulon: iso seems to of worked without fault21:51

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!