[10:57] tjaalton: now that I think about it we'll have to recreate the orig for the nvidia driver since we're going to update the driver to the latest release. I have already filed a SRU for Hardy for the lrm-envy. This is definitely something we want to have in Intrepid ASAP since it also adds "preliminary support for X.Org server 1.5". What do you think? [10:58] tseliot: sure, although 1.5 is not in intrepid yet [10:58] and it might take a few weeks [10:58] the driver is future-proof ;) [10:59] and we might also take the chance to remove those files which you wanted me to keep [10:59] since compatibility with Debian will break anyway [10:59] why? [11:00] a different orig tarball [11:00] if they are not installed, it's harmless to keep them [11:00] debian will update theirs sooner or later [11:00] and their existence might make things a bit more confusing for any potential contributor [11:01] not that I think that there will be any ;) [11:01] document it [11:02] shall I write something like "the following files are useless"? [11:02] README.Ubuntu or something [11:04] ok, I can do it as soon as I'm done with the rest of the package. [11:04] I'm reviewing the diversions [11:08] ok [11:29] tjaalton: shall I replace the list of the supported cards in the control.in with the new cards or just comment them out and add the new list? [11:30] or maybe I should add it to the changelog [11:34] also, shall I keep revision ubuntu1 instead of ubuntu2? [11:41] ubuntu1 [11:41] ok, and about the control.in? [11:42] what do you mean by commenting out? [11:42] add the new cards to the list perhaps [11:43] you told me not to remove lines but to comment them out (i.e. put a # before a line) [11:44] what lines are you talking about? [11:45] unless you comment out the whole package, I don't think it would work in control [11:45] read where it says " The following GPU's are supported:" [11:45] but yes, I can just add the new cards [11:46] to the list [11:47] so, since nvidia-kernel-source is not needed you can either comment or delete it [11:49] nvidia-kernel-source = DKMS [11:49] I believe the diff didn't have it [11:49] we still need it [11:49] but you know better [11:49] I didn't remove it [11:49] ok, maybe it was the broken diff [11:50] I will give you the full source once I think it's complete [11:50] this might happen today, so that we can test it together [11:50] ah, it was -ia32 [11:50] right [11:50] n-g-ia32 [11:51] of course [11:52] so hmm.. commenting out is better in the sense that then you know what has been "removed" [11:53] aah, without having to read the diff, you mean [11:53] yes [11:54] well, merge diff against the debian version [11:54] diff.gz doesn't show that [15:51] nice, security updates for the xserver [15:56] for some value of 'nice' :) [15:57] url? [15:58] http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=shortlog;h=server-1.4-branch [15:58] kees: ^ [15:58] kees: http://lists.freedesktop.org/archives/xorg/2008-June/036026.html [15:58] oh, that's much better :) [15:58] right, didn't notice the announce [15:58] -ment [15:59] kees: it wasn't posted to vendor-sec? [16:00] jcristau: yeah, found it now -- only 2 days lead time. whee [16:00] (last time we had like a month, weird) [16:00] kees: it was reported to xorg long ago... [16:16] kees: i guess next time i can cc you when i send mail to team@security.d.o [16:18] jcristau: security@ubuntu.com please, yes. and bryce, if he's not already on the security.d.o list [19:19] kees: the cve patches built fine for intrepid and hardy, shall I go ahead and upload both of those, or do you want to do some testing first? [19:20] bryce: I'll leave it to you for intrepid, but for hardy (and the others) they need to go through the -security queue: [19:20] https://wiki.ubuntu.com/SecurityUpdateProcedures [19:21] mostly, if you can create debdiffs, I can start testing. getting reproducers for the problem, or ways to test the affect code paths would be cool too. :) [19:21] it might be easiest to open a bug for it [19:21] yeah no clue on reproducers [19:22] there are some on the upstream bug [19:22] but it's still restricted [19:23] i'll send it to you [19:23] kees, hardy debdiff: http://people.ubuntu.com/~bryce/Testing/xorg-server_1.4.1~git20080131-1ubuntu9.2.debdiff [19:24] {kees,bryce}@u.c? [19:24] that should work [19:25] jcristau: security@ubuntu.com for security notices, but yeah [19:25] jcristau: that way jdstrand gets them too [19:25] ok [19:25] thx :) [19:25] intrepid debdiff just for completeness - http://people.ubuntu.com/~bryce/Testing/xorg-server_1.4.1~git20080131-1ubuntu12.debdiff [19:26] bryce: why is it ubuntu9.2 for hardy? [19:26] ...uploading the intrepid fixes now... [19:26] kees, there is a 9.1 already in hardy-proposed [19:26] although I just spotted an error in it [19:28] feel free to renumber or whatever as appropriate [19:29] bryce: ah, righto. The debdiff itself needs be applied to ubuntu9 (though 9.2 is the correct version). And the 9.1 needs to be respun to include the security updates and pushed back to -proposed. (i.e. -security updates only every build on top of things -updates, as -proposed packages haven't officially cleared QA) [19:29] error spotting in which thing? [19:30] kees, the patch added in 9.1 for -geode was not actually listed in series (probably my fault) [19:31] erf, that sounds messy - would you be willing to sort those out while I do the patch backports? [19:34] kees: sent [19:38] bryce: sure, I can re-base the hardy debdiff. [19:38] jcristau: thanks [19:41] kees: cool thanks. looks like the patches are applying fairly cleanly except for dapper [19:42] the patches for dapper shouldn't be too different from etch [19:43] and i don't think i had any issues with that, hmm [19:45] jcristau: there's just one patch that isn't applying - org-xserver-1.4-cve-2008-2360.diff [19:45] 1 out of 2 hunks FAILED -- saving rejects to file render/glyph.c.rej [19:46] oh, ok [19:46] I'll take a look in a minute [19:46] probably the #include [19:47] kees, gutsy debdiff: http://people.ubuntu.com/~bryce/Testing/xorg-server_1.3.0.0.dfsg-12ubuntu8.4.debdiff [19:47] for feisty (only), the debdiff is including a bunch of .gitignore deletion garbage [19:48] cool [19:55] kees: do you care about these .gitignore bits? I'm not exactly certain how to exclude those changes... but they're obviously completely harmless, just messy [19:58] bryce: while I like cleanliness, I can live with the mess. :) I suspect it's due to .devscript settings for the -I options during the build [19:58] or dpkg-source behaviour change [19:58] ok, feisty debdiff: http://people.ubuntu.com/~bryce/Testing/xorg-server_1.2.0-3ubuntu8.4.debdiff [19:59] more ~/.devscripts [19:59] # debuild [19:59] DEBUILD_PRESERVE_ENVVARS="DISPLAY,GNOME_KEYRING_SOCKET,XAUTHORITY" [19:59] DEBUILD_DPKG_BUILDPACKAGE_OPTS="-i -I.bzr -I.svn" [19:59] is there something there I could/should change to prevent this issue? [19:59] e.g. -I.gitignore ? [19:59] see if removing -I.bzr for that debuild makes it go away. if not, no big deal. (the bug is that the original released builder didn't use -I.bzr I think) [19:59] oh, .git [20:00] er [20:00] sure, give it a shot. :P [20:00] newer dpkg-source filters out .git and .gitignore by default [20:00] ok, well I guess let's not worry about it... it's just feisty that's affected [20:17] tjaalton: I've just sent an email with my PPA with the driver to superm1 and CCed you [20:20] hmm, dapper's xserver uses a different patch system [20:36] kees, ok here's dapper: http://people.ubuntu.com/~bryce/Testing/xorg-server_1.0.2-0ubuntu10.11.debdiff [20:37] kees, I think that should be it for the debdiffs. [20:37] bryce: very cool, thanks. [20:38] the broken dapper patch was a pretty trivial conflict, I don't think it'll affect functionality [21:10] ah, its so hard to remember that the envy guy albert milone uses the screen name tseliot [21:11] pwnguin: yes, it's me ;) [21:14] tseliot: so you a poetry fan or is the nick derived from some other source? [21:15] bryce: yes, I like poetry and my first exam at the university was on T.S. Eliot [21:16] ah cool [21:16] bryce: so, I received the notification from the spec [21:17] cjwatson should approve it, right? [21:18] let me rephrase it. We need his approval, right? [21:19] yes [21:19] ok [21:19] to be honest the whole blueprint approval process is a tad fuzzy for me, but that's how I understand it [21:20] last time around I don't think my specs got set to Approved, but cj verbally ok'd them so I went ahead and did them. [21:21] since colin was in for the discussion on this and seemed cool with it, getting it set to approved may be more of just a formality but he often has useful comments [21:21] great, this makes things a lot clearer [21:23] I'll keep working on it [21:23] I'm also not sure if they need to be set to Review or Pending Approval... I'll find out and adjust [21:23] cool; I still owe you review comments. it's on my todo list but after a few other things [21:24] ok, I wait for your comments then ;) [22:32] jcristau: just as a note, in the ProcShmPutImage fix, should the errorValue be totalHeight instead of totalWidth? [22:54] tseliot: I've updated the X/OptionsEditor spec a bit with some thoughts based on the mockup. [23:03] bryce: great, I'll have a look at the changes tomorrow since it's 00:03 AM here. Good night [23:04] great, 'night [23:50] kees: hrm. probably, yes