[Bug 206816] Review Request: freedoom-freedm - Deathmatch levels for freedoom

[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 report.

Summary: Review Request: freedoom-freedm - Deathmatch levels for freedoom


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


tibbs at math.uh.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|163778                      |163779
              nThis|                            |




------- Additional Comments From tibbs at math.uh.edu  2006-09-23 00:35 EST -------
The source URL is failing for me; it's probably some sourceforge breakage.  I
specified a mirror (superb-west.dl.sourceforge.net) and it came through fine.

* source files match upstream:
   340a3e884729c22f45ff73353e2cc67a  freedoom-freedm-0.5.zip
* package meets naming and packaging guidelines.
* specfile is properly named, is cleanly written and uses macros consistently.
* dist tag is present.
* build root is correct.
* license field matches the actual license.
* license is open source-compatible.  License text included in package.
* latest version is being packaged.
* BuildRequires are proper.
* %clean is present.
* package builds in mock (development, x86_64).
* package installs properly
* rpmlint is silent.
* final provides and requires are sane:
   freedoom-freedm = 0.5-1.fc6
  =
   freedoom
   prboom
* package is not relocatable.
* owns the directories it creates.
* doesn't own any directories it shouldn't.
* no duplicates in %files.
* file permissions are appropriate.
* no scriptlets present.
* game levels are acceptable content.
* documentation is small, so no -docs subpackage is necessary.
* desktop file is properly installed.

APPROVED

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