https://bugzilla.redhat.com/show_bug.cgi?id=1139043 --- Comment #2 from Denis Fateyev <denis@xxxxxxxxxxx> --- (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.) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review