Skip to content
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

CURL_OPENSSL_3 on heroku/stack18 #2

Open
ryanto opened this issue Nov 19, 2018 · 6 comments
Open

CURL_OPENSSL_3 on heroku/stack18 #2

ryanto opened this issue Nov 19, 2018 · 6 comments

Comments

@ryanto
Copy link

ryanto commented Nov 19, 2018

Hi there!

I've tried installing this build pack on heroku stack18 (https://devcenter.heroku.com/articles/heroku-18-stack) and receive the following error when running mediainfo:

heroku run bash

$ mediainfo
mediainfo: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found
(required by mediainfo)
@tadast
Copy link

tadast commented Jan 8, 2019

@ryanto I'm facing the same issue, if you've ever managed to get it working, would you mind sharing the solution?

@tadast
Copy link

tadast commented Jan 8, 2019

What I've discovered so far is that the newest (heroku-18 at the time of writing this) stack does not have libcurl3 which is required by the mediainfo binary in this pack. You can either use an older stack (e.g. heroku-16) or fork the repo and update the mediainfo binary to work with libcurl4 (haven't tried the latter approach)

@ryanto
Copy link
Author

ryanto commented Jan 8, 2019

@tadast I ended up downgrading to heroku-16.

Do you have instructions for how to update mediainfo with libcurl4?

@tadast
Copy link

tadast commented Jan 8, 2019

I haven't tried it, but you can check out the forks on this repo, the last few commits here should provide some guidance. This branch also doesn't work on on heroku-18, so it probably needs another binary built with libcurl4

@blimpage
Copy link

I ran into this same problem after upgrading from heroku-16 to heroku-20, and was able to get a working version of mediainfo by installing it via heroku-buildpack-apt, following the advice of this Heroku help article: How do I install additional software packages that my application requires?

@nikita-kazakov
Copy link

I just went through the same error and found a fix for it through blimpage's solution using heroku-buildpack-apt above. Here's exactly what I did to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants