[07:36] <smb> morning
[08:24]  * apw looks out on the world ... and does not like what he sees
[08:28] <ppisati> apw: rain?
[08:28] <cking> perhaps apw has looked in a mirror
[08:28] <smb> A pile of washing to do?
[08:28] <smb> cking, Or that. :)
[08:34] <smb> Must have fallen over from shock...
[08:50] <apw> ppisati, cirtainly rain, bah
[08:50] <apw> i was hoping to have a nice lunch on the new patio table, seems that is out
[08:56] <ppisati> guys, did you ever setup a swift node?
[08:57] <ppisati> i wonder if there's some $magic somewhere so i can get a node up&running quickly
[09:00] <apw> ppisati, not me, i would hope if anyone had it would be smb, but I also don't recall him telling us he had :)
[09:00] <smb> What is a swift node? :-P
[09:02] <smb> ppisati, Guessing it might be openstack related, maybe some people over on #ubuntu-server may know
[09:03] <ppisati> smb: actually i already found how to do it
[09:03] <ppisati> http://docs.openstack.org/developer/swift/development_saio.html
[09:04] <ppisati> but i wonder if there is a shorter way...
[09:04] <ppisati> gosh
[09:04] <ppisati> let's start...
[09:07] <smb> apw, If you are recovered from the rain shock and bored, maybe you could have a look at the prepared crash package for saucy which I put on chinstrap?
[09:07] <apw> smb, sure
[09:08] <apw> ppisati, i am sure the answer is juju
[09:08] <smb> ppisati, something high available, distributed and eventually consistent sound like needing pain
[09:09] <ppisati> smb: :(
[09:32] <ppisati> ok so, the official ubuntu doc about swift points back to that page when setting up a node for development or testing
[09:32]  * ppisati gets another mug of coffee and starts the setup...
[09:53] <apw> smb, just so you know, i am fighting the cve scripts right now, so i have not yet looked at your package
[09:53] <smb> apw, ack, no worries
[10:06] <jjohansen> apw: are there some good notes on working with the phablet kernel?
[10:15] <Kano> hi, will you rebase saucy to 3.9.1 or wait for 3.10?
[10:25] <apw> saucy will go 3.10-rcN fairly soon
[10:25] <apw> jjohansen, hmmm, ppisati is the best resource for knowledge, like how to flash a new kernel in from outside etc
[10:26] <apw> (though i should remember more, i have them installed after all)
[10:26] <apw> jjohansen, and why are you awake :)
[10:26] <jjohansen> heh okay I'll bug ppisati some time :)
[10:27] <apw> ppisati should be about now :)
[10:27] <Kano> apw: it would not hurt when you update it to 3.9.1
[10:27] <jjohansen> apw: uhm, still adjusting to jet lag from last week ;)
[10:28] <apw> jjohansen, jet lag, hmmm, fib
[10:28] <jjohansen> hehe :)
[10:32] <jjohansen> apw: so 2 more things, to do with the apparmor backport
[10:32] <jjohansen> 1. we made some changes to the abi late last week and are still doing some work around that so you won't get the backport pull request until then
[10:32] <jjohansen> 2. the backport is currently done as. Patch to bring kernel up to current upstream. new apparmor patches, then patches to backport.
[10:32] <jjohansen> This keeps the changes for the backport from having to ripple through the new patchset, which keeps the change set smaller.
[10:32] <jjohansen> Any issues with this scheme?
[10:33] <apw> sounds reasonable, and as you have to 'maintain' it i think we want whatever is easiest for you
[10:33] <jjohansen> okay thanks
[10:34] <apw> as you are maintainer we are happy to be guided by simplicity for you, particularly on these arm branches
[10:36] <jjohansen> well I am hoping its easier :)
[10:37] <jjohansen> ppisati: so do you have any notes you can point me to for the phablet kernel
[10:37] <ppisati> jjohansen: about installing the kernel&c?
[10:37] <ppisati> jjohansen: https://wiki.ubuntu.com/Kernel/Dev/AndroidKernel
[10:40] <jjohansen> ppisati: okay thanks, I wasn't sure if that was what is recommend for the current phablet images
[12:02]  * henrix -> lunch
[13:19]  * henrix -> back in 20 min
[13:23] <tnt> Does anyone know if the ubuntu kernel patches are available somewhere as a patch stack/list rather than 1 giant diff ?
[13:24] <ogra_> in git on kernel.ubuntu.com ?
[13:25] <tnt> ogra_: ah yes indeed thanks. I was looking in the package sources and on packages.ubuntu.com ...
[13:25] <tnt> thanks.
[14:27] <rtg_> apw, any info on mako and the gcc bug ? I'm planning to rebuild manta today.
[14:29]  * ogra_ whispers maguro
[14:30] <apw> rtg_, nothing that has come to my ear as yet.  ppisati are you able to test the 3.9 saucy kernel on an arm board?  to confirm -generic is workign there?
[14:31] <apw> rtg_, the next step was as above to confirm if the -generic was bust so we knew where to target
[14:31] <rtg_> apw, ack
[14:31]  * rtg_ hears ogra whispering
[14:35]  * bjf nudges apw to read his email from ppisati
[14:50] <zequence> apw: So, if I were to maintain -lowlatency also for the development release this time, how would that work?
[14:56] <zequence> 48
[15:37] <apw> zequence, a good question, i'll have a think about it and see how we might swing it
[17:15] <apw> bjf, sconklin, the matrix is mia right now as i foolishly added linux-lts-raring to it, and ... well ... it is missing :)  working with security on it now
[17:15] <sconklin> apw: ack
[17:16] <bjf> apw, while they are fixing it, they should go ahead and remove hardy and oneiric
[17:16] <apw> bjf, that they have on their list for tommorrow
[17:17] <apw> bjf, though i have just dropped them from teh auto-triager just in case it steps on their shlongs for them
[17:17] <apw> sconklin, bjf, did we add lts-raring to the ABIPackages page?
[17:18] <apw> actually it seems both lts-quantal and lts-raring are missing ... oops
[17:44] <rtg_> cking, jsalisbury_: need to reboot gomeisa for kernel and SSL update
[17:45] <jsalisbury_> rtg_, ack
[17:45] <cking> ack
[17:45]  * cking calls it a day :-)
[17:47]  * smb too
[17:51] <jsalisbury_> rtg_, ok to use gomeisa again?
[17:54] <rtg_> jsalisbury_, rebooting tangerine...
[17:54] <jsalisbury_> rtg_, ack
[17:58] <rtg_> jsalisbury_, you are good to go on gomeisa
[18:08] <apw> sconklin, i am fiddling with the autotriager so don't review and accept its results for the moment
[18:10] <sconklin> apw: ack. I ran it early today (my time) and won't touch it again until I hear from you
[23:40] <hallyn_> will there be a kernel support cortex A15?
[23:40] <hallyn_> (in saucy)
[23:41] <rtg_> hallyn_, what platform names have an A15 ? 
[23:42] <hallyn_> arndale
[23:43] <hallyn_> or exynos 5 if that means more
[23:43] <rtg_> hallyn_, so far these are the device tree based platforms that I have in saucy: imx6q-sabrelite.dtb omap3-beagle-xm.dtb omap4-panda.dtb omap4-panda-es.dtb highbank.dtb
[23:44] <hallyn_> dannf: ^ the arndale system you gave rbasak, would it be able to boot one of those (and have a15 kvm support)?
[23:45] <hallyn_> nm, rbasak says "no you fool"
[23:45] <hallyn_> rtg_: thanks
[23:45] <rtg_> hallyn_, I see device tree support for some xynos platforms, but not for arndale
[23:45] <rtg_> exynos*
[23:45] <rbasak> rtg_: my question was really: do we have anything on the roadmap which involves support for an A15 based system in Saucy?
[23:46] <rbasak> (or any non A15 but virt-supporting system)
[23:46] <rbasak> I suspect the answer may well be no - I just wanted to check.
[23:46] <rtg_> rbasak, if it has DTB support, then we kind of get it for free. otherwise I either have to create a flavour or a separate tree.
[23:48] <rbasak> rtg_: OK, but your config wouldn't have driver support unless all driver requirements happen to be covered by other platform support, right?
[23:48] <rtg_> rbasak, if exynos is A15, then we _could_ enable one or more of these platforms:
[23:48] <rtg_> arch/arm/boot/dts/exynos5250-snow.dts
[23:48] <rtg_> arch/arm/boot/dts/exynos5250-smdk5250.dts
[23:48] <rtg_> arch/arm/boot/dts/exynos4210-trats.dts
[23:48] <rtg_> arch/arm/boot/dts/exynos4210-origen.dts
[23:48] <rtg_> arch/arm/boot/dts/exynos4210-smdkv310.dts
[23:48] <rtg_> arch/arm/boot/dts/exynos4412-smdk4412.dts
[23:48] <rbasak> I think the hardware I have access to all has DTB support. But not full driver support
[23:48] <rtg_> arch/arm/boot/dts/exynos5440-ssdk5440.dts
[23:48]  * rbasak is typing this from a exynos5250-snow.dts machine
[23:49] <rtg_> rbasak, then perhaps we can enable those drivers
[23:49] <rbasak> Would that create much work?
[23:49] <rbasak> ie. how much inconvenience for you?
[23:49] <rtg_> rbasak, not really, as long as you know what config options are required.
[23:50] <rbasak> OK. Thanks!
[23:50] <dannf> hallyn_: no you fool! :)
[23:57]  * rbasak didn't actually say that. hallyn paraphrased.
[23:57]  * rbasak is far too polite for that :)