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

nvidia_x11: 2019-11.1 #73167

Merged
merged 2 commits into from Dec 1, 2019
Merged

nvidia_x11: 2019-11.1 #73167

merged 2 commits into from Dec 1, 2019

Conversation

eadwu
Copy link
Member

@eadwu eadwu commented Nov 10, 2019

Motivation for this change
Things done
  • 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 nix-review --run "nix-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.
Notify maintainers

cc @

@eadwu
Copy link
Member Author

eadwu commented Nov 10, 2019

Reused old url since for some reason some revisions don't exist as tags in the Github repository.

@eadwu eadwu mentioned this pull request Nov 10, 2019
10 tasks
@eadwu eadwu changed the title nvidia_x11: 2019 11.1 nvidia_x11: 2019/11.1 Nov 11, 2019
@eadwu eadwu changed the title nvidia_x11: 2019/11.1 nvidia_x11: 2019-11.1 Nov 11, 2019
@veprbl
Copy link
Member

veprbl commented Nov 24, 2019

@GrahamcOfBorg eval

@veprbl
Copy link
Member

veprbl commented Nov 24, 2019

cc @baracoder

@veprbl
Copy link
Member

veprbl commented Nov 24, 2019

@eadwu I believe the eval error is not spurious. I am not sure where it comes from.

@eadwu
Copy link
Member Author

eadwu commented Nov 24, 2019

Supposedly it comes from bumblebee.nix and specifically from nvidia_x11.useGLVND though I have no idea how just changing the versions and hashes results in something unrelated popping up.

@baracoder
Copy link
Contributor

How can I reproduce the eval check locally?

@7c6f434c
Copy link
Member

7c6f434c commented Nov 30, 2019 via email

@srhb
Copy link
Contributor

srhb commented Nov 30, 2019

You're no longer applying generic in the right place because you rewrote the expression for stable -- hence the null. If you reuse the existing structure, everything evals just fine.

Actually, the issue is the nulling at the top of this package. You'll have to flip your if-then-else, and all is good.

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