Closed illicitonion closed 7 years ago
While re-publishing an existing binary should actually work in the context of S3, reusing version numbers is error prone. Maybe we could just build an ever-so-slightly-newer. I'll tackle that and reopen.
...interesting. it looks like the issue is that the Vagrant image that we're using (ubuntu/trusty64
) is not compatible with wheezy
, which is probably the root cause of the original bad binary.
Landed via #40: thanks!
The current one requires a newer libc than wheezy has.
Also, fix up the compile script.