Pin libjpegturbo to 2.x #390
Merged
Conversation
This file contains 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
joecorall
force-pushed
the
issue-389-libjpeg
branch
from
5832757 to
58188dc
Compare
joecorall
changed the title
joecorall
force-pushed
the
issue-389-libjpeg
branch
from
f9265a3 to
ac417ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #389
The cantaloupe image was installing libjpeg-turbo with apk, which installs libjpeg-turbo 3.x. However, that library wasn't getting loaded in cantaloupe, so cantaloupe was falling back to
Java2dProcessorfor jpgsOnce the package was installed properly, we discovered cantaloupe does not work with 3.x. With libjpeg-turbo 3.x installed correctly in cantaloupe it was throwing another error
So I rolled back to
2.0.2as the cantaloupe docs recommend and saw the errors went away. Then bumped to the latest version on the 2.x branch:2.1.5.1and see cantaloupe loaded it OK