Bug 600629 - perl-Crypt-OpenSSL-X509-1.4 is available
Summary: perl-Crypt-OpenSSL-X509-1.4 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-OpenSSL-X509
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Wes Hardaker
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-05 10:15 UTC by Upstream Release Monitoring
Modified: 2011-03-29 21:06 UTC (History)
3 users (show)

Fixed In Version: 1.4-1
Clone Of:
Environment:
Last Closed: 2011-03-29 21:06:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2010-06-05 10:15:47 UTC 
Latest upstream release: 1.2
Current version in Fedora Rawhide: 0.7
URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Comment 1 Upstream Release Monitoring 2010-08-07 10:19:35 UTC 
Latest upstream release: 1.3
Current version in Fedora Rawhide: 0.7
URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Comment 2 Upstream Release Monitoring 2010-09-06 18:48:04 UTC 
Latest upstream release: 1.4
Current version in Fedora Rawhide: 0.7
URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring
Note You need to log in before you can comment on or make changes to this bug.