[00:13] jtaylor: hmm which bug? [00:13] 851383 [00:13] bug 851383 [00:13] Launchpad bug 878933 in gtk+2.0 (Ubuntu) "duplicate for #851383 Crash when attempting to open a second file from the recent file list" [Undecided,Confirmed] https://launchpad.net/bugs/878933 [00:14] hmm wasn't that the bug with the most info? [00:14] it has sufficient info, doesn't it? [00:14] an upstream link [00:14] another had the commit ids fixing it [00:14] and the upstream link has a patch [00:14] oh woops [00:14] the upstream link is insufficient [00:14] the patch there was already applied [00:14] but its not enough [00:14] oh crap [00:15] which bug should be the master, then? [00:15] I pasted the important info [00:15] also -desktop knows about it so doesn't matter so much anymore [00:15] okay [00:16] its an ugly situation [00:16] =\ [00:16] you could have just changed the master bug [00:16] these days if you change one duplicate, the rest follow. [00:16] the debdiff between .5 and .6 are ~1500 lines in a single file, .6 and .7 another ~1000 lines [00:16] and in there somewhere are important bug fixes fore breakage in .6 ^^ [00:16] nice [00:16] oh yay [00:18] 851383 should probably be master [00:20] it would be nice when the affect number would include all duplicates [00:21] last time I talked to -desktop they didn't want to fix it because it had to few bugs/affects (~beta 2 I think) [02:30] Do I have to requestsync during DIF? [02:30] erm, debian-import, where we are now [02:33] not if it's unmodified in ubuntu, and the version that you want is in testing [02:33] ajmitch: Ah, right, because this is a LTS. Forgot about testing. [02:33] Thanks, just wondering why it was on such a lag :) [02:34] we are still before DIF [02:34] tumbleweed: I corrected myself directly after :) [02:34] of course if something should be rushed from unstable, file a request [02:34] tumbleweed: nope, no rush [02:34] just wondering :) [02:37] I went to the wiki so I could throw a link at you, but it looks like someone broke the wiki [02:37] tumbleweed: it's no worries at all, I was just doing my rounds and got to wondering [02:38] alright, I'm off. Thanks, ajmitch / tumbleweed [12:55] paultag: why aren't you uds'ing this year? === yofel_ is now known as yofel [13:01] highvoltage: nope :) [13:01] Oh, why [13:02] highvoltage: because I'm leaving, and UDS is a waste of my time, as well as spaceman's :) [13:02] you're leaving? [13:03] tumbleweed: long time coming, my friend. Yeah, I've been dropping roles, and I'm dowm to my last one now [13:03] tumbleweed: I'm coming up here to Debian [13:03] but I'm done with my Ubuntu work, sadly, that part of my life is slowly coming to a close [13:03] right, just moving around a bit then :) [13:03] erm, wow, thought this was the other channel [13:03] this is ubuntu-motu, shoot. [13:04] tumbleweed: yeah, I'll still be contributing, but indirectly :) === Quintasan_ is now known as Quintasan [17:31] hrm, the Ubuntu diff for xmakemol looks weird [17:31] it talks about lesstif not being in main, but the package is in universe anyway [17:32] but are the gl libraries built against it? [17:35] but yes it does look weird [17:36] now I remember some issues in/with Ubuntu and libglw1-mesa [17:36] actually, I might just drop the GL version [17:37] people who want to look at something pretty won't use xmakemol [17:57] jtaylor: i guess it was because mesa did not build against lesstif2-dev cause the former is main and the latter universe [17:57] but now libglw1-mesa is built from mesa-glw, which is universe === jemparing_ is now known as jemparing === txwikinger2 is now known as txwikinger [22:45] anyone know if there is a general developer community/MOTU check-in or anything at UDS this time around? I'm not really seeing it on the schedule... [22:46] * ajmitch saw a MOTU session on the schedule [22:47] I just have to find it again [22:48] friday at 11, it's in the 'other' track [22:48] ajmitch, Thanks!