/srv/irclogs.ubuntu.com/2008/06/11/#ubuntu-x.txt

tseliottjaalton: 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:57
tjaaltontseliot: sure, although 1.5 is not in intrepid yet10:58
tjaaltonand it might take a few weeks10:58
tseliotthe driver is future-proof ;)10:58
tseliotand we might also take the chance to remove those files which you wanted me to keep10:59
tseliotsince compatibility with Debian will break anyway10:59
tjaaltonwhy?10:59
tseliota different orig tarball11:00
tjaaltonif they are not installed, it's harmless to keep them11:00
tjaaltondebian will update theirs sooner or later11:00
tseliotand their existence might make things a bit more confusing for any potential contributor11:00
tseliotnot that I think that there will be any ;)11:01
tjaaltondocument it11:01
tseliotshall I write something like "the following files are useless"?11:02
tjaaltonREADME.Ubuntu or something11:02
tseliotok, I can do it as soon as I'm done with the rest of the package.11:04
tseliotI'm reviewing the diversions11:04
tjaaltonok11:08
tseliottjaalton: 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:29
tseliotor maybe I should add it to the changelog11:30
tseliotalso, shall I keep revision ubuntu1 instead of ubuntu2?11:34
tjaaltonubuntu111:41
tseliotok, and about the control.in?11:41
tjaaltonwhat do you mean by commenting out?11:42
tjaaltonadd the new cards to the list perhaps11:42
tseliotyou told me not to remove lines but to comment them out (i.e. put  a # before a line)11:43
tjaaltonwhat lines are you talking about?11:44
tjaaltonunless you comment out the whole package, I don't think it would work in control11:45
tseliotread where it says " The following GPU's are supported:"11:45
tseliotbut yes, I can just add the new cards11:45
tseliotto the list11:46
tjaaltonso, since nvidia-kernel-source is not needed you can either comment or delete it11:47
tseliotnvidia-kernel-source = DKMS11:49
tjaaltonI believe the diff didn't have it11:49
tseliotwe still need it11:49
tjaaltonbut you know better11:49
tseliotI didn't remove it11:49
tjaaltonok, maybe it was the broken diff11:49
tseliotI will give you the full source once I think it's complete11:50
tseliotthis might happen today, so that we can test it together11:50
tjaaltonah, it was -ia3211:50
tseliotright11:50
tjaaltonn-g-ia3211:50
tseliotof course11:51
tjaaltonso hmm.. commenting out is better in the sense that then you know what has been "removed"11:52
tseliotaah, without having to read the diff, you mean11:53
tjaaltonyes11:53
tjaaltonwell, merge diff against the debian version11:54
tjaaltondiff.gz doesn't show that11:54
tjaaltonnice, security updates for the xserver15:51
jcristaufor some value of 'nice' :)15:56
keesurl?15:57
tjaaltonhttp://gitweb.freedesktop.org/?p=xorg/xserver.git;a=shortlog;h=server-1.4-branch15:58
tjaaltonkees: ^15:58
jcristaukees: http://lists.freedesktop.org/archives/xorg/2008-June/036026.html15:58
tjaaltonoh, that's much better :)15:58
tjaaltonright, didn't notice the announce15:58
tjaalton-ment15:58
jcristaukees: it wasn't posted to vendor-sec?15:59
keesjcristau: yeah, found it now -- only 2 days lead time.  whee16:00
kees(last time we had like a month, weird)16:00
jcristaukees: it was reported to xorg long ago...16:00
jcristaukees: i guess next time i can cc you when i send mail to team@security.d.o16:16
keesjcristau: security@ubuntu.com please, yes.  and bryce, if he's not already on the security.d.o list16:18
brycekees: 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:19
keesbryce: I'll leave it to you for intrepid, but for hardy (and the others) they need to go through the -security queue:19:20
keeshttps://wiki.ubuntu.com/SecurityUpdateProcedures19:20
keesmostly, 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
keesit might be easiest to open a bug for it19:21
bryceyeah  no clue on reproducers19:21
jcristauthere are some on the upstream bug19:22
jcristaubut it's still restricted19:22
jcristaui'll send it to you19:23
brycekees, hardy debdiff:  http://people.ubuntu.com/~bryce/Testing/xorg-server_1.4.1~git20080131-1ubuntu9.2.debdiff19:23
jcristau{kees,bryce}@u.c?19:24
brycethat should work19:24
keesjcristau: security@ubuntu.com for security notices, but yeah19:25
keesjcristau: that way jdstrand gets them too19:25
jcristauok19:25
keesthx :)19:25
bryceintrepid debdiff just for completeness - http://people.ubuntu.com/~bryce/Testing/xorg-server_1.4.1~git20080131-1ubuntu12.debdiff19:25
keesbryce: why is it ubuntu9.2 for hardy?19:26
bryce...uploading the intrepid fixes now...19:26
brycekees, there is a 9.1 already in hardy-proposed19:26
brycealthough I just spotted an error in it19:26
brycefeel free to renumber or whatever as appropriate19:28
keesbryce: 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
keeserror spotting in which thing?19:29
brycekees, the patch added in 9.1 for -geode was not actually listed in series (probably my fault)19:30
bryceerf, that sounds messy - would you be willing to sort those out while I do the patch backports?19:31
jcristaukees: sent19:34
keesbryce: sure, I can re-base the hardy debdiff.19:38
keesjcristau: thanks19:38
brycekees: cool thanks.  looks like the patches are applying fairly cleanly except for dapper19:41
jcristauthe patches for dapper shouldn't be too different from etch19:42
jcristauand i don't think i had any issues with that, hmm19:43
brycejcristau: there's just one patch that isn't applying - org-xserver-1.4-cve-2008-2360.diff19:45
bryce1 out of 2 hunks FAILED -- saving rejects to file render/glyph.c.rej19:45
jcristauoh, ok19:46
bryceI'll take a look in a minute19:46
jcristauprobably the #include <stdint.h>19:46
brycekees, gutsy debdiff:  http://people.ubuntu.com/~bryce/Testing/xorg-server_1.3.0.0.dfsg-12ubuntu8.4.debdiff19:47
brycefor feisty (only), the debdiff is including a bunch of .gitignore deletion garbage19:47
keescool19:48
brycekees: do you care about these .gitignore bits?  I'm not exactly certain how to exclude those changes... but they're obviously completely harmless, just messy19:55
keesbryce: while I like cleanliness, I can live with the mess.  :)  I suspect it's due to .devscript settings for the -I options during the build19:58
jcristauor dpkg-source behaviour change19:58
bryceok, feisty debdiff:  http://people.ubuntu.com/~bryce/Testing/xorg-server_1.2.0-3ubuntu8.4.debdiff19:58
bryce more ~/.devscripts 19:59
bryce# debuild19:59
bryceDEBUILD_PRESERVE_ENVVARS="DISPLAY,GNOME_KEYRING_SOCKET,XAUTHORITY"19:59
bryceDEBUILD_DPKG_BUILDPACKAGE_OPTS="-i -I.bzr -I.svn"19:59
bryceis there something there I could/should change to prevent this issue?19:59
brycee.g. -I.gitignore ?19:59
keessee 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
keesoh, .git19:59
keeser20:00
keessure, give it a shot.  :P20:00
jcristaunewer dpkg-source filters out .git and .gitignore by default20:00
bryceok, well I guess let's not worry about it...  it's just feisty that's affected20:00
tseliottjaalton: I've just sent an email with my PPA with the driver to superm1 and CCed you20:17
brycehmm, dapper's xserver uses a different patch system20:20
brycekees, ok here's dapper:  http://people.ubuntu.com/~bryce/Testing/xorg-server_1.0.2-0ubuntu10.11.debdiff20:36
brycekees, I think that should be it for the debdiffs.20:37
keesbryce: very cool, thanks.20:37
brycethe broken dapper patch was a pretty trivial conflict, I don't think it'll affect functionality20:38
pwnguinah, its so hard to remember that the envy guy albert milone uses the screen name tseliot21:10
tseliotpwnguin: yes, it's me ;)21:11
brycetseliot: so you a poetry fan or is the nick derived from some other source?21:14
tseliotbryce: yes, I like poetry and my first exam at the university was on T.S. Eliot21:15
bryceah cool21:16
tseliotbryce: so, I received the notification from the spec21:16
tseliotcjwatson should approve it, right?21:17
tseliotlet me rephrase it. We need his approval, right?21:18
bryceyes21:19
tseliotok21:19
bryceto be honest the whole blueprint approval process is a tad fuzzy for me, but that's how I understand it21:19
brycelast 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:20
brycesince 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 comments21:21
tseliotgreat, this makes things a lot clearer21:21
tseliotI'll keep working on it21:23
bryceI'm also not sure if they need to be set to Review or Pending Approval...  I'll find out and adjust21:23
brycecool; I still owe you review comments.  it's on my todo list but after a few other things21:23
tseliotok, I wait for your comments then ;)21:24
keesjcristau: just as a note, in the ProcShmPutImage fix, should the errorValue be totalHeight instead of totalWidth?22:32
brycetseliot: I've updated the X/OptionsEditor spec a bit with some thoughts based on the mockup.22:54
tseliotbryce: great, I'll have a look at the changes tomorrow since it's 00:03 AM here. Good night23:03
brycegreat, 'night23:04
jcristaukees: hrm. probably, yes23:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!