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
pythonPackages.elasticsearch-curator: fix on staging #41603
Conversation
As for |
@@ -5,12 +5,12 @@ | |||
|
|||
buildPythonPackage rec { | |||
pname = "certifi"; | |||
version = "2018.1.18"; | |||
version = "2018.4.16"; | |||
name = "${pname}-${version}"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this line. name
is set automatically.
@danbst Please squash the last commit into the appropriate one and format your commit messages according to the contributing guidelines, i.e. as the title of this PR. @GrahamcOfBorg build python2.pkgs.certifi python3.pkgs.certifi python2.pkgs.elasticsearch-curator python3.pkgs.elasticsearch-curator |
Success on aarch64-linux (full log) Attempted: python2.pkgs.certifi, python3.pkgs.certifi, python2.pkgs.elasticsearch-curator, python3.pkgs.elasticsearch-curator Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: python2.pkgs.certifi, python3.pkgs.certifi, python2.pkgs.elasticsearch-curator, python3.pkgs.elasticsearch-curator Partial log (click to expand)
|
Also rebase to staging. |
Staging already has elasticsearch-curator: 5.5.4. We should include the certifi bump in the next package set update however. |
Oh, indeed! And it fails to build exactly because
|
rebased over staging which dropped curator update - staging has newer one |
Please get rid of the superfluous commits. |
Also, @FRidh is that a direct requirement to have base16 encoded sha256 hash? |
You can take the base16 one from PyPI or leave it as is, it doesn't matter very much. However, the hash from PyPI makes it a bit easier to confirm that the right archive is used. |
@dotlambda done! |
Commit message still not formatted correctly :( |
@dotlambda aye, sorry, forgot the colon. Do we have automated tools to process/aggregate commit messages? |
Only @GrahamcOfBorg which processes commit messages to run the appropriate builds. |
Motivation for this change
Fix build of
elasticsearch-curator
.cc @basvandijk
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)