/srv/irclogs.ubuntu.com/2011/06/17/#ubuntu-installer.txt

=== shadeslayer_ is now known as shadeslayer
CIA-14debian-installer: cjwatson * r1318 lucid-proposed/ (8 files in 2 dirs): Move to 2.6.32-32 kernels.10:14
CIA-14debian-installer: cjwatson * r1319 lucid-proposed/debian/changelog: releasing version 20081029ubuntu102.910:17
CIA-14user-setup: cjwatson * r237 ubuntu/ (debian/changelog user-setup-apply): Add LightDM autologin support (LP: #797669).12:57
CIA-14debian-installer: cjwatson * r1467 ubuntu/ (5 files in 2 dirs): Move to 3.0-1 kernels.12:59
CIA-14user-setup: cjwatson * r238 ubuntu/ (debian/changelog user-setup-apply): merge 1.28ubuntu15 upload, apparently not pushed to bzr13:00
CIA-14user-setup: cjwatson * r239 ubuntu/debian/changelog: releasing version 1.28ubuntu1613:01
CarlFKhttp://imagebin.org/158729  "No network interface detected" ... "could not find valid BOOTIF="14:06
CarlFKqemu-system-x86_64 -m 512 -drive file=natty.qcow2,cache=writeback -kernel linux -initrd initrd.gz --append 'root=/dev/rd/0 rw     DEBCONF_DEBUG=5     '14:07
cjwatsonthat can't possibly be natty14:19
cjwatsoncan't really debug based on an image of the tail of the syslog either14:20
CarlFKthat's what I just built14:20
CarlFKI am trying to figure out how to get files out of vm without networking14:21
cjwatsonit can't be natty because that error message did not exist in the natty code14:21
cjwatsonattach something that looks like a USB device14:21
cjwatsonanyway, I think the BOOTIF message is irrelevant; looks more like your build doesn't contain any relevant network drivers, or else your VM doesn't have any network devices14:22
cjwatsonperhaps because your build didn't have the right kernel version or something?14:22
CarlFKbuild box is oneiric 3.0-0-generic - do I need to keep it current?14:24
CarlFKI figured the di build would fail14:25
cjwatsonkernel version on the build system shouldn't matter14:30
cjwatsonyou do need to keep d-i in sync with the archive you're building from though14:31
CarlFKhttp://paste.ubuntu.com/628413/  syslog14:49
CarlFKlooks like the ??? thing is fixed in http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/linux14:54
cjwatsonit wasn't fixed in the kernel, no.  it was fixed in parted.  and it was never a problem in natty anyway14:54
cjwatsonthat syslog shows that your image doesn't have any kernel modules in it14:55
CarlFKk - I'll stop trying to build.  didn't think that was a good idea ;)14:58
CarlFKoh... natty.. grumble.14:59
CIA-14debian-installer: cjwatson * r1468 ubuntu/ (build/config/armel.cfg debian/changelog): re-enable linaro-omap and linaro-vexpress flavours, following MIR17:16
CIA-14debian-installer: cjwatson * r1469 ubuntu/debian/changelog: releasing version 20101020ubuntu3617:19
cjwatsonlool: this will FTBFS as I'm going out and don't have time to wait a publisher cycle for linux-linaro-{omap,vexpress} to show up in main; I'd appreciate it if somebody could hit retry in about an hour and a half, otherwise I'll do it next time I'm online17:19
loolcjwatson: ok17:27
loolcjwatson: thanks a lot for promotion and reenabling these two17:27
CIA-14debian-installer: lool * r1470 ubuntu/debian/ (changelog control):23:44
CIA-14debian-installer: Add parted [armel] build-dep; needed for armel+omap and armel+omap423:44
CIA-14debian-installer: netboot images (via build/boot/arm/generate-partitioned-filesystem).23:44
loolNB: this is not related to the linaro-* images23:44
loolUploaded ubuntu37 to fix the armel build23:45

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