Bug 704257

Summary: Crypt-OpenSSL-RSA 0.26 fails to build with perl 5.14.0
Product: [Fedora] Fedora Reporter: Iain Arnell <iarnell>
Component: perl-Crypt-OpenSSL-RSAAssignee: Wes Hardaker <wjhns174>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: wjhns174
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-12 16:54:02 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 Iain Arnell 2011-05-12 15:22:37 UTC
Wes,

sorry. One more for you. There's a trivial one line fix upstream at https://rt.cpan.org/Public/Bug/Display.html?id=65947, but no obvious hint of a new version for two months now. Would you mind carrying the necessary patch in the package for rawhide? (Or updating to 0.27 if it appears, of course).

Comment 1 Wes Hardaker 2011-05-12 16:36:20 UTC
No problem.  When you provide the problem *and* the fix, patching the code is easy!

I've pushed a new build to rawhide.  Which version of perl is f15 using?  Is it needed there too?

Comment 2 Iain Arnell 2011-05-12 16:51:54 UTC
This is only for rawhide. Perl 5.14.0 won't actually be released until Saturday (at the earliest), so will only be for f16 (in fact, probably 5.14.1 by then, but that will be a minor change). I'm just trying to ensure that when Marcela hits her mass-rebuild button that there will be as few surprises as possible.

And if you have no objections, I could add you to my list of people that don't mind if I make minor updates to their packages. Then you can have the problem, fix, and new build without even touching your keyboard.

Comment 3 Wes Hardaker 2011-05-12 16:54:02 UTC
No, go ahead if you like.  Though an informational note that you're touching it would be good.  I actually started working the repo before doing a pull and hit a conflict because I didn't realize someone else had been tinkering.  Thanks for the help!

Comment 4 Iain Arnell 2011-05-12 17:45:34 UTC
Thanks. Will do. Though, hopefully, it'll be a while before 5.16 breaks things again.