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

collision between groovy LICENSE openjdk LICENSE #19872

Closed
pmahoney-raise opened this issue Oct 25, 2016 · 7 comments
Closed

collision between groovy LICENSE openjdk LICENSE #19872

pmahoney-raise opened this issue Oct 25, 2016 · 7 comments

Comments

@pmahoney-raise
Copy link

Issue description

There is a conflict installing groovy and openjdk in the same nix profile. The LICENSE file exists at the toplevel; it should probably be located elsewhere for both packages.

Steps to reproduce

$ nix-env -iA nixpkgs.groovy nixpkgs.openjdk
...
collision between ‘/nix/store/mjd2gsnx14q6n05f8fwjk0ry6kms0m40-groovy-2.4.6/LICENSE’ and ‘/nix/store/g26vd7kl13vsfpghs9pks4avrwl8drng-openjdk-7u60b30/LICENSE’; use ‘nix-env --set-flag priority NUMBER PKGNAME’ to change the priority of one of the conflicting packages

Technical details

  • System: OS X 10.10.5 Yosemite
  • Nix version: (run nix-env --version) nix-env (Nix) 1.11.4
  • Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) 17.03pre94294.a057dfc
@Mic92
Copy link
Member

Mic92 commented Oct 25, 2016

I think you could make a pull request, where you delete LICENSE in both package, within postInstall.

@NeQuissimus
Copy link
Member

May be related to what I am seeing with bind in #19761

@sternenseemann
Copy link
Member

Wouldn't it be more sensible to move it to, say, ${out}/share/<pkgname>/LICENSE in postInstall?

@vcunat
Copy link
Member

vcunat commented Oct 29, 2016

Yes, this stuff should not be installed in top level.

@sternenseemann
Copy link
Member

sternenseemann commented Oct 29, 2016

Okay, I will fix that. (Can someone assign me?)

@NeQuissimus
Copy link
Member

I think only people with commit access can be assigned. But it's yours :)

@calvertvl
Copy link
Contributor

@pSub: It looks like this can be closed, unless you want to cherry pick to 16.09

@pSub pSub closed this as completed Mar 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants