[Bug 227676] Review Request: scorchwentbonkers - Realtime remake of Scorched Earth

[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: scorchwentbonkers - Realtime remake of Scorched Earth
Alias: scorchwentbonkers

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


chris.stone at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|163778                      |163779
              nThis|                            |
               Flag|fedora-review?              |fedora-review+




------- Additional Comments From chris.stone at gmail.com  2007-03-14 20:51 EST -------
==== REVIEW CHECKLIST ====
- rpmlint output clean
- package named according to package naming guideliens
- spec file name matches %{name}
- package meets packaging guidelines
- licensed with open source compatible license
- license matches actual license
- license included in %doc
- spec written in American english
- spec file legible
- sources match upstream dfaf1a509d2776edf983cd5e1540df95
- package successfully compiles and builds on FC-6 x86_64
- all build dependencies listed in BR
- no locales
- no shared libraries
- package is not relocatable
- package owns all directories it creates
- all directories it does not create are owned pulled in from Requires
- no duplicates in %files
- file permissions set properly
- package contains proper %clean
- macro usage is consistent
- contains code
- no large documentation
- files in %doc do not affect runtime
- no header files
- no static libraries
- no pkgconfig files
- no need for devel subpackage
- no libtool archives
- contains proper desktop file
- package does not own files or directories owned by other packages

*** 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.