Biber not working
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- latex, shell
- Domain
- build-system, devops
Research direction
Start by reproducing the supplied MWE in an Overleaf instance created with the toolkit, then inspect how the container exposes /usr/local/texlive/2024/bin/x86_64-linux/biber and /usr/local/bin/biber. Clear cached files and confirm that compilation invokes biber successfully without the manual symlink; the issue is done when the MWE builds in a fresh toolkit-created instance.
Written by the indexing model from the issue text.
Description
Hi,
I've been playing around with the toolkit lately, and for containers created with the toolkit it seems like biber is not working. I also found a solution, please consider including it as fix into future versions.
MWE:
\documentclass[]{article}
\usepackage[autostyle]{csquotes}
\usepackage[
backend=biber,
style=authoryear-icomp,
sortlocale=de_DE,
natbib=true,
url=false,
doi=true,
eprint=false
]{biblatex}
\addbibresource{biblatex-examples.bib}
\usepackage[]{hyperref}
\hypersetup{
colorlinks=true,
}
%% ##############################
\begin{document}
Lorem ipsum dolor sit amet~\citep{kastenholz}.
At vero eos et accusam et justo duo dolores et ea rebum~\citet{sigfridsson}.
\printbibliography
\end{document}
biblatex-examples.bib is the example file coming with TeXlive 2024, you can also find it here.
This does work with my local vscode setup, but not with overleaf instances created with the toolkit. However, it will work also with said overleaf instance, if the following command is executed inside the container first:
ln -s /usr/local/texlive/2024/bin/x86_64-linux/biber /usr/local/bin/biber
Now if all cached files are cleared and the document is compiled again it'll work as expected.
References:
- Example taken from solution in this thread
- Solution was found in this thread
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 311
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from overleaf/toolkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in overleaf/toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppImage/appimage.github.io#9676 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
YunoHost-Apps/pixelfed_ynh#346 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ChrisTitusTech/dwm-titus#367 ·
Maintainers usually reply within 1 day