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

Installing 'nodejs' installs '7f' library instead #7091

Closed
wemrysi opened this issue Mar 30, 2015 · 3 comments
Closed

Installing 'nodejs' installs '7f' library instead #7091

wemrysi opened this issue Mar 30, 2015 · 3 comments

Comments

@wemrysi
Copy link

wemrysi commented Mar 30, 2015

I'm not sure if this is an issue with the nodejs package, the nodejs-7f package or with nix itself, but in the current version of the unstable channel, nix-env -i nodejs installs the nodejs-7f library and not node itself.

I suspect this has something to do with the 7f library beginning with a number and that number being greater than the existing versions of the nodejs package, the highest of which is currently 0.12.0, however my knowledge of nix internals is nonexistent, so this is pure speculation.

The following terminal transcript illustrates the issue

~ ❯❯❯ nix-channel --list nixpkgs
http://nixos.org/channels/nixpkgs-unstable

~ ❯❯❯ nix-channel --update
downloading Nix expressions from ‘http://nixos.org/releases/nixpkgs/nixpkgs-15.05pre59184.e07ea5c/nixexprs.tar.xz’...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current Dload  Upload   Total   Spent    Left  Speed
100 4826k  100 4826k    0     0  3319k      0  0:00:01  0:00:01 --:--:-- 3321k
unpacking channels...

~ ❯❯❯ nix-env -qaP '.*nodejs.*'
nixos.pkgs.nodejs                                 nodejs-0.10.33
nixos.pkgs.nodejs-unstable                        nodejs-0.11.13
nixpkgs.nodejs-unstable                           nodejs-0.11.13
nixpkgs.nodejs                                    nodejs-0.12.0
nixpkgs.nodePackages.7f                           nodejs-7f-1.1.3
nixpkgs.nodePackages.almond                       nodejs-almond-0.3.0
nixpkgs.nodePackages.amdefine                     nodejs-amdefine-0.1.0
nixpkgs.nodePackages.ansi-remover                 nodejs-ansi-remover-0.0.2
nixpkgs.nodePackages.assert                       nodejs-assert-1.3.0

***rest of output elided***

~ ❯❯❯ nix-env -i nodejs
installing ‘nodejs-7f-1.1.3’  <-- this is a library, not a version of nodejs

~ ❯❯❯ nix-env -iA nixpkgs.nodejs
replacing old ‘nodejs-7f-1.1.3’
installing ‘nodejs-0.12.0’
building path(s) ‘/nix/store/nyaadw4hn1pcbkmvlp7rz8y34qlxb4mc-user-environment’
created 1512 symlinks in user environment
@lucabrunox
Copy link
Contributor

Yes that name must not have -7f.

@flosse
Copy link
Contributor

flosse commented Apr 3, 2015

yes, I think we can safely remove the 7f package, it's not used by any other package.

@wemrysi
Copy link
Author

wemrysi commented Apr 3, 2015

Would it make sense to rename it instead? Maybe to lib7f or sevenf? Are there any precedents or guidelines for how to name packages that begin with a number?

@flosse flosse mentioned this issue Jan 5, 2016
@vcunat vcunat closed this as completed in 45ade79 Jan 5, 2016
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

No branches or pull requests

3 participants