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

Graphite #28297

Closed
wants to merge 6 commits into from
Closed

Graphite #28297

wants to merge 6 commits into from

Conversation

apeschar
Copy link
Contributor

@apeschar apeschar commented Aug 15, 2017

Motivation for this change
  • Graphite 1.0.2 is newer.
  • This also fixes carbonRelay and carbonAggregate services, that specified a PIDFile in a non-existent RuntimeDirectory.
  • django_tagging_0_3 was only used by the older Graphite, so can be removed. (I suppose.)
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
    • Linux
  • 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/)
    • Made sure all the services work
  • Fits CONTRIBUTING.md.

@apeschar apeschar requested a review from FRidh as a code owner August 15, 2017 14:21
};

propagatedBuildInputs = with self; [ django django_tagging_0_3 whisper pycairo ldap memcached pytz ];
propagatedBuildInputs = with self; [ django_1_8 (django_tagging.override { django = django_1_8; }) whisper pycairo ldap memcached pytz urllib3 cairocffi scandir pyparsing ];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No overriding within the package set. All Django packages will need to depend just on django, and not on a specific version. If you application needs a specific version, then you need to override the whole Python package set when deploying it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When deploying it -> you mean in the service?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

@cstrahan cstrahan self-assigned this Aug 15, 2017
@apeschar
Copy link
Contributor Author

@FRidh:

  • graphite_web now uses just django and django_tagging
  • django is overridden in the pythonPackages that is used in the service

This means the 'stock' pythonPackages.graphite_web doesn't build, since it relies on Django 1.8. Is that expected?

Copy link
Member

@matthewbauer matthewbauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolve merge conflicts

@FRidh
Copy link
Member

FRidh commented Apr 22, 2018

We are moving Python expressions out of pkgs/top-level/python-packages.nix into pkgs/development/python-modules/<module>/default.nix.

Please move the expression there, and call it from pkgs/top-level/python-packages.nix using callPackage ../development/python-modules/<package> { };.

@FRidh
Copy link
Member

FRidh commented Apr 22, 2018

@apeschar yes, that can be fine.

@apeschar
Copy link
Contributor Author

This was already done in another pull request, so no longer relevant.

@apeschar apeschar closed this Apr 23, 2018
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

4 participants