<clever>
devalot: usually when it causes major breaking changes, and some people refuse to update their code
<clever>
devalot: if you do anything else, your package will depend on 2 different lenses (via other libraries) and bad things will happen
<clever>
devalot: write an overlay that does lens = self.lens_4_18;
<clever>
fresheye1: nix-store --verify --check-contents --repair, i think
<clever>
fresheye1: or just nix-store --delete the path that is corrupt, dont force it
<clever>
fresheye1: nix-store --repair-path
<clever>
fresheye1: nix-store --verify --check-contents, would have told you what was corrupt
2019-10-13
<clever>
Ralith_: is the fix in home-manager or nixpkgs?
<clever>
Ralith_: then it will be within your own users home
<clever>
Ralith_: depends on if your using plain home-manager or the home-manager module in nixos
<clever>
for the user doing the eval
<clever>
Ralith_: thats in ~/.cache/nix/tarballs/
<clever>
Ralith_: is the fix in a channel yet?
<clever>
ornx: only the nixpkgs buildenv can run thngs in the post hook
<clever>
ornx: its a limitation of the buildenv that nix-env uses to merge things
<clever>
then install just that with nix-env
<clever>
ornx: you could manually implement it if you make your own drv with buildEnv and a post command, and then put everything with icons into that buildEnv
<clever>
ornx: only systemPackages via configuration.nix supports running commands after merging, to update such caches
<clever>
danderson: lib.mkEnableOption may also interest you
<clever>
danderson: ah, yep, that will do weird things
<clever>
they should all be under config
<clever>
danderson: you can also do `nix repl '<nixpkgs/nixos>'` and then eval any option you want, to see what is set to what
<clever>
danderson: does the file exist in /etc/systemd/system/ ?
<clever>
danderson: that error makes no sense to me either, but i would try `= lib.mkIf cfg.autoStart [ "multi-user.target" ];`
<clever>
fresheye1: nix tells you, on the like immediately after that one
<clever>
hpfr[m]: what does it hang on if you use -vvvv ?
<clever>
hpfr[m]: are all substituters reachable?
<clever>
hpfr[m]: its part of this clause
<clever>
hpfr[m]: In addition, nixos-rebuild accepts various Nix-related flags, including --max-jobs / -j, --show-trace, --keep-failed, --keep-going and --verbose / -v. See the Nix manual for details.
<clever>
fresheye1: you never answered that question
<clever>
fresheye1: what did the nix-store -r over ssh return?
<clever>
danderson: then it can figure out what your doing later, and not cause recursion
<clever>
danderson: but if you instead config.environment = mkMerge ... ; config.systemd = mkMerge ...;
<clever>
danderson: and it cant know what your mkMerge returns, until it knows what config.networking was
<clever>
danderson: the problem, is that it must know every attribute of config.<?> before it can give you the value of config.networking.pppd
<clever>
danderson: you also dont use the @ sign if you are giving each IF its oan ExecStart
<clever>
danderson: nixos needs to know which attrs of config you are setting, so it can route around your value, and figure it out later
<clever>
fresheyeball: then $NIX_PATH isnt being set, need a different test
<clever>
fresheyeball: what error does ti fail with?
<clever>
fresheyeball: what about `ssh user@host nix-build '<nixpkgs>' -A hello` ?
<clever>
fresheyeball: what about `ssh user@host nix-store --version?
<clever>
evanjs: and what channels you have
<clever>
evanjs: i think the failure depends on the value of $NIX_PATH
<clever>
fresheyeball: sshServe just uses sshd
<clever>
its nixos, what do you even need state for? :D
<clever>
gchristensen: in my case, its much more of a mystery, the entire network is just offline, including the router, so i have no way to debug anything!
<clever>
gchristensen: ouch
<clever>
j4m3s__: and what about the 2nd machine?
<clever>
gchristensen: ah, still not fixed?
<clever>
,paste
<clever>
,pastebin j4m3s__
<clever>
j4m3s__: how do the configs between the 2 differ? can you give more info like the lsblk of both?
<clever>
gchristensen: all vpn's that connect out are mia, the public ip doesnt respond
<clever>
gchristensen: that reminds me, my entire house just dropped off the face of the internet, while out for thanks giving
<clever>
j4m3s__: would need to run tests in a vm to see if it does or doesnt work
<clever>
j4m3s__: then something else must be wrong with the cryptodisk setup, are you using luks?, hmmm, maybe grub doesnt understand lvm on luks?
<clever>
o1lo01ol1o: usually is
<clever>
o1lo01ol1o: most of the time, you can just change the nix-channel, `nixos-rebuild boot`, and reboot
<clever>
evanjs: so if the package is in the release.nix, the channel wont update until hydra has tried (but a failure still counts)
<clever>
evanjs: the channel doesnt update until hydra has at least tried to build every single package
<clever>
evanjs: thats what channels do
<clever>
j4m3s__: setting the nixos option will pass that env var to grub for you
<clever>
evanjs: either your own, or file a pr to nixpkgs, to hydra.nixos.org could pre-build it
<clever>
j4m3s__: ah, that env var is a direct option for grub
<clever>
cjpbirkbeck: is hardware-configuration.nix listed in configuration.nix?
<clever>
lukash_: for the nix-channel cmd
<clever>
cjpbirkbeck: is it added to hardware-configuration.nix?
<clever>
lukash_: try with --option sandbox false
<clever>
cjpbirkbeck: what part doesnt work?
<clever>
cjpbirkbeck: how does it not work when you run nixos-generate-config?
<clever>
cjpbirkbeck: if /boot isnt mounted, then you wont be updating the boot config
<clever>
cjpbirkbeck: is /boot mounted?
<clever>
evanjs: that could explain random crashes in many programs
<clever>
evanjs: id give memtest86 a pass
<clever>
evanjs: got a backtrace?
<clever>
lukash_: did you use strace -f?
<clever>
bbl
<clever>
lukash_: what does dmesg say?
<clever>
lukash_: is this on nixos?
<clever>
lukash_: is something mounted read-only?
<clever>
pikajude: nix will use localhost automatically
<clever>
lukash_: what user did you run it as?
<clever>
lukash_: what error does --update give?
<clever>
lukash_: nix-channel --list?
<clever>
nornagon: nix-shell always uses bash, you can also try `nix run nixpkgs.jdk11_headless`
<clever>
nornagon: yeah
<clever>
nornagon: only add one of them to systemPackages, or add zero, and use nix-shell to pick one as-needed
<clever>
Aleksejs: installing it wont add the headers, only nix-shell can do that
<clever>
Aleksejs: you should use `nix-shell -p udev`
<clever>
danderson: create a foo@.service, and then several foo@bar.service things, and it will spawn several instances of foo@.service, with %i filled in with bar
<clever>
it will basically just `nix-store -qR` that binary
<clever>
nornagon: ExecStart is a path to a binary in the store
<clever>
i learned about the cache caches, because they broke :P
<clever>
infinisil: an improper shutdown of my rpi corrupted those caches, causing all nix options on the rpi to fail
<clever>
infinisil: fun fact, nix disables some sqlite safeties when interacting with those files (at least in the old days), to make it perform faster
<clever>
if you delete them, it will re-check things
<clever>
and these files are what hold the cache about the caches
<clever>
[root@system76:~]# ls ~/.cache/nix/binary-cache-v6.sqlite*
<clever>
superbaloo: oh, that reminds me, you may want to also look into the nix copy flags...
<clever>
i should give things another spin
<clever>
superbaloo: looks like a fairly basic cross-compile setup, last i heard, most packages broke with that, but it sounds like the recent nixpkgs has improve things
<clever>
superbaloo: can you pastebin the nix files you used?
<clever>
ah, nice, ive heard that had trouble
<clever>
superbaloo: just nix? or all of nixos?
<clever>
dsx: even if you add the script, what will run it? when do you want it ran?
2019-10-12
<clever>
isd: and if you run `vgchange -a y`, does the `LV Status` in `lvdisplay` change?
<clever>
isd: can you pastebin the output of `pvdisplay ; vgdisplay ; lvdisplay` ?
<clever>
id say this is a bug in nix, when it decides if it should copy to the store or not
<clever>
leo_: but youve got pkgs.path pointing to a symlink, which confuses nix, causing it to copy from store->store, and prefix another hash onto it
<clever>
leo_: so nixops will always unpack that tar to a stable path, and pkgs.path points to that, and no copying happens
<clever>
AmandaC: some of the output paths will have to be tweaked
<clever>
AmandaC: find the drv for the that path, and run `nix show-derivation` on it, to see the build command, then see if you can reproduce it by manually running the cmd
<clever>
AmandaC: 404
<clever>
and if its already built, it will just print the path to the result
<clever>
and i own my own dir
<clever>
drwxr-xr-x 3 clever users 13 Oct 9 04:11 /nix/var/nix/profiles/per-user/clever/
<clever>
i just look at the permissions on a nixos machine and copy them over, for any dir that fails
<clever>
you need to own your subdir from /nix/var/nix/profiles/per-user/
<clever>
and then fixing ownership for profiles
<clever>
yeah
<clever>
isd: recursive chown, -R
<clever>
isd: it sounds like you dont have a multi-user setup fully configured, /nix/store and /nix/var should be owned by root (along with most of the subdirs), and nix-daemon has to be running as root
<clever>
isd: is nix-daemon running?
<clever>
infinisil: if you have write to /nix/var/nix/db/ then nix wont try to contact the daemon, and wont gain root automatically
<clever>
isd: is nix-daemon running? who owns /nix/var/db ?
<clever>
infinisil: --option sandbox false, is the simplest fix
<clever>
infinisil: if you run it as root, it will fail because the nixbld group has no members
<clever>
infinisil: yep, thats exactly it
<clever>
AmandaC: you can run `nix-store -l /nix/store/foo` to get the logs for a build, if it passed
<clever>
AmandaC:not sure what else to do then
<clever>
and all context around it
<clever>
AmandaC: can you pastebin the exact error?
<clever>
matthuszagh: you want something like this, to append to it
<clever>
pkgs/default.nix:postUnpack = "sourceRoot+=/socket-io; echo source root reset to $sourceRoot";
<clever>
matthuszagh: sourceRoot must remain relative to . via the copy
<clever>
matthuszagh: the unpackphase will copy $src to ., then set sourceRoot to be the path relative to ., after unpackPhase, it will cd $sourceroot
<clever>
freedan42x: it looks like you forgot .env
<clever>
but you can also add shellHook at the same time
<clever>
freedan42x: this uses overrideAttrs to mutate a cabal2nix drv, and add buildInputs