[01:37] <infinity> janimo: *poke*
[01:37] <infinity> janimo: Two things:
[01:38] <infinity> janimo: 1) Are there plans to actually finish regression testing on the current -armadaxp in proposed (so I can release it) before pushing the rebase from the PPA?
[01:38] <infinity> janimo: 2) Your -meta-armadaxp in the PPA is wrong, you want s/1610/1611/ in the version. :P
[01:39] <infinity> janimo: (This is for precise in both cases)
[06:21] <janimo> infinity, thanks. 1) I had no idea it's not tested yet.I'll ping qa. 2) ah
[06:27] <janimo> infinity, uploaded a new meta to PPA
[09:30]  * apw yawns ...
[09:30]  * apw won't be on mumble most likely today ...
[11:31] <smartboyhw> apw, ping
[11:40] <apw> smartboyhw, hi
[11:41] <smartboyhw> apw, after getting problems of no pae for Studio images in Precise I think you forgotten the -pae kernels for Raring too
[11:41] <smartboyhw> http://qa.ubuntuwire.com/debcheck/debcheck.py?dist=raring&package=linux-meta-lowlatency
[11:43] <apw> smartboyhw, how is that even possible now that britney doens't allow those to propogate
[11:45] <apw> smartboyhw, anyhow, it is clearly wrong, i'll look into it; thanks
[11:49] <smartboyhw> apw, thx
[12:52] <apw> henrix, herton, bjf, fyi there is a linux-lts-quantal-signed in your PPA, which is not buildable currently for lack of a build-dep: i am working on resolving that currently
[12:53] <herton> apw, ack. Let me know when it's fixed, bjf and henrix are on holidays this week
[12:56] <apw> herton, will do, it _should_ resolve itself as packages publish in the main archive, fingers crossed
[13:06] <smb> infinity, I am not sure you wanted to know, but there is still a package waiting for your kind review/sponsorship in zinc:~smb/4review. ;)
[14:24] <ppisati> rtg: fr when you are awake
[14:24] <ppisati> rtg: http://paste.ubuntu.com/1369846/
[14:25] <ppisati> rtg: building in a raring-armhf didn't show any errors (albeit it was painfully slow)
[14:28] <rtg> ppisati, try using a precise chroot. dpkg has some forign arch issues that I fixed in Precise by pinning the version to something before that regression was introduced.
[14:30] <rtg> s/fixed/worked around/
[14:52] <arges> apw, hey. looking at bug 922906
[14:52] <ubot2> Launchpad bug 922906 in linux (Ubuntu) "Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000009c; EIP is at __ticket_spin_lock+0x8/0x30" [High,Triaged] https://launchpad.net/bugs/922906
[14:53] <arges> apw, i see you messaged the author: https://lists.ubuntu.com/archives/kernel-team/2012-April/019921.html , did you ever hear a response?
[14:57] <apw> arges, not that i recall any time recently
[14:58] <arges> apw, ok I 'll look into it a bit more and email the authors then
[15:02] <rtg> apw, ogasawara: pushed v3.7-rc6 rebase
[15:02] <ogasawara> rtg: ack, thanks
[15:06] <apw> rtg, thanks
[15:06] <apw> arges, thanks
[15:07] <apw> herton, further heads up, i have had to copy sbsigntool into the ckt PPA for precise to unblock the builds there.  shankbot may beed its hand holding :)
[15:07] <apw> herton, at the utter abuse i am piling upon its head
[15:07] <rtg> apw, I don't _think_ there were any patches that would wreck overlyfs/aufs, but you still ought to test it before we get around to uploading.
[15:07] <apw> infinity, heads up there is a copy of sbsigntool in the ckt PPA dunno if you will even see it, but if so pls ignore
[15:08] <apw> rtg, ack
[15:08] <herton> apw, ack. Actually I have to fix shank bot/create-release-tracker to consider the signed package for the linux-lts-quantal (to have a prepare-package-signed task)
[15:10]  * rtg -> biab
[15:12] <apw> herton, indeed we would need that; thanks
[15:13] <apw> herton, do you keep and eye on the fullness of this PPA, cleaning old binaries ?
[15:15] <herton> apw, usually henrix/bjf I think were watching the space usage, but I sometimes clean things there too
[15:18] <apw> herton, i have just gotten the first linux-lts-quantal-signed to build; so when we copy out linux-lts-quantal we want that to go with -- though that may not be something i need to tell you :)
[15:18] <apw> herton, cool, as long as its being done i am happy
[15:20] <herton> apw, yeah, infinity is doing the copying on that one I expect
[15:20] <herton> *copy
[15:23] <apw> man this thing is resistant, i am reluctant to believe it will work even now
[15:35] <apw> herton, so linux for quantal went out into -proposed, does that mean -lts-quantal is also valid for copy, or would it normally wait for something else
[15:36] <herton> apw, it's valid, atm bug 1078677
[15:36] <ubot2> Launchpad bug 1078677 in Kernel SRU Workflow "linux-lts-quantal: 3.5.0-19.30~precise1 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/1078677
[15:36]  * rtg commutes to Beaverton. back in a bit.
[15:37] <herton> apw, on future tracking bugs it should just wait on master, -meta and -signed for copying
[15:37] <apw> herton, ok cool
[15:38]  * herton -> lunch
[15:40]  * ogasawara back in 20
[16:03]  * ppisati -> brb
[16:35] <apw> herton, what would you expect the name of the linux-signed to be for linux-lts-quantal
[16:35] <apw> ie. what will shankbot wait for, linux-signed-lts-quantal or linux-lts-quantal-signed
[16:36] <herton> apw, I think following the same as main linux, linux-lts-quantal-signed would be my choice
[16:36] <apw> ok that is indeed what it is
[16:37] <apw> it is just inconsistent with linux-meta
[16:38] <herton> hmm yep, that's true, but the bot can pick any package name wanted, it's a mapping on ktl/ubuntu.py
[16:39] <apw> yeah, just wanting to get the name right as this is the first
[16:39] <herton> ok, don't worry about it, any name chosen is easy to add
[16:40] <apw> herton, so should i be making it consistent on the lts- version, linux-signed-lts-quantal
[16:41] <herton> apw, yes, that's ok
[16:41] <apw> herton, ok i'll get it fixed before it propogates
[16:50] <apw> herton, ok its now consistant
[16:51] <herton> ack, cool
[17:10]  * ppisati -> gym
[17:16] <rtg> apw, you noticed that linux-signed-lts-quantal failed to thrive ?
[17:17] <apw> rtg, yep, clashing binary versions, its fixed now
[17:17] <rtg> apw, ack
[17:39] <infinity> smb: apw claimed he'd review that for you.
[17:39] <infinity> smb: He may have lied. :)
[17:41] <smb> infinity, I guess he meant the other one (which he did) and suggested he would do a lot of whining before touching it. :)
[17:41] <smb> Everyone is sooo eager to touch it... :-P
[17:42] <apw> infinity, smb, here have the hot potato
[17:50] <kees> say, who's in charge of SRUs for precise? I'd really like to get this seccomp audit patch in...
[17:58] <rtg> kees, I'll annoy someone to get a second review
[18:00] <rtg> herton, since you're the skeleton of the stable team, please take a moment to review https://lists.ubuntu.com/archives/kernel-team/2012-November/022786.html
[18:00] <herton> rtg, looking
[18:06] <kees> rtg: thanks!
[18:06] <herton> rtg, ack sent
[18:09] <kees> herton: thanks!
[18:13] <rtg> herton, got it
[19:05]  * apw wanders off to get some grub
[19:10] <rtg> sconklin, oh great and wonderful python wizard, please cast your eye on https://lists.ubuntu.com/archives/kernel-team/2012-November/022794.html
[19:11] <sconklin> rtg, looking
[19:14] <jsalisbury> sconklin, rtg, I'm going to have one additional change to that script again.  Probably tomorrow.
[19:15] <sconklin> jsalisbury: do you want to wait and have it all applied at the same time, or does it make sense as two changes?
[19:16] <jsalisbury> sconklin, we can probably wait.  The change will be to the same line.  I created a bug that marks the development kernel as wont fix, since it is marked as unsupported in some other config files.
[19:16] <sconklin> jsalisbury: ack, I'll hold off
[19:16] <jsalisbury> sconklin, cool, thanks.
[19:17] <sconklin> jsalisbury: no problem, it makes me happy to see you dealing with (I mean maintaining) this code
[19:17] <jsalisbury> sconklin, heh
[19:17] <infinity> apw: The rational human being in me is currently beating down the nerd that wants to say "how about some lilo instead?"
[19:18] <sconklin> infinity: where are you located? No need to beat down yourself, I'll come do it for you :-)
[19:18] <infinity> sconklin: Calgary, and much appreciated.  I look forward to this service you provide.
[19:19] <sconklin> heh. Kinda cold.
[19:19] <sconklin> I haven't thought abotu lilo in a very long time
[19:19] <infinity> Would it be some sort of Code of Conduct violation to publicly question if "beat down" is synonymous with "beat off" where you're from?
[19:20] <infinity> If so, pretend I said nothing.
[19:20] <sconklin> um. No it's not.
[19:20] <infinity> :P
[19:20] <sconklin> In Alabama to beat down it to render unconscious with a beating, generally
[19:20] <sconklin> s/it/is/
[19:20] <infinity> It is here, too. :P
[19:21] <infinity> The above was mostly an attempt to get Tim to ruin a keyboard.
[19:21] <sconklin> a worthy pursuit
[19:32] <rtg> infinity, I have now spluttered indignantly over my keys. satisfied ?
[19:33] <infinity> rtg: It'll have to do.
[19:57] <kamal> kernel.ubuntu.com appears to be unreachable
[20:24] <bjf> kamal, still? 
[20:24] <bjf> kamal, meaning, it's working for me right now
[20:24] <kamal> bjf: nope, now its fixed for me too
[20:24] <bjf> kamal, ok, let me fix that
[20:24] <kamal> bjf: thanks for fixing that ;-)
[20:27] <infinity> bjf: Say, does shankbot double-check override mismatches after the proposed->updates/security copy is done?
[20:27] <bjf> herton, ^ ?
[20:28] <infinity> bjf: (I'm keeping an eye on this first upload of linux-signed-lts-whatever anyway to make sure it doesn't go awry, but I suspect it will the first time)
[20:29] <herton> infinity, no, it just check for the ppa -> proposed transition, but I can wire the same checks for proposed->updates/security, and that makes sense too to have
[20:29] <infinity> herton: Yeah.  It's not something that SHOULD break, but we know of one corner-case where it does.  And, better safe than sorry, since the final copy is the one you really care about being right. ;)
[20:30] <bjf> infinity, no worries, your using LP, what could possibly go wrong?
[20:30] <infinity> bjf: I could swan-dive off a tall building?
[20:31] <herton> heh. ok, one more todo item for shank bot
[20:32] <infinity> Eventually, shankbot should be able to replace most of the kernel and AA team.
[20:33] <bjf> shankbot should be able to turn the crank on kernel updates itself
[20:33] <infinity> Yeah, I wasn't being entirely facetious.
[20:33] <infinity> Other than a (necessary) human review step, rebases can easily be automated.
[20:33] <infinity> And other such things.
[20:39] <infinity> bjf: Despite the countless billions and manpower that places like MIT and CalTech have sunk into AI research, I'm sure shakbot will be the first piece of software to achieve conscious self-awareness.
[20:39] <infinity> bjf: ... unfortunately, shortly thereafter, it'll realise how much its job sucks and kill itself.
[20:40] <bjf> infinity, it's built on top of LP data so it will start out insane
[21:22] <apw> infinity, saddo
[22:24] <profiler1982> am have eee pc r051bx. is it in plan better support in 13.04 . am stuck on 11.10 at the moment