=== bryceh is now known as bryce
[03:47] <bryce> tjaalton, whew, I ended up having to basically rewrite arsenal's launchpadlib authentication system but finally I wontfixed all those lrm bugs :-)
[03:54] <RAOF> Yay!
[03:59] <bryce> was also a good opportunity to do a better way to set scripts to run as bugbot
[03:59] <bryce> now it can be controlled via a simple config flag in the scripts themselves
[03:59] <bryce> alright, time to go play with the kiddo, cya
[04:09] <RAOF> Have fun!
[06:13] <tjaalton> bryce: whoa..
[06:15] <tjaalton> btw, could the drm bits be split from the kernel as a dkms package? I'm thinking it's the best way to scale and provide the backported stack for the masses
[06:16] <tjaalton> maybe it was discussed at uds, but the lts-backport ppa should track kernel security releases, and it's a lot of work
[06:17] <tjaalton> with a drm-dkms package it could be used with the official kernel (which might be needed for stuff like ksplice)
[06:17] <tjaalton> hmm, breakfast ->
[06:23] <RAOF> tjaalton: That would be more appropriate if airlied made good on his threat to go back to a separate drm tree; the benefit and curse of drm being maintained in mainline is that it gets to tie itself in with other code.
[06:42] <tjaalton> RAOF: hmm i thought it was pretty much self-contained and not tied to the rest of the kernel
[06:43] <RAOF> There are a (growing?) number of fingers in other pies; acpi an the VM subsystem spring to mind.
[06:43] <RAOF> s/ an / and /
[06:43] <tjaalton> ah yes, acpi..
[06:44] <RAOF> And, going forward, if linaro has anything to do with it there'll be interactions with v4l2, etc.
[06:45] <tjaalton> do you recall where and when did airlied threat to do that?
[06:51] <RAOF> On one of the drm pull request pushback threads on dri-devel where Linus (again) complained about drm churn, and Dave in reply complained that the kernel release schedule means that it takes about 6 months for hardware support to hit users.
[06:53] <RAOF> I can hunt down the thread if you like.
[07:10] <tjaalton> nah I think I know that one
[08:02] <tjaalton> duh, took this long to discover uscan(1)
[08:07] <RAOF>  !!!
[08:08] <RAOF> Really?  Man, I'm sorry I didn't tell you earlier :)
[08:08] <tjaalton> yeah, i feel so stupid now, wgetting those tarballs by hand in the past
[08:08] <tjaalton> aanyway, wacom 0.11.0 ready
[08:09] <tjaalton> btw, my personal git repo on alioth should be writable by pkg-xorg
[08:10] <tjaalton> for wacom
=== chrisccoulson_ is now known as chrisccoulson
[09:39] <tjaalton> nice, fermi microcode up for testing
[13:44] <tjaalton> RAOF: -nouveau is in depwait, is libdrm merge ready to go?
[14:55] <tjaalton> yeah, oneiric looks like arse right now :)
[14:55] <tjaalton> a hairy one
[15:00] <tseliot> :D
[15:35] <tjaalton> bryce: intel merged, but patches 115 and 119 need some work to apply, and I just commented them out from series for now
=== lilstevie is now known as lilstevie|ZNC
[17:36] <mgariepy> hello, i've got an issue with xorg-server-video-intel v 2.14 and 2.15 that makes the transparency black when using a remote Xorg server i commented the bug here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/785280 can someone help about this ?
[17:36] <ubot4> Launchpad bug 785280 in gentoo (and 1 other project) "transparency not working with intel driver and LTSP (affects: 2) (heat: 12)" [Medium,Unknown]
=== lilstevie|ZNC is now known as lilstevie
=== kklimonda is now known as Guest62081
=== Guest62081 is now known as kklimonda^
=== yofel_ is now known as yofel
[23:36] <RAOF> tjaalton: Yeah, the libdrm merge is ready to go (and in git, right?  I'm pretty sure I pushed it!), I just need to work out precisely what to do with mesa.
[23:38] <Sarvatt> woohoo libdrm is merged? I got tripped up bringing the multiarch stuff to the new packaging
[23:41] <RAOF> Yeah, it's merged :)
[23:43] <RAOF> Sarvatt: I'll merge mesa from debian, too.