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

Please make the build reproducible #289

Merged
merged 1 commit into from Feb 18, 2018

Conversation

lamby
Copy link
Contributor

@lamby lamby commented Feb 17, 2018

Whilst working on the Reproducible Builds effort [0], we noticed
that redisearch could not be built reproducibly. This is because
it links (etc.) in filesystem ordering which is non-determinstic.

Adding some $(sort ...) calls fixes this for me. You can test this
by using our "disorderfs" tool to mangle the directory ordering.

[0] https://reproducible-builds.org/

Whilst working on the Reproducible Builds effort [0], we noticed
that redisearch could not be built reproducibly. This is because
it links (etc.) in filesystem ordering which is non-determinstic.

Adding some $(sort ...) calls fixes this for me. You can test this
by using our "disorderfs" tool to mangle the directory ordering.

 [0] https://reproducible-builds.org/
@dvirsky
Copy link
Contributor

dvirsky commented Feb 18, 2018

Just out of curiosity - what situation makes the build (without your fix) fail?

@lamby
Copy link
Contributor Author

lamby commented Feb 18, 2018

Fail? The build is not failing, it does just not produce the same binary every time. :)

@dvirsky
Copy link
Contributor

dvirsky commented Feb 18, 2018 via email

@dvirsky dvirsky merged commit cc71686 into RediSearch:master Feb 18, 2018
@lamby
Copy link
Contributor Author

lamby commented Feb 18, 2018

Thanks!

@lamby lamby deleted the reproducible-build branch February 18, 2018 12:53
@lamby
Copy link
Contributor Author

lamby commented Feb 21, 2018

Any chance of a release with this in? :)

@dvirsky
Copy link
Contributor

dvirsky commented Feb 21, 2018

@lamby sure, we've squashed a potential crash as well, so I guess a new bug fix release is due. I'll try to release it tomorrow.

@lamby
Copy link
Contributor Author

lamby commented Feb 28, 2018

Gentle ping on this @dvirsky :)

@dvirsky
Copy link
Contributor

dvirsky commented Feb 28, 2018

Ooops, forgot about it :) I'll do it today hopefully.

@dvirsky
Copy link
Contributor

dvirsky commented Feb 28, 2018

@lamby 1.0.8 is out

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

Successfully merging this pull request may close these issues.

None yet

2 participants