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

secretstorage init at version 2.3.1 #28916

Closed
wants to merge 3 commits into from
Closed

Conversation

teto
Copy link
Member

@teto teto commented Sep 3, 2017

Motivation for this change

A program I use (i3pystatus) has modules depending on this python module (via the keyring python module).
https://pypi.python.org/pypi/SecretStorage

I've tested it through:
nix-shell -p python36Packages.keyring -p python36Packages.secretstorage -I ~/nixpkgs --command "keyring set gmail password"
This is my first PR to nixpkgs so this might need more work. I'll try to look into the sandboxing thing.

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/)
  • Fits CONTRIBUTING.md.

@teto teto requested a review from FRidh as a code owner September 3, 2017 02:52
propagatedBuildInputs = [ dbus-python cryptography ];
doCheck = false;

meta = with stdenv.lib; {
Copy link
Member

Choose a reason for hiding this comment

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

Did you want to add yourself as maintainer?

Copy link
Member Author

Choose a reason for hiding this comment

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

not really. I am not proficient with nixos nor I am knowledgeable about dbus/keyring stuff. If it's mandatory, I can put myself as a best effort thing.

Copy link
Member

Choose a reason for hiding this comment

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

I think it is mandatory, but maybe someone else will want to be a maintainer. However, it shouldn't be too hard to be a maintainer, it should mainly just be about updating the revision and sha256 whenever there's a new release, and checking to see if it builds/works.

src = pkgs.fetchFromGitHub {
owner = "mitya57";
repo = "secretstorage";
rev = "2636a47b45aff51a21dfaf1cbd9f1f3c1347f7f4";
Copy link
Member

Choose a reason for hiding this comment

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

This should just be "${version}". And note the sha256 will therefore also change.

sha256 = "1sjd2jjbxgkkxyrfwx89x0hsnn39w2cr2qkxbg1iz52znr4sqism";
};

postPatch = "patchShebangs .";
Copy link
Member

Choose a reason for hiding this comment

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

why is this needed?

Copy link
Member Author

Choose a reason for hiding this comment

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

this is a leftover from the derivation I took inspiration from. It should not be necessary.

@FRidh FRidh self-assigned this Sep 4, 2017
@FRidh
Copy link
Member

FRidh commented Sep 6, 2017

Thank you. Added it to #29009.

@FRidh FRidh closed this Sep 6, 2017
@teto teto deleted the secretstorage branch September 6, 2017 14:26
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

5 participants