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

cargo-geiger: 0.9.0 -> 0.9.1 #78804

Merged
merged 1 commit into from Jan 31, 2020
Merged

cargo-geiger: 0.9.0 -> 0.9.1 #78804

merged 1 commit into from Jan 31, 2020

Conversation

evanjs
Copy link
Member

@evanjs evanjs commented Jan 30, 2020

Motivation for this change

https://github.com/rust-secure-code/cargo-geiger/releases/tag/cargo-geiger-0.9.1

Things done
  • add cargo-lock.patch
  • add update-cargo-lock.sh
  • update src owner and homepage to reflect new main repository

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

- add cargo-lock.patch
- add update-cargo-lock.sh
- update src owner and homepage to reflect new main repository
@evanjs evanjs requested a review from Ma27 January 31, 2020 00:48
@Ma27 Ma27 merged commit b7b7fda into NixOS:master Jan 31, 2020
@evanjs evanjs deleted the cargo-geiger/0.9.1 branch January 31, 2020 16:18
anna328p pushed a commit to anna328p/nixpkgs that referenced this pull request Feb 2, 2020
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

2 participants