[01:14] <infinity> Counting is hard.  Why did we go from -9.16 to -11.17? :P
[04:07] <bjf> infinity, we're using a random number generator now
[06:46] <tjaalton> apw: mind testing a new -intel version on your gen3? won't fix the slow dash, but I'd like to hear if it works otherwise fine
[07:15] <ppisati> moin
[07:25] <apw> tjaalton, sure point me at it
[07:25] <apw> ppisati, moin
[07:25] <smb> morning
[07:25] <apw> smb, moin
[07:25]  * smb lazily waves
[07:26] <smb> and does not mind putting words in the wrong order
[07:30] <tjaalton> apw: pushed it to the staging ppa, I'll give the link once it's built
[07:33] <apw> tjaalton, great, and ... i didn't see anything from Sarvatt yesterday on that test version for that machine, which was implodoing X when going to maps.google.com
[07:35] <apw> (unless i missed it)
[07:37] <smb> apw, Ok, so (as you undoubtedly already did) I checked the no-change rebuild of libvirt with the merged xen-4.3 and at least found a libxl connection driver which at least proves the headers and lib from libxen(-dev) are as expected.
[07:38] <apw> smb, heh no it is far too early
[07:38] <smb> Oh yeah not today but yesterday. :)
[07:40] <apw> smb, so on the rdepends, it seems everything other than opennebula built, but i see that hasn't been built since like quantal, so i was going to try and rebuild it in the old place if you didn't alreayd know it is borked either way
[07:40] <smb> apw, Hm, opennebula.... where did I read that recently...?
[07:42] <tjaalton> apw: hmm remind me of that one? the mesa revert causes that?
[07:44] <apw> tjaalton, yeah the version you guys did for me which reverted something for gen3, this does amke it use 1.4 generally but starting chrome and navigating to 1.4 just implodes
[07:45] <tjaalton> hmm ok
[07:50] <tjaalton> apw: anyway, the new -intel is at https://launchpad.net/~canonical-x/+archive/x-staging/+build/5068918
[07:51] <apw> tjaalton, ok will try and get that tested shortly
[07:52] <tjaalton> great, thanks
[07:52] <tjaalton> ah I see bug 1233540 now
[07:52] <ubot2> Launchpad bug 1233540 in xorg-server (Ubuntu) "X server core dumped seemingly when starting chromium" [High,Incomplete] https://launchpad.net/bugs/1233540
[08:35] <apw> zequence-work, yo ... am just doing a lowlatency rebase to get you up to the latest in time for kernel freeze
[09:25] <zequence-work> apw: Ah, right
[09:25] <zequence-work> apw: Is there a orig file for it?
[09:34] <apw> zequence-work, a good point i will make one of those at the same time
[09:34] <apw> zequence-work, i am just fixing something i broke :)
[09:41] <apw> BenC, i am doing some maintenance on linux-ppc, and propose to rebase it for release for you at the saem time
[09:44] <zequence-work> Seems the dentist took away a piece of my brain, while removing my wisdom tooth today. All that appears in my head now is Bacardi.
[09:44] <apw> zequence-work, heh ... nice ... i say go with the bacardi option myself
[09:52] <zequence-work> apw: Yep. Since I can't see any other options right now..
[09:52] <zequence-work> So, it's not really an option
[09:52] <apw> that is a fiar point, just go with it
[10:18] <apw>  /b 9
[10:18] <apw> smb, so did you say you had had good test results with libvirt et al on your kit with new xen ?
[10:30] <smb> Sorry got people and my landlord look at the flat
[10:30] <smb> Err yes, a very quick test but yes
[10:42] <apw> smb, ok ... in the queue, infinity is doing the do
[10:42] <smb> apw, cool, thanks
[10:42] <apw> now all you have to do is the same for precise :)
[10:48] <Kaloz> apw: feel free to close #1197451
[10:49] <smb> apw, precise?
[10:51] <apw> Kaloz, i assume you are talking saucy here
[10:51] <apw> (ie that boots saucy just fine)
[10:56] <Kaloz> apw: yup, since the resync with 3.11.2
[10:58] <apw> Kaloz, sweet closed off for saucy thanks
[11:00] <apw> henrix, i've acked and applied that perl patch for you
[11:00] <apw> dunno if you are respinning or just pulling that one fix onto master ... do as you feel fit obviosly
[11:01] <henrix> apw: thanks. bjf asked me to respin ;)
[11:01] <apw> henrix, either works, go for it :)
[11:23] <infinity> smb: Out of curiosity, did you check this new Xen on an i386 userspace as well?  There were some changes in i386/defines whose effect I couldn't quite divine.
[11:24] <smb> infinity, There where but I don't think we use that file at all
[11:25] <smb> infinity, At least the package still produces a hypervisor amd64 for i386
[11:25] <infinity> smb: Yeah, I checked that in your PPA before I accepted. :P
[11:25] <smb> infinity, Ba just a test
[11:33] <smb> infinity, But yeah, as far as I read that it looked like that defines file would only have an effect when creating the control file from other files and that step only is done by debian. In fact they guard changes there with md5sums and the thing that runs then fails always because we have no special kernel helper thingy
[11:34] <smb> (not that I could not fake a md5sum but decided I don't do that if not really needed)
[11:37] <infinity> smb: Fair enough.
[11:42] <tjaalton> apw: looks like your xserver crash should be fixed by the latest update
[11:43] <apw> tjaalton, ta, sorry not had a chance to test that yet
[11:43] <tjaalton> apw: that's xserver update, so do the daily dance before testing chromium :)
[11:44] <apw> tjaalton, heh
[11:59] <Marex> apw: hey, any news on https://bugs.launchpad.net/ubuntu/+source/git/+bug/1228148 ?
[11:59] <ubot2> Launchpad bug 1228148 in git (Ubuntu) "git clone -q ends with "early EOF" error on large repositories" [Undecided,Confirmed]
[12:36] <apw> Marex, we asked for an update for that machine to bring it somewhere more fixable, that is in progress as far as i know
[12:38] <apw> Marex, though mid release run up is not the best time to try and get changes
[12:38] <BenC> apw: Works for me, thanks
[12:42] <Marex> apw: it's quite serious breakage tho, not being able to clone from the repo ...
[12:42] <Marex> apw: thanks for looking into it though
[12:45] <apw> Marex, and only affects you if you don't use -q, so not hightly impacting
[12:46] <Marex> apw: OK, I will remember ubuntu as not fixing severe bugs, no problem
[12:47] <apw> Marex, it isn't severe because it doens't affect the majority case common use model
[12:48] <apw> yes it pisses you off, and it isn't at the top of my todo list because we 
[12:48] <apw> oh have a release to do, and kernel freeze on friday, silly me
[12:48] <apw> and the people who need to do the upgrade are busy, oh prepping our world
[12:49] <apw> to be pounded shitless by a ... release
[12:49] <Marex> it'd be nice if one would then be able to git clone the stuff you release ... but oh, yeah, roll out stuff, dont care if it's broken
[12:49] <apw> Marex but one can clone it, as long as you don't use -q
[12:50] <apw> it is not unavailable, it is unavable for one use case, which you can even fix by
[12:50] <Marex> that's wonderful ... as long as you don't use -q
[12:50] <apw> git clone FOO
[12:50] <apw> and then using the tool against a local FOO so you anr't even stopped from working
[12:50] <apw> and therefore it is not my highesst priority for the very limited hours i have in every dau
[12:50] <apw> befopre release
[12:51] <apw> tell me where my analysis of the issue is wrong
[12:53] <Marex> apw: I keep wondering why you dont postpone the release ... do you focus on the actual deadline or on quality ?
[12:53] <apw> postpone the release because we have a bug in a version of git from a previous release?
[12:54] <Marex> apw: is the current release not buggy too ?
[12:54] <Marex> apw: the patches were picked into master 2 weeks ago or so
[12:54] <apw> quite possibly, but holding a release for a problem that only affects a neish use case
[12:55] <apw> would make no sense what so ever, clearly it is not a common use case or someone would have found the issue much much sooner
[12:55] <apw> there are probabally a 1000 such issues in any release, if you held to fix them all you would literally never release
[12:56] <Marex> apw: the issue was known since like 2009 unfortunatelly, it was reported but noone got around to push it
[12:57] <apw> right but as it doens't affect the common case, us who use the thing didn't notice
[12:57] <apw> and its is not like over half my commands every day are git ones, and it literally does not happen
[12:57] <apw> now, that isn't to say it isn't worth fixing, it is
[12:58] <apw> and once i have the machine on a level where it can be fixed i will be fixing it
[13:00] <Marex> apw: can you give some ETA at least ?
[13:01] <apw> i would think we will get the machine upgraded within a couple of weeks
[13:05] <Marex> apw: ok, thanks
[13:15] <rtg> jjohansen, henrix, ppisati: rebooting tangerine for kernel update
[13:15] <henrix> rtg: ack
[13:15] <jjohansen> rtg: ack
[13:16] <ppisati> rtg: i guess you rebooted tangerine
[13:16] <rtg> I guess
[13:16] <ppisati> :)
[13:17] <rtg> ppisati, things looked pretty quiet. did I catch you in the middle of something ?
[13:17] <ppisati> rtg: no, i was done
[13:35]  * henrix -> late lunch
[15:39] <caribou> what's the trick to build a kernel source package ? do_source_package=true fakeroot debian/rules binary-generic doesn't seem to work
[15:45] <infinity> caribou: binary-indep might work better.
[15:45] <apw> jsalisbury, this hid revert, wasn't there a bluetooth component, or has that been eliminated
[15:49] <apw> caribou, do you really want a kernel -source package ?
[15:49] <apw> caribou, rather than a .dsc source pacakge ?
[15:50] <caribou> apw: I just want to be sure that the patch that I added is *indeed* in the package I built
[15:59] <caribou> infinity: ok, will try that
[16:21] <petn-randall> kees: Thanks for the info. Then I'll set an ACL to allow the user nagios to read it for the check.
[17:03] <alex116> im writing a kernel module for the power management and I set up an irq to listen on a gpio pin for a toggle and I get the handler to fire but it only fires once, then it wont fire again. Do I have to set the irq up again if I want it to listen again?
[17:52]  * henrix -> EOD
[19:52] <rtg> sconklin, pushed patches to precise LBM. now builds against 3.2.0-55. I'll let you finish the packaging.
[19:53] <sconklin> rtg: ack, thanks! I'll spin it now
[20:13] <sconklin> rtg: uploaded
[20:13] <rtg> sconklin, ack
[22:46]  * rtg -> EOD