[00:25] <rsalveti> sveinse: did you try with latest qemu-linaro from https://launchpad.net/~linaro-maintainers/+archive/tools?
[00:26] <sveinse> rsalveti: Yes. I just commented it on the bug. It works using the newer backported qemu
[00:26] <rsalveti> sveinse: great, so at least you have a working version
[00:27] <sveinse> Yes. This was a serious blocker for us, since the build server is running i386 natty...
[00:29] <sveinse> rsalveti: Did you see my question the other day? For some reason rootstock adds the fuse group, but without any explanation to why. Do you recall if it was a particular reason?
[00:31] <rsalveti> sveinse: hm, don't remember the reason why it was added
[00:31] <rsalveti> sveinse: any issues with it?
[00:34] <sveinse> rsalveti: Nope. Just ooi, so don't bother. In fact, I'm not using rootstock any more. I'm using qemu-debootstrap instead. But when changing over from rootstock to deboostrap, I had to ensure my script had similar setup to rootstock, and that's when I discovered the fuse setting.
[00:34] <rsalveti> sveinse: I'd recommend you to use live-build if you can
[00:35] <rsalveti> I know there's support for qemu at the latest live-build version
[00:35] <rsalveti> and you can hook scripts and etc
[00:40] <sveinse> rsalveti: I'll check it out. However we are satisfied with way debootstrap works. I.e. run debootstrap and then apt-get install everything under chroot qemu emulation. The only risk is the qemu armel emulation during dpkg install when building the rootfs on an intel host. But it has proved to work successfully on a larger set of prototypes.
[00:40] <rsalveti> sveinse: yeah, great
[00:40] <rsalveti> and it seems for precise mono, tomboy and banshee was removed from desktop
[00:41] <rsalveti> then no mono issue when cross debootstraping the desktop anymore :-)
[00:42] <sveinse> rsalveti: I'm doing it in two steps: I'm debootstrapping to minimal, and then include the rest under chroot. And our app is not using desktop, its Qt QWS, so no X11.
[00:42] <rsalveti> cool, then you can build it quickly
[00:43] <sveinse> But one of the developers are talking about adding mono. Should I expect issues with installing it under chroot?
[00:46] <rsalveti> sveinse: yup, there are quite a few issues when installing mono packages
[00:47] <rsalveti> sveinse: bug 530000
[00:47] <ubot2> Launchpad bug 530000 in qemu-kvm "mono assembly installation under qemu-arm-static hangs" [Medium,Won't fix] https://launchpad.net/bugs/530000
[00:47] <sveinse> rsalveti: good to know. Does this also include native installation of mono on armel?
[00:47] <rsalveti> nops, just under qemu iirc
[00:50] <sveinse> rsalveti: One thing I've been considering, is to only run dpkg unpack in image creation, and wait to do configure until the customer boots the product. I suppose this is the same as running the second stage natively
[00:50] <rsalveti> sveinse: ye
[00:50] <rsalveti> yes
[00:50] <rsalveti> depending on the amount of packages you have, it's quite a sane solution
[00:51] <rsalveti> and you don't rely on qemu anymore
[00:51] <sveinse> Except that "See I bought this product. Now I just have to wait 20 minutes for it to start for the first time"
[00:53] <rsalveti> well, it all depends on the amount of packages you have
[00:54] <rsalveti> and for sure some packages could be changed to avoid doing stuff at the post inst
[00:55] <sveinse> rsalveti: Would it be possible to debootstrap the first stage on intel, and then move the root into a chroot on a armel native and run the second stage using a chroot there?
[00:55] <sveinse> E.g. does that resolve the mono issues, right?
[00:55] <rsalveti> sveinse: yes
[00:59] <sveinse> rsalveti: BTW I don't know if there is much activity on rootstock, but during an installation of a package I discovered that it can be smart to dpkg-divert /sbin/start since some packages tries to start the services from their postinst's.
[01:00] <rsalveti> yeah, this would help avoiding starting services while running with qemu
[01:01] <rsalveti> I need to spend some time on it, to at least fix some of the bugs
[01:01] <rsalveti> but we're kind of moving to live-build now
[01:01] <sveinse> yup, just a suggestion
[01:02] <rsalveti> but yeah, useful, thanks anyway :-)