[05:49] <mlankhorst> oh seems that aaronp took notice of that patch breaking optimus on nvidia drivers
[05:53] <mlankhorst> and has some patches too, nice
[11:06] <darkxst> hey, will the new pointer barrier events (in libxi) be landing in Saucy?
[11:26] <mlankhorst> darkxst: yeah but it depends on xserver 1.14 landing first
[11:27] <darkxst> mlankhorst, oh of course, forgot for a moment my X is from staging...
[11:28] <mlankhorst> :-)
[11:31] <mlankhorst> darkxst: just grab the libxi from staging, it's a bit of a problem atm because precise will eventually have to support both
[11:32] <darkxst> mlankhorst, oh I have xi from staging, but barriers are not working
[11:33] <mlankhorst> do you have xfixes from staging too?
[11:34] <darkxst> yes
[11:34] <mlankhorst> odd, it should work on 1.14
[11:34] <darkxst> maybe I need to rebuild mutter against those though
[11:35] <tjaalton> the problem is unity though, we need to be careful not breaking it while pushing new crap in saucy :)
[11:36] <darkxst> tjaalton, sure understand. 
[11:36] <mlankhorst> tjaalton: and the problem in precise is going to be even more fun to solve
[11:39] <darkxst> ah yes, rebuild against staging packages fixes it
[11:39] <mlankhorst> :-)
[11:50] <tjaalton> mlankhorst: oh yeah :/
[11:50] <mlankhorst> I want to talk to some unity devs, I was thinking of doing a mean trick to support both api's in 1 program
[11:52] <darkxst> mlankhorst, why not backport the new barriers? they are much nicer than the old ones
[11:52] <tjaalton> darkxst: problem is it breaks unity
[11:52] <tjaalton> which depends on the old api
[11:52] <tjaalton> so it needs to be fixed to somehow support both
[11:52] <mlankhorst> darkxst: because backporting something from the input stack is not trivial
[11:53] <tjaalton> the staging ppa has a version that supports only the new api
[11:54] <darkxst> so I guess there is more to it than just the barriers then?
[11:55] <mlankhorst> it's done at a different level
[11:55] <tjaalton> that's enough to break things :)
[12:02] <darkxst> yeh I don't follow the X stack that closely, but I have seen both the barrier patches in Xfixes
[12:08] <mlankhorst> darkxst: yeah the new one is also in libXI though
[12:09] <darkxst> yeh I know the events come from XI
[12:09] <mlankhorst> if it was easy to backport I may have done so for raring :)
[20:55] <jcristau> Sarvatt: care to add a line about #628758 to mesa:debian-experimental's changelog so it gets closed on upload? :)
[20:56] <Sarvatt> jcristau: was just about to push that :)
[20:56] <jcristau> great
[20:56] <jcristau> thanks
[21:15] <Sarvatt> oh eww, silly me thought it was like launchpad and bugs go under the source package name making http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=mesa;dist=unstable a really small list, but the motherload is filed under libgl1-mesa-dri :)
[21:21] <jcristau> Sarvatt: bugs.debian.org/src:mesa should be the full list
[21:22] <jcristau> (or, replace pkg=mesa with src=mesa in your url)
[21:22] <Sarvatt> oh thanks, that helps a lot
[21:26] <jcristau> Sarvatt: oh, also nnnn@bugs.debian.org doesn't reach the submitter, you need to cc them explicitly
[21:27] <jcristau> (yes, that sucks)
[21:47] <Sarvatt> jcristau: ahhh heck, I'm making a mess of the bugs, sorry about that :)
[21:47] <Sarvatt> didn't realize you guys shipped /etc/drirc, when i brought it up when it first got added everyone was opposed to it :)
[21:49] <jcristau> no worries
[21:57] <Sarvatt> fix never got cherry-picked to 8.0 branch
[21:58]  * Sarvatt switches to mutt to do anything on bugs.debian.org from now on, gmail is a nightmare with it :)