[00:59] When are we going to see an xserver 1.6.0 beta in jaunty, and is there a way I can help speed this up? [03:50] tjaalton: I've written a page on how to do git-bisect for X in ubuntu. Would you mind reviewing it? https://wiki.ubuntu.com/X/Bisecting [03:50] (my git-fu is not strong; there might be better ways to explain the process) [04:24] bryce_, you still here? [04:24] yep, in and out [04:24] just a quick q about BART [04:25] http://bart.gov/schedules/bylineresults.aspx?route=11&date=12%2F4%2F2008 . those times listed, so say the last one for bay fair is 1:02, does that mean that one runs all the way to milbrae still, you board at bay fair at 1:02? [04:25] just wanted to make sure i've planned ahead to understand when to be back to the BART stop at for uds [04:25] (er for the days before uds) [04:27] bryce_, that howto on git biset looks useful. i've not known how to use git bisect myself, but that looks to explain it well [04:34] yeah I don't know much about the end times for the bart. I tended to use it only for getting to/from work and didn't push the late times [04:35] superm1: yeah, I know upstream often asks to do git bisecting, but ubuntu users find it a bit technically perplexing, so having it documented like we do for backtracing could only help [04:36] this is particularly aimed at our OEM team, since they're very often wishing to backport fixes for earlier releases (esp. hardy) [04:48] ah right [08:25] bryce: looks good, I've bisected mesa once [09:08] tjaalton: You seem to have a duplicate account on LP (~tepsipakki; some packages are showing up with that as the uploader) [09:15] http://www2.bryceharrington.org:8080/Photos/Woodworking/Desk/ <-- some photos of recent work on my desk :-) [09:16] bryce: Oh, it's done? [09:18] wgrant: yep! [09:19] I'm sitting at it right now :-) [09:19] bryce: Not bad. It's nice and shiny. [09:22] yep, went kind of mad with the varnishing ;-) [09:23] more importantly, it's extremely solid. I'm happy with it. Nice to be back on a normal desktop with a couple big dual heads :-) [09:23] been stuck on only a laptop for the last month [09:24] It also looks remarkably straight for a piece of home-built furniture. [09:26] yeah, the angle the wall makes is not exactly 90 degrees, so getting it all to fit in, be level, and be straight, was quite challenging [09:26] Oh, ouch. [09:35] wgrant: yes, I changed that a year ago, now I've removed tepsipakki@ email and waiting for tjaalton@u.c [09:37] tjaalton: what or who is/was tepsipakki? Or what does it mean? [09:38] tseliot: my nickname in certain circles :) [09:39] tepsi = TPS (the hockey team I cheer), pakki=defenseman [09:39] nite [09:39] night bryce, the desk looks nice :) [09:39] Night bryce [09:40] very nice :-) [09:40] tjaalton: But you should probably merge the account... [09:40] night bryce [09:40] wgrant: how? [09:40] tjaalton: https://launchpad.net/~tepsipakki, there's a link there. [09:40] oh [09:43] well, msg'd jpds about it [09:43] since tepsipakki@ doesn't seem to work anymore [09:44] so I can't merge the accounts :) [09:47] oh, it does work [09:48] done now [09:48] so it's not wise to remove the address from my list of addresses [22:26] bryce: ping? should I blueprint'ify xserver-1.6 etc? can't figure out what talk to host otherwise (unless you have suggestions) :) [22:26] tjaalton: yep that sounds good [22:27] bryce: ok, good. maybe xorg-jaunty is better [22:27] are there any other major changes we intend for X this go around? [22:27] so far mostly the blueprints are for toolsmithing type stuff [22:27] oh also I had a question for you, non-X related [22:28] I'm merging nfs-utils and there is a patch 100-gssd-use-kernel-supported-enctypes.diff [22:28] I've refreshed it to apply to the new release, but I'm wondering if it's still necessary? [22:28] tjaalton: I emailed kevin coffman and here is his reply: [22:29] Hi Bryce! [22:29] This patch isn't needed. There is still no code in the kernel to [22:29] return the enctype information and, as it turns out, the way we're [22:29] going to get this information from the kernel has changed. (Which is [22:29] why this has never gone upstream.) [22:29] Bruce and Olga are working on a new upcall interface for gssd which [22:29] will include the ability to send up the supported encryption types. [22:29] The code to add new encryption support in the kernel (besides des) is [22:29] waiting on that new upcall interface to be completed... [22:29] HTH, [22:29] K.C. [22:29] sounds like we should drop the patch, but I wanted to doublecheck with you first [22:30] dunno really, I didn't add it originally [22:31] ..but the original changelog entry is not preserved thanks to me.. maybe launchpad helps [22:31] okie. Guess if anyone needs it, they can bring it back in [22:31] yeah [22:32] I'll notice when we start testing/using nfsv4+krb5 again :) [22:34] phoronix claims that nvidia blob will support randr-1.2 soon [22:34] about time ;-) [22:34] did they indicate if it'd be full support? [22:35] iirc -fglrx said they added randr 1.2 support but left out a few functions [22:36] it didn't say [22:36] oh speaking of fglrx, I told amd we'd have a beta version of xserver 1.6 in alpha2 (which is immediately after uds). [22:36] I bet they are cheering [22:36] heh [22:37] well, they're going to wait on updating fglrx until that's in [22:37] probably tseliot is too :) [22:38] tseliot: oh btw there was a question on whether you'd be providing the newer -nvidia packages in envy for Hardy? [22:40] I got mesa master to build just fine, so we just need to update randrproto and dri2proto before it and xserver 1.6beta [22:40] bryce: the problem is that I don't know how to provide it. 170 and 180 don't support geforce 5xxx series [22:41] bryce: providing an upload which drops the support for certain devices can be a bit risky [22:41] I need a plan [22:41] yeah [22:41] maybe something we all can chat about next week [22:42] yes, right