Bug 624094

Summary:	Push lyx-1.6.7-1.el5
Product:	[Fedora] Fedora EPEL	Reporter:	Garrett Holmstrom <gholms>
Component:	lyx	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	el5	CC:	jamatos, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	lyx-1.6.7-1.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-30 17:54:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Garrett Holmstrom 2010-08-13 16:11:07 UTC

Description of problem:
The current version of lyx in stable EPEL-5 is 1.6.6.1-1.el5, while the latest build in koji is 1.6.7-1.el5, which reportedly contains a bunch of bugfixes.


Version-Release number of selected component (if applicable):
lyx-1.6.6.1-1.el5

Comment 1 Fedora Update System 2010-08-13 17:04:01 UTC

lyx-1.6.7-1.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/lyx-1.6.7-1.el5

Comment 2 Fedora Update System 2010-08-13 22:37:40 UTC

lyx-1.6.7-1.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lyx'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/lyx-1.6.7-1.el5

Comment 3 Garrett Holmstrom 2010-08-26 00:52:30 UTC

I encountered no regressions.  It didn't fix the crash we've been experiencing, but the person who asked me to file this hasn't given me a test case or backtrace for that anyway.

Comment 4 Fedora Update System 2010-08-30 17:54:54 UTC

lyx-1.6.7-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.