<clever>
infinisil: yaml2json is go, but there was a matching binary in haskell at one point
<clever>
kitemikaze_: then you can just builtins.readFile + fromJSON
<clever>
haskellPackages.yaml.out 26,688 x /nix/store/q99hymykq8858kg37f56gibx5cp9gjj6-yaml-0.8.22/bin/yaml2json
<clever>
kitemikaze_: using import-from-derivation, you should be able to call yaml2json
<clever>
gchristensen: the last time i tried to use it on nixos, the buttons just had a 0x0 size
<clever>
gchristensen: they also delete the old binaries, disable them from connecting to the servers, and make changes that break the nix package with every update
<clever>
sagnik: lately, ive only gotten it to work by running windows 10 inside virtualbox, lol
2018-07-05
<clever>
cocreature: is the nixos cache in nix.conf?
<clever>
cocreature: in your case, curl cache.nixos.org/8kp1k26il5n08bqm3f18nhxm0p8qimjc.narinfo
<clever>
cocreature: using the hash from the output (cat the .drv file, its one of the first paths)
<clever>
bpye: and how cacti has been removing features i used to improve performance
<clever>
bpye: my main issues with cacti currently, is that you have to configure what to graph at a central point, while push-based things like DD have that configured on the remote machines
<clever>
bpye: but the cacti ui has been getting worse lately, and a push based model is just simpler to use
<clever>
bpye: prior to getting into nixos, i used cacti and net-snmp for everything
<clever>
bpye: but i have seen his alerts go off a few times
<clever>
bpye: i know somebody that uses prometheous heavily, but i havent seen how he configured it
<clever>
bpye: the free version also has a fairly low host count
<clever>
cocreature: it should be in the binary cache
<clever>
bpye: yep
<clever>
bpye: and also make sure it can still boot
<clever>
bpye: yeah
<clever>
worldofpeace: read the wrapper script, manually run the export statements, then run gdb against the -wrapped binary
<clever>
hyper_ch: i helped somebody debug something a few days ago, where his channel was configured with nginx+nixos, and was hosting a tar directly from the store
<clever>
infinisil: and nginx etag's are generated based on the filesize and last-mod timestamp, so nix's timestamp fudging can massively break it
<clever>
infinisil: fetchTarball will use the last-modified and etag headers the remote server advertises to cache the reply
<clever>
on nixos, it can look under roots channels
<clever>
eren: ~/.nix-profile/share/man for things in your local profile
<clever>
pie_: just use bind, its a lot less painful :P
<clever>
also open here, and i dont see wmertens being mentioned
<clever>
nlytend: --delete-older-than 3d will delete generations from older then 3 days, then the normal GC deletes all garbage, including partial results from a recent nixos-rebuild
<clever>
booglewoogle: nix-store --delete, and dont use force if it says its in use
<clever>
sphalerite: it shows both of these right on the site
<clever>
and then make an override to add that to patches
<clever>
then make a patch with `diff src-orig src -u > foo.patch`
<clever>
booglewoogle: then edit the non-orig version, to look for the config elsewhere, maybe obey a $FOO_CONFIG_PATH var
<clever>
booglewoogle: then copy the entire directory to src-orig
<clever>
booglewoogle: first, i would nix-shell into an env suitable for building the package, and run unpackPhase and patchPhase in the unpacked directory
<clever>
booglewoogle: or patched to look for the config in a better location
<clever>
booglewoogle: it has to be patched at build time to have the new config
<clever>
disasm: look at the shell.nix in iohk-ops, under passthru
<clever>
Lisanna: nix-instantiate?
<clever>
arahael: i grepped all of nixpkgs, nothing refers to it
<clever>
arahael: that is a different project that some people have been working on
<clever>
pile*
<clever>
nix-darwin is just a pipe of scripts that let you manage some things in a nixos like way
<clever>
kernel is also untouched
<clever>
the ui is untouched
<clever>
it just manages a few files in /etc/ via nix
<clever>
arahael: nix-darwin still runs on the darwin kernel and the whole darwin ui
<clever>
it looks like valgrind needs fixed, but it appears to actually support darwin
<clever>
valgrind: mmap-FIXED(0x0, 253952) failed in UME (load_segment1) with error 12 (Cannot allocate memory).
<clever>
arahael: oh and the nix command is new and lacks man pages
<clever>
arahael: the manpages are in ~/.nix-profile/share/man/ and the man from your distro doesnt look there
<clever>
arahael: your MANPATH has to be updated
<clever>
that command is more about finding a package that contains a given file, then searching by package name
<clever>
arahael: there is also this bot on irc
<clever>
,locate bin/firefox
<clever>
nix-env has some magic flags for that, cant remember the exact ones
<clever>
s/can/scan/
<clever>
arahael: in nixos, its done via /run/current-system mostly, which replaces /bin and /lib for example
<clever>
angerman: if you try to ++ yourself, the bot will take away a point
<clever>
:D
<clever>
it works best under the linux kernel, but can also function on darwin, and it can generate results that are usable on more platforms
<clever>
you must untar nix from ubuntu, then rename things
<clever>
so you have no way to just install a nix based os
<clever>
arahael: you also have no way to manage a 2nd rootfs within a given user
<clever>
arahael: so the only way to install a custom WSL distro is to untar it inside ubuntu, then use atomic move's from explorer to swap the rootfs
<clever>
arahael: one WSL problem ive heard, is that the files in the rootfs have to be tagged with a special attribute, which windows explorer cant copy when copying files
<clever>
:D
<clever>
no need for any cross-compile fun
<clever>
arahael: this command will build the darwin version of hello, using darwin build slaves
<clever>
nix-build '<nixpkgs>' -A hello --argstr system x86_64-darwin
<clever>
there is also qemu-user, which can run linux binaries for the "wrong" arch
<clever>
aminechikhaoui: but you still need enough free to complete max-jobs in parallel
<clever>
aminechikhaoui: oh, min-free also lets you go a lot lower, because it will auto-gc at the start of any action on the store, so you dont need to keep enough free to survive the next 24 hours
<clever>
LnL: it has also caused builds to fail randomly, by deleting something thats in use by a building derivation
<clever>
LnL: import-from-derivation sometimes triggers a GC and eats stuff the build needs, but hasnt computed the path to yet
<clever>
LnL: i have them enabled on 2 or 3 of my machines
<clever>
but it has some bugs involving gcroots and sometimes breaks builds
<clever>
that triggers a gc with 3gig free, and aims to get 6gig free
<clever>
max-free = 6442450944
<clever>
min-free = 3221225472
<clever>
aminechikhaoui: but the new min-free and max-free in nix.conf work better, doing a larger gc less often, rather then a small gc every day at the same time
<clever>
aminechikhaoui: the goal is to get 128gig free, and keep anything that remains, so it can still act as a cache
<clever>
and i keep that in a git repo of nixos configs, so all hosts automatically known all other host keys, from the first install
<clever>
i like programs.ssh.knownHosts, because it eliminates the risk of a mitm on the 1st connection
<clever>
aminechikhaoui: or use programs.ssh.knownHosts in configuration.nix to configure the known_hosts globally