=== rsalveti_ is now known as rsalveti === yp is now known as ypwong === jjardon_ is now known as jjardon === oCrazyLemn is now known as CrazyLemon === ogra_ is now known as 21WAAGN94 === siel_ is now known as siel === qengho is now known as CardinalFang === CardinalFang is now known as qengho === qengho_ is now known as CardinalFang === tsimpson is now known as lubotu2 === lubotu2 is now known as tsimpson === tsimpson is now known as taimpson === rsalveti_ is now known as rsalveti === strycore_ is now known as strycore === taimpson is now known as tsimpson === infinity_ is now known as infinity === dobey_ is now known as dobey === m_conley is now known as m_conley_away === m_conley_away is now known as m_conley [04:02] no straight-up ubuntu utopic alpha-1? [04:13] no, Ubuntu itself doesn't participate in the opt-in milestones [04:17] ya... just read about this on omgubuntu [04:17] how long has that gone on for? [04:17] * desrt remembers downloading alphas back in the day [04:18] I can't remember exactly when that started, at least a couple of years [04:19] * desrt does as always: upgrade from previous release [04:20] Ubuntu dropped those milestones when doing the whole automated CI testing, flavours preferred to continue relying on manual testing, so we ended up with those being opt-in and everyone getting confused because the set of flavours participating changes all the time :) [04:20] (also, the Ubuntu cloud images are participating in those milestones for added confusion :)) [04:20] stgraber: on another topic: do you have a recommended arm setup? [04:21] (for qemu) [04:23] if all you want to do is some builds and minimal testing, a foreign debootstrap + qemu-user-static usually works reasonably well. Alternatively you can use LXC which will do something like that but let you start a container. Or you can run a full system with qemu-system but that's usually pretty slow and unnecessary. [04:23] huh. i was actually leaning towards the full-system approach [04:24] qemu-user-static seems like it would be slightly flaky [04:24] qemu-user-static isn't too bad, that's what we use for all the PPA buildds and the only obvious problem we hit are when something we run wants to call ptrace or do something over netlink (there are a couple more corner cases but that's about it) [04:26] I've never tried booting Ubuntu with qemu-system for armhf but I know that qemu now does devicetree so things should pretty much just work with a generic kernel + initrd (you'll probably need to use -kernel and -initrd as I doubt qemu simulates any kind of firmware/bootloader) [04:26] I've got plenty of reasonably fast armhf hardware around here and remote access to arm64 systems when I need something fast, so I've never really had a reason to look into qemu-system for armhf [04:27] what do you use for hardware? [04:27] my main armhf build box here is a wandboard-quad. I added d-i and flash-kernel support for it back in trusty and it works with a generic kernel. [04:29] looks nice [04:30] yeah, it met my criteria at the time which was gigabit, SATA, quadcore, >= 2GB of RAM [04:31] it's roughly equivalent to what we use for the LP buildds except it only has 2GB of regular RAM instead of 4GB of ECC RAM [04:31] who did you order from (and did you do it inside of canada)? [04:32] I think I got mine from future electronics which is based in Quebec, otherwise Digikey Canada also has it in stock I think [04:32] ya... digikey is marking it up quite a bit [04:33] oh, just one thing, if you need working graphics you may need to figure out how to get that working by yourself as I've never bothered (I use mine as a buildd, so serial console + ssh is fine) [04:34] not too likely to care about that... [04:34] yeah, apparently nobody does as I know some other Ubuntu folks using our d-i image and none of them complained about the lack of HDMI support :) === m_conley is now known as m_conley_away [04:41] stgraber: thanks for the infos [04:41] -> bed time === Ursinha-afk is now known as Ursinha [06:45] stgraber, curious, what testing do you guys run on the Ubuntu ISO's? we have manual testing because we have no auto testing [06:46] is it just the jenkins tests? or you have specific ISO testing? [07:10] darkxst, Not sure if they're finished, but autopilot tests exist [07:10] Noskcaj, autopilot does not work on gnome-shell, it doesnt use gtk+ [07:11] Yeah, it's for ubiquity [07:12] I was under the impression that no tests run on the flavour ISO's [07:13] but that is probably a cjwatson question === lan3y is now known as Laney === oCrazyLemn is now known as CrazyLemon === dkessel__ is now known as dkessel_ === jjardon_ is now known as jjardon === fginther` is now known as fginther === m_conley_away is now known as m_conley === m_conley is now known as m_conley_away [22:20] Laney: Yeah agreed.