Bug 987489 - Update libev to upstream 4.15
Summary: Update libev to upstream 4.15
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libev
Version: 20
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-23 13:33 UTC by Igor Gnatenko
Modified: 2013-09-23 00:21 UTC (History)
4 users (show)

Fixed In Version: libev-4.15-1.fc20
Clone Of:
Environment:
Last Closed: 2013-09-23 00:21:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Igor Gnatenko 2013-07-23 13:33:35 UTC
http://dist.schmorp.de/libev/
Please update it.

Comment 1 Fabian Affolter 2013-09-07 11:40:01 UTC
I would like to have 4.15 because I need the python binding which only builds against 4.15. Thanks.

Comment 2 Igor Gnatenko 2013-09-08 05:47:36 UTC
Updating to 4.15 on f20,f21

Comment 3 Fedora Update System 2013-09-08 06:07:30 UTC
libev-4.15-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/libev-4.15-1.fc20

Comment 4 Fedora Update System 2013-09-08 16:25:20 UTC
Package libev-4.15-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libev-4.15-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16093/libev-4.15-1.fc20
then log in and leave karma (feedback).

Comment 5 Fedora End Of Life 2013-09-16 17:08:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 6 Fedora Update System 2013-09-23 00:21:42 UTC
libev-4.15-1.fc20 has been pushed to the Fedora 20 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.