<clever>
what about the dns, router, nat, port fortwarding, and firewalls?
<clever>
is port 80 on your domain pointing to the nginx?
<clever>
what does "systemctl status nginx" say?
<clever>
it should have auto-started
<clever>
atis_: yes
<clever>
ixxie: more about how the differences between the sandbox and normal env are making it less reproducable, in that the stable env lacks things that snmp expected every distro to have
<clever>
atis_: nixos will create services to do it automatically, watch "journalctl -f"
<clever>
kiloreux: you need to put the opencore derivation into the buildInputs of ffmpeg
<clever>
and you configure the entries using efibootmgr, which writes to flash memory
<clever>
i think efi supports multiple efi system partitions
<clever>
Phillemann: i think efi has native support for that, but ive not messed with it
<clever>
i clone it once from the installer, directly to /mnt/etc/nixos/
<clever>
i leave nix-channel in control of that
<clever>
and i keep all of that in a subdir of /etc/nixos/
<clever>
same
<clever>
so the stuff specific to the actual hardware isnt controlled, because it will change with every install
<clever>
and then configuration.nix just contains the bare minimum to boot (where / and /boot are and such), along with imports = [ ./nixcfg/hostname.nix ];
<clever>
i have a nixcfg folder with all of the configs, named after each host
<clever>
yeah
<clever>
i git clone from the install cd, so nixos-install does everything at once
<clever>
selecting is faster then select, copy
<clever>
i just always use the selection buffer
<clever>
it pastes whatever you selected, not what you copied
<clever>
thats the selection buffer
<clever>
though some terminals like xterm just dont support the clipboard at all, and only work via the selection buffer
<clever>
but ctrl+c is special in a terminal, so most of them rebind paste to ctrl+shift+c/v
<clever>
and a normal clipboard (ctrl+c, ctrl+v)
<clever>
a selection buffer (whatever you select, middle click to paste)
<clever>
linux has 2 clipboards
<clever>
adelbertc: try the last cmd dtzWill gave
<clever>
yeah, so there should be a channel called nixos-unstable that nix-env can access
<clever>
ls is weird like that when you use -l
<clever>
with the extra / at the end
<clever>
adelbertc: what does this say?
<clever>
ls ~/.nix-defexpr/channels/ -lh
<clever>
ah wait, i was checking an old nixos-unstable
<clever>
alacritty doesnt exist in nixos-unstable
<clever>
i checked, alacritty isnt an attribute in nixos-unstable
<clever>
dod you nix-channel --update ?
<clever>
nix-env -iA nixos-unstable.alacritty
<clever>
after --add, you need to --update
<clever>
that tells it to use the channel called nixos
<clever>
if you do nix-env -iA nixos.hello
<clever>
adelbertc: i usualy try to stick to one
<clever>
rnhmjoj[m]: ah
<clever>
which testing library is it?
<clever>
if thats not possible, then just disable the tests
<clever>
then we still get coverage and it works for everybody
<clever>
like the directory its building in
<clever>
if possible, id modify the tests to use a directory that is known to exist at build time
<clever>
rnhmjoj[m]: hmmm, whats up with that random seed at the end?, why is there any rng in here?
<clever>
rnhmjoj[m]: yeah, all builds on hydra are ran under a container, no /home folder and $HOME points to the /homeless-shelter
<clever>
i wonder, if you do foo = ./symlink; and the symlink points into the store, it may just reuse the store path, since its already immutable
<clever>
catern: dont think ive seen that anywhere
<clever>
if the nix expressions are in the same dir as the source, you can src = ./foo;
<clever>
only if you set the sandbox mode to relaxed, then you can opt-out on a per-derivation basis
<clever>
so its on by default, and you can opt-out
<clever>
where you can specify in the derivation that you want it off
<clever>
oh, but there is a relaxed mode
<clever>
and then it can be hard to figure out why
<clever>
if sandboxing is off, you can do things the wrong way, and it will half work
<clever>
your also trusting that packages havent been written poorly
<clever>
the main hydra also has sandboxing enabled, so it wont get binary cache support from nixos
<clever>
then git cant even clone
<clever>
if sandboxing is enabled, a lack of a sha256 will disable the network
<clever>
adisbladis: it has a fetchSubmodule option
<clever>
and stores that into a file nix can load
<clever>
the most you can do is create a script that pre-runs nix-prefetch-git over each hash
<clever>
nix barely even understands how fetchurl works
<clever>
and nix doesnt understand how git works
<clever>
all network io needs a hash of the resulting output, so nix can know when things have changed and how to reproduce it
<clever>
ah
<clever>
ah
<clever>
catern: submodules?
<clever>
it sounds simpler to run the proper install script, then set the right env variables, then to build it from scratch
<clever>
cbarrett: what files are present under /nix/var/nix/profiles/ ?
<clever>
what was the main problem again, as to why you cant install nix normally?
<clever>
powerpc64?
<clever>
the install script gets around that bootstrap problem by just unpacking a pre-made nix tarball to /nix/store/
<clever>
which will build nix (from nixpkgs) using nix, and add it to the profile
<clever>
nix-env -f '<nixpkgs>' -A nix -i
<clever>
cbarrett: it comes from having the nix package installed with nix-env