[05:58] morning [06:19] Hi, yo. [06:25] RAOF: did you get anywhere with -core? [06:26] mlankhorst: Yup. Pushed a patch to lightdm to add that; we can drop 100_rethrow_signals [06:34] perfect [06:35] feel free to upload server-core then, I should probably update intel to 20.1 first and then the rest needd [06:35] needs xorg-server-core >= 13rc1 for building [06:48] mlankhorst: Will do. [06:58] RAOF: ok intel updated to 2.20.1 :-) [06:58] want a copy of all the *.orig.tar.gz I have? [07:02] Eh. [07:02] I'm happy to uscan --download-current-version. [07:02] Of course, I'm *also* happy to accept git repositories with pristine-tar branches, so git-buildpackage Just Works™ ;( [07:02] :) [07:03] optimist :P [07:04] Ah. [07:04] RAOF: but openchrome needs love, there was already a openchrome 0.3.0 in hardy which might have been optimistically numbered like that [07:08] ok pushed cirrus to 1.5.1, seems a new release was amde in the last time I looked with the build fix [07:09] We also need to update the proto first, right? We don't have the necessary proto in quantal or -proposed yet? [07:10] probably I think some were pushed [07:10] x11proto-dri2, x11proto-gl, x11proto-randr [07:11] dri2 needs 2.8 [07:11] gl 1.4.16 [07:11] Ah, and a bunch of them are in Debian experimental, and can be syncd. But that needs me to manually flick the switch. [07:11] randr 1.4.0 [07:12] dri2 hasn't been updated in Debian yet, but that can be done. [07:12] rest I'm unsure about, those were the ones I encountered at least :-) [07:12] i can probably push dri2proto to experimental if that helps [07:13] sure [07:13] I bumped all the standards-versions to 3.9.3 too mostly [07:13] Oh, *arse*. We've got some ungodly x11proto-randr version from 2010 that claims to be 1.4 [07:14] that + should have been a ~ [07:14] yeah it's fun [07:14] Yup [07:15] openchrome has the same issue with hardy [07:15] i uploaded it as 1.3.99.1 at the time to avoid just this :) [07:15] Time for a sourceful upload of Debian syncage! [07:15] mlankhorst: hmm? xserver-xorg-video-openchrome | 1:0.2.901-0ubuntu4 | hardy | source, amd64, i386 [07:16] jcristau: launchpad refused 0.3.0 though [07:17] jcristau: https://launchpad.net/ubuntu/hardy/i386/xserver-xorg-video-openchrome/0.3.0-0ubuntu2 [07:17] Yeah, that's the epoch. [07:17] so you need to fudge around with that one to make it work [07:17] ah, yeah, ok. [07:18] just wait for 0.3.1 :p [07:18] shouldn't take more than a year [07:18] or just call it fakesync1 and append that to orig.tar.gz [07:19] nobody said it would have to be because of debian a fakesync is required >:D [07:19] heh [07:21] but yeah the mess with openchrome was worse in multiple ways. I did get it to switch from git-svn to git though. [07:42] jcristau: Pushing dri2proto to experimental *would* help a bit; you still up for it? [07:43] RAOF: yeah, looking at it now, see #d-x :) [08:44] mlankhorst, hi, is 1.13rc2 suppose to land in quantal this week? [08:45] think so [08:45] i see :) [08:46] is there already any news about any compatible nvidia blob? [08:46] nah it tends to lag behind [08:47] i know, aaronp mention 304.x is suppose to get support [08:47] no prime though :p [08:48] but uploading 1.13 will break for quite some people with a new one [08:48] but maybe those changes will finally force nvidia to coexist with other drivers [08:48] *without [08:49] maybe [08:58] yeah you're right, it most likely stays crap :p [09:01] but way better than fglrx ;P [09:01] I don't know if I want to word it like that [09:01] ricotz: like that's hard [09:02] any bets on whether fglrx will have something before the Q release that's compatible? [09:02] :p [09:02] mlankhorst: i thought usually they manage to have something a week before the ubuntu release [09:03] hehe [09:05] but with s3tc package installed I'm getting more luck with r600 nowadays [10:28] RAOF: how is uploading going? [11:42] mlankhorst: It's not really, at the moment :) [11:43] mlankhorst: Got as far as the proto stuff, and then had to go to pilates, have dinner, etc ;) [11:43] ok, I'm just taking a closer look at the precise x server, see if I can fix that issue or if it it's too much work :) [11:45] just noticed I forgot to kill a patch that was upstream so uploaded that fix [12:04] I'll finish off 1.13 uploading tomorrow. [12:06] wow, first time in all my messing with X that I've seen the failsafe-X screen ;) [12:09] RAOF: Yeah I just realized I should check if the gimp bug is also in x1.13 before I try to diagnose it further. Might safe me some work if it turns out to be a bug in upstream too. [12:23] aw unfortunately it works [12:51] RAOF: hm should I just drop it? The same patches work on x1.12, so likely it's caused by our weird backported input stack [12:51] and x1.13 with gimp worked fine too