<clever>
roots channels are available for user by all, but cant directly be listed
<clever>
inkbottle: yes, every user has its own set of channels
<clever>
inkbottle: thats not the wifi card
<clever>
`nix-channel --list` will show which channel your currently on
<clever>
i happen to be on nixos-unstable
<clever>
inkbottle: nix-channel --update
<clever>
inkbottle: my wifi has been crap since i last did an update
<clever>
inkbottle: double-check lspci
<clever>
inkbottle: intel card?
2019-11-04
<clever>
exarkun: i would watch `watch -d df -h` while its building, and see which one fills up
<clever>
exarkun: nixos doesnt put builds in /run/user
<clever>
sondr3: try again with just pkgs.postgresql
<clever>
sondr3: ah, i think it has to do with the postgresql version, i did have code here to change it, but it was messy, so i went with the older version
<clever>
leo_: i would try using concatLists to generate the big list from smaller ones
<clever>
leo_: while this, will copy 1+2->1st, then copy 1+2+3 -> 2nd
<clever>
> [1] ++ [2] ++ [3]
<clever>
leo_: if you have a list of lists, its cheaper to use concatLists, that will pre-allocate room for 3 elements, then copy things from each input to the 1 output
<clever>
> builtins.concatLists [ [1] [2] [3] ]
<clever>
leo_: each time you append to a list, it has to copy the entire list, so it gets slower with each item
<clever>
Twey: you would need to strace the nix-daemon to see what its doing
<clever>
Twey: hmmm, yeah, i'm not sure then
<clever>
Twey: that stdenv may be horribly broken and unable to do anything
<clever>
Twey: buildCommand is ran by the stdenv, which is ran by the args for builder
<clever>
Twey: i'm guessing that you broke the stdenv and the stdenv is now unable to run buildCommand
<clever>
Twey: then you want buildCommand
<clever>
Twey: a lot of the depenency tracking is based on the contents of $out, which your changing
<clever>
Twey: you probably want to use pkgs.runCommand
<clever>
samueldr: .override { stdenv = ... } first
<clever>
CMCDragonkai: you want nix repl '<nixpkgs/nixos>' -I nixos-config=modules/installer/cd-dvd/installation-cd-minimal.nix
<clever>
CMCDragonkai: isoimage is only present if you do `-I nixos-config=modules/installer/cd-dvd/installation-cd-minimal.nix` when you load nixos/default.nix
<clever>
pie_: behind the scenes, <nixpkgs> parses to __findFile __nixPath "nixpkgs"
<clever>
so nix can do that fetch in parallel
<clever>
infinisil: main benefit of it, is that it happens at build time, but to make things pure, you must know $out before you know the value
<clever>
infinisil: when the system is "builtin" and the builder is "builtin:fetchurl", nix will run builtinFetchurl() inside a normal fixed-output derivation sandbox
<clever>
if the hardware is lost, that has to change anyways, so why preserve it in git
<clever>
deni: and configuration.nix only has stuff tied to the hardware, like filesystem uuid's and such
<clever>
deni: personally, i do imports = [ /path/to/foo.nix ]; in configuration.nix
<clever>
deni: ddclient only has one output, so both of those are identical
<clever>
> ddclient.outputs
<clever>
deni: merely referencing the string makes it a dependency, thats how all dependency tracking works in nix
<clever>
deni: so nix must download the binary before it can build nixos
<clever>
deni: the binary is just a dependency of the .service file, which is a dependency of the nixos build
<clever>
deni: depends on the service, ive seen a few that dont add to systemPackages, just cant think of which
<clever>
deni: cant think of one that doesnt add to systemPackages
<clever>
talqu: then you need to make a new nix expr, that will merge things like buildInputs from both
<clever>
talqu: why do you want to load 2 files at once, are you trying to get the deps of both, or the result of building both?
<clever>
deni: and nixos then just shoves all of those .service files into a single directory, and drops a symlink in /etc/systemd/system/ pointing to that dir
<clever>
deni: a service is just another derivation, that generates a systemd .service file
<clever>
deni: callPackage just imports another nix file, and calls the function within, passing it arguments from pkgs.
<clever>
deni: callPackage typically returns a string, saying where to find the binary
<clever>
deni: basically, any string you refernece, gets copied to /nix/store, it doesnt have to be in a magic variable to be downloaded
<clever>
deni: the systemd services always ignore the system wide PATH, and use their own PATH value
<clever>
but you may not be able to interact with it after it starts, depending on what it is
<clever>
you will never need to add something to systemPackages to make it work
<clever>
for things like openvpn, you cant interact with it
<clever>
for things like postgresql and mysql, its expected that you get a psql and mysql binary, so you can interact with the daemon
<clever>
deni: depends on if your meant to be running it on the cli often or not
<clever>
deni: you should read the module for foo, and see what it does when enable is true
<clever>
talqu: zfs snapshots will just keep a copy of everything, so you can undo any changes
<clever>
kraem: which is usually your configuration.nix file
<clever>
kraem: which reads whatever <nixos-config> maps to
<clever>
tomberek: and also ssh://user@host to query a remote box
<clever>
tomberek: it will also support things like "local?root=/mnt", which reads /mnt/nix/var/nix/db
<clever>
tomberek: if you open the "auto" store, it will auto-detect if you can read db.sqlite directly, or need nix-daemon, and then return a Store*, with virtual functions to deal with the differences
<clever>
chris__: i think hydra is only pre-building for ghc 8.6.4, and your forcing 8.6.5
<clever>
chris__: line 2 of shell.nix doesnt really do anything, does it behave any different if you switch to pkgs.haskellPackages, instead of pkgs.haskell.packages.${compiler} ?
<clever>
Miyu-saki: it doesnt need to, thats more of a side-effect of the de-perling, nix-build was once a perl script that ran nix-instantiate and nix-store -r seperately
<clever>
chris__: can you link a github repo with your nix exprs?
<clever>
chris__: and the path doesnt match what hydra has for that rev
<clever>
chris__: 404 means that directory is not in the binary cache
<clever>
chris__: the storepath doesnt match up, so your either on a different nixpkgs, or you have an overlay that changes something