I got the _module.args.pkgs to (almost) work but I think it somehow
mixes up the two nixpkgs versions (running on unstable, overriding
_module.args.pkgs to stable):
error: attribute ‘ipset’ missing, at
Hi Rob Nicolas,
thank you for your suggestions.
The option -I nixpkgs=/path/to/your/nixpkgs sets the nixpkgs globally
for nixops. That is not what I need.
I have tried using nixops set-attrs, but that is also doesn't allow me
to use stable for one machine and unstable for the other.
Maybe
The problem of using the `_module.args.pkgs` is that you have the
NixOS module system of the nix-channel, but the package resolution of
the version that you specified. The error that you are seeing is that
the latest module might use a package which got packaged/renamed
recently.
Strangely
Hi Tomas,
you can use -I nixpkgs=/path/to/your/nixpkgs when using nixops. You
can also make it persistent using 'nixops create/modify', the nix path
will be stored in the nixops database, and you can inspect it with
'nixops info'.
Cheers,
Rob
On Fri, Jul 24, 2015 at 3:10 PM, Tomas Hlavaty
Hi,
in nixops, how can i specify a nix-channel per machine? Or any other
way to have different machines running different versions of nixos?
Thank you,
Tomas
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Otherwise, if you are using the latest master of NixOS, then you
should be able to define which set of packages you are interested in
within the module system, while using the modules from the latest
NixOS.
{ config, lib, ... }:
{
config = {
_module.args.pkgs = lib.mkForce (import
