Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 197411 (php-pear-Date) - Review Request: php-pear-Date - Date and Time Zone Classes
Summary: Review Request: php-pear-Date - Date and Time Zone Classes
Keywords:
Status: CLOSED NEXTRELEASE
Alias: php-pear-Date
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Tibbitts
QA Contact: Fedora Package Reviews List
URL:
Whiteboard:
Depends On: 196802
Blocks: FE-ACCEPT php-pear-Validate
TreeView+ depends on / blocked
 
Reported: 2006-07-01 04:49 UTC by Christopher Stone
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-07 21:23:55 UTC
Type: ---
Embargoed:
jwboyer: fedora-cvs+


Attachments (Terms of Use)

Description Christopher Stone 2006-07-01 04:49:19 UTC
Spec URL: http://tkmame.retrogames.com/fedora-extras/php-pear-Date.spec
SRPM URL: http://tkmame.retrogames.com/fedora-extras/php-pear-Date-1.4.6-1.src.rpm

Description:
Generic classes for representation and manipulation of dates, times and time
zones without the need of timestamps, which is a huge limitation for php
programs. Includes time zone data, time zone conversions and many date/time
conversions.  It does not rely on 32-bit system date stamps, so you can display
calendars and compare dates that date pre 1970 and post 2038. This package also
provides a class to convert date strings between Gregorian and Human calendar
formats.

Comment 1 Jason Tibbitts 2006-09-07 04:58:31 UTC
rpmlint complains:
W: php-pear-Date dangerous-command-in-%post install
but this is obviously bogus.  Hopefully rpmlint will eventually be fixed to stop
complaining about this as going to show up in every pear package.

There seems to be a test suite included in the tarball.  Is it possible to call
it?  It looks like many of the tests need an external mopdule called PHPUnit.php
and I don't know enough about PHP to get the paths set up properly.

The test suite question is the only thing that keeps me from approving this. 
The spec itself and the template it came from are quite clean and should work
great in practise. 
 
* source files match upstream:
   9acd7e19d094877c6d26be1fbabe79cb  Date-1.4.6.tgz
* package meets naming and packaging guidelines.
* specfile is properly named, is cleanly written and uses macros consistently.
* specfile follows the suggested PHP-Pear specfile template currently under
development.
* 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 has only bogus complaints.
* final provides and requires are sane:
   php-pear(Date) = 1.4.6
   php-pear-Date = 1.4.6-1.fc6
  =
   /bin/sh
   /usr/bin/pear
   php-pear(PEAR)
? %check is not present, but there are some tests upstream.
* 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 present are 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.

Comment 2 Christopher Stone 2006-09-07 06:05:51 UTC
The rpmlint warning is mentioned here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198705

pear has no way to do a make check.  It does include the test files in the rpm
however.

Comment 3 Jason Tibbitts 2006-09-07 17:02:52 UTC
Hmm.  It doesn't have a "make check" but there must be some way to run the tests.

Also, I don't see the point of packaging the tests.  Are they somehow useful to
the installed module?  However, for some reason some Python modules do the same
thing, and it seems to be accepted, so I don't suppose it's a blocker.  So,

APPROVED

Comment 4 Christopher Stone 2006-09-07 21:05:33 UTC
I'm not sure, but the test dir is a standard php-pear dir and is defined in the
macros, so I'm sure lots of packages have stuff there.  But AFAIK, there is no
standard way to run tests that are there.  Perhaps we should assess the
situation after more php packages have been approved and see if the tests
directory is really needed.

Comment 5 Christopher Stone 2007-04-21 17:35:55 UTC
Branch Package CVS Request
=======================
Package Name: php-pear-Date
Short Description: Date and Time Zone Classes
Owners: chris.stone
Branches: EL-5
InitialCC: 


Note You need to log in before you can comment on or make changes to this bug.