Bug 525914 (perl-Net-GitHub) - Review Request: perl-Net-GitHub - Perl interface for github.com
Summary: Review Request: perl-Net-GitHub - Perl interface for github.com
Keywords:
Status: CLOSED NEXTRELEASE
Alias: perl-Net-GitHub
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Klepek
QA Contact: Fedora Extras Quality Assurance
URL: http://search.cpan.org/dist/Net-GitHub
Whiteboard:
Depends On: 525913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-27 04:21 UTC by Chris Weyl
Modified: 2009-11-04 06:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-04 06:53:27 UTC
jan.klepek: fedora-review+
kevin: fedora-cvs+


Attachments (Terms of Use)

Description Chris Weyl 2009-09-27 04:21:00 UTC
Spec URL: http://fedorapeople.org/~cweyl/review/perl-Net-GitHub.spec
SRPM URL: http://fedorapeople.org/~cweyl/review/perl-Net-GitHub-0.19-1.fc11.src.rpm

Description:
GitHub (http://github.com) is a popular git host; this package is a Perl API
for working with GitHub users and repositories.

*rt-0.10_01

Comment 1 Jan Klepek 2009-10-06 18:49:59 UTC
sorry for late response, i tried to build it in koji and it failed, seems that it runs cpan to do dependency checks.
http://koji.fedoraproject.org/koji/taskinfo?taskID=1731189

Comment 2 Jan Klepek 2009-10-12 09:00:52 UTC
any progress?

Comment 4 Jan Klepek 2009-11-01 19:35:17 UTC
*md5sum source ok
*naming ok
*rpmlint ok
*license ok
*build ok
*file ownage ok
*guidelines & perl specific guidelines ok
*latest version
*spec legible

approved

Comment 5 Chris Weyl 2009-11-03 06:38:40 UTC
New Package CVS Request
=======================
Package Name: perl-Net-GitHub
Short Description: Perl interface for github.com
Owners: cweyl
Branches: F-10 F-11 F-12 devel
InitialCC: perl-sig

Comment 6 Kevin Fenzi 2009-11-03 19:12:39 UTC
cvs done.

Comment 7 Chris Weyl 2009-11-04 06:53:27 UTC
Thanks for the review! :-)


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