build-pdf: Prevent infinite loop in dblatex #113
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, dblatex goes on an infinite loop if it can't find a font.
Contributor
|
I've added this fix to the master, libsigc++-3-6 and libsigc++-2-12 branches. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a font (usually from texlive) is missing, dblatex goes on an infinite loop and prints no error message (not even in logs).
Issue happened because a dependency update on my side might be missing from dblatex package. In any case, should fail and print something useful, not go on forever. Failing on error really should be a dblatex built-in default, but upstream seems dead, therefore adding safety here.
Should be applied on both 2.12.x and 3.x branches. Tested with release libsigc 2.12.1 and 3.6.0.