Skip to content

stdenv: fix "grep: invalid range" #25501

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

Merged
merged 1 commit into from
May 4, 2017
Merged

Conversation

lheckemann
Copy link
Member

Motivation for this change

Fix the unnecessary error message, and the logic that the grep command is actually part of (presumably). @vcunat what's it actually meant to do? For now all it does is print "grep: invalid range" because the regex is actually malformed, so grep returns an error code and the if condition will never evaluate to true.

Things done

Not tested at all, because it causes a mass rebuild.

  • 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 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.

Sorry, something went wrong.

@mention-bot
Copy link

@lheckemann, thanks for your PR! By analyzing the history of the files in this pull request, we identified @vcunat, @lethalman and @dezgeg to be potential reviewers.

@Mic92 Mic92 merged commit 5fa8a5c into NixOS:staging May 4, 2017
@vcunat
Copy link
Member

vcunat commented May 4, 2017

Thanks, you got the intended meaning right. I assumed the ranges were more permissive.

@lheckemann lheckemann deleted the stdenv-grep-range branch May 5, 2017 07:34
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