[Nix-dev] jam passing in hydra but not locally

Hi, I am curious to know why is jam building cleanly in hydra: http://hydra.nixos.org/build/24879066/nixlog/1 But failing consistently for me locally: Yacc1 jamgram.c jamgram.h /bin/sh: 2: yacc: not found yacc -d jamgram.y [...] Makefile:62: recipe for target 'all' failed I have fixed it

[Nix-dev] Changing Nix expressions / Git branches during a build

Hi all, I'm wondering if it's safe to take a single nixpkgs repository, kick off a build (nix-build, nixos-rebuild, etc.), and then once packages are compiling, to change Git branches, edit things, and build more packages without affecting the existing build. I would guess that it's okay because

Re: [Nix-dev] npm2nix issue: github:metaraine/semver-utils is not a valid repository name

Hi, I'm having the same problem. Is there any update on it? Thanks, Thomas On 08/13/2015 03:19 AM, Tinker wrote: > Hi > > I have some problems with the npm2nix command: > npm2nix node-packages.json node-packages-generated.nix > > I get the following error (more or less, logs are a bit messy):

Re: [Nix-dev] Changing Nix expressions / Git branches during a build

Hi, On 07/09/15 18:13, Bryan Gardiner wrote: > I'm wondering if it's safe to take a single nixpkgs repository, kick > off a build (nix-build, nixos-rebuild, etc.), and then once packages > are compiling, to change Git branches, edit things, and build more > packages without affecting the

Re: [Nix-dev] Changing Nix expressions / Git branches during a build

On Mon, 7 Sep 2015 18:57:56 +0200 Eelco Dolstra wrote: > Hi, > > On 07/09/15 18:13, Bryan Gardiner wrote: > > > I'm wondering if it's safe to take a single nixpkgs repository, kick > > off a build (nix-build, nixos-rebuild, etc.), and then once packages > > are

Re: [Nix-dev] Atom 1.0.11 failing to start (need help with debugging)

Well, what I mean is that there could be some bug in Node that is triggered... So using a diffferent Node might fix it. On Sun, Sep 6, 2015 at 7:12 PM Domen Kožar wrote: > It's using bundled nodejs, so that should be the same... It appears that > one of the javascript libraries

Re: [Nix-dev] jam passing in hydra but not locally

Here's one (pretty random) guess: your machine's clock is set in the past, before the timestamps that the files in the source archive have, causing the build system to think some files aren't up-to-date. I've even seen configure scripts getting in infinite loop due to clock being in the past...