[Bug 231830] Review Request: python-inotify - Monitor filesystem events with Python under Linux

[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: python-inotify - Monitor filesystem events with Python under Linux


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


lxtnow at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|fedora-review?              |fedora-review+




------- Additional Comments From lxtnow at gmail.com  2007-03-21 00:45 EST -------
Sorry for the late.

So,

OK - Mock Build on FC-6 and FC-Devel (i386)
OK - Package meets naming and packaging guidelines
OK - Spec file matches base package name.
OK - Spec has consistant macro usage.
OK - Meets Packaging Guidelines.
OK - License is GPL
OK - License field in spec matches
OK - License file included in package
OK - Spec in American English
OK - Spec is legible.
OK - Sources match upstream md5sum:
159ba32d41c087d98da6248890958ba0  pyinotify-0.7.0.tar.bz2
OK - Package has correct buildroot.
OK - BuildRequires isn't redundant.
OK - Sub-package is proper.
OK - %build and %install stages is correct and work.
OK - Package has %defattr and permissions on files is good.
OK - Package has a correct %clean section.
OK - Package is code or permissible content.
OK - Packages and Sub-package %doc files don't affect runtime.
OK - Package and Sub-package has no duplicate files in %files.
OK - Package and Sub-package don't own any directories other packages own.
OK - Changelog section is correct.
OK - rpmlint output are silent on RPMs (including sub-package) and SRPM files.

OK - Should function as described.
OK - Should package latest version

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