SPEC: http://netbsd.sk/~lkundrak/SPECS/perl-TAP-Harness-JUnit.spec SRPM: http://netbsd.sk/~lkundrak/SRPMS/perl-TAP-Harness-JUnit-0.01-1.el5.src.rpm Description: The only difference between this module and TAP::Harness is that this adds mandatory 'xmlfile' argument, that causes the output to be formatted into XML in format similar to one that is produced by JUnit testing framework.
I note that upstream has updated this package twice since this ticket was opened, but I guess you know that since you're the upstream. Should we wait for an updated package?
Jason: No need to. The changes did not affect the way this is packaged, so the spec file remains basically the same.
ping?
Package looks sane. + source files match upstream: bdf902ea7a92272def706871a6c1bd5e TAP-Harness-JUnit-0.01.tar.gz + package meets naming and versioning guidelines. + dist tag is present + build root is correct + license is ok + latest version is being packaged + package builds in mock (f8, devel) + rpmlint is silent APPROVED
New Package CVS Request ======================= Package Name: perl-TAP-Harness-JUnit Short Description: Generate JUnit compatible output from TAP results Owners: lkundrak Branches: EL-5 F-9 F-10
CVS Done
Thanks Marek. Thanks Dennis. Imported and built.
Package Change Request ====================== Package Name: perl-TAP-Harness-JUnit New Branches: epel7 Owners: lkundrak eseyman A message from eseyman, the current Fedora maintainer of the package: "I don't use EPEL so I'm probably not the best choice for a maintainer. Feel free to ask for a branch for any of my modules. If you do, please consider adding me as co-maintainer."
Git done (by process-git-requests).