[MacPorts] #54351: biber of biblatex-biber fails
MacPorts
noreply at macports.org
Mon Jun 19 20:52:34 UTC 2017
#54351: biber of biblatex-biber fails
----------------------------+----------------------------
Reporter: JeffFessler | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.4.1
Keywords: biber biblatex | Port: biblatex-biber
----------------------------+----------------------------
I recently did a selfupdate and after the update the biber command of
biblatex-biber package no longer works. It worked fine for years before
this. I have the current macports version:
biblatex-biber @2.5_2+perl5_24 (active)
(There is a newer version of biber at sourceforge but macports is behind
it seems.)
And the current biblatex version (from tex.log file) is:
Package: biblatex 2016/05/14 v3.4
Here is the error message when running biber:
{{{
Undefined subroutine &Encode::define_alias called at
/opt/local/lib/perl5/vendor_perl/5.24/darwin-thread-multi-2level/Encode.pm
line 102.
Compilation failed in require at /opt/local/lib/perl5/vendor_perl/5.24
/darwin-thread-multi-2level/Encode/Alias.pm line 7.
BEGIN failed--compilation aborted at /opt/local/lib/perl5/vendor_perl/5.24
/darwin-thread-multi-2level/Encode/Alias.pm line 7.
Compilation failed in require at
/opt/local/lib/perl5/vendor_perl/5.24/Biber/Constants.pm line 6.
BEGIN failed--compilation aborted at
/opt/local/lib/perl5/vendor_perl/5.24/Biber/Constants.pm line 6.
Compilation failed in require at
/opt/local/lib/perl5/vendor_perl/5.24/Biber/Internals.pm line 7.
BEGIN failed--compilation aborted at
/opt/local/lib/perl5/vendor_perl/5.24/Biber/Internals.pm line 7.
Compilation failed in require at /opt/local/lib/perl5/5.24/parent.pm line
16.
BEGIN failed--compilation aborted at
/opt/local/lib/perl5/vendor_perl/5.24/Biber.pm line 5.
Compilation failed in require at /opt/local/bin/biber line 17.
BEGIN failed--compilation aborted at /opt/local/bin/biber line 17.
}}}
Any ideas? Or could someone update biber and biblatex to current versions
in macports which might just resolve the issue?
--
Ticket URL: <https://trac.macports.org/ticket/54351>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list