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

elasticsearch-curator-5.4.1 on release-17.09 #33760

Merged

Conversation

basvandijk
Copy link
Member

Motivation for this change

@orivej I would like to use elasticsearch-curator on 17.09 so I cherry picked the commits from #32905 on release-17.09.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

basvandijk and others added 4 commits January 12, 2018 00:52
Needed by elasticsearch-curator.

(cherry picked from commit b513fc7)
because it requires python.pkgs.elasticsearch 1.x.y, which is compatible only
with the ancient Elasticsearch 1.

(cherry picked from commit f0c4bea)
@basvandijk
Copy link
Member Author

@FRidh thanks for the review. I think it's better if we first make these changes on master and then cherry-pick them on release-17.09. I can do that if you don't beat me to it.

@FRidh
Copy link
Member

FRidh commented Jan 14, 2018

@basvandijk ah, I had missed this was for 17.09.

@basvandijk
Copy link
Member Author

@FRidh I cherry-picked #33774 into this PR. It should be ready to merge now.

@FRidh
Copy link
Member

FRidh commented Jan 14, 2018

Actually, not yet. Implicit name attribute was added after branching off (#31173). That means, either name should be added again, or we should backport 78ed9da. We should go for the latter as it is harmless.

@FRidh
Copy link
Member

FRidh commented Jan 14, 2018

Pushed eb2e3be.

@FRidh FRidh merged commit 1c104f9 into NixOS:release-17.09 Jan 14, 2018
@basvandijk
Copy link
Member Author

Woops we pushed eb2e3be at the same time causing it to occur twice in release-17.09. But that doesn't really matter. Thanks for help and merge!

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

Successfully merging this pull request may close these issues.

None yet

4 participants