Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1638635 - Upgrade perl-bignum to 0.51
Summary: Upgrade perl-bignum to 0.51
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-bignum
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-12 06:46 UTC by Jitka Plesnikova
Modified: 2018-10-30 17:26 UTC (History)
2 users (show)

Fixed In Version: perl-bignum-0.51-1.fc30 perl-bignum-0.51-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 17:26:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jitka Plesnikova 2018-10-12 06:46:38 UTC
Latest Fedora delivers 0.50 version. Upstream released 0.51. When you have free time, please upgrade it

Comment 1 Fedora Update System 2018-10-12 08:15:31 UTC
perl-bignum-0.51-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ed27d0729c

Comment 2 Fedora Update System 2018-10-12 18:26:10 UTC
perl-bignum-0.51-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ed27d0729c

Comment 3 Fedora Update System 2018-10-30 17:26:08 UTC
perl-bignum-0.51-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.