Spec URL: http://www.fateyev.com/RPMS/Fedora20/testing/perl-Array-Unique.spec SRPM URL: http://www.fateyev.com/RPMS/Fedora20/testing/SRPMS/perl-Array-Unique-0.08-1.fc20.denf.src.rpm Description: This package lets you create an array which will allow only one occurrence of any value. In other words, no matter how many times you put in 42 it will keep only the first occurrence and the rest will be dropped. You use the module via tie and once you tied your array to this module it will behave correctly. Uniqueness is checked with the 'eq' operator so among other things it is case sensitive. As a side effect the module does not allow undef as a value in the array. Fedora Account System Username: dfateyev Koji scratch builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=7540753 (Rawhide) https://koji.fedoraproject.org/koji/taskinfo?taskID=7540751 (EPEL 5) https://koji.fedoraproject.org/koji/taskinfo?taskID=7540746 (EPEL 6) https://koji.fedoraproject.org/koji/taskinfo?taskID=7540744 (EPEL 7)
Builds okay in rawhide http://koji.fedoraproject.org/koji/taskinfo?taskID=7711524 license is good. rpmlint only has incorrect spelling warnings and may be ignored. BR: perl(Test::Pod) BR: perl(Test::Pod::Coverage) BR: perl(Test::Perl::Critic) can be removed as they are not included in the test suite that is run. They are only in the xt directory. The "find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;" line can be removed. It is not necessary for >= EPEL5 How are you building your EPEL5 packages?
(In reply to David Dick from comment #1) > BR: perl(Test::Pod) > BR: perl(Test::Pod::Coverage) > BR: perl(Test::Perl::Critic) > > can be removed as they are not included in the test suite that is run. They > are only in the xt directory. OK. I thought whether they were needed if they were mentioned in "xt". > The "find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;" line > can be removed. It is not necessary for >= EPEL5 OK. I was concerned if it was working with EPEL5 too. Updated spec: http://www.fateyev.com/RPMS/Fedora20/testing/perl-Array-Unique.spec SRPM: http://www.fateyev.com/RPMS/Fedora20/testing/SRPMS/perl-Array-Unique-0.08-2.fc20.denf.src.rpm Koji scratch builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=7714825 (Rawhide) https://koji.fedoraproject.org/koji/taskinfo?taskID=7714827 (EPEL7) > How are you building your EPEL5 packages? Well, it's not possible to push F20 SRPMs directly due to a bug with MD5 checking in RHEL5. Since I've got here some OpenVZ containers with RHEL5 installed, I wrote a tiny script which copies and installs SRPMs into EL5 container (`rpm -ivh --nomd5 package.src.rpm`), runs `rpmbuild` or `mock` inside, and gets me results back. Such "native" SRPM can be passed in EPEL5 scratch build. (Of course, OpenVZ is not the only option here.)
(In reply to Denis Fateyev from comment #2) > (In reply to David Dick from comment #1) > > > BR: perl(Test::Pod) > > BR: perl(Test::Pod::Coverage) > > BR: perl(Test::Perl::Critic) > > > > can be removed as they are not included in the test suite that is run. They > > are only in the xt directory. > > OK. I thought whether they were needed if they were mentioned in "xt". Every module that is required during build/test/install. The "make test" does not use the "xt" directory, so it may be ignored. > > The "find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;" line > > can be removed. It is not necessary for >= EPEL5 > > OK. I was concerned if it was working with EPEL5 too. I'm pretty sure that it is not required. If you get a build failure for EPEL5, just re-add it. Package APPROVED!
New Package SCM Request ======================= Package Name: perl-Array-Unique Short Description: Tie-able array that allows only unique values Owners: dfateyev Branches: f19 f20 f21 el5 el6 epel7 InitialCC: perl-sig
Git done (by process-git-requests).
perl-Array-Unique-0.08-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.fc21
perl-Array-Unique-0.08-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.fc20
perl-Array-Unique-0.08-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.fc19
perl-Array-Unique-0.08-2.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.el7
perl-Array-Unique-0.08-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.el6
perl-Array-Unique-0.08-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/perl-Array-Unique-0.08-2.el5
perl-Array-Unique-0.08-2.el6 has been pushed to the Fedora EPEL 6 testing repository.
perl-Array-Unique-0.08-2.fc21 has been pushed to the Fedora 21 stable repository.
perl-Array-Unique-0.08-2.fc19 has been pushed to the Fedora 19 stable repository.
perl-Array-Unique-0.08-2.fc20 has been pushed to the Fedora 20 stable repository.
perl-Array-Unique-0.08-2.el6 has been pushed to the Fedora EPEL 6 stable repository.
perl-Array-Unique-0.08-2.el7 has been pushed to the Fedora EPEL 7 stable repository.
perl-Array-Unique-0.08-2.el5 has been pushed to the Fedora EPEL 5 stable repository.