Re: [Nix-dev] Building 32bit java on 64bit system
On 10/31/2013 01:51 AM, shacka wrote: I don't need to have both in my $PATH, I just need 32bit version to get installed in order to run third-party binary that is 32bit. I'm getting the following error when trying to run the command you provided: error: attribute `pkgsi686Linux' in selection path `pkgsi686Linux' not found I don't understand why it says that. The attribute *is* there in current master -- it has been there for very long time, and the command itself works for me. (I must say I'm a little confused with notion of attributes, is there any good description describing them available?) In nixpkgs we don't have just packages, but many other things (e.g. functions), as it's written in a full language (called nix). Things in there are denoted by these attribute names. They have to be unique, but e.g. can be hierarchical. You can find details in the nix manual http://hydra.nixos.org/job/nix/trunk/tarball/latest/download-by-type/doc/manual Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Building 32bit java on 64bit system
On Thursday, October 31, 2013 08:47:31 AM Vladimír Čunát wrote: On 10/31/2013 01:51 AM, shacka wrote: I don't need to have both in my $PATH, I just need 32bit version to get installed in order to run third-party binary that is 32bit. I'm getting the following error when trying to run the command you provided: error: attribute `pkgsi686Linux' in selection path `pkgsi686Linux' not found I don't understand why it says that. The attribute *is* there in current master -- it has been there for very long time, and the command itself works for me. Doesn't work for me either. Had to do: nix-env -iA nixos.pkgs.pkgsi686Linux.jre Must be a slightly different setup ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Building 32bit java on 64bit system
Hi, On 31/10/13 09:13, phree...@yandex.ru wrote: Doesn't work for me either. Had to do: nix-env -iA nixos.pkgs.pkgsi686Linux.jre Must be a slightly different setup That is in fact the default setup. FWIW, you can also do: $ nix-env -i openjre --argstr system i686-linux I.e. install by package name rather than by attribute name. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Building 32bit java on 64bit system
Thanks guys! That worked! On Thu, Oct 31, 2013 at 3:43 AM, Eelco Dolstra eelco.dols...@logicblox.comwrote: Hi, On 31/10/13 09:13, phree...@yandex.ru wrote: Doesn't work for me either. Had to do: nix-env -iA nixos.pkgs.pkgsi686Linux.jre Must be a slightly different setup That is in fact the default setup. FWIW, you can also do: $ nix-env -i openjre --argstr system i686-linux I.e. install by package name rather than by attribute name. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Juniper VPN on nixos
Hi, my company uses Juniper Networks VPN for remote access and I'm trying to get it working on my 64bit nixos setup. Did anyone dealt with this? Thanks, Andrii ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] type for path-or-string ?
Hi all,
I used to put local/relative paths in my openssh.authorizedKeys.keyFiles.
Basically, I store the public ssh keys in the git repo that contains
my configuration.nix so I point to them by [ ./laptop.pub ./server.pub
]
However, the type for this option got set to listOf str, breaking my setup.
Changing to ./laptop.pub of course won't work. I tried
${./laptop.pub} as well, but that moves the file to the nix store,
then complains about the path referencing other paths.
So I changed the type of this option to listOf path locally.
Is there a way to allow both? Something like listOf (Either str path)?
Thanks,
Mathijs
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] NixOS 13.10
Hi, I'm pleased to announce the availability of the first stable branch of NixOS, namely 13.10 (a.k.a Aardvark)! The purpose of this branch is to receive only conservative changes, such as bug fixes, safe minor package upgrades and new packages [1]. This is important for people who want to use NixOS in a production environment: you do want to get (security) fixes, but you don't want to be afraid of the system changing in fundamental ways, as may be the case on the master branch. Note that NixOS 13.10 is a branch, not a release in the sense of a static revision. Just like the NixOS master branch, it receives updates, just safer ones. The idea is to maintain this branch at least until the next stable branch (14.04?) is created. The 13.10 branch lives here in GitHub: https://github.com/NixOS/nixpkgs/tree/release-13.10 It also has an associated channel: http://nixos.org/channels/nixos-13.10 (Notice that versions of releases in the 13.10 channel have no pre string, indicating they're stable versions, such as 13.10.35427.6fda96b.) If you want to switch an existing machine from the nixos-unstable channel over to the 13.10 channel, just do: $ nix-channel --add http://nixos.org/channels/nixos-13.10 nixos After this, subsequent calls to nixos-rebuild switch --upgrade will fetch from the nixos-13.10 channel. See here for details on switching between NixOS channels: http://nixos.org/nixos/manual/#sec-upgrading Like the nixos-unstable channel (which gets build from the master branch), the 13.10 channel is updated only after Hydra has built all packages and all release-critical tests have succeeded. The Hydra jobset is: http://hydra.nixos.org/jobset/nixos/release-13.10 and the status of the release-critical jobs can be seen here: http://hydra.nixos.org/job/nixos/release-13.10/tested#tabs-constituents The plan for maintaining the branch is that it will primarily receive cherry-picked commits from master. Other than that, doing a stable branch is an experiment, and we'll have to see what the best way to do it is. Any feedback/suggestions are welcome. On that topic, now is probably a good time to start thinking about what the next release should look like, in terms of features. If you have any features (especially potentially high-impact ones like upgrading GCC) that you would like to see, please create GitHub issues for them, and add them to the 14.0x milestone: https://github.com/NixOS/nixpkgs/issues?milestone=4state=open [1] New major versions of existing packages are also fine as long as they are marked as lowPrio in all-packages.nix. That is, nix-env -i package should continue to install the old version. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] type for path-or-string ?
Hi, On 31/10/13 23:37, Mathijs Kwik wrote: So I changed the type of this option to listOf path locally. Is there a way to allow both? Something like listOf (Either str path)? Hm yes, that would be useful. But in the meantime we should change it back to listOf unspecified. I actually made it listOf path first, but then I realised you can have strings like ~/.ssh/authorized_keys in there. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS 13.10
Congratulations on another great milestone :) It will be interesting to see how this stable experiment goes. But together with the new nixos-rebuild profiles, I think this will be very smooth. On Thu, Oct 31, 2013 at 11:59 PM, Eelco Dolstra eelco.dols...@logicblox.com wrote: Hi, I'm pleased to announce the availability of the first stable branch of NixOS, namely 13.10 (a.k.a Aardvark)! The purpose of this branch is to receive only conservative changes, such as bug fixes, safe minor package upgrades and new packages [1]. This is important for people who want to use NixOS in a production environment: you do want to get (security) fixes, but you don't want to be afraid of the system changing in fundamental ways, as may be the case on the master branch. Note that NixOS 13.10 is a branch, not a release in the sense of a static revision. Just like the NixOS master branch, it receives updates, just safer ones. The idea is to maintain this branch at least until the next stable branch (14.04?) is created. The 13.10 branch lives here in GitHub: https://github.com/NixOS/nixpkgs/tree/release-13.10 It also has an associated channel: http://nixos.org/channels/nixos-13.10 (Notice that versions of releases in the 13.10 channel have no pre string, indicating they're stable versions, such as 13.10.35427.6fda96b.) If you want to switch an existing machine from the nixos-unstable channel over to the 13.10 channel, just do: $ nix-channel --add http://nixos.org/channels/nixos-13.10 nixos After this, subsequent calls to nixos-rebuild switch --upgrade will fetch from the nixos-13.10 channel. See here for details on switching between NixOS channels: http://nixos.org/nixos/manual/#sec-upgrading Like the nixos-unstable channel (which gets build from the master branch), the 13.10 channel is updated only after Hydra has built all packages and all release-critical tests have succeeded. The Hydra jobset is: http://hydra.nixos.org/jobset/nixos/release-13.10 and the status of the release-critical jobs can be seen here: http://hydra.nixos.org/job/nixos/release-13.10/tested#tabs-constituents The plan for maintaining the branch is that it will primarily receive cherry-picked commits from master. Other than that, doing a stable branch is an experiment, and we'll have to see what the best way to do it is. Any feedback/suggestions are welcome. On that topic, now is probably a good time to start thinking about what the next release should look like, in terms of features. If you have any features (especially potentially high-impact ones like upgrading GCC) that you would like to see, please create GitHub issues for them, and add them to the 14.0x milestone: https://github.com/NixOS/nixpkgs/issues?milestone=4state=open [1] New major versions of existing packages are also fine as long as they are marked as lowPrio in all-packages.nix. That is, nix-env -i package should continue to install the old version. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS 13.10
Awesome. I remember the discussion about the release at sprint, feels like yesterday. Keep it up! On Fri, Nov 1, 2013 at 12:07 AM, Mathijs Kwik math...@bluescreen303.nlwrote: Congratulations on another great milestone :) It will be interesting to see how this stable experiment goes. But together with the new nixos-rebuild profiles, I think this will be very smooth. On Thu, Oct 31, 2013 at 11:59 PM, Eelco Dolstra eelco.dols...@logicblox.com wrote: Hi, I'm pleased to announce the availability of the first stable branch of NixOS, namely 13.10 (a.k.a Aardvark)! The purpose of this branch is to receive only conservative changes, such as bug fixes, safe minor package upgrades and new packages [1]. This is important for people who want to use NixOS in a production environment: you do want to get (security) fixes, but you don't want to be afraid of the system changing in fundamental ways, as may be the case on the master branch. Note that NixOS 13.10 is a branch, not a release in the sense of a static revision. Just like the NixOS master branch, it receives updates, just safer ones. The idea is to maintain this branch at least until the next stable branch (14.04?) is created. The 13.10 branch lives here in GitHub: https://github.com/NixOS/nixpkgs/tree/release-13.10 It also has an associated channel: http://nixos.org/channels/nixos-13.10 (Notice that versions of releases in the 13.10 channel have no pre string, indicating they're stable versions, such as 13.10.35427.6fda96b.) If you want to switch an existing machine from the nixos-unstable channel over to the 13.10 channel, just do: $ nix-channel --add http://nixos.org/channels/nixos-13.10 nixos After this, subsequent calls to nixos-rebuild switch --upgrade will fetch from the nixos-13.10 channel. See here for details on switching between NixOS channels: http://nixos.org/nixos/manual/#sec-upgrading Like the nixos-unstable channel (which gets build from the master branch), the 13.10 channel is updated only after Hydra has built all packages and all release-critical tests have succeeded. The Hydra jobset is: http://hydra.nixos.org/jobset/nixos/release-13.10 and the status of the release-critical jobs can be seen here: http://hydra.nixos.org/job/nixos/release-13.10/tested#tabs-constituents The plan for maintaining the branch is that it will primarily receive cherry-picked commits from master. Other than that, doing a stable branch is an experiment, and we'll have to see what the best way to do it is. Any feedback/suggestions are welcome. On that topic, now is probably a good time to start thinking about what the next release should look like, in terms of features. If you have any features (especially potentially high-impact ones like upgrading GCC) that you would like to see, please create GitHub issues for them, and add them to the 14.0x milestone: https://github.com/NixOS/nixpkgs/issues?milestone=4state=open [1] New major versions of existing packages are also fine as long as they are marked as lowPrio in all-packages.nix. That is, nix-env -i package should continue to install the old version. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] NixOS 13.10
awesome! and tnx for all the work. Quoting Eelco Dolstra (2013-10-31 23:59:19) Hi, I'm pleased to announce the availability of the first stable branch of NixOS, namely 13.10 (a.k.a Aardvark)! The purpose of this branch is to receive only conservative changes, such as bug fixes, safe minor package upgrades and new packages [1]. This is important for people who want to use NixOS in a production environment: you do want to get (security) fixes, but you don't want to be afraid of the system changing in fundamental ways, as may be the case on the master branch. Note that NixOS 13.10 is a branch, not a release in the sense of a static revision. Just like the NixOS master branch, it receives updates, just safer ones. The idea is to maintain this branch at least until the next stable branch (14.04?) is created. The 13.10 branch lives here in GitHub: https://github.com/NixOS/nixpkgs/tree/release-13.10 It also has an associated channel: http://nixos.org/channels/nixos-13.10 (Notice that versions of releases in the 13.10 channel have no pre string, indicating they're stable versions, such as 13.10.35427.6fda96b.) If you want to switch an existing machine from the nixos-unstable channel over to the 13.10 channel, just do: $ nix-channel --add http://nixos.org/channels/nixos-13.10 nixos After this, subsequent calls to nixos-rebuild switch --upgrade will fetch from the nixos-13.10 channel. See here for details on switching between NixOS channels: http://nixos.org/nixos/manual/#sec-upgrading Like the nixos-unstable channel (which gets build from the master branch), the 13.10 channel is updated only after Hydra has built all packages and all release-critical tests have succeeded. The Hydra jobset is: http://hydra.nixos.org/jobset/nixos/release-13.10 and the status of the release-critical jobs can be seen here: http://hydra.nixos.org/job/nixos/release-13.10/tested#tabs-constituents The plan for maintaining the branch is that it will primarily receive cherry-picked commits from master. Other than that, doing a stable branch is an experiment, and we'll have to see what the best way to do it is. Any feedback/suggestions are welcome. On that topic, now is probably a good time to start thinking about what the next release should look like, in terms of features. If you have any features (especially potentially high-impact ones like upgrading GCC) that you would like to see, please create GitHub issues for them, and add them to the 14.0x milestone: https://github.com/NixOS/nixpkgs/issues?milestone=4state=open [1] New major versions of existing packages are also fine as long as they are marked as lowPrio in all-packages.nix. That is, nix-env -i package should continue to install the old version. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rok Garbas - http://www.garbas.si ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
