Bug 1230080 - Upgrade perl-CHI to 0.60
Summary: Upgrade perl-CHI to 0.60
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-CHI
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1230120
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-10 08:38 UTC by Petr Pisar
Modified: 2015-07-03 18:37 UTC (History)
2 users (show)

Fixed In Version: perl-CHI-0.60-1.fc21
Clone Of:
Environment:
Last Closed: 2015-07-03 18:37:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2015-06-10 08:38:44 UTC
Latest Fedora delivers perl-CHI 0.59. Upstream released 0.60. Please upgrade.

Also please enable monitoring service to receive reports about new releases.

Comment 1 Ralf Corsepius 2015-06-10 09:43:42 UTC
Updates built and submitted for fc22 and fc23.

fc21 is stuck, because CHI-0.60 requires perl(JSON::MaybeXS) >= 1.003003, while fc21 only has an outdated perl(JSON::MaybeXS)
...
Error: No Package found for perl(JSON::MaybeXS) >= 1.003003
...

Comment 2 Fedora Update System 2015-06-24 04:34:07 UTC
perl-CHI-0.60-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/perl-CHI-0.60-1.fc21

Comment 3 Fedora Update System 2015-06-25 08:20:04 UTC
Package perl-CHI-0.60-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-CHI-0.60-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10688/perl-CHI-0.60-1.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2015-07-03 18:37:58 UTC
perl-CHI-0.60-1.fc21 has been pushed to the Fedora 21 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.