Fedora Account System
Red Hat Associate
Red Hat Customer
Spec URL: http://grid.et.redhat.com/files/perl-Net-Amazon-EC2.spec SRPM URL: http://grid.et.redhat.com/files/perl-Net-Amazon-EC2-0.06-1.fc8.src.rpm Description: This module provides an interface to the Amazon Elastic Compute Cloud (EC2) This is 1 of 2 "first" packages, and I am looking for a sponsor.
Reviewed according to guidelines at http://fedoraproject.org/wiki/Packaging/ReviewGuidelines Builds under mock (on devel): $ mock perl-Net-Amazon-EC2-0.06-1.fc8.src.rpm init clean prep This may take a while create cache setup build ending done Results and/or logs in: /var/lib/mock/fedora-development-i386/result $ cd /var/lib/mock/fedora-development-i386/result $ ls -alF total 124 drwxrwsr-x 2 nsantos mock 4096 2008-03-07 14:31 ./ drwxrwsr-x 5 nsantos mock 4096 2008-03-07 14:27 ../ -rw-rw-r-- 1 nsantos mock 11831 2008-03-07 14:31 build.log -rw-rw-r-- 1 nsantos mock 165 2008-03-07 14:27 mockconfig.log -rw-r--r-- 1 nsantos mock 25187 2008-03-07 14:31 perl-Net-Amazon-EC2-0.06-1.fc9.noarch.rpm -rw-r--r-- 1 nsantos mock 32448 2008-03-07 14:31 perl-Net-Amazon-EC2-0.06-1.fc9.src.rpm -rw-rw-r-- 1 nsantos mock 38886 2008-03-07 14:31 root.log $ rpmlint *.rpm (no output) The only two things missing are: - Every %files section must include a %defattr(...) line. - missing packager name on the changelog
Addressed the above two issues.
Specfile looks fine now (have also rebuilt under mock and installed the noarch rpm). Marking as fedora-review+
New Package CVS Request ======================= Package Name: perl-Net-Amazon-EC2 Short Description: Perl interface to the Amazon Elastic Compute Cloud (EC2) Owners: rrati Branches: InitialCC: perl-sig Cvsextras Commits: yes
Fixing summary
Package Change Request ====================== Package Name: perl-Net-Amazon-EC2 New Branches: el6 Owners: lkundrak Fedora maintainer was asked about willingness to maintain this in EPEL, no response in 5 days. That might not be much, but I've a looked up a mail from him about perl-Net-Amazon-S3 (a different but related package) in EPEL 5 and his response was that he doesn't have much time to take care of it in el5. I assume this could be a similar situation and proceeded with filing the VCS request; if it turns out to be false and rrati objects (which is unlikely) it's easy to switch maintainership to him.
Git done (by process-git-requests).