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

procps-ng: updated project location #37731

Merged
merged 2 commits into from Mar 24, 2018
Merged

procps-ng: updated project location #37731

merged 2 commits into from Mar 24, 2018

Conversation

typetetris
Copy link
Contributor

@typetetris typetetris commented Mar 24, 2018

Motivation for this change
  • use the real project location and not some sf.net mirror
  • the meta attribute shouldn't point users to a website cluttered
    with ads (sf.net) where they probably just follow the link
    to the real project location
  • adapted the build to the new archive
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"
    My box didn't have nix 2 and with some nix-shell -p nixUnstable tried to build all derivations, which
    seemed unlikely to be caused by this.
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

I also offer to take maintainership of procps-ng, if so desired.

owner ="procps-ng";
repo = "procps";
# should be tag v3.3.12, but the sha is immutable of course, which is desirable
rev = "e0784ddaed30d095bb1d9a8ad6b5a23d10a212c4";
Copy link
Member

Choose a reason for hiding this comment

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

I'd still use

rev = "v${version}";

Git tags are meant not to be moved; we check the hash of the output anyway. It will also be less error-prone on updates.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok, will add that

@vcunat
Copy link
Member

vcunat commented Mar 24, 2018

Otherwise I like the changes. EDIT: but it will need to target the staging branch instead, due to rebuilding thousands of packages.

@typetetris
Copy link
Contributor Author

Should I take maintainership of procps-ng, too?

- use the real project location and not some sf.net mirror
- the meta attribute shouldn't point users to a website cluttered
  with ads (sf.net) where they probably just follow the link
  to the real project location
- adapted the build to the new archive
@vcunat
Copy link
Member

vcunat commented Mar 24, 2018

@typetetris: yes. The main implications are getting e-mails from hydra.nixos.org when build status changes and being a point of contact about the package.

@typetetris
Copy link
Contributor Author

I guessed that much and am willing to do that. Should I add the commits to this pr too?

@vcunat
Copy link
Member

vcunat commented Mar 24, 2018

Yes, let's merge that together.

@vcunat vcunat changed the base branch from master to staging March 24, 2018 13:50
@vcunat vcunat self-assigned this Mar 24, 2018
@vcunat vcunat merged commit 59a9165 into NixOS:staging Mar 24, 2018
vcunat added a commit that referenced this pull request Mar 24, 2018
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

3 participants