[08:06] I'm entirely new to the ARM platform, and I got my IGEPv2 yesterday. Now, I want to get Ubuntu up and running. As I understand it, there should be packages ready and available? I found two armel images on the download site. Which one should I use? IGEPv2 is based on Cortex-A8. === rsalveti is now known as rsalveti-away [08:58] I'm using rootstock to generate a new image for my IGEPv2. I'll put it on a microsdhc card and boot from it. Rootstock gives me a .tgz-file. What do I do with it? [10:03] jo-erlend: it's a tarball with the contents of a root filesystem [10:05] jo-erlend: so then it depends where you want your rootfs on your device [10:05] on a microSDHC card. [10:22] that's the device, yes [10:23] in other words, I need to manually create partitions, setup file systems, install grub on the mbr, etc and then simply copy the files over to the respective filesystems? [10:37] if you replace grub with the actual arm bootloader your device needs that sentence is true [10:38] (and you only uncompress the tarball on the root partition, no need to copy stuff around) [10:40] jo-erlend: It depends what your board expects [10:41] jo-erlend: perhaps it has a builtin bootloader in Flash or something === Meizirkki_ is now known as Meizirkki [20:18] Hi, I'm looking at bug 586760 for sponsoring, and I'm wondering if anyone with a working qrmel qemu image can try to build the package from Debian? [20:18] Launchpad bug 586760 in atlas (Ubuntu) "Please merge atlas 3.8.3-22 (universe) from Debian unstable (main) (affects: 2) (heat: 10)" [Undecided,In progress] https://launchpad.net/bugs/586760 [20:18] the FTBFS in armel is the only change left [20:46] fabrice_sp: This might be hardware specific [20:47] Or specifric to the armel buildds rather, for instance a bunch run a very old kernel version [21:22] lool, so you think I can sync the package and check if it blocks the buildds?