[08:07] <tjaalton> bryce: exactly my point. it's just too easy to let xorg get filled up
[08:07] <bryce> tjaalton: yep I agree
[08:07] <bryce> tjaalton: today I've been really taking advantage of my busted up jaunty desktop
[08:08] <tjaalton> "advantage" :)
[08:08] <bryce> I had this weird mouse cursor flickering in firefox, found a patch for it that solved it, and uploaded :-)
[08:08] <tjaalton> oh taht
[08:08] <tjaalton> that
[08:08] <tjaalton> so you didn't use git then, because it has the tip of 1.6 branch ;)
[08:09] <tjaalton> which fails to build a source package because of change xquartz stuff
[08:09] <tjaalton> changeD
[08:09] <bryce> nah, I looked at the real patch but it looked pretty involved, so just put in the much simpler workaround patch for the time being
[08:09] <tjaalton> don't think 1.6-branch has it yet
[08:10] <bryce> yeah, doesn't sound like it.  So when it does, we can drop this patch.
[08:10] <tjaalton> just wondering what to do in git
[08:11] <bryce> the workaround patch has been working perfectly so far for me
[08:12] <bryce> also sorted out a bug where right clicking on urls in gnome apps wasn't loading right in firefox
[08:12] <bryce> that turned out to be a glib bug.  I made a workaround patch but didn't root-cause it
[08:12] <tjaalton> ok, has worked for me
[08:13] <bryce> it seems to have something to do with gvfs
[08:13] <bryce> maybe something isn't quite kosher with my setup
[08:14] <bryce> anyway, whatever, another annoyance eliminated :-)
[08:21] <tjaalton> good :)
[08:39] <tjaalton> afk, to the skating rink ->
[08:40]  * bryce chuckles
[08:40] <bryce> sounds fun
[10:05] <tjaalton> yep, it was
[10:05] <tjaalton> it's across the street, so easy to go to :)
[11:04] <tjaalton> bryce: ati dithering stuff regression on intrepid, bug 314326
[16:09] <superm1> bryce, is AMD aware of any ABI problems that will be happening for jaunty so that they have time to plan appropriately?
[17:03] <seb128> tseliot: could you look to bug #314406? it's g-s-d crashing in jaunty due to your change
[17:03]  * tseliot has a look at the report
[17:06] <tseliot> seb128: ok, I think I know how to fix it. When do you need the fix?
[17:07] <seb128> tseliot: no hurry there is not so many jaunty users yet
[17:07] <tseliot> seb128: ok, I'll add it to my todo list. Thanks for reporting
[19:42] <tjaalton> superm1: AIUI yes they are
[22:14] <bryce> tjaalton: I've modified the colorization and accounting on http://bryceharrington.org/X/PkgList/versions_current.html a bit, to better distinguish better when we're in sync with debian, but they're behind upstream (since there's so many packages in that state currently)
[22:15] <bryce> (gets rid of a lot of red for us :-) )
[22:18] <andersk> Is it intentional that xft 2.1.13-2 was synced rather than merged into Jaunty?  The sync dropped two patches that I believe are still needed (bug 305399). 
[22:24] <bryce> andersk: thanks, I'll upload
[22:29] <tjaalton> bryce: so lime means that we are in sync with debian but not upstream, and blue means we are not in sync?
[22:30] <tjaalton> with either
[22:31] <bryce> (still tinkering with colors a bit)
[22:32] <bryce> tjaalton: correct
[22:32] <bryce> I'm adding another color to distinguish between needing merges vs. syncs to experimental
[22:33] <bryce> also I corrected needs-merge vs. needs-sync; for some reason I'd not gotten the logic right for ubuntu packages
[22:34] <bryce> while I'm at it, any other change requests for this page?
[22:35] <tjaalton> nothing I can think of
[22:39] <bryce> actually, blue means we're not in sync with experimental
[22:39] <bryce> dark blue means we need to merge with experimental, light blue means we just need to sync
[22:39] <bryce> red/orange means we need a merge/sync with unstable
[22:57] <tjaalton> yeah, didn't notice it was explained at the bottom