<clever>
fooker: if you do `foo = "bar"; passAsFile = [ "foo" ];` then youll get a $fooPath instead of a $foo at build time, which saves you all the escaping nightmares
<clever>
fooker: either buildEnv a few writeFile's together, or just use runCommand and maybe passAsFile
<clever>
jluttine: only real effect is if you start having weird stuff like maybe a ? or spaces in the url, otherwise they are the same
<clever>
jluttine: id prefer to have it quoted
<clever>
:D
<clever>
lovesegfault: then nix can generate the script for you
<clever>
lovesegfault: i also like using pkgs.writeShellScript, then doing `nix-build && ./result`
<clever>
git will keep the symlink intact, and the file wont exist on the remote end
<clever>
to make it cease to be a symlink
<clever>
you may need to `nix-build -o foo.yaml.temp && cat foo.yaml.temp > foo.yaml`
<clever>
lovesegfault: make an expression using writeTextFile, and nix-build -o foo.yaml
<clever>
lovesegfault: the only place nix can write, is the store, but nix-build can produce symlinks to that result
<clever>
kolby_: what is wrong with the default buildPhase ?
<clever>
kolby_: if that variable is empty, you wind up doing `make -j` which tells make to spin up infinite jobs
<clever>
kolby_: each nix job, will spin up its own $NIX_BUILD_CORES jobs, so if you `nix-build -j 5`, it will be up to 5 seperate derivations, each doing make -j $NIX_BUILD_CORES
<clever>
kolby_: that sounds fine
<clever>
cole-h: and that change will result in you needing to re-compile glibc and gcc from scratch
<clever>
cole-h: only using an overlay
<clever>
pie_[bnc]: to me, that says that qtah isnt in the cabal.project file, and/or the hackage snapshot
<clever>
ah, that issue title would explain things
<clever>
the library gets built, the executables get built seperately, each test gets built in one drv, then ran in a 2nd
<clever>
pie_[bnc]: if a .cabal file defines a library, 3 executeables, and 4 tests, it will turn into 1+3+(4*2) derivations
<clever>
pie_[bnc]: derivation per component
<clever>
pie_[bnc]: nix-instantiate the drv before and after adding qt, then run nix-diff, what did adding qt change?
<clever>
cole-h: yeah, it depends on what has changed in master recently, and how long its been like that
<clever>
cole-h: the channels only update after hydra has finished building everything
<clever>
cole-h: master hasnt been built by hydra yet
<clever>
cole-h: are you getting that nixpkgs from a channel?
<clever>
pie_[bnc]: all drv files are named after a hash of their contents, there might be a way to add the drv back into the store, but i dont know it off-hand
<clever>
pie_[bnc]: isnt really possible
<clever>
pie_[bnc]: haskell.nix will find the file on its own, in src
<clever>
pie_[bnc]: about all you can really do is read `nix show-derivation`, and then manually call `builtins.derivation` with the same values, using ${/nix/store/foo` where possible to maintain context
<clever>
pie_[bnc]: then manually run each phase the .drv would have ran
<clever>
pie_[bnc]: you can run nix-shell on a .drv file, to get that env loaded
<clever>
pie_[bnc]: ah, thats the same kind of digging ive been doing, to fix all of the IFD stuff
<clever>
pie_[bnc]: why cant you import the original nix expr?
<clever>
pie_[bnc]: note, that all functions like .overrideAttrs are lost
<clever>
pie_[bnc]: run import on the path to the drv
<clever>
gchristensen: something else that surprised me early on, is how none and ec2 handle ssh keys in vastly different ways
<clever>
adisbladis: that just leaves stateVersion then
<clever>
adisbladis: second, the auto-created private keys
<clever>
adisbladis: first, nixops will query the stateVersion, and remember it in the state file
<clever>
adisbladis: i can see 2 features that would break when doing that...
2020-03-10
<clever>
,tell johnw that might be a bug with --verify not obeying ?root=/path
<clever>
ah
<clever>
Henson: ?
<clever>
Henson: what value did you assign to it?
<clever>
Henson: yeah, what are you setting it to exactly?
<clever>
ashkitten: systemd also has its own isolation that can do similar, without needing full containers
<clever>
ashkitten: none that i know of, but you could search github
<clever>
ashkitten: currently, the nixos containers dont support that
<clever>
selfsymmetric-mu: yeah, thats definitely the kernel, can you gist the entire configuration.nix file?
<clever>
selfsymmetric-mu: what derivation is it building often during updates?
<clever>
thats not a patch, but it may need you to build just exfat-nofuse
<clever>
selfsymmetric-mu: do you have any kernel patches set?
<clever>
selfsymmetric-mu: what exactly is `nix-channel --list` saying?
<clever>
selfsymmetric-mu: which channel are you set to?
<clever>
johnw: then your just using local->local copies
<clever>
johnw: daemon means talk to nix-daemon to get access to /nix/store
<clever>
johnw: local means just open things in /nix/store directly
<clever>
johnw: local is also the name of the main /nix/store dir
<clever>
johnw: do you have several things in the substituters list?
2020-03-09
<clever>
evanjs: you may need pkgs.runCommand to unpack the tar
<clever>
fresheyeball: it may be off by a few minutes around newyears
<clever>
fresheyeball: but now you need to deal with leap seconds in nix
<clever>
fresheyeball: note that it will change every second, and ruin any hope of caching the builds if you dont divide down in nix
<clever>
> builtins.currentTime
2020-03-08
<clever>
lovesegfault: the readme makes it sound like just a very stripped down nixops
<clever>
ah, no, ive not used that any
<clever>
lovesegfault: dont remember what morph does
<clever>
yep
<clever>
nice
<clever>
lovesegfault: you pinned all the things? :D
2020-03-07
<clever>
jlv: i see an example in one of my old clones of nixops
<clever>
pie_[bnc]: last time i used it, eclipse was pretty nice
<clever>
pie_[bnc]: it also has special handling for several languages, but ive not really bothered configuring them, the c++ stuff magically comes to life if i run vim under nix-shell
<clever>
pie_[bnc]: youcompleteme + vim will auto-complete any token found in any open file, out of the box
<clever>
lovesegfault: the submodule can set a config= for each sub-module, and if you begin adding your own options like i did, then you can also add your own config= .....
<clever>
lovesegfault: enless you modify the submodule maybe, check iscsi-boot.nix
<clever>
lovesegfault: not really
<clever>
lovesegfault: check iscsi-boot.nix in nixos-configs
<clever>
lovesegfault: yes
<clever>
lovesegfault: submodules
<clever>
lovesegfault: then you run that returned map, on the function, and overlayFiles
<clever>
lovesegfault: you are running traceVal on map (which prims primop) and returns map
<clever>
lovesegfault: i just did it my way, to group other stuff together
<clever>
lovesegfault: youd have to check the nixpkgs docs, but i think it works the way your expecting
<clever>
lovesegfault: for <nixpkgs-overlays> it needs a certain format, and i was using foo/default.nix, so foo/other-files.nix would be grouped in a foo/ dir
<clever>
lovesegfault: for nixos overlays, you just need to populate nixpkgs.overlays with a list of functions, how you get them doesnt matter
<clever>
infinisil: nix eval nixpkgs.lib.version
<clever>
pie_[bnc]: i believe cmake is smart enough to know when the CMakeLists.txt is changed
<clever>
lovesegfault: use map to generate a list of sets, each with a name/value pair, then listToAttrs to convert
<clever>
> :p lib.nameValuePair "name" 42
<clever>
> :p lib.listToAttrs [ { name = "a"; value = 42; } ]
<clever>
lovesegfault: > :p ...
<clever>
lovesegfault: yep
<clever>
no idea
<clever>
zeta_0: ghcjs can do that too
<clever>
zeta_0: no clue, ive never used elm
<clever>
2020-03-06 21:50:24 < clever> zeta_0: line 1 wants a path to nixpkgs, not a pkgs set, so you must either change line 1 to <nixos-unstable> or you must `import /path/to/default.nix { nixpkgs = <nixos-unstable>; }`
<clever>
zeta_0: or edit line 1
<clever>
zeta_0: when using nix-shell or nix-build, you must `--arg nixpkgs '<nixos-unstable>'`
<clever>
zeta_0: what does `--show-trace` show with the error?
<clever>
zeta_0: the default.nix that is doing elm stuff, where is it loaded?
<clever>
zeta_0: line 1 wants a path to nixpkgs, not a pkgs set, so you must either change line 1 to <nixos-unstable> or you must `import /path/to/default.nix { nixpkgs = <nixos-unstable>; }`
<clever>
zeta_0: you need to `import <nixos-unstable>` to get the fix
<clever>
zeta_0: that change isnt in 19.09
<clever>
zeta_0: what does `nix-channel --list` report?
<clever>
zeta_0: then your nixpkgs is too old, and is expecting the older style
<clever>
cole-h: if you remove the result symlink, and `nix-store --delete /nix/store/hash-dolphin` you can purge it from your store, and then try again without root
<clever>
cole-h: either its random network problems that resolved themself, or something is broken with non-root nix
<clever>
zeta_0: the error says that fetchElmDeps wants a certain param, try adding that param to the default.nix?
<clever>
cole-h: try an strace on that, as root
<clever>
cole-h: what happens if you try just `nix-build '<nixpkgs>' -A dolphin` ?
<clever>
cole-h: that looks like nix-shell talking to nix-daemon
<clever>
bqv[m]: buildInputs doesnt do much at the nix layer, and just becomes an env var for the shell code in stdenv to handle
<clever>
bqv[m]: all keys are passed on
<clever>
cole-h: what if you use -vvv ?
<clever>
cole-h: because you cranked the verbosity up enough to see debug within the http area
<clever>
zeta_0: the error does not appear to be coming from the default.nix you pasted
<clever>
,callPackage zeta_0
<clever>
lovesegfault: youll need to map over it, and append each filename to the dir
<clever>
alexfmpe[m]: i ran into the exact same problem on an rpi, many years ago
<clever>
alexfmpe[m]: and because of how disposable the file is, nix disabled all atomic logic in sqlite to make it perform better, which opens the risk of it becoming corrupt
<clever>
alexfmpe[m]: that file is re-created any time its missing
<clever>
alexfmpe[m]: you can just `rm /root/.cache/nix/binary-cache-v6.sqlite*`
<clever>
Shell: ahh
<clever>
coderobe: does that path exist within the bundle?
<clever>
coderobe: if you use strace to run the bundle, what errors does execve give?
<clever>
coderobe: getting nix itself to work in nix-bundle is tricky
<clever>
coderobe: why are you unable to use nix on the host?
<clever>
fresheyeball: ref = "branch";
<clever>
fresheyeball: you must tell fetchgit what branch the rev is part of
<clever>
softinio[m]: what is the exact error it gave?
<clever>
softinio[m]: nix-instantiate said it does exist
<clever>
softinio[m]: ls -l /nix/var/nix/profiles/per-user/root/channels /nix/var/nix/db/big-lock
<clever>
softinio[m]: oops, ^
<clever>
sixx: as root, `cat ~/.nix-channels`
<clever>
sixx: when doing it with the none backend (as shown here), you need to take care that all of the config for fileSystems."/" is present in the file, or it will loose the ability to boot
<clever>
sixx: then you just `nixops create -d name house.nix` and `nixops deploy -d name`
<clever>
sixx: lines 12 and 16 tell nixops what to ssh into when deploying
<clever>
sixx: nas.nix and router.nix are basically just configuration.nix files, for 2 different machines