I am running Tex Live 2013 from OpenBSD-current. The versions of biblatex and biblatex-chicago seem to be a bit old there, which is in turn causing some of my documents to not compile.

I've downloaded the latest versions of these two packages from CTAN and placed them in my ~/texmffolder. kpsewhich seems to find the correct versions:

% kpsewhich biblatex.sty biblatex-chicago.sty

Compiling a document where I import biblatex-chicago fails. I believe this is because pdflatex is finding the old version of these packages in spite of kpsewhich seeing the correct versions:

% pdflatex summaries.tex                     
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013-OpenBSD_Ports)
 restricted \write18 enabled.
entering extended mode
LaTeX2e <2011/06/27>
Babel <3.9f> and hyphenation patterns for 78 languages loaded.
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class

Package biblatex Warning: 'labelyear' option is deprecated, use 'labeldate' ins

! Undefined control sequence.
<argument> \DeclareLabelyear 
                             [music,review,video]{\field {eventyear}\field {...
l.92 \csuse{cms@\cms@style}

I found this question that describes this issue with a patched version of pdflatex. However, since I'm using the packaged version of texlive, I'm not entirely sure rebuilding pdftex is the right approach here. I'm begining to suspect this is a bug in the OpenBSD texlive package, but am posting this here as a question just in case I'm simply being daft.

  • 3
    Your file locations look odd: should be /home/peter/texmf/tex/latex/biblatex/biblatex.sty rather than /home/peter/texmf/tex/biblatex/latex/biblatex.sty, for example. – Joseph Wright Apr 22 '15 at 5:53
  • 4
    Use kpsewhich as kpsewhich --progname=pdflatex biblatex.sty which shows the location where pdflatex finds biblatex.sty. – Akira Kakuto Apr 22 '15 at 9:21
  • Joseph is correct. I botched the installation into my local texmf folder. Fixing the paths issues fixed the problem. And an extra thanks to Akira for pointing me to --progname=pdflatex. That clearly indicated that it was looking to the wrong location. Thus confirming my fears that I was simply being daft :-) – Peter Apr 22 '15 at 14:18
  • @JosephWright An answer? – egreg Oct 3 '15 at 22:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.