-
Notifications
You must be signed in to change notification settings - Fork 346
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
Update binaries to the 0.12.1 #15
Conversation
Hold off on this. The linux binaries don't include libjpeg so they would blow up on heroku. Looking for a fix. |
+1 for updating to the latest binary. In my project, we need the new version for pagination in pdf. @tbugai Thanks for your PR. I just downloaded the binary and replaced the old one in the gem. It seems working fine. |
This should be good to go. Can we get it merged and an new gem released @zakird? |
+1
|
@butzopower do you have any concerns |
I've replaced the binary file in the locally installed gem with @tbugai binary, renamed it, and it works. |
Hi, This binary need dependent libraries. Ubuntu 14.04 64bit
Ubuntu 14.04 32bit
CentOS 6.3 64bit
CentOS 6.3 32bit
OMG, dependent libraries does not exist in the standard RPM repositories of CentOS... Do you have a solution? |
Did you install libjpeg on your 32 bit CentOS 6.3 system? Maybe there is another version like libjpeg.so.62 installed. Maybe, you could try creating a symbolic link to the other library.
On Thu, Sep 11, 2014 at 11:24 AM, Hiroshi Hoaki notifications@github.com
Hermes Ojeda Ruiz |
@zakird @tbugai I think this all looks fine. I currently don't have any projects that use wkhtmltopdf, but I know a team that does and I'll have them try this out before we do a release on rubygems. I think we'll want to create a README and let people know what libraries they'll need for their distribution. Also, as I'm not sure of any backwards incompatible changes that may have been made in the wkhtmltopdf binary from 0.9 to 0.12, it may be good that we note in our README that if people are seeing issues they can point to the old gem. |
Update binaries to the 0.12.1
I tried:
It does not seem to work because the version is different... |
@rewish |
Update binaries to the 0.12.1
Update binaries to the 0.12.1
Update binaries to the 0.12.1
Update binaries to the 0.12.1
This PR upgrades the binaries to be version 0.12.1. This is a stop gap to get things rolling until a better update process (per the conversation in issue #13).