On Mon, Apr 27, 2015, at 03:56 PM, Ramakrishnan Muthukrishnan wrote:
Hi,
Sorry for the badly worded subject line.
NixOS newbie here. Playing with NixOS on a VirtualBox installation and
really really liking it so far.
I am using nix-shell and the quick start example in the manual
Hi,
Sorry for the badly worded subject line.
NixOS newbie here. Playing with NixOS on a VirtualBox installation and
really really liking it so far.
I am using nix-shell and the quick start example in the manual (step #6
listed here: https://nixos.org/nix/manual/) does not seem to work for
me:
Thanks all of you. I added the following to my dependee (bin_prot) and it
worked nicely.
setupHook = writeText setupHook.sh ''
export
CAML_LD_LIBRARY_PATH=''${CAML_LD_LIBRARY_PATH}''${CAML_LD_LIBRARY_PATH:+:}''$1/lib/ocaml/${ocaml_version}/site-lib/bin_prot/
'';
On Mon, Apr 27, 2015 at 12:37
On 04/27/2015 09:14 PM, Vincent Laporte wrote:
Le 2015-04-27 21:08, Vladimír Čunát a ēcrit :
On 04/27/2015 09:03 PM, Eric Merritt wrote:
When ocaml build B, then it fails because it can't load the *.so
that is part of A.
That all seems to boil down to the question: how are those
so-files
Hi folks,
just a quick update for your information: we now have fully automatic updates
of hackages-packages.nix. The process is driven by the update-nixpkgs.sh
script [1], which is part of the cabal2nix Git repository [2]. Basically, that
script re-generates hackages-packages.nix once per hour
I just discovered that I can successfully manually add the route if I
Ieave of the via gateway option:
# ip route add 10.180.0.0/24 src 172.16.48.17 dev eth0
After this I can successfully ping hosts on the other side of the VPN!
I'll just settle with adding this to my local networking
Dear Nixers,
I've a slightly off-topic question but since I know there are some
excellent Unix networking experts on this list I hope to get a pointer
in the right direction.
After some changes in my networking setup (I added an IP address to my
eth0 interface) my strongswan VPN service fails to
Hi,
There is a project that as part of its tests has to create a postgresql
database which means that the postgres server needs to be running.
Is there an easy way to achieve this? How does one go about testing such
packages to begin with?
--
Mateusz K.
It's possible to run postgres with just a unix domain socket for
communication, and no network access. Then, you can point your tests at
that self-contained postgres environment. Would that work for your
situation?
On Mon, Apr 27, 2015 at 8:52 PM, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk
wrote:
Passing the chroot flag to nixos-install without arguments should now give you a
Bash shell as intended rather than try an empty path.
This was masked by the user's shell (usually /bin/bash) being defaulted to by
chroot, and being found since their paths used NixOS conventions.
---
When bootstrapping from other distributions, nixos-install is unable to find
various tools in the chroot since their paths aren't aware of NixOS conventions.
This makes a small change to existing code by specifying nixpkgs/nixos instead
of just nixos when running nix-instantiate in the chroot. I
Hello,
I found the commit relating to my problem:
https://github.com/NixOS/nixpkgs/commit/12e77fdc3f6f223be1a4d5c88d6c79bff63ae70c#commitcomment-10932244
I made a comment regarding the lack of zpool.cache file. It's required
for `zdb` to work. Perhaps we can generate the `zpool.cache` file at
Due to issues with environmental variables, nixos-install failed to install when
the host operating system wasn't NixOS. This broke bootstrapping from Debian.
Jookia (2):
nixos-install: Fix password prompt failing outside NixOS.
nixos-install: Fix chroot flag not defaulting to Bash outside
Hi,
To people using ZFS on NixOS, does your `zdb` command work?
I tried using `zdb` and it just gives:
```
cannot open '/etc/zfs/zpool.cache': No such file or directory
```
This file `/etc/zfs/zpool.cache` file does not exist if you follow the
instructions regarding installing ZFS on NixOS.
I've configured a system using the nix-daemon with build-use-chroot = true
and came across the following problem (using the unstable packages)
[tyson@test-centos6 .nixpkgs]$ nix-env -iA nixpkgs.texinfo4
installing ‘texinfo-4.13a’
these derivations will be built:
On NixOS, nix is configured to not only provide the chroot but also /bin/sh
compatability. This is fixed in nix 1.9 so I recommend just using the
unstable version of nix as it should just work.
On Apr 27, 2015 11:42 AM, Tyson Whitehead twhiteh...@gmail.com wrote:
I've configured a system using
On Mon, Apr 27, 2015, at 03:56 PM, Ramakrishnan Muthukrishnan wrote:
Hi,
Sorry for the badly worded subject line.
NixOS newbie here. Playing with NixOS on a VirtualBox installation and
really really liking it so far.
I am using nix-shell and the quick start example in the manual (step
Guys,
I am packaging up some ocaml projects and running into a problem. Certain
syntax extensions (bin_prot) include a *.so component that isn't getting
picked up. So when another package has that package as dependency it
doesn't build, because the code from that package gets loaded during build
On 04/27/2015 09:03 PM, Eric Merritt wrote:
When ocaml build B, then it fails because it can't load the *.so that is
part of A.
That all seems to boil down to the question: how are those so-files
searched for? (by the ocaml compiler, I guess, or by what?)
Vladimir
smime.p7s
Description:
On 04/27/2015 09:03 PM, Eric Merritt wrote:
When ocaml build B, then it fails because it can't load the *.so that is
part of A.
That all seems to boil down to the question: how are those so-files
searched for? (by the ocaml compiler, I guess, or by what?)
Vladimir
smime.p7s
Description:
I upgraded to nixUnstable (nix-1.9pre4074_e659978) but it does not seem to have
resolved this issue
1 - installed the nixpkgs.nixUnstable (nix-1.9pre4074_e659978) package,
2 - switched the default system profile over to it,
3 - restarted the nix-daemon so it is running 1.9
[root@test-centos6:~]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 2015-04-27 21:08, Vladimír Čunát a ēcrit :
On 04/27/2015 09:03 PM, Eric Merritt wrote:
When ocaml build B, then it fails because it can't load the *.so
that is part of A.
That all seems to boil down to the question: how are those
so-files
22 matches
Mail list logo
