This is the mail archive of the
mailing list for the Cygwin project.
Re: Fwd: texlive-collection-bibtexextra-20140523-1 -- biblatex & biblatex-chicago version mismatch
- From: Ken Brown <kbrown at cornell dot edu>
- To: Jon Hood <squinky86 at gmail dot com>
- Cc: cygwin <cygwin at cygwin dot com>, Reini Urban <rurban at x-ray dot at>
- Date: Thu, 21 Aug 2014 07:54:09 -0400
- Subject: Re: Fwd: texlive-collection-bibtexextra-20140523-1 -- biblatex & biblatex-chicago version mismatch
- Authentication-results: sourceware.org; auth=none
- References: <CAD0jTRtrDyontmV7r+9q-AbAm1L80-vYEywX=hZ5oO+_c8UOxw at mail dot gmail dot com> <CAD0jTRvGh4ULAC9eJXkjD6q4jwbXUitVfT1WsC+H8D+vQi+6qg at mail dot gmail dot com>
On 8/20/2014 4:17 PM, Jon Hood wrote:
Unfortunately, the message I sent 24 hours ago still
isn't showing up on the mailing list, and I don't know why
---------- Forwarded message ----------
After installing all texlive packages available in the current Cygwin
64-bit repos, I encountered a problem with a biblatex version
mismatch. Cygwin repositories provide biblatex 2.8, but
biblatex-chicago is at 2.9a (which is incompatible with biblatex 2.8).
A more detailed issue is available at
Trying to use biblatex-chicago with these packages produces the following error:
! LaTeX Error:
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help. ...
I am unable to attach cygcheck.out as this is pushed to a secure
system with no internet access. Of relevance is that
texlive-collection-bibtexextra is at version 20140523-1
Are there plans to put everything at version 2.9a in the near future?
I don't know why your message didn't appear, but I'll answer on the list.
biblatex on 64-bit Cygwin is currently stuck at version 2.5. That's for
compatibility with biber, which is stuck at version 1.5. Unfortunately,
I can't update biber until perl gets updated. This is in the works, but
progress on it seems to have stalled. (Reini?)
The mismatch you're seeing is a result of my forgetting to downgrade the
various biblatex-* packages to match the main biblatex. I'll do that
when I get a chance.
If you don't use biber, then you can upgrade biblatex yourself and put
it in your local texmf tree or your personal texmf tree, as suggested in
one of the comments on tex.stackexchange. You can find the paths for
those trees as follows:
$ kpsewhich -var-value TEXMFLOCAL
$ kpsewhich -var-value TEXMFHOME
For technical reasons having to do with the way biber is built, I'm able
to supply up-to-date versions of biber and biblatex on 32-bit Cygwin, so
another option is to switch to that.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple