[Bug 197417] Review Request: php-pear-Validate - PEAR: Validation class

[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: php-pear-Validate - PEAR: Validation class
Alias: php-pear-Validate

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


tibbs at math.uh.edu changed:

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




------- Additional Comments From tibbs at math.uh.edu  2006-09-08 16:08 EST -------
* source files match upstream:
   70be4bfc7cf759e3451fb4f8faf251cb  Validate-0.6.4.tgz
* 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).
* rpmlint is silent (except for the bogus warning)
* final provides and requires are sane:
   php-pear(Validate) = 0.6.4
   php-pear-Validate = 0.6.4-1.fc6
  =
   /bin/sh
   /usr/bin/pear
   php-pear(Date)
   php-pear(PEAR)
* %check is not present; there are tests but it is not possible to execute them
automatically.
* 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.
* scriptlets OK (PEAR module installation)
* code, not content.
* documentation is small, so no -docs subpackage is necessary.
* %docs are not necessary for the proper functioning of the package.

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.