-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install libgvc6 for cedar-16 #17
Conversation
Hey there, thanks for the PR (and sorry for the delayed review). Does this change only work on the new stack, or will it work on |
I tried it and I was unable to get it working. It compiled with this fix, but heroku run convert --version showed the built-in imagemagick version, not 6.9.5-10. I did a heroku repo:purge_cache afterwards to resolve an issue with downgrading from Heroku-16 to Cedar-14, in case anyone runs into a strange "missing libIlmImf-2_2.so.22" error in mini-magick. |
Just come across exactly the same issue with a Ruby app using ImageMagick on heroku-16 stack: According to Heroku's docs Moving my app to the old stack as workaround for now. |
add some additional debug echo statements
trying to debug...
I managed to get the buildpack working on heroku-16 by including the GraphViz buildpack, as mentioned in OP's comment. app.json "buildpacks": [
{ "url": "https://github.com/heroku/heroku-buildpack-ruby" },
{ "url": "https://github.com/ello/heroku-buildpack-imagemagick" },
{ "url": "https://github.com/weibeld/heroku-buildpack-graphviz" }
], |
We had the same issue and solved it in the same way: adding the graphviz buildpack. If merging this PR is out of the question to keep compatibility with cedar-14, at the very least please indicate this workaround in the README (in the install instructions). |
Sorry for the delayed response on this one. I'd love to keep compatibility with both stacks if possible - I'll update the README to mention that workaround. Looking at the imagemagick forums I think we could just pass the |
As per ello#17 (comment) t-352130869
I experienced this issue now and I just tried the fork at https://github.com/einSelbst/heroku-buildpack-imagemagick which adds the |
Hi I have tried the workaround of adding Error: Command failed: convert: error while loading shared libraries: libIlmImf.so.6: cannot open shared object file: No such file or directory I think the following code where it crashes. const gm = require('gm').subClass({imageMagick: true});
gm(buffer)
.resize(length*2, length*2)
.quality(77)
.sharpen(0, 3.0)
.gravity('Center')
.extent(length*2, length*2)
.background(colour)
.flatten()
.transparent(colour)
.write(path, (err) => {
if (err) {
return reject(err);
} else {
return resolve(path);
}
}) The same code works just fine on cedar-14. |
As discussed in ello#17.
Finally got it working with our fork of heroku-buildpack-imagemagick that has the An important thing I had to do was to make sure it actually compiled it anew with that flag rather than restore a previous cached build. I did this by adding "v1" to the end of the cache filename in our fork of the buildpack. If you don't do that, you may get an old build that is not compiled I'm not entirely sure if we needed both that flag and to include the EDIT 2019-04-02: Co-workers tried removing the graphviz buildpack and report it works fine without :) |
Fixed with dokku on cedar-16 as follows:
|
Hello, please help am having these error: |
Hello!
I was using this buildpack on Heroku and running in to issues with libgvc6.so not being present (or able to be located properly).
I stole some of https://github.com/weibeld/heroku-buildpack-graphviz to manage installing that dependency, as well as adding the install directory to the
LD_LIBRARY
variable. After doing that, imagemagick was working properly for me on Heroku.(It's completely possible that I had a different issue or that
libgvc6.so
is actually present on Heroku Cedar-16 and I just didn't configure something properly - I wasn't able to find any concrete documentation on whether that library was pre-installed or not, but I can confirm that this PR is working properly on my own app).