The lyx package in EPEL is really old, version 1.4.5.1. It would be nice if it would be updated, especially now that lyx 1.6 has been released.
I've purposely left in 1.4, since that was the last qt3-based build of lyx. Newer versions use qt4, and rhel5's version is quite old. But, I'm willing to give it a try, and see how things go.
The minimum version of qt4 required for lyx 1.6 is 4.2.0.
Would it at least make sense to patch the lyx2lyx script up to the 1.6 version so that files could be exchanged, between epel version and newer version lyx users, with less hassle? BTW which version of qt4 is available on RHEL 5.3? I see qt4-4.2.1-1 in my CentOS 5.3 system from the 5.3/os/ (AKA Base) part of the repository, which I assume means it is available on RHEL 5.3 now too. With what I thought the policy of epel was, i.e., stick with whatever major.minor rev is initially put in, I thought going to a newer version would be blocked. If we are going to go to 1.6 or 1.5, would it make sense to put out a 1.4 lyx package with the updated lyx2lyx, and a note on how to make that a "sticky" version in yum, before putting out a later version? Boy but the new features of 1.5 &1.6 look shiny :)
Thanks for the ping, I kinda had left this sit since making comment #1.
Here we go, http://koji.fedoraproject.org/koji/taskinfo?taskID=1431277
false start, here's one that actually worked, https://koji.fedoraproject.org/koji/taskinfo?taskID=1431293
lyx-1.6.3-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/lyx-1.6.3-1.el5
lyx-1.6.3-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/EL-5/FEDORA-EPEL-2009-0013
lyx-1.6.3-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.