Bug 1114230 - update lzo to 2.07
Summary: update lzo to 2.07
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lzo
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Huzaifa S. Sidhpurwala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-28 22:19 UTC by Harald Reindl
Modified: 2014-10-12 13:56 UTC (History)
3 users (show)

Fixed In Version: lzo-2.08-1.fc19
Clone Of:
Environment:
Last Closed: 2014-07-03 04:02:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Reindl 2014-06-28 22:19:26 UTC
given that there is a security flaw, kernel and ffmpeg released updates and lzo 2.07 is available staying Fedora at 2.06 is questionable

Comment 1 Fedora Update System 2014-06-30 05:35:28 UTC
lzo-2.08-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/lzo-2.08-1.fc20

Comment 2 Fedora Update System 2014-06-30 05:37:24 UTC
lzo-2.08-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lzo-2.08-1.fc19

Comment 3 Fedora Update System 2014-06-30 23:25:25 UTC
Package lzo-2.08-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 lzo-2.08-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7926/lzo-2.08-1.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-07-03 04:02:06 UTC
lzo-2.08-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2014-10-12 13:56:17 UTC
lzo-2.08-1.fc19 has been pushed to the Fedora 19 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.