Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27474 - [texlive-bin] texlive 2011.2-1 includes a non functional /usr/bin/biber

Attached to Project: Arch Linux
Opened by Kazuo Teramoto (kazuo) - Tuesday, 06 December 2011, 18:03 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Sunday, 11 December 2011, 21:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The texlive-bin on testing includes biber, but in this email <4e71a2db.218b650a.6395.fffff58bSMTPIN_ADDED@mx.google.com> Rémy talked about not including it because of dependencies.

And really running biber give me some unsatisfied perl dependencies:

% biber --help 16:01:51
Can't locate PAR.pm in @INC (@INC contains: /usr/local/perl/lib/site_perl/5.14.1/x86_64-linux-thread-multi /usr/local/perl/lib/site_perl/5.14.1 /usr/local/perl/lib/5.14.1/x86_64-linux-thread-multi /usr/local/perl/lib/5.14.1 /usr/local/perl/lib/site_perl .) at -e line 951.

% biber -v 16:02:03
Can't locate Config.pm in @INC (@INC contains: /usr/local/perl/lib/site_perl/5.14.1/x86_64-linux-thread-multi /usr/local/perl/lib/site_perl/5.14.1 /usr/local/perl/lib/5.14.1/x86_64-linux-thread-multi /usr/local/perl/lib/5.14.1 /usr/local/perl/lib/site_perl .) at -e line 939.
This task depends upon

Closed by  Rémy Oudompheng (remyoudompheng)
Sunday, 11 December 2011, 21:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2011.3-1
Comment by Rémy Oudompheng (remyoudompheng) - Wednesday, 07 December 2011, 23:14 GMT
Latest changes to biblatex requires the biber utility, if I understand correctly.
I see that this is caused to the combination of unwanted stripping and incorrect upstream packaging.

An update is available so I will redo the package when possible.

Loading...