Bug 1322671 - Please include a more recent texlive package
Summary: Please include a more recent texlive package
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 25
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1274105
TreeView+ depends on / blocked
 
Reported: 2016-03-31 05:23 UTC by Răzvan Sandu
Modified: 2016-09-29 14:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 14:29:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Răzvan Sandu 2016-03-31 05:23:33 UTC
Description of problem:

Please include a more recent (after October 2015) textlive package in Fedora 24, since they already include critical bug corrections that are significant for a large category of users (all Romanian authors).

Please see LaTeX bug no. 4460 as reference
https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=latex/4460&introduction=yes&state=open

Currently, the version that is anticipated in Fedora 24 beta (texlive-2015-24.20150728_r37987.fc24) is pretty old; by number designation, it seems even older than the one anticipated in Ubuntu 2016.04 (texlive-base 2015.20160320-1)

Version-Release number of selected component (if applicable):
In Fedora 23, we have texlive-2014-19.20140525_r34255.fc23.x86_64

Thanks a lot,
Răzvan

Comment 1 Tom "spot" Callaway 2016-04-26 19:00:48 UTC
I realize this is unpleasant, but the amount of change it would cause to Fedora to update to TL2016 at this point is not something we can do this late in the Fedora 24 schedule. I'm willing to work on it for Fedora 25.

Comment 2 Jan Kurik 2016-07-26 05:07:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 3 Than Ngo 2016-09-29 14:29:02 UTC
it's fixed in f25/rawhide


Note You need to log in before you can comment on or make changes to this bug.