[Bug 225999] Merge Review: libdrm

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=225999


Orcan 'oget' Ogetbil <oget.fedora at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?                   |




--- Comment #8 from Orcan 'oget' Ogetbil <oget.fedora at gmail.com>  2009-01-31 12:05:17 EDT ---
(In reply to comment #7)
> I've no idea what is going on in this bug. Its a 2 year old review request,
> that nobody cared about.
> 
There are plenty of Merge Reviews that are waiting for a reviewer. Sorry, we
didn't have the manpower to finish them up in the last two years. People are
working on them.

> Just read the spec file and review it.
> 
> You aren't the maintainer so you can't decide when we need to upgrade to the
> latest upstream version, esp when we are also upstream maintainers, and libdrm
> is a pretty messy system component to just go upgrading due to links to X/mesa
> etc.
> 
Thank you for the explanation. Being verbose just *helps*.

> I'm also nearly sure I did push 2.4.4 into rawhide 2-3 days ago, 
Again, I'm sorry. I didn't check the rawhide SPEC. I was busy with monitoring
many SPEC files and this one just slipped through. It would be nice if the
maintainer wrote about the update here.


> but again what
> has the version got to do with the spec file review?
> 
> confused.
> Dave.

Dave, this is not a "SPEC file review". It is a "package review". The former is
only a subset of the latter. For reference, look at 
    http://fedoraproject.org/wiki/Packaging/ReviewGuidelines
Some of these elements cannot be checked within SPEC file only and they need to
be re-checked with each upstream version.

I'll do the "package review" now.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.