=== shadeslayer_ is now known as shadeslayer
[10:14] <CIA-14> debian-installer: cjwatson * r1318 lucid-proposed/ (8 files in 2 dirs): Move to 2.6.32-32 kernels.
[10:17] <CIA-14> debian-installer: cjwatson * r1319 lucid-proposed/debian/changelog: releasing version 20081029ubuntu102.9
[12:57] <CIA-14> user-setup: cjwatson * r237 ubuntu/ (debian/changelog user-setup-apply): Add LightDM autologin support (LP: #797669).
[12:59] <CIA-14> debian-installer: cjwatson * r1467 ubuntu/ (5 files in 2 dirs): Move to 3.0-1 kernels.
[13:00] <CIA-14> user-setup: cjwatson * r238 ubuntu/ (debian/changelog user-setup-apply): merge 1.28ubuntu15 upload, apparently not pushed to bzr
[13:01] <CIA-14> user-setup: cjwatson * r239 ubuntu/debian/changelog: releasing version 1.28ubuntu16
[14:06] <CarlFK> http://imagebin.org/158729  "No network interface detected" ... "could not find valid BOOTIF="
[14:07] <CarlFK> qemu-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:19] <cjwatson> that can't possibly be natty
[14:20] <cjwatson> can't really debug based on an image of the tail of the syslog either
[14:20] <CarlFK> that's what I just built
[14:21] <CarlFK> I am trying to figure out how to get files out of vm without networking
[14:21] <cjwatson> it can't be natty because that error message did not exist in the natty code
[14:21] <cjwatson> attach something that looks like a USB device
[14:22] <cjwatson> anyway, 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 devices
[14:22] <cjwatson> perhaps because your build didn't have the right kernel version or something?
[14:24] <CarlFK> build box is oneiric 3.0-0-generic - do I need to keep it current?
[14:25] <CarlFK> I figured the di build would fail
[14:30] <cjwatson> kernel version on the build system shouldn't matter
[14:31] <cjwatson> you do need to keep d-i in sync with the archive you're building from though
[14:49] <CarlFK> http://paste.ubuntu.com/628413/  syslog
[14:54] <CarlFK> looks like the ??? thing is fixed in http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/linux
[14:54] <cjwatson> it wasn't fixed in the kernel, no.  it was fixed in parted.  and it was never a problem in natty anyway
[14:55] <cjwatson> that syslog shows that your image doesn't have any kernel modules in it
[14:58] <CarlFK> k - I'll stop trying to build.  didn't think that was a good idea ;)
[14:59] <CarlFK> oh... natty.. grumble.
[17:16] <CIA-14> debian-installer: cjwatson * r1468 ubuntu/ (build/config/armel.cfg debian/changelog): re-enable linaro-omap and linaro-vexpress flavours, following MIR
[17:19] <CIA-14> debian-installer: cjwatson * r1469 ubuntu/debian/changelog: releasing version 20101020ubuntu36
[17:19] <cjwatson> lool: 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 online
[17:27] <lool> cjwatson: ok
[17:27] <lool> cjwatson: thanks a lot for promotion and reenabling these two
[23:44] <CIA-14> debian-installer: lool * r1470 ubuntu/debian/ (changelog control):
[23:44] <CIA-14> debian-installer: Add parted [armel] build-dep; needed for armel+omap and armel+omap4
[23:44] <CIA-14> debian-installer: netboot images (via build/boot/arm/generate-partitioned-filesystem).
[23:44] <lool> NB: this is not related to the linaro-* images
[23:45] <lool> Uploaded ubuntu37 to fix the armel build