<srhb>
I have a bizarre problem that I can't figure out. I have a derivation that I can build on one host just fine, but on another I get "s not allowed to refer to the following paths: .... bootstrap-tools, ... busybox" -- as far as I can see all nix daemon configuration is identical aside from the fact that one uses remote builders, the other does not. Are remote builds something I should even suspect here? Can
<srhb>
I force a remote build to test it?
<srhb>
Or a local one, even.
<srhb>
Hm, same issue with --builders '' which looks to force a local build, so that's not it.
<sphalerite>
you can force a remote one using --max-jobs 0
srhb has quit [Quit: Quit]
srhb has joined #nixos-dev
jtojnar has quit [Remote host closed the connection]
contrapumpkin has joined #nixos-dev
goibhniu has quit [Ping timeout: 256 seconds]
drakonis has joined #nixos-dev
contrapumpkin has quit [Remote host closed the connection]
Sonarpulse has joined #nixos-dev
pxc1 has joined #nixos-dev
ckauhaus has joined #nixos-dev
drakonis has quit [Remote host closed the connection]
ckauhaus has quit [Remote host closed the connection]
<copumpkin>
niksnut: would you expect --check on a FO derivation whose current hash is valid in the store to ever fail?
<copumpkin>
oh, never mind, PEBKAC :)
<copumpkin>
I think
Synthetica has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
ckauhaus has joined #nixos-dev
ckauhaus has quit []
goibhniu has joined #nixos-dev
orivej has joined #nixos-dev
globin has quit [Ping timeout: 276 seconds]
globin has joined #nixos-dev
goibhniu1 has joined #nixos-dev
goibhniu has quit [Ping timeout: 245 seconds]
<copumpkin>
hmm, our nixos releases still have a `nixpkgs -> .` symlink in them
<copumpkin>
which feels a bit like a historical relic at this point
<copumpkin>
(the channel tarballs)
<gchristensen>
I think it is necessary for <nixpkgs> to work?
<copumpkin>
yeah, wondering if we can't normalize the nixos/nixpkgs separation now
<copumpkin>
and just make everything use nixpkgs so we don't have to give different instructions for folks on nixos and other platforms
<copumpkin>
seems to confuse just about everyone, including me after working with it for years
<clever>
gchristensen: NIX_PATH has a nixpkgs= entry, so its not using that symlink
<gchristensen>
ah
<copumpkin>
I think it is
<clever>
*looks*
<copumpkin>
because my homegrown nixpkgs channel doesn't have the symlink