<clever>
drakonis: yeah, re-opening the shell will remove it from NIX_PATH
<clever>
then another --update
<clever>
rm /home/drakonis/.nix-defexpr/channels
<clever>
its a symlink into the store
<clever>
i said just rm
<clever>
what is the exact command you ran?
<clever>
it shouldnt be
<clever>
try deleting /home/drakonis/.nix-defexpr/channels then, just simple rm
<clever>
oh
<clever>
i dont think lustrate has much to do with this
<clever>
drakonis: double-check the contents of ~/.nix-channels
<clever>
but home manager is likely using <nixpkgs> (as nonroot)
<clever>
i can also see that <nixos> and <nixpkgs> (as root) will map to the channel you want, with the new version
<clever>
thats saying you currently have 2 chnanels on your user, home-manager and nixpkgs, try running `nix-channel --update` again and see if it changes anything?
<clever>
can you pastebin the output of `ls -l /home/drakonis/.nix-defexpr/channels*/`
<clever>
when did you last --update without root?
<clever>
thats strange
<clever>
and what exactly does nix-channel --list return? on both users
<clever>
that means you have a channel called nixpkgs on your current user
<clever>
colemickens: and because i run screen, that just makes things worse, it maps to the tty above screen, not inside screen
<clever>
colemickens: ah, from reading that gpg page, i'm guessing nixos runs `UPDATESTARTUPTTY` any time you login over ssh
<clever>
i just have normal keys in my gpg state, no hardware tokens
<clever>
oh, and gpg-agent has been giving this error for months, any idea what the solution is?
<clever>
agent key RSA SHA256:Xn2yZ3FAQeRqcF7EDiXsPtiuptNLzEAxtOo1DRDzhDM returned incorrect signature type
<clever>
and you dont notice it, so ssh just appears to lock up
<clever>
the problem it causes, is that any time it wants a password, the prompt opens in a terminal in the other room
<clever>
if you turn it off, then it just goes to the first place you logged in, which is typically your X11 session
<clever>
selfsymmetric-mu: so the unix socket maps to wherever you last "logged in"
<clever>
selfsymmetric-mu: its more that the nixos options tie it into systemd/logind, and rebind to any login sessions
<clever>
and then the passphrase prompts open in that ssh session, not in xfce!
<clever>
selfsymmetric-mu: if you turn on the gpg-agent stuff in nixos, it will auto-restart it, any time you connect over ssh
<clever>
selfsymmetric-mu: i'm not really sure how i setup gpg-agent, i cant find it in ~/.bashrc or anywhere else obvious, and i know i didnt turn on programs.gpg-agent, that causes even more trouble
<clever>
selfsymmetric-mu: that means the parent process has since quit
<clever>
selfsymmetric-mu: `ps -eH x` and see what the parent process is
2019-05-31
<clever>
samueldr: hydra-build-products would make it a lot simpler
<clever>
nefix: you can do that on any arch with nix installed
<clever>
nefix: just run `nix-store -r /nix/store/hash-foo` on the storepath in hydras details page
<clever>
fresheyeball: try grepping the nixpkgs src for networkmanager
<clever>
fresheyeball: some things like gnome enable it automatically
<clever>
well, 2 if you only look at the first level, but it casdades up the tree
<clever>
catern: if you have 2 nearly identical derivations, for the same thing, but on 32 and 64bit, they will still differ in many ways: the system attribute, the storepath for all of its inputs (32 or 64bit version, which each have the same difference casdading)
<clever>
habbah: haskell.lib.doJailbreak
<clever>
after that, its all fairly obvious stuff, based on insmod cmds in grub.cfg
<clever>
nh2: then it loads the normal module, which upgrades grub from the bare-bones rescue mode, to a fairly fully functioning grub (adds help, and tab completion)
<clever>
the grub on in the bios-boot-partition will fail to load the bulk of grub, and drop you into a rescue shell with very limited capability
<clever>
so you need a /boot partition on the non-nvme disk, or switch to efi
<clever>
but if your booting in legacy, it cant access the EFI firmware
<clever>
grub technically doesnt support nvme, it relies on the EFI firmware to provide nvme drivers
<clever>
that likely explains all of your problems
<clever>
nh2: also, if you put grub on the non-nvme disk, it cant access a nvme /boot while booting
<clever>
nh2: nvme cant boot via legacy, only efi
<clever>
nh2: what type of ssd is it?
<clever>
nh2: yeah, sounds like you want to go into the bios, and turn off efi booting
<clever>
mac10688: what is the other OS?
<clever>
samueldr: the paths of the inputs appear within the disk image file, so the disk image depends on its inputs
<clever>
nh2: i would try adding the SSD to the devices
<clever>
nh2: what FS is / on? is there any raid involved?
<clever>
samueldr: i once moved a win95 machine to a nearly identical laptop, and it never ran right since
<clever>
nh2: why are you setting the grub device to 4 different drives? and what is special with / and /boot ?
<clever>
i think i'm on soyoustart
<clever>
ive had to use activex *barf* based KVM before, lol
<clever>
no kvm access on my ovh box
<clever>
ah
<clever>
nh2: where are you getting a black screen, how are you looking at the monitor?
<clever>
nh2: have you tried it with just one entry, on the same device as a single /boot partition?
<clever>
nh2: what is boot.loader.grub.device set to?
2019-05-30
<clever>
fasd: i try to avoid autoUpgrade, it tends to waste disk space and make things update when your not expecting, causing random changes/breakage
<clever>
fasd: yes
<clever>
so, callHackageDirect { pkg="foo"; ver="foo"; sha256="foo"; } {};
<clever>
followed by the normal callpackage empty-set
<clever>
it takes a set containing a pkg, ver, and sha256
<clever>
mitch-1002: you probably want callHackageDirect instead
<clever>
and this variant exists, if the version you want isnt in all-cabal-hashes
<clever>
li_matrix: you can get that list at build-time
<clever>
li_matrix: what do you need that list for?
<clever>
li_matrix: the runtime deps are based on the subset of buildtime deps, found in the built result
<clever>
li_matrix: you cant
2019-05-27
<clever>
talqu: and what does /etc/sudoers say about wheel?, do you know for sure the pw is correct?
<clever>
talqu: does `id` say your in wheel?
2019-05-26
<clever>
DigitalKiwi: ive also heard that production=false has higher ratelimits, but ive never ran into issues, since ive just set it right from the start by chance/luck
<clever>
DigitalKiwi: nope, but i notice the IP on your domain is different