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

Xenial support #4

Open
kvz opened this issue Sep 18, 2016 · 5 comments
Open

Xenial support #4

kvz opened this issue Sep 18, 2016 · 5 comments

Comments

@kvz
Copy link

kvz commented Sep 18, 2016

Hey there, thanks a lot for this project!

I'm currently running into this issue:

TASK [/srv/current/core/node_modules/frey/roles/nix/v1.0.1 : Download Nix] *****
fatal: [54.209.132.103]: FAILED! => {"failed": true, "msg": "'dict object' has no attribute u'xenial'"}
fatal: [52.91.125.180]: FAILED! => {"failed": true, "msg": "'dict object' has no attribute u'xenial'"}
fatal: [54.162.210.238]: FAILED! => {"failed": true, "msg": "'dict object' has no attribute u'xenial'"}

Are there any plans of supporting Ubuntu's latest LTS?

Kind regards,
Kevin

@ktosiek
Copy link
Owner

ktosiek commented Sep 18, 2016

Not from me, as I'm not using this role anymore.
I'll be glad to review a PR, it should be enough to add the right URLs to nix_package_urls here: https://github.com/ktosiek/ansible-nix/blob/master/defaults/main.yml#L6

Actually it wouldn't hurt to bump the nix version too, as this role is still using 1.8 and the current one is 1.11

@kvz
Copy link
Author

kvz commented Sep 18, 2016

Thanks, I looked into it but it seems there are no official debs for it (NixOS/nix#891 (comment)). This would mean falling back to the install script but I'm hesitant to put such moving parts into a role.

@ktosiek
Copy link
Owner

ktosiek commented Sep 18, 2016

Using the script is not that bad, but you'll still need to setup multi-user if you want it. You can copy a specific version of the install script into a role if you want to control that :-)

The package is basically just bootstraping + some config anyway, as you'll probably be using nix-managed nix soon after installing the package. And without setting up multi-user, the Nix from .deb can only be used by root.

@kvz
Copy link
Author

kvz commented Sep 19, 2016

If anyone wants to submit a PR for this, I just got a link to this deb http://hydra.nixos.org/job/nix/maintenance/deb_ubuntu1604x86_64/latest in NixOS/nix#891 (comment) (I personally don't have the time currently)

@mstone
Copy link

mstone commented Apr 18, 2017

FWIW, I solved this problem by pinning my desired nix version, building the necessary debs from source using a nixexpr like this one so that I didn't have to pay any further attention to the state of which job outputs Hydra has or has not cached:

with import <nixpkgs> {};
let
  nix = fetchFromGitHub {
    owner = "nixos";
    repo = "nix";
    rev = "1.11.8";
    sha256 = "1qlddlzkpavhsrb7h3cyqhif5qc2qhkhjwnv4pbzg9hamqbd45wc";
  };
in
  (import "${nix}/release.nix" {
    officialRelease = true;
  }).deb_ubuntu1404x86_64

and then adapting the first task in ktosiek's ansible-nix role to use the copy module instead of the get_url module that it uses today.

(NB: for Xenial debs, you would presumably need to replace "deb_ubuntu1404x86_64" with, e.g., "deb_ubuntu1604x86_64")

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