-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fix tarball #77
Fix tarball #77
Conversation
Don't stress about the failed CI. Looks like I broke develop branch. |
also, Travis seems to be dead? |
Travis build fired off but it isn't reporting here. |
Looks like I broke the travis credentials recently. Will look into that, too. |
@jeffdaily did you have time to bump the version and cut a new release? |
Didn't have time yesterday to tag and release. Hopefully by end of today. |
Thanks Jeff! |
@jeffdaily you seem to be missing the bootstrapped tarballs |
yup. been too long since I last deployed. trying to fix this. auth failed when trying to push assets from travis to github. |
pardon the delay. had auth issues for both travis and appveyor release deployment. retagged with updated auth tokens for each. new release (same version number 2.4.2). Just waiting for assets to finish building. |
done |
Hi @jeffdaily
your latest tarballs are missing a header. I've added it in
Makefile.am
and changed Travis to usemake distcheck
, which catches such issues (it tries to build the package out-of-source using the produced tarball). Could we cut a new release after merging my fixes?