On 07.08.2014 01:39, Dirk Bächle wrote:
Hi guys,
[...]
I removed the "/tmp/par-*" folders, and biber seems to work again
(versions of biber and biblatex match locally).
In the next days, I'll let another pull request follow to get my
Buildslaves "green" again
Okay, I created pull reque
Hi Dirk,
While I have no objection I will note that with biblatex version 1.2 the .bcf
file gets generated even for the minimal case of only including the
\usepackage{bib latex}. I am presuming that you have a later version that does
not bother to write out the boilerplate material unless it is
Dirk,
I just realized that my desktop got updated to TeXLive 2013 recently and I now
have biblatex 2.8 and biber 1.8 available (previously I was using versions 2.2
and 1.2 respectively). With those versions I still get the .bcf file generated.
What versions did your system end up with? I am gu
Rob,
On 08.08.2014 00:04, Managan, Rob wrote:
Dirk,
I just realized that my desktop got updated to TeXLive 2013 recently
and I now have biblatex 2.8 and biber 1.8 available (previously I was
using versions 2.2 and 1.2 respectively). With those versions I still
get the .bcf file generated. W
Dirk,
Thanks for the info. I will assume that the absence of the .bcf file is due to
the older versions of biblatex and biber. It makes sense to have the test
tailored for old versions and yet still work with newer ones. Your change
should allow for that. I tested it on my system and it does pa
Dirk,
Merged.
Let's see how that works!
Thanks!
-Bill
On Thu, Aug 7, 2014 at 2:00 PM, Dirk Bächle wrote:
> On 07.08.2014 01:39, Dirk Bächle wrote:
>
> Hi guys,
> [...]
>
> I removed the "/tmp/par-*" folders, and biber seems to work again
> (versions of biber and biblatex match locally).
> In
