Oh that makes sense. Might not be too hard to fix either. I'll try
when I get home tonight. Thanks!
On 1/23/15, Wout Mertens wout.mert...@gmail.com wrote:
those errors seem to come from a shell trying to interpret perl source...
On Mon Jan 12 2015 at 9:04:34 PM Jeff Johnson jef...@gmail.com
Oh weird, maybe I need to go back and see if I did something wrong
with the hostname, because now that I think about it you're
right--they should all be evaluated at once. I think the
system.activationScripts are an exception though. They seem to run
after everything's evaluated (they print their
In case there isn't a hook I just thought of the obvious solution:
wrap `nixos-rebuild` in a shell script.
On 1/23/15, Jeff Johnson jef...@gmail.com wrote:
Oh weird, maybe I need to go back and see if I did something wrong
with the hostname, because now that I think about it you're
right--they
Hi all! I'm trying to set up tarsnap on nixos. This is my tarsnap.nix so far:
config:
let
keySrc = ../rawpriv/tarsnap;
cacheDir = /var/cache/tarsnap;
rcSrc = builtins.toFile tarsnaprc ''
aggressive-networking # TODO is this a good idea?
What do you mean with only get installed at the end?
Also, networking.hostName should work, the whole config gets evaluated at
once. There's no running in Nix, only side-effects of evaluation.
Wout.
On Fri Jan 23 2015 at 7:45:38 PM Jeff Johnson jef...@gmail.com wrote:
Hi all! I'm trying to
Why not cd into the modules directory and grep for mkdir?
Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
That would work except the mkdir commands are evaluated using ${nixVars} so
the dirs aren't literally in there. I think I'm more comfortable adding
duplicated variables one by one in the shell script than trying to do any
magic.
Jeff
On Fri, Jan 23, 2015 at 11:49 AM, Marc Weber
Hi Luke,
How difficult would it be to track a different repository? Say, Stackage?
Simply replace the current contents of defaultPackageOverrides in [1] with
the choices from [2], run hackage2nix, and then you'll have a package set
that corresponds to Stackage.
Alternatively, we could add the
I'm thinking that it might be a good idea to have unit tests for the
configuration.nix descriptions. That way we can be more sure that a change
doesn't have unintended consequences.
For example, we could have tests like if you set config.foo and
config.bar, the evaluation should fail and if you
OK I'm a little lost. The shell is doing something weird, but I'm not sure
what. When I `_NIXOS_REBUILD_REEXEC=1 nixos-rebuild switch`, it says:
/run/current-system/sw/bin/nixos-rebuild: like 141:
/root/.nix-profile/bin/nix-instantiate: cannot execute binary file
building the system
Pulseaudio stopped working for me after upgrading to 14.12. It seems
that all PA clients start their own server, which eventually fails
because the pulseaudio daemon is already running.
For example, if I kill pulseaudio and then start it by hand with -vvv, I
can see it start correctly and write
Hi William,
Feel free to try enabling timesyncd by simply setting
`services.timesyncd.enable` in your nixos config. It should work as a drop
in replacement and respect the servers set in `services.ntp. servers`.
I tried that on a system running the current unstable channel, but the
service
On 01/22/2015 10:43 PM, Raahul Kumar wrote:
bit-identical builds. How far are we from that point? Is it the
timestamps that most build tools add to their build that prevents it?
What's the blocker?
We still don't even have fully reproducible stdenv, not even with all of
Peter Simons sim...@cryp.to writes:
We could also add the runHook setupCompilerEnvironmentPhase ... bit to the
nix-shell variable in the build environment so that these commands are run
automatically when you enter the interactive environment. Does that sound
useful?
It does to me.
John
On 01/23/2015 07:57 AM, Peter Simons wrote:
Hi Mateusz,
Does http://permalink.gmane.org/gmane.linux.distributions.nixos/15524
help?
Yes though it seems that we now need to update two files when making
any changes: default.nix so that we can callPackage it in overrides
and such
On 23-01-2015 14:04:22, Wout Mertens wrote:
I'm thinking that it might be a good idea to have unit tests for the
configuration.nix descriptions. That way we can be more sure that a change
doesn't have unintended consequences.
Really good idea!
For example, we could have tests
Hi,
On 23/01/15 15:04, Wout Mertens wrote:
I'm thinking that it might be a good idea to have unit tests for the
configuration.nix descriptions. That way we can be more sure that a change
doesn't have unintended consequences.
For example, we could have tests like if you set config.foo and
17 matches
Mail list logo
