Bug 490865 - Review Request: perl-Date-Leapyear - Is a particular year a leap year?
Summary: Review Request: perl-Date-Leapyear - Is a particular year a leap year?
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 490867
TreeView+ depends on / blocked
Reported: 2009-03-18 11:45 UTC by Xavier Bachelot
Modified: 2009-03-27 02:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-03-27 02:03:25 UTC
Type: ---
rc040203: fedora-review+
kevin: fedora-cvs+

Attachments (Terms of Use)

Description Xavier Bachelot 2009-03-18 11:45:33 UTC
Spec URL: http://www.bachelot.org/fedora/SPECS/perl-Date-Leapyear.spec
SRPM URL: http://www.bachelot.org/fedora/SRPMS/perl-Date-Leapyear-1.71-2.fc10.src.rpm
Description: Date::Leapyear exports one function - isleap - which returns 1 or 0 if a year is leap, or not, respectively.

Comment 1 Xavier Bachelot 2009-03-18 11:47:42 UTC
There is a license issue with this package (Artistic 1.0), but upstream has agreed to re-license to same terms as perl (GPL+ or Artistic). I've added the mail to the package in Source1 and pro-actively changed the license to get the review going.

Comment 2 Ralf Corsepius 2009-03-18 12:47:51 UTC
Please include the license related email in this package's /usr/share/doc/.../

APPROVED, provided you add the email.

Comment 3 Xavier Bachelot 2009-03-18 19:38:05 UTC
Thanks for the review Ralf. I've added the mail, as suggested.

New Package CVS Request
Package Name: perl-Date-Leapyear
Short Description: Is a particular year a leap year?
Owners: xavierb
Branches: F-9 F-10 EL-4 EL-5
InitialCC: perl-sig

Comment 4 Kevin Fenzi 2009-03-20 01:45:48 UTC
cvs done.

Comment 5 Xavier Bachelot 2009-03-20 15:15:34 UTC
Imported and built for F-9, F-10, EL-4 and EL-5.

Comment 6 Xavier Bachelot 2009-03-27 02:03:25 UTC
hmm, this should have been closed when the packages were pushed to stable...

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