Bug 1165437 - If we have texlive-2014, why is texlive-biblatex still 2.8a (from 2013-11)?
Summary: If we have texlive-2014, why is texlive-biblatex still 2.8a (from 2013-11)?
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-19 00:55 UTC by Colin Macdonald
Modified: 2015-08-11 23:28 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-11 23:28:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Colin Macdonald 2014-11-19 00:55:00 UTC
On my machine texlive-biblatex is "4:svn32245.2.8a-1.1.fc21".

From https://apps.fedoraproject.org/packages/texlive-biblatex, it looks like: 2014-1.1.20140525_r34255.fc21

Is the reason these don't match something to do with subpackages?

-----------------------------

(I'm trying to fix up dependencies for my biber package in Bug #584063, and the version of texlive-biblatex needs to line up with which version of biber I propose).

From http://pkgs.fedoraproject.org/cgit/texlive.git, I can see the upgrade to texlive 2014 months ago in July.

http://www.ctan.org/pkg/biblatex lists current version as 2.9a.  I think, but haven't confirmed, that texlive 2014 has either 2.9 or 2.9a.

------------------------------

Is there a bug here?  Or just my poor understanding of texlive?

Comment 1 Fedora Admin XMLRPC Client 2015-08-11 05:32:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Colin Macdonald 2015-08-11 08:08:47 UTC
I will try to confirm this after new texlive 2015 appears in my rawhide install and then adjust accordingly...

Comment 3 Colin Macdonald 2015-08-11 23:28:15 UTC
No longer relevant as in F24 we have 3.0 as expected.


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