Red Hat Bugzilla – Bug 477298
perl-Test-Warn needs updating to 0.11
Last modified: 2009-01-23 21:43:57 EST
Description of problem:
perl-Test-Warn-0.10-3.fc11 fails to build with recently update perl-Sub-Uplevel-0.2002-1.fc11. According to upstream changelog, this is fixed in Test::Warn 0.11
0.11 Jun 09 2008
- better Makefile.PL
- mention Test::Trap
- uplevel 2 changed to uplevel 1 to work with Sub::Uplevel 0.19_02
- small fixes
Version-Release number of selected component (if applicable): 0.10-3.fc11
Steps to Reproduce:
1. checkout and build perl-Test-Warn/devel
Updating Test::Warn should also fix the FTBFS on Net::SSLeay:
Oh, yeah. I forgot to mention that. Current perl-Test-Warn doesn't work with current perl-Sub-Uplevel at all (rather than not just build against it). This is responsible for several of the perl-* FTBFS reported by Matt, including
and probably others.
OK, given that this is affecting quite a few other packages, and that this is one of JPO's packages that's effectively under the maintainership of the perl SIG (IIRC spot is the "legal owner" of all of those packages simply because a group couldn't be made the owner in pkgdb), I've updated it myself:
I'll leave the ticket open for now in case anyone else (e.g. spot) wants to chime in.
Works for me. As per usual, I'm okay with perl SIG folks making changes to my perl packages.
Cheers, Paul. That certainly seems to solve it for the packages I mentioned in comment 2.
OK, I think we're done here then.
I think, we should update FC-10 and FC-9, also.
(In reply to comment #7)
> I think, we should update FC-10 and FC-9, also.
Anybody object to me updating F-9 and F-10 the same way?
perl-Test-Warn-0.11-1.fc10 has been submitted as an update for Fedora 10.
perl-Test-Warn-0.11-1.fc9 has been submitted as an update for Fedora 9.
perl-Test-Warn-0.11-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
perl-Test-Warn-0.11-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.