drm version issue in xorg-x11-drv-nouveau-0.0.16-1.20100211gitf7deabf.fc13

[Bruno Wolff III]

Since most people won't see this until after the next f13/rawhide compose
is out and some people might want it to work for the color test day tomorrow,
I thought I'd give a heads up here as well as filing a bug.
(https://bugzilla.redhat.com/show_bug.cgi?id=566348)
In switching from version 0.0.15 to 0.0.16 one place was missed. The
configure.ac file still has 0.0.15. I changed it to 0.0.16, rebuilt the
package and it worked. That may or may not be the correct fix, but should
point any of the video guys in the right direction to fix it. (Tonight
might be good with the testing scheduled for tomorrow.)

[Bruno Wolff III]

On Wed, Feb 17, 2010 at 21:20:06 -0600,
  Bruno Wolff III <bruno(a)wolff.to&gt; wrote:
>  Since most people won't see this until after the next f13/rawhide
> compose
>  is out and some people might want it to work for the color test day tomorrow,
>  I thought I'd give a heads up here as well as filing a bug.
>  (https://bugzilla.redhat.com/show_bug.cgi?id=566348)
>  In switching from version 0.0.15 to 0.0.16 one place was missed. The
>  configure.ac file still has 0.0.15. I changed it to 0.0.16, rebuilt the
>  package and it worked. That may or may not be the correct fix, but should
>  point any of the video guys in the right direction to fix it. (Tonight
>  might be good with the testing scheduled for tomorrow.) 
It looks like they (libdrm and xorg-x11-drv-nouveau with drm-nouveau version
16) missed the first compose after branch and so they should only show up in
testing or rawhide and not directly into F13.

[Bruno Wolff III]

On Wed, Feb 17, 2010 at 21:20:06 -0600,
  Bruno Wolff III <bruno(a)wolff.to&gt; wrote:
>  Since most people won't see this until after the next f13/rawhide
> compose
>  is out and some people might want it to work for the color test day tomorrow,
>  I thought I'd give a heads up here as well as filing a bug.
>  (https://bugzilla.redhat.com/show_bug.cgi?id=566348) 
Ben fixed this in xorg-x11-drv-nouveau-0.0.16-2.20100218git2964702.fc13.
The real problem was in a version being pulled from the kernel headers
and just rebuilding with the current kernel would have fixed it. However
it was changed so that won't be a problem going forward.