gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | 18.03 release managers: fpletz and vcunat | https://logs.nix.samueldr.com/nixos-dev
obadz- has joined #nixos-dev
obadz has quit [Ping timeout: 240 seconds]
obadz- is now known as obadz
mbrgm has quit [Ping timeout: 268 seconds]
mbrgm has joined #nixos-dev
Cale has quit [Ping timeout: 265 seconds]
Cale has joined #nixos-dev
phreedom has quit [Ping timeout: 250 seconds]
phreedom has joined #nixos-dev
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 240 seconds]
lassulus_ is now known as lassulus
ckauhaus has joined #nixos-dev
ckauhaus has quit [Ping timeout: 260 seconds]
pxc1 has joined #nixos-dev
pxc1 has quit [Ping timeout: 248 seconds]
Sonarpulse has quit [Ping timeout: 260 seconds]
orivej has quit [Ping timeout: 245 seconds]
ckauhaus has joined #nixos-dev
ckauhaus has quit [Ping timeout: 240 seconds]
Cale has quit [Ping timeout: 260 seconds]
MichaelRaskin has quit [Quit: MichaelRaskin]
pxc1 has joined #nixos-dev
orivej has joined #nixos-dev
pxc1 has quit [Ping timeout: 260 seconds]
MichaelRaskin has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
Cale has joined #nixos-dev
orivej has joined #nixos-dev
<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
<clever> nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs:nixos-config=/etc/nixos/configuration.nix:/nix/var/nix/profiles/per-user/root/channels
<clever> oh
<copumpkin> and is failing miserably if I make it my main channel on a nixos box
<clever> its pointing to the symlink in the channel
<clever> the nixpkgs= has to be fixed first
<copumpkin> yeah
jtojnar has joined #nixos-dev
<MichaelRaskin> I think nixpkgs/nixos distinction is partially rooted in the capacity questions…
<copumpkin> capacity questions?
<copumpkin> I get the distinction in the human support between the channels
<copumpkin> I don't think that has to imply that they have slightly different directory structures or shouldn't be technically interchangeable
<MichaelRaskin> Well, there are significantly different sets of tests and build jobs, I think
<MichaelRaskin> They are probably already interchangeable — when everything is well
<copumpkin> yeah, definitely agree there
<copumpkin> just saying that forcing there to be a `nixpkgs -> .` symlink in there isn't great
<copumpkin> they aren't, that's why I did this
<MichaelRaskin> Ouch.
<MichaelRaskin> (I just juggle a repository checkout without ever touching channels)
<copumpkin> also, do we require a top-level directory in channel tarballs?
<copumpkin> like if we buildEnv multiple channels together
<copumpkin> it seems weird to trust the channel tarball to name itself: https://github.com/NixOS/nix/blob/master/corepkgs/unpack-channel.nix
<copumpkin> I'd expect there to either be a -C in there when we invoke tar
<copumpkin> MichaelRaskin: the issue is partly that nix.nixPath defaults to channels/nixos/nixpkgs
<copumpkin> for historical reasons
<copumpkin> so if you point nixos at a git clone, it wants to see a `nixpkgs -> .` symlink in there or you need to explicitly create a nixpkgs entry
<MichaelRaskin> OK, using neither channels nor mainline NixOS does make me forget small details
<MichaelRaskin> That definitely is worth fixing, sure.
<copumpkin> yeah :)
<copumpkin> shlevy: you around?
jtojnar_ has joined #nixos-dev
jtojnar has quit [Ping timeout: 245 seconds]
jtojnar_ is now known as jtojnar
<copumpkin> so if you don't have a top-level directory in your tarball, it unpacks to the root
<copumpkin> and then buildEnv screws that up
jtojnar has quit [Ping timeout: 252 seconds]
goibhniu1 has quit [Ping timeout: 245 seconds]
pxc1 has quit [Ping timeout: 252 seconds]