Hi Mateusz,
Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk writes:
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
On Tue, Apr 28, 2015, at 04:05 PM, Domen Kožar wrote:
Could you open an issue at github.com/NixOS/nixpkgs ? Thanks!
Yes, done: https://github.com/NixOS/nixpkgs/issues/7611
--
Ramakrishnan Err and err and err again, but less and less and less
⟶ Piet Hein
Hello fellow Haskellers,
I have a bunch of local Haskell packages, mostly libraries. The package
X lives in the directory `ertes-src/X/main`. There are lots of direct
and indirect dependencies between them. My current solution is ad hoc
and rather ugly. I'm using the following hand-crafted
I believe Peter's message 87mw5qvj9x@write-only.cryp.to could
answer my question. I will give it a try.
Hello fellow Haskellers,
I have a bunch of local Haskell packages, mostly libraries. The package
X lives in the directory `ertes-src/X/main`. There are lots of direct
and indirect
Hello!
Recently I've bootstrapped NixOS on to a new ARM platform from an
existing Debian install on the same platform. I figured this is useful
knowledge so I've written up some documentation which I'm in the process
of convert to Docbook. It's kind of a tutorial but expects users to
modify
I am on commit b2f426d9816ae1b0dfc8e6cd2e8dd23d9326182f and the following
error is occuring.
$ nix-shell -f /path/to/nixpkgs
error: assertion failed at
/home/rahulmutt/src/nixpkgs/pkgs/top-level/all-packages.nix:4971:15
Tracing, I find that it corresponds to binutilsCross expression and the
So https://github.com/NixOS/nixpkgs/pull/7603 can be closed as well. Thank
you Jookia and Shea!
On Tue, Apr 28, 2015 at 12:38 PM, Shea Levy s...@shealevy.com wrote:
Applied in 71910be9ea225895e36f60ed23a1bdce402b3088, thanks!
On Apr 27, 2015, at 10:16 PM, Jookia 166...@gmail.com wrote:
So this is the setuphook of the dependee not the compiler. The directory is
there because the package creates it. Is there some subtlety I am missing
in the way nix handles packages?
On Tue, Apr 28, 2015 at 3:14 AM, Vladimír Čunát vcu...@gmail.com wrote:
On 04/27/2015 10:42 PM, Eric Merritt
Well, on github we have travis, and line comments, and bug references etc.
It's just nicer, and I haven't seen many patches come in via ML (this was
the first I noticed) so I didn't really have a workflow ready...
On Tue, Apr 28, 2015 at 12:40 PM Shea Levy s...@shealevy.com wrote:
As long as
I keep running into this issue whenever I run `nix-env --upgrade` that
nix-env thinks that nodePackages.7f is an upgrade to nodejs. Consequently,
I have to force a downgrade to the nodejs package after every upgrade.
Is there a way to avoid this?
Thanks,
Rich
I believe Peter's message 87mw5qvj9x@write-only.cryp.to could
answer my question. I will give it a try.
It does and works well. Thanks anyway!
I have a bunch of local Haskell packages, mostly libraries. The package
X lives in the directory `ertes-src/X/main`. There are lots of
I switch to the nixos-unstable channel as I noticed the nixpkgs-unstable last
update was March 22nd.
http://nixos.org/channels/
Installed the nixpkgs.pkgs.nixUnstable (nix-1.9pre4088_1711679) from this and
it seems to have resolved the issue.
Thanks! -Tyson
On April 27, 2015 15:13:22 Tyson
It's not specific to Haskell (and I haven't tried haskellng at all yet) but for
personal packages I have mypkgs/pkgname/default.nix, and then a top-level
mypkgs/default.nix:
let
nixpkgs = import nixpkgs {};
callPkg = nixpkgs.newScope
( nixpkgs
//
Hi,
I'm writing a nix expression for PyBitMessage:
{stdenv, fetchgit, python27, qt4, pyqt4, sqlite, openssl, mpg123}:
stdenv.mkDerivation rec {
name = pybitmessage-v0.4.4;
src = fetchgit {
url = https://github.com/Bitmessage/PyBitmessage.git;;
rev =
Hi Jeff,
I'm using a similar approach for non-Haskell packages. However, for
Haskell packages it doesn't interact well with cabal2nix. Hence my
question. I have now solved it the following way in
`~/.nixpkgs/config.nix`:
haskellPackageOverrides = self: super:
let asDarcs = path:
On 28 April 2015 at 09:16, Kirill Elagin kirela...@gmail.com wrote:
It would be nice if you showed us the output of `ip route` at the point
where `ip route add` fails.
Also `ip route get 136.243.17.1` might give some hints.
# ip route show
default via 136.243.17.1 dev eth0
136.243.17.0/26 via
Hi,
On 28/04/15 19:04, Richard Wallace wrote:
I keep running into this issue whenever I run `nix-env --upgrade` that nix-env
thinks that nodePackages.7f is an upgrade to nodejs. Consequently, I have to
force a downgrade to the nodejs package after every upgrade. Is there a way
to avoid
It would be nice if you showed us the output of `ip route` at the point
where `ip route add` fails.
Also `ip route get 136.243.17.1` might give some hints.
It totally looks like the gateway you are trying to use is unreachable. To
be honest, I have no idea what does the `mainIPv4 =
These patches look useful, but normally we work via github...
On Tue, Apr 28, 2015, 4:17 AM Jookia 166...@gmail.com wrote:
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
On 04/27/2015 10:42 PM, Eric Merritt wrote:
Thanks all of you. I added the following to my dependee (bin_prot) and
it worked nicely.
setupHook = writeText setupHook.sh ''
export
Hi Tyson,
many packages depend on /bin/sh in one way or another. Remedying that
impurity is a huge effort that's probably characterized best as
on-going. For the time being, we work around this problem by providing a
/bin/sh in the chroot environment through the following /etc/nix/nix.conf
I'd send emails to both authors asking if they plan to update the images :)
On Tue, Apr 28, 2015 at 9:45 AM, Rok Garbas r...@garbas.si wrote:
Quoting Rok Garbas (2015-04-28 09:35:18)
Quoting Christian Theune (2015-04-25 13:41:19)
Hi,
I’ve been working on getting vagrant-based setups
Could you open an issue at github.com/NixOS/nixpkgs ? Thanks!
On Tue, Apr 28, 2015 at 7:34 AM, Ramakrishnan Muthukrishnan
r...@rkrishnan.org wrote:
On Mon, Apr 27, 2015, at 03:56 PM, Ramakrishnan Muthukrishnan wrote:
Hi,
Sorry for the badly worded subject line.
NixOS newbie here.
Applied in 71910be9ea225895e36f60ed23a1bdce402b3088, thanks!
On Apr 27, 2015, at 10:16 PM, Jookia 166...@gmail.com 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
Applied in 7b37a5f168706db5efa33599354f5c1967ac4c51, thanks!
On Apr 27, 2015, at 10:16 PM, Jookia 166...@gmail.com wrote:
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
As long as I’ve been around we’ve also accepted patches via ML, why not?
On Apr 28, 2015, at 2:34 AM, Wout Mertens wout.mert...@gmail.com wrote:
These patches look useful, but normally we work via github...
On Tue, Apr 28, 2015, 4:17 AM Jookia 166...@gmail.com wrote:
When bootstrapping
Quoting Christian Theune (2015-04-25 13:41:19)
Hi,
I’ve been working on getting vagrant-based setups working nicely in the last
weeks and found
https://github.com/oxdi/vagrant-nixos
https://github.com/oxdi/nixos
and
https://github.com/zimbatm/nixbox
The zimbatm has images available,
Quoting Rok Garbas (2015-04-28 09:35:18)
Quoting Christian Theune (2015-04-25 13:41:19)
Hi,
I’ve been working on getting vagrant-based setups working nicely in the last
weeks and found
https://github.com/oxdi/vagrant-nixos
https://github.com/oxdi/nixos
and
28 matches
Mail list logo
