[00:06] <CarlFK> cjwatson:  bug 796865
[00:06] <ubot2> Launchpad bug 796865 in ubuntu "alt installer asks ??? ??? <go back> <continue>" [Undecided,New] https://launchpad.net/bugs/796865
[02:07] <CIA-29> base-installer: mcasadevall * r955 base-installer/ (5 files in 4 dirs): Added omap4 subarchitecture
[02:07] <NCommand1r> anyone around to review this before I commit on the trunk?
[11:48] <CIA-29> debian-installer: lool * r1459 ubuntu/ (build/config/armel.cfg debian/changelog): config/armel.cfg: order targets alphabetically.
[11:48] <lool> Hmm that's out of order
[11:48] <lool> now I remember why I used not to setup the cia-project name  :-)
[11:50] <cjwatson> lool: care to push, too?
[11:51] <cjwatson> NCommand1r: base-installer omap4> looks fine to me
[11:51] <lool> cjwatson: That's the point, I didn't push yet because I want to test build it
[11:51] <cjwatson> ah
[11:51] <cjwatson> I just don't commit before test-building in such cases :)
[11:52] <lool> it's just that I have a bunch of revisions and don't intend to test-build every single of them
[11:52]  * cjwatson nods
[12:25] <CIA-29> ubiquity: cjwatson * r4753 trunk/debian/ (changelog rules): Don't run xvfb-run under fakeroot, as that confuses the X server.
[12:31] <CIA-29> ubiquity: cjwatson * r4754 trunk/ (debian/changelog tests/run-pyflakes):
[12:31] <CIA-29> ubiquity: Exclude everything under debian/ from tests/run-pyflakes, as otherwise
[12:31] <CIA-29> ubiquity: it's impossible to clean a built tree.
[13:25] <lool> cjwatson: so I'm just realizing that if I want to build d-i images with linaro kernels, they need to be in main, correct?
[13:27] <lool> cjwatson: What would you suggest in this case?  I could think of introducing a debian-installer-universe package, or promoting the packages but marking them as unsupported
[13:32] <CIA-29> ubiquity: cjwatson * r4755 trunk/ (4 files in 2 dirs): Convert to dh_python2.
[13:33] <cjwatson> is there any reason not to just promote those kernels?  we've promoted/demoted kernels fairly freely in the past
[13:34] <cjwatson> I absolutely do not want a debian-installer-universe package; it would be hell to maintain
[13:34] <lool> cjwatson: I certainly wouldn't mind if they got promoted
[13:34] <cjwatson> that's what I'd advise then
[13:34] <lool> cjwatson: Hey, would you mind promoting linux-linaro-omap and linux-linaro-vexpress to main?  :-)
[13:35] <ogra_> doesnt promoting indicate security support ?
[13:35] <cjwatson> well, I think you ought to at least talk to some other MIR folks first ...
[13:40] <lool> I filed https://bugs.launchpad.net/ubuntu/+source/linux-linaro-omap/+bug/797160
[13:40] <ubot2> Ubuntu bug 797160 in linux-linaro-omap "[MIR] Please promote linux-linaro-omap and linux-linaro-vexpress to main" [Undecided,New]
[14:42] <brendand> anyone else getting a wierd error dialog when trying to run the partitioner on todays O image?
[14:42] <brendand> all question marks
[14:42] <CarlFK> yep
[14:43] <CarlFK> i filed a lp bug on it...  looking...
[14:43] <CarlFK> bug 796865
[14:43] <ubot2> Launchpad bug 796865 in ubuntu "alt installer asks ??? ??? <go back> <continue>" [Undecided,New] https://launchpad.net/bugs/796865
[14:45] <brendand> CarlFK - I see the same thing in ubiquity too
[14:45] <cjwatson> yeah, I'll have a look now
[14:45] <cjwatson> it's much easier to debug in d-i
[14:45] <brendand> CarlFK - then it returns to the previous screen if you're formatting the whole disk, or freezes if you're trying to do a side-by-side install
[14:45] <cjwatson> I don't need further details right now
[14:46] <cjwatson> thanks
[15:23] <cjwatson> hmm, I think I'll have to strace this
[15:46] <lool> NCommand1r: when building d-i on a panda, I get a build failure in the omap netboot image with the kernel version I'm running:
[15:46] <lool> http://paste.ubuntu.com/626604/
[15:46] <lool> it seems some tools assumes that there is a module index in the build tree, not sure why
[15:46] <lool> it looks like a depmod bug
[16:02] <lool> ah
[16:02] <lool> 3.0 broke depmod
[16:02] <lool> >-------sscanf(version, "%u.%u.%u", &major, &sub, &minor);
[16:03] <cjwatson> that was fixed in more current module-init-tools
[16:03] <cjwatson> in oneiric
[16:04] <lool> I am looking at 3.13-1ubuntu1, weird
[16:05] <lool> Hmm oddly my chroot is running an old module-init-tools despite an earlier dist-upgrade
[16:06] <lool> cjwatson: thanks
[16:07] <lool> oh and scanf doesn't fail it it can't read all, it will just return 2
[16:07] <lool> a bit scary though
[17:04] <CIA-29> debian-installer: lool * r1458 ubuntu/ (build/config/armel/omap4.cfg debian/changelog):
[17:04] <CIA-29> debian-installer: build/config/armel/omap4.cfg: flip order or netboot and cdrom targets to
[17:04] <CIA-29> debian-installer: match other *.cfg.
[17:04] <CIA-29> debian-installer: lool * r1459 ubuntu/ (build/config/armel.cfg debian/changelog): config/armel.cfg: order targets alphabetically.
[17:04] <CIA-29> debian-installer: lool * r1460 ubuntu/ (5 files in 4 dirs):
[17:04] <CIA-29> debian-installer: * Add vexpress netboot target to armel images, copied from versatile; this
[17:04] <CIA-29> debian-installer:  is useful to run an ARMv7 userspace in QEMU.
[17:04] <CIA-29> debian-installer:  - build/config/armel.cfg: list vexpress.
[17:04] <CIA-29> debian-installer:  - build/config/armel/{vexpress.cfg,vexpress/}: copy from versatile,
[17:04] <CIA-29> debian-installer:  tweaking comments and setting kernel version to
[17:04] <CIA-29> debian-installer:  2.6.38-1002-linaro-vexpress.
[17:04] <CIA-29> debian-installer: lool * r1461 ubuntu/debian/changelog: Fix path build/config/armel.cfg in debian/changelog.
[17:04] <CIA-29> debian-installer: lool * r1462 ubuntu/ (4 files in 3 dirs): Rename vexpress to linaro-vexpress to be consistent with kernel names.
[17:04] <CIA-29> debian-installer: lool * r1463 ubuntu/build/config/armel/linaro-vexpress.cfg: Another vexpress -> linaro-vexpress rename.
[17:04] <CIA-29> debian-installer: lool * r1464 ubuntu/ (5 files in 4 dirs):
[17:04] <CIA-29> debian-installer: * Add linaro-omap netboot target to armel images, copied from versatile;
[17:04] <CIA-29> debian-installer:  this is useful for all OMAP2+ boards supported in this kernel.
[17:04] <CIA-29> debian-installer:  - build/config/armel.cfg: list linaro-omap.
[17:04] <CIA-29> debian-installer:  - build/config/armel/linaro-{omap.cfg,omap/}: copy from versatile,
[17:04] <CIA-29> debian-installer:  tweaking comments and setting kernel version to 2.6.38-1002-linaro-omap.
[17:04] <CIA-29> debian-installer: lool * r1465 ubuntu/ (9 files in 6 dirs):
[17:04] <CIA-29> debian-installer: Drop disabled imx51 bits and corresponding redboot-tools build-dep; this
[17:04] <CIA-29> debian-installer: has been unused for years, allows dropping Debian delta and a build-dep,
[17:04] <CIA-29> debian-installer: demoting this build-dep to universe and can be resurrected from history if
[17:04] <CIA-29> debian-installer: needs be, albeit i.MX51 support would likely use U-Boot nowadays.
[17:04] <CIA-29> debian-installer: lool * r1466 ubuntu/ (build/config/armel.cfg debian/changelog):
[17:04] <CIA-29> debian-installer: Disable linaro-omap and linaro-vexpress flavors for now as the kernel
[17:04] <CIA-29> debian-installer: packages are needed in main first; see LP #797160.
[17:04] <ubot2> Launchpad bug 797160 in linux-linaro-vexpress "[MIR] Please promote linux-linaro-omap and linux-linaro-vexpress to main" [Undecided,New] https://launchpad.net/bugs/797160
[17:05] <lool> cjwatson: build tested and pushed
[17:16] <lool> (but disabled the linaro-omap and linaro-vexpress flavors as the kernels aren't in main)
[18:08] <ogra_> lool, just dont break NCommand1r's bits ... he added omap4 support ofver the weekend afaik
[18:08] <ogra_> ;)
[18:10] <lool> ogra_: I didn't since I test-built that
[18:11] <ogra_> :)
[18:11] <lool> I did change one thing, which is the order of the targets
[18:11] <ogra_> yeah, no worries
[18:11] <lool> and it doesn't build with -j2/-j8 but that's another story
[18:11] <ogra_> -j8 ?
[18:11] <ogra_> on arm HW ?