| Summary: | perl-Test-Harness-3.29 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | perl-Test-Harness | Assignee: | Petr Pisar <ppisar> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | paul, perl-devel |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | perl-Test-Harness-3.29-1.fc21 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-14 09:26:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Upstream Release Monitoring
2013-10-11 10:52:51 UTC
I'm going to need this for the current version of Module::Build::Tiny, so a buildroot override in F-20 would be nice when the update's ready. (In reply to Paul Howarth from comment #1) > I'm going to need this for the current version of Module::Build::Tiny, so a > buildroot override in F-20 would be nice when the update's ready. I do not want to push this into F20 because this Test-Harness release breaks API, it removes TAP::Parser::Utils module. Do you have a serious reason why to break API? (In reply to Petr Pisar from comment #2) > (In reply to Paul Howarth from comment #1) > > I'm going to need this for the current version of Module::Build::Tiny, so a > > buildroot override in F-20 would be nice when the update's ready. > > I do not want to push this into F20 because this Test-Harness release breaks > API, it removes TAP::Parser::Utils module. > > Do you have a serious reason why to break API? Well only that the new TAP::Harness::Env module is needed by Module::Build::Tiny, and some upstream authors (notably Karen Etheridge who works on lots of toolchain modules) always seem to specify the current version of Module::Build::Tiny whenever they release a new version of a module that uses it (perhaps this is the work of a dzil plugin?). The new version of Test::Warnings asks for the current version for instance. Also I can't see anything in Fedora that requires TAP::Parser::Utils. However, if you feel it's too late in the F20 cycle to make this change, I could probably patch around the requirement for current Module::Build::Tiny versions as and when necessary, I think it's to late for F20. |