[Nix-dev] VMware Guest Tools

[Brandon Martin]

Hey everyone,

New NixOS user here. I have installed NixOS on my MacBook with VMware Fusion. I 
want to install the guest tools but am not sure how. I tried following the 
directions here 
https://wiki.archlinux.org/index.php/Installing_Arch_Linux_in_VMware#Official_VMware_Tools,
 but when trying to run the perl script it asks for the path for each program 
it uses in the script (depmod, more, rmmod, etc...). Then errors with a 
/bin/bash no file error (don't have the exact error right now). How should I be 
handling this? 

Thanks!

--
Brandon Martin
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] NixOS Postfix service module config: why empty local_recipient_maps value?

[aldiyen]

Hello,

I just started trying to use NixOS a little under a week ago, and after
installing the Postfix service I found that I was having trouble preventing
my server from sending backscatter. After some searches, I found that when
the local_recipient_maps setting is empty (which it always is with the
config that is created), Postfix will accept email for unknown local
recipients and then send a delayed bounce notification. (See
http://www.postfix.org/LOCAL_RECIPIENT_README.html)

What is the reasoning behind the decision to set it up this way, without
the option to override it? Is there some expected configuration or use case
that I'm missing here?

Thanks! Hopefully I'm following proper etiquette here -- I just joined the
mailing list today

-aldiyen
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Change in networking with 15.05?

[Thomas Bereknyei]

Not sure why, but the problem was resolved after some tinkering with 15.05.
My current config:

networking = {
enableIPv6=false;
networkmanager.enable = true;
firewall = {
  enable = true;
  allowedTCPPorts = [xxx];
};
  };


On Wed, Dec 31, 2014 at 9:41 AM, Luca Bruno  wrote:

> Could you try reverting cbd30b2bde17a87075138cf0443f110e5ac0e373 ?
>
>>
>>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Change in networking with 15.05?

[Thomas Bereknyei]

Luca,

Not sure why, but the problem was resolved after some tinkering with 15.05.
My current config:

networking = {
enableIPv6=false;
networkmanager.enable = true;
firewall = {
  enable = true;
  allowedTCPPorts = [xxx];
};
  };
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] [erlang-questions] Erlang Package Manager

[stewart mackenzie]

On Wed, Dec 31, 2014 at 11:47 PM, Anthony Ramine  wrote:
> How do you handle multiple versions of a single package?

Okay allow me to give a rather detailed answer describing in how NixOS
works. I'll also describe how I envisage Erlang adopting Nix as its
package manager.

So I like to think of Nix as the Matrix, you, Neo, can reconfigure
your world at a command. Your entire environment is made up of
thousands of symlinks that can shifted about in an instant. Dodge
speeding bullets - no problem.

Now some code.

A convenient way of creating an environment is using nix-shell. These
files sit in your project folder.

(contents of dev-shell)
#! /bin/sh
s=$(type -p nix-shell)
exec $s release.nix -A erlangEnv

(contents of release.nix)
let
  pkgs = import  {};
stdenv = pkgs.stdenv;
  in rec {
erlangEnv = stdenv.mkDerivation rec {
  name = "erlang-env";
  version = "1.1.1.1";
  src = ./.;
  buildInputs = [ pkgs.erlang_odbc pkgs.git pkgs.openssl
pkgs.libyaml pkgs.expat pkgs.zlib pkgs.libcouchbase pkgs.automake
pkgs.autoconf pkgs.rebar ];
};
  }

Typically the above is used for short quick projects they are project
specific environments.

See the above 'pkgs.erlang_odbc' that currently points to erlang 17
with odbc support. I can change that to 'pkgs.erlangR16' and it'll
point to Erlang R16.03.

These are the Erlang versions supported
https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/interpreters/erlang
They are exposed via the all-packages.nix file
https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix#L3994

You cannot have Erlang R16 and Erlang R17 in the same environment you
will get a conflict.

One could commit dev-shell and release.nix into your repo and
thereafter run  './dev-shell' and you'll leave your current
environment and an environment as dictated by the release.nix will be
created for you.

Now if the Erlang community is considering adopting Nix as its package
manager then the below is the way to do it: Nix already supports
python, perl, php, haskell, node, lua and guile:
https://github.com/NixOS/nixpkgs/tree/master/pkgs/top-level please
notice the language specific *.nix files.

For example
When adding a node package one simply adds the package name to this
file 
https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/node-packages.json
and run npm2nix on the file like such: 'npm2nix node-packages.json
node-packages-generated.nix'. The program npm2nix will go to the
canonical https://www.npmjs.com/ and download all the node packages,
update each package and create nix expressions accordingly. The
packager then commits the edited *.json file and the generated file
and makes a pull request for everyone's disposal.

So referring to the previous release.nix example, notice there are no
erlang code dependencies (yes yes forget about rebar).  one would add
'erlangPackages.cowboy'. This then gets the cowboy package that is
part of the nixpkgs.

In other words the Nix community and Erlang community need to start
banging their heads together, create an erlang-packages.nix and extend
it accordingly.

So a rebar2nix program (see https://github.com/NixOS/npm2nix and
https://github.com/NixOS/cabal2nix) could simply be pointed at a git
cloned erlang project from github and it'll parse the rebar.config
file pulling down dependencies, compiling them then making them
immutable derivatives in your nix-store. Note these packages are
obviously not available to everyone in the community. Though if you
run the very same rebar2nix program on the canonical
erlang-packages.nix in
https://github.com/NixOS/nixpkgs/tree/master/pkgs/top-level and
generate a new file, then that would become available to everyone.

Both communities are filled with terribly smart people. You'll get
along just fine.

Now, Nix also supports creating long lasting custom environments
similar to nix-shell but essentially you install this environment as a
package in your /nix/store so to speak.

I have this file ~/.nixpkgs/erlang.nix
```
# $ nix-env -iA erlangEnv -f erlang.nix -p
/nix/var/nix/gcroots/profiles/per-user/erlang
# Make a convenience link.
#  $ ln -sf
/nix/var/nix/gcroots/profiles/per-user/erlang/bin/load-env-erlang .
# Activate the environment.
#  $ ./load-env-erlang
# Optionally, rollback to an earlier generation of this profile.
#  $ nix-env --list-generations -p
/nix/var/nix/gcroots/profiles/per-user/erlang

let
  pkgs = import  {};
  stdenv = pkgs.stdenv;
   in rec {
   erlangEnv = pkgs.myEnvFun {
 name = "erlang";
 buildInputs = with pkgs; [ erlang rebar openssl git binutils
bash emacs which libyaml expat zlib automake autoconf mc libtool
python libevent meld tig libpcap cmake libcouchbase pidgin ];
   };
   }
```

So this allows one to have generations such that one can rollback if
something messed up. These environments can be quite complex if
needed. You are limited by your creativity and the understanding of
the nix expre

Re: [Nix-dev] NixOS 14.12 released

[Sergey Mironov]

Thanks and happy new year!

2014-12-31 17:19 GMT+03:00 Luca Bruno :
> Thanks a lot to everybody for the effort. Will be a great release.
>
> On Wed, Dec 31, 2014 at 2:13 PM, Rok Garbas  wrote:
>>
>> Awesome news! tnx everybody.
>> Domen you rock!
>>
>> On Wed, Dec 31, 2014 at 1:29 PM, Jascha Geerds  wrote:
>> > Awesome! Thanks to everyone and especially Domen.
>> >
>> > --
>> >   Jascha Geerds
>> >   j...@ekby.de
>> > ___
>> > 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
>> r...@garbas.si
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
>
>
> --
> NixOS Linux
>
> ___
> 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] Scala packages in Nix?

[Mateusz Kowalczyk]

On 12/31/2014 04:59 PM, Ryan Newton wrote:
> Hi all,
> 
> Just recently there was a thread about Erlang adopting Nix as its package
> manager.
> 
> Scala already has a package manager (sbt, which uses maven to my limited
> understanding).  *Has anyone tried to get that working with Nix?*
> 
> My own motivation is that I want a version of Virtualized Scala
>  and Delite
>  that can reproducibly install via
> nix.
> 
> Thanks,
>   -Ryan
> 
> 

I know Daniel Peebles has looked at Java packaging in the past, for
stuff that uses maven. Perhaps it'd be worthwhile to contact him and see
if you can't get any useful info; he goes by ‘copumpkin’ on IRC but I
think he's subscribed here too.


-- 
Mateusz K.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Fwd: Scala packages in Nix?

[Eric des Courtis]

-- Forwarded message --
From: Eric des Courtis 
Date: Wed, Dec 31, 2014 at 12:02 PM
Subject: Re: [Nix-dev] Scala packages in Nix?
To: Ryan Newton 


It far from decided. It has been suggested by many members of the community
however.

On Wed, Dec 31, 2014 at 11:59 AM, Ryan Newton  wrote:

> Hi all,
>
> Just recently there was a thread about Erlang adopting Nix as its package
> manager.
>
> Scala already has a package manager (sbt, which uses maven to my limited
> understanding).  *Has anyone tried to get that working with Nix?*
>
> My own motivation is that I want a version of Virtualized Scala
>  and Delite
>  that can reproducibly install via
> nix.
>
> Thanks,
>   -Ryan
>
>
> ___
> 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] Scala packages in Nix?

[Ryan Newton]

Hi all,

Just recently there was a thread about Erlang adopting Nix as its package
manager.

Scala already has a package manager (sbt, which uses maven to my limited
understanding).  *Has anyone tried to get that working with Nix?*

My own motivation is that I want a version of Virtualized Scala
 and Delite
 that can reproducibly install via
nix.

Thanks,
  -Ryan
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix as an Erlang Package Manager

[Mateusz Kowalczyk]

On 12/31/2014 02:29 AM, Eric des Courtis wrote:
> It seems many people on the Erlang mailing list have been contemplating
> using Nix as the official Erlang package manager. I think it's an
> interesting idea worth exploring.
> 
> Could someone from the Nix team jump in and take a look? Perhaps make some
> suggestions?
> 
> 
> http://erlang.org/pipermail/erlang-questions/2014-December/082119.html
> (Thread root)
> 
> http://erlang.org/pipermail/erlang-questions/2014-December/082270.html
> (Comments from Joe Armstrong one of the designers of the Erlang programming
> language)
> 
> 
> Eric
> 
> 
> 

The server is down for those URLs so I'll just pipe in in here: I think
using nix as a package manager for Erlang or another language is a great
idea.

I package Agda stuff in nixpkgs (though there is not a lot of libraries
available around) and Agda does not have a package manager. It works out
fine IMHO and I certainly prefer to please one package manager/build
system than two.

There is of course an advantage that language-specific systems have over
things like nix: nix is effectively a self-contained system, it will
grab all the build dependencies like GCC itself while things like
Haskell's cabal &c do nothing but Haskell and make the user fulfill
system dependencies by hand or alternatively use Haskell from their
system's package manager. Most people already have GCC so questions like
‘why do I have to get it again’ might arise.

I guess it just depends whether Erlang folk is ready to accept that they
will be incurring the weight of a second, full-fledged package manager
on their system. Of course my hopes as nix advocate is that they will
embrace it and maybe even make it their main one after a while ;).


-- 
Mateusz K.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Can't get anything to build on Mac OS X

[John Wiegley]

> Michael Sperber  writes:

> I'm (still) running Mavericks, and just pulled from github.  I ran against
> these problems:

> - A large number of packages have indirect dependencies on Kerberos, which
> by default is set to be Heimdal - which is marked broken on Mac OS X.  I did
> this, which allowed me to proceed:

I ran into the heimdal issues yesterday, and created the following issue to
document them:

https://github.com/NixOS/nixpkgs/issues/5512

Using krb5 didn't work for me, but then I'm on Yosemite.

>   Or should I just give up here and move to the pure, clang-based branch?

We'd welcome your testing. :)

John
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix as an Erlang Package Manager

[Eric des Courtis]

try this
https://groups.google.com/forum/#!topic/erlang-programming/nMqpPjht7-8

On Wed, Dec 31, 2014 at 11:03 AM, Eric des Courtis <
eric.des.cour...@gmail.com> wrote:

> Looks like the server is down currently.
>
>
> On Wed, Dec 31, 2014 at 9:22 AM, Luca Bruno  wrote:
>
>> I get an empty response from the server from those urls.
>>
>> Nix is currently re-packaging python, haskell, nodejs packages etc. So
>> I'm sure nix would do the job for erlang too, without the need to roll your
>> own package manager.
>>
>> On Wed, Dec 31, 2014 at 3:29 AM, Eric des Courtis <
>> eric.des.cour...@gmail.com> wrote:
>>
>>> It seems many people on the Erlang mailing list have been contemplating
>>> using Nix as the official Erlang package manager. I think it's an
>>> interesting idea worth exploring.
>>>
>>> Could someone from the Nix team jump in and take a look? Perhaps make
>>> some suggestions?
>>>
>>>
>>> http://erlang.org/pipermail/erlang-questions/2014-December/082119.html
>>> (Thread root)
>>>
>>> http://erlang.org/pipermail/erlang-questions/2014-December/082270.html
>>> (Comments from Joe Armstrong one of the designers of the Erlang programming
>>> language)
>>>
>>>
>>> Eric
>>>
>>> ___
>>> nix-dev mailing list
>>> nix-dev@lists.science.uu.nl
>>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>>
>>>
>>
>>
>> --
>> NixOS Linux 
>>
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix as an Erlang Package Manager

[Eric des Courtis]

Looks like the server is down currently.


On Wed, Dec 31, 2014 at 9:22 AM, Luca Bruno  wrote:

> I get an empty response from the server from those urls.
>
> Nix is currently re-packaging python, haskell, nodejs packages etc. So I'm
> sure nix would do the job for erlang too, without the need to roll your own
> package manager.
>
> On Wed, Dec 31, 2014 at 3:29 AM, Eric des Courtis <
> eric.des.cour...@gmail.com> wrote:
>
>> It seems many people on the Erlang mailing list have been contemplating
>> using Nix as the official Erlang package manager. I think it's an
>> interesting idea worth exploring.
>>
>> Could someone from the Nix team jump in and take a look? Perhaps make
>> some suggestions?
>>
>>
>> http://erlang.org/pipermail/erlang-questions/2014-December/082119.html
>> (Thread root)
>>
>> http://erlang.org/pipermail/erlang-questions/2014-December/082270.html
>> (Comments from Joe Armstrong one of the designers of the Erlang programming
>> language)
>>
>>
>> Eric
>>
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
>
> --
> NixOS Linux 
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] [erlang-questions] Erlang Package Manager

[stewart mackenzie]

Nix has cabal2nix, npm2nix what is needed is a rebar2nix.

Lets not get too dramatic about it all.

Next you could package Erl deps in the same fashion nix packages
python, perl and other languages ie include the name
pythonPackages.package_name. It really isnt far flung to imagine an
erlangPackages.cowboy

/s
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Can't get anything to build on Mac OS X

[Michael Sperber]

I'm (still) running Mavericks, and just pulled from github.  I ran
against these problems:

- A large number of packages have indirect dependencies on Kerberos,
  which by default is set to be Heimdal - which is marked broken on Mac
  OS X.  I did this, which allowed me to proceed:

{
  packageOverrides = pkgs: rec {
kerberos = pkgs.krb5;
  };
}

- After this, it proceeds to build a gcc which doesn't work:

\[\][nix-shell:~/Downloads]$\[\] gcc -v -v -v x.c
Using built-in specs.
COLLECT_GCC=/nix/store/nxva8pj5v62582qw3sh4zg9b8i49jl54-gcc-4.8.3/bin/gcc
COLLECT_LTO_WRAPPER=/nix/store/nxva8pj5v62582qw3sh4zg9b8i49jl54-gcc-4.8.3/libexec/gcc/x86_64-apple-darwin10.2.0/4.8.3/lto-wrapper
gcc: error: unrecognized command line option ‘-stdlib=libc++’

  Or should I just give up here and move to the pure, clang-based branch?

Any help would be much appreciated!

-- 
Regards,
Mike

___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Change in networking with 15.05?

[Luca Bruno]

Could you try reverting cbd30b2bde17a87075138cf0443f110e5ac0e373 ?

On Tue, Dec 30, 2014 at 5:44 PM, Thomas Bereknyei 
wrote:

> Upgrading from 14.02pre5678.gfedcba to the nixos-unstable (
> http://nixos.org/releases/nixos/unstable/nixos-15.05pre54730.cbe467e/)
> seems to removes the non-loopback network interfaces.
>
> The following configuration worked well with 14.02 as well as 14.*
> unstable releases.
>
> networking = {
>   enableIPv6=false;
>   interfaceMonitor.enable = false;
>   enableB43Firmware = true;
>   networkmanager.enable = true;
>   useDHCP = false; # sometimes true
>   wicd.enable = false;
>   dnsSingleRequest = true;
> };
>
> Where before this computer had an "enp2s1" and "lo" interface, it only has
> "lo" after a nixos-rebuild switch.
>
> Was there a change in networking or NetworkManager that would cause
> something like this? I'd like to know if there was something obvious that
> changed before I start debugging by trial and error. It's a headless server
> and with the network interface going down I can't SSH into it while it's
> down. Though I can look at logs after a boot into a rollback generation.
>
> The following event does not occur when booting into 15.05, but not 14.02:
> systemd-udevd[1124]: renamed network interface eth0 to enp2s1
>
> I also notice the following during 15.05 boots:
>  systemd-udevd[19958]: specified group 'input' unknown
>
>
> -Tom
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>


-- 
NixOS Linux 
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Nix as an Erlang Package Manager

[Luca Bruno]

I get an empty response from the server from those urls.

Nix is currently re-packaging python, haskell, nodejs packages etc. So I'm
sure nix would do the job for erlang too, without the need to roll your own
package manager.

On Wed, Dec 31, 2014 at 3:29 AM, Eric des Courtis <
eric.des.cour...@gmail.com> wrote:

> It seems many people on the Erlang mailing list have been contemplating
> using Nix as the official Erlang package manager. I think it's an
> interesting idea worth exploring.
>
> Could someone from the Nix team jump in and take a look? Perhaps make some
> suggestions?
>
>
> http://erlang.org/pipermail/erlang-questions/2014-December/082119.html
> (Thread root)
>
> http://erlang.org/pipermail/erlang-questions/2014-December/082270.html
> (Comments from Joe Armstrong one of the designers of the Erlang programming
> language)
>
>
> Eric
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>


-- 
NixOS Linux 
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[Luca Bruno]

Thanks a lot to everybody for the effort. Will be a great release.

On Wed, Dec 31, 2014 at 2:13 PM, Rok Garbas  wrote:

> Awesome news! tnx everybody.
> Domen you rock!
>
> On Wed, Dec 31, 2014 at 1:29 PM, Jascha Geerds  wrote:
> > Awesome! Thanks to everyone and especially Domen.
> >
> > --
> >   Jascha Geerds
> >   j...@ekby.de
> > ___
> > 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
> r...@garbas.si
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
NixOS Linux 
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Service composition

[Ertugrul Söylemez]

Hi Ludovic,

>> As a first approximation there would be a Service monoid, which would
>> combine certain typical attributes about a service, including startup
>> scripts, required bind-mounts, required system resources and if
>> really necessary shutdown scripts (most programs should shutdown
>> properly when the container goes down).
>>
>> Service : Mon
>>
>> Its identity idS would be the empty service, which you can think of
>> as an empty group of processes with no mounts, no resources, etc.
>>
>> The Bitlbee service would be constructed through a regular function
>> that takes the typical bitlbee options.  Nothing special here:
>>
>> bitlbee : BitlbeeConf -> Service
>
> OK.  I suppose ‘Service’ would specify required user accounts, PAM
> services, etc., right?

Yes.  It specifies everything to build a machine for the purpose of
carrying out the task that the service denotes, but in such a way that
two such machines can be combined into a single machine.

I still need to figure out a few details though, especially since I'm
relying on a lot of Linux technology here.  I'd like to keep it
sufficiently general that users of other kernels (most notably FreeBSD)
can benefit from it as well.


>> The nginx function is more interesting.  It involves a second monoid,
>> the monoid of web services (identity idW):
>>
>> WebService : Mon
>>
>> Then nginx is a monoid morphism,
>>
>> nginx : WebService -> Service
>>
>> that is a function with additional structure, in particular:
>>
>> nginx x ◇ nginx y ≡ nginx (x ◇ y)
>> nginx idW ≡ idS
>
> Very interesting.  I wonder what other types of services would benefit
> from similar treatment.

It would split the view on the configuration into two parts:  services
and environment.  For example networking belongs to the environment, so
requirements on the network as well as networking options will be part
of a service.

This means that creating a bridge device amounts not to adding a
service, but to applying a service morphism:

withBridge brCfg (br:
service1 br <> service2 br)

This reminds me that it would be great if Nix would allow some way to
define custom infix operators or at least provide a few generic ones.
At this point we will need to use prefix notation, which might make this
a bit uglier:

withBridge brCfg (br:
compose (service1 br)
(service2 br))

Although it's just monoid composition, so using a list argument would do
the trick.  Just a nice-to-have.


Greets,
Ertugrul
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[Rok Garbas]

Awesome news! tnx everybody.
Domen you rock!

On Wed, Dec 31, 2014 at 1:29 PM, Jascha Geerds  wrote:
> Awesome! Thanks to everyone and especially Domen.
>
> --
>   Jascha Geerds
>   j...@ekby.de
> ___
> 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
r...@garbas.si
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[Jascha Geerds]

Awesome! Thanks to everyone and especially Domen.

-- 
  Jascha Geerds
  j...@ekby.de
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[stewart mackenzie]

Great way to start off the new year!

Thank you!
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[Wout Mertens]

Woohoo!

Thanks for everyone's hard work and Domen especially!

Now I wonder if you shouldn't have made it 15.01 so it would seem all shiny
and new :-D

On Wed, Dec 31, 2014, 10:29 Domen Kožar  wrote:

> Hi all,
>
> community is proud to announce another NixOS stable release  "Caterpillar"
> 14.12.
>
> The release brings many improvements including Nix 1.8 and many packages
> updates. 11972 commits were pushed by 310 contributors since the last
> release (14.04).
>
> ISOs, VirtualBox images and EC2 AMIs can be downloaded from:
>
> http://nixos.org/nixos/download.html
>
> Fresh installation can be done by following Installation chapter in the
> manual:
>
>
> http://hydra.nixos.org/build/18399157/download/2/nixos/sec-installation.html
>
> Upgrade existing NixOS machines:
>
> $ nix-channel --add https://nixos.org/channels/nixos-14.12 nixos
> $ nixos-rebuild switch --upgrade
>
> Report any issues to the bug tracker on
> https://github.com/NixOS/nixos/issues
>
> Thank you all for being involved!
>
> Domen
> ___
> 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 14.12 released

[Bjørn Forsman]

On 31 December 2014 at 10:29, Domen Kožar  wrote:
> Hi all,
>
> community is proud to announce another NixOS stable release  "Caterpillar"
> 14.12.
> [...]

Awesome! Thanks to everyone that contributed.

Have a happy new year!

Best regards,
Bjørn Forsman
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] how to use stdenv

[Bjørn Forsman]

On 31 December 2014 at 11:42, Ganesh Sittampalam  wrote:
> Hi,
>
> https://nixos.org/wiki/Howto_develop_software_on_nixos talks about
> including stdenv in a myEnvFun environment to get gcc etc.
>
> However gcc and a bunch of other standard build tools don't seem to be
> part of stdenv any more:
>
> https://github.com/NixOS/nixpkgs/commit/328f7a621e0e2c37159e4cdd86fa279417fa3b9e
>
> ["stdenv: Remove propagatedUserEnvPkgs
> Stdenv is not really intended as an installable package. Nowadays it's
> much better to use "nix-shell -p" to get a build environment."]
>
> Is that wiki page out of date now? Is there a new recommended way of
> getting the build tools into a myEnvFun environment now?

I can think of a couple of ways:

- include gcc etc. in buildInputs
- use nix-shell instead of myEnvFun (like the commit message suggests)

Best regards,
Bjørn Forsman
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] how to use stdenv

[Ganesh Sittampalam]

Hi,

https://nixos.org/wiki/Howto_develop_software_on_nixos talks about
including stdenv in a myEnvFun environment to get gcc etc.

However gcc and a bunch of other standard build tools don't seem to be
part of stdenv any more:

https://github.com/NixOS/nixpkgs/commit/328f7a621e0e2c37159e4cdd86fa279417fa3b9e

["stdenv: Remove propagatedUserEnvPkgs
Stdenv is not really intended as an installable package. Nowadays it's
much better to use "nix-shell -p" to get a build environment."]

Is that wiki page out of date now? Is there a new recommended way of
getting the build tools into a myEnvFun environment now?

Cheers,

Ganesh
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 14.12 released

[Domen Kožar]

A bit more detailed list of changes is in the manual, see:
http://hydra.nixos.org/build/18399157/download/2/nixos/sec-release-14.12.html

On Wed, Dec 31, 2014 at 10:29 AM, Domen Kožar  wrote:

> Hi all,
>
> community is proud to announce another NixOS stable release  "Caterpillar"
> 14.12.
>
> The release brings many improvements including Nix 1.8 and many packages
> updates. 11972 commits were pushed by 310 contributors since the last
> release (14.04).
>
> ISOs, VirtualBox images and EC2 AMIs can be downloaded from:
>
> http://nixos.org/nixos/download.html
>
> Fresh installation can be done by following Installation chapter in the
> manual:
>
>
> http://hydra.nixos.org/build/18399157/download/2/nixos/sec-installation.html
>
> Upgrade existing NixOS machines:
>
> $ nix-channel --add https://nixos.org/channels/nixos-14.12 nixos
> $ nixos-rebuild switch --upgrade
>
> Report any issues to the bug tracker on
> https://github.com/NixOS/nixos/issues
>
> Thank you all for being involved!
>
> Domen
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] NixOS 14.12 released

[Domen Kožar]

Hi all,

community is proud to announce another NixOS stable release  "Caterpillar"
14.12.

The release brings many improvements including Nix 1.8 and many packages
updates. 11972 commits were pushed by 310 contributors since the last
release (14.04).

ISOs, VirtualBox images and EC2 AMIs can be downloaded from:

http://nixos.org/nixos/download.html

Fresh installation can be done by following Installation chapter in the
manual:

http://hydra.nixos.org/build/18399157/download/2/nixos/sec-installation.html

Upgrade existing NixOS machines:

$ nix-channel --add https://nixos.org/channels/nixos-14.12 nixos
$ nixos-rebuild switch --upgrade

Report any issues to the bug tracker on
https://github.com/NixOS/nixos/issues

Thank you all for being involved!

Domen
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Firefox test in 14.04

[Lluís Batlle i Rossell]

On Wed, Dec 31, 2014 at 09:18:39AM +0100, Lluís Batlle i Rossell wrote:
> Hello all,
> 
> the 14.04 channel has something strange about firefox 32-bit. It failed to 
> build
> several times, but the firefox 32-bit nixos test was succeeding. Check the
> result and the Inputs tab.
> http://hydra.nixos.org/build/17689092

From this link, of special attention are the Build Steps lines; one failing and
the other not, of the same store path.

1   Build of /nix/store/dr791i26dli0g7dlmilk34zamgi09vy7-firefox-34.0.5 0s 
Failed: builder for 
‘/nix/store/p1j53dk2zx2d17sh01qggkr5lvyrjvl9-firefox-34.0.5.drv’ failed with
exit code 100 (log, raw, tail)
2   Build of /nix/store/dr791i26dli0g7dlmilk34zamgi09vy7-firefox-34.0.5 20m 
38s wendy   Succeeded (log, raw, tail) 

Regards,
Lluís.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Firefox test in 14.04

[Lluís Batlle i Rossell]

Hello all,

the 14.04 channel has something strange about firefox 32-bit. It failed to build
several times, but the firefox 32-bit nixos test was succeeding. Check the
result and the Inputs tab.
http://hydra.nixos.org/build/17689092

This resulted in having a 14.04 channel without firefox 32-bit binaries.

Moreover, after the build I gave, firefox 32-bit was fixed by an update of
version, but then the nixos test started to fail, therefore the channel never
being updated since the failing firefox 32-bit build (the link I gave, 22nd of
december).

Some logs have disappared from hydra, so maybe someone knows quickly what is
happening.

Have happy vacations, and good luck finding the man of the noses today! :)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev