Bug 18907 - Update Lyx to version 2.1.5, at least, to have compatibility with newer versions of the files
Summary: Update Lyx to version 2.1.5, at least, to have compatibility with newer versi...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-09 17:39 CEST by Pana Sum
Modified: 2016-09-30 20:05 CEST (History)
2 users (show)

See Also:
Source RPM: lyx-2.1.4-4.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pana Sum 2016-07-09 17:39:28 CEST 
Description of problem:
Lyx in Mageia 6 sta 1 is version 2.1.4. However, versions 2.1.5 and 2.2 are avilable. As we are in version freeze, I do not think updating to 2.2 is possible, but it would be good to update the Lyx version to 2.1.5 at least.

2.1.5 is able to read files saved in version 2.2, and some crashes have been fixed: http://www.lyx.org/announce/2_1_5.txt



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Pana Sum 2016-07-09 22:12:54 CEST

Source RPM: lyx-2.1.3-1.mga5.src.rpm => lyx-2.1.4-4.mga6.src.rpm

David GEIGER 2016-07-09 22:21:50 CEST

CC: (none) => geiger.david68210
Assignee: bugsquad => thomas

Comment 1 Thierry Vignaud 2016-07-12 15:48:41 CEST 
I'm pushing 2.2 into core/updates_testing as:
- lyx is a leaf package
- there won't be any more release in the 2.1.x branch
  (which is not good for security updates and the like)

Also having less packages using deprecated Qt4 is nice...

CC: (none) => thierry.vignaud

Comment 2 Thomas Spuhler 2016-07-12 18:50:30 CEST 
Please go ahead with the update. I would favor 2.2
I will be out of town for 2+ weeks on a vacation trip.
Comment 3 Pana Sum 2016-09-30 20:05:23 CEST 
I am closing this bug since this is already available in Cauldron. Thanks

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.