<clever>
lejonet: security.wrappers is how the wrappers get made
<clever>
preferably in a pastebin
<clever>
ruhatch: yeah
<clever>
the option i named puts it there
<clever>
you can also remove it from systemPackages
<clever>
foldingcookie: yes, without that, you wont have a /etc/zshrc and stuff
<clever>
ruhatch: what do you see when you ls /etc/systemd/system/ on the machine nixops was controlling?
<clever>
foldingcookie: did you programs.zsh.enable = true; ?
<clever>
ottidmes: nixos will autodetect that
<clever>
ruhatch: nope
<clever>
ruhatch: it might be /root/.ssh/id_charon_vpn
<clever>
you should find the path to the private in there
<clever>
ruhatch: check the .service file for the vpn in /etc/systemd/system/
<clever>
ruhatch: you still need your own keys to get a shell, the vpn key is only for the vpn itself
<clever>
ruhatch: what happens if you run ssh against that ip?
<clever>
ruhatch: you should be able to connect to the ip of the other machine
<clever>
[Leary]: it depends on what the type was set to when the option was defined
<clever>
there should be an ip on both ends, which you can just use
<clever>
ruhatch: if you run `ip addr`, do you see an extra interface?
<clever>
ruhatch: i think it generated a systemd service that setup an ssh link between the 2 machines
<clever>
ruhatch: nixops configured that
<clever>
[Leary]: for most, it will inteligently merge things, for some, it will give a clear failure when they conflict, and for a rare few, it will just pick one over another
<clever>
[Leary]: depends on the types of each attribute and the merge functions for those types
<clever>
ottidmes: and nixops deploy will revert all changes nixos-rebuild had done
<clever>
ottidmes: if you run nixos-rebuild, then it will revert all changes nixops was doing
<clever>
Acou_Bass: that would explain why none of my nixos machines have a ~/.pulse/
<clever>
Acou_Bass: what about the last-mod timestamp on the symlink?, it may be from ages ago and /tmp has been cleaned up
<clever>
Acou_Bass: what exactly does it point to?
<clever>
that part msg is perfect, lol
<clever>
ShalokShalom2: generally, development time things shouldnt be installed globally when using nix
<clever>
Kim_: you can use pkgsi686Linux to access the 32bit versions of packages when doing patchelf
<clever>
Kim_: what needs both 32 and 64?
<clever>
why are you trying to globally install something with npm?
<clever>
you just need to get into the right mindset, then it all makes sense
<clever>
they defeat the whole point of nix
<clever>
and nix is very against global things like that
<clever>
ShalokShalom2: a normal user wont have write access to that path
<clever>
ottidmes: and that will only work if the bin of that is already in $PATH
<clever>
ShalokShalom2: yeah
<clever>
ShalokShalom2: where else would you have it install to?
<clever>
ottidmes: i dont think npm global installs can ever work, because they assume the dir npm was installed to is mutable
<clever>
benny: yeah, just assign it to another attribute, and that will become an env var at build-time
<clever>
benny: run patchShebangs on that directory
<clever>
benny: buildInputs only ever land in $PATH
<clever>
detran: you could potentially bisect nixpkgs now, but it might take an hour to narrow down the cause
<clever>
detran: you should be able to just change the nix-channel after booting the iso, then install
<clever>
detran: i'm guessing the kernel doesnt like your hardware, try an older iso
<clever>
detran: that should work
<clever>
detran: and rdisk2 is the full drive?
<clever>
detran: how are you dd'ing the iso to the usb?, what is the exact command?
<clever>
judson: librarySystemDepends
<clever>
judson: its not a haskell dependency
<clever>
nix 2 auto-detects it, so it is now unset
<clever>
disasm: originally, nixos was setting that system wide, because nix 1.11 cant auto-detect it
<clever>
disasm: that could handle it
<clever>
nix-repl has better tab completion, no history, and it uses nix 1.11
<clever>
nix repl has somewhat worse tab completion, the repl history persists between restarts, and it uses nix2
<clever>
apostolis: there is also `nix repl` without the -, but its ui is slightly different
<clever>
apostolis: its an issue caused by nix2
<clever>
apostolis: export NIX_REMOTE=daemon
<clever>
apostolis: what error?
<clever>
judson: gnome3.gtk
<clever>
MichaelP: cli
<clever>
yeah, if the warning keeps happening, thats generally due to installing nix 2 with nix-env, while running nix 1 as the daemon
<clever>
zybell_: so nix has to run with the old config, to make the new config
<clever>
zybell_: nope, the issue is that the config is built with nix
<clever>
just a bit slow
<clever>
that sounds entirely normal
<clever>
which will happen any time your doing the upgrade
<clever>
zybell_: that warning happens if you run nix2 with a nix1.11 /etc/nix/nix.conf file
<clever>
?
<clever>
it should warn you if it took over a minute
<clever>
it should be
<clever>
stumble: thats nix checking the binary caches
<clever>
stumble: name?
<clever>
strange
<clever>
stumble: if you check top while its hung, is there any high cpu usage?
<clever>
stumble: does it hang again if you try the same command again?
<clever>
the difference, is that double-single will strip common indents
<clever>
mightybyte: double as in ''foo bar''
<clever>
mightybyte: yes
<clever>
stumble: gist.github.com
2018-04-05
<clever>
xxxnasheedxxx: it needs both minetest and minetest_game
<clever>
xxxnasheedxxx: oh, minetest is doing weird things with its src
<clever>
xxxnasheedxxx: put it in place of fetchurl
<clever>
abcrawf: there is a clangStdenv.mkDerivation that may help somethings
<clever>
ottidmes: nixos will also save those levels at clean shutdown, and restore them on bootup, so its only ever an isue for fresh boots and maybe newly hot-plugged devices
<clever>
ottidmes: alsamixer, f6
<clever>
nioncode: virtualbox is a bit more complex to pin, because it involves kernel components
<clever>
guillaum1: and if i then run diffoscope on it, i can see that i had refactored the import statements in the haskell code to silence all compiler warnings, but forgot to nixos-rebuild switch
<clever>
guillaum1: in this example, my configuration.nix is intact, but there is a single difference within a util i use in builtkite
<clever>
guillaum1: that will tell you how the 2 differ, and then you can manually edit configuration.nix to bring the differences down to zero
<clever>
guillaum1: one trick you can use, is to do `nixos-rebuild dry-run` and then use nix-diff to compare it against the .drv from the original system
<clever>
guillaum1: not by default, you need some special config to do that
<clever>
mpcsh: the problem could be the reverse of what your thinking, some other font is currently missing, and its using FreeMono as a fallback
<clever>
sphalerite: if a directory with files exists in /etc, but environment.etc says it should be a symlink to a directory in the store, it currently fails to update the entire entry
<clever>
sphalerite: RENAME_EXCHANGE sounds like something setup-etc.pl could use
<clever>
but if you set builder, that is disabled
<clever>
fresheyeball: the default builder copies the src to . for you
<clever>
fresheyeball: can you gist the nix expression you currently have?
<clever>
fresheyeball: if you are using builder.sh, all of the helper scripts that copy the src are non-functional
<clever>
lejonet: you may also want to look at the nixpkgs expressions for ubootBananaPi to see what makes it special, and how it may need to be modified to suit your board
<clever>
lejonet: you also need all the files that qemu-user.nix refers to within the overlays dir
<clever>
lejonet: try cloning all of nixos-configs, and add the absolute path of qemu.nix to imports
<clever>
dhess: it took several hours just to run the perl configure script, so, really slow :P
<clever>
lejonet: the overlay is fully automatic in the module i made, as long as all of the files are in the right place
<clever>
lejonet: and it will also upgrade you to 2.0 if you didnt already have it
<clever>
lejonet: this module also patches nix 2.0 for you, and configures it
<clever>
lejonet: yep
<clever>
lejonet: then nix-daemon will believe you can run the native arm gcc, and just work
<clever>
lejonet: add this file to your imports in configuration.nix, and then set qemu-user.arm = true; and it will magically configure everything
<clever>
patrl: the only valid way to update nix on nixos is to set nix.package in configuration.nix
<clever>
and then just passwd your way to owning the machine
<clever>
Aleksejs: you can always use init=/nix/var/nix/profiles/system/sw/bin/sh in grub to force it into single-user mode
<clever>
Aleksejs: it works by just upgrading a single-user nix install into a full nixos install, and renaming everything the old distro left in /
<clever>
Aleksejs: i believe jeaye made it based on what i had done when messing around with an old netbook
<clever>
infinisil: lol
<clever>
infinisil: nice
<clever>
yeah, its only an issue if you shadow a binary with a path earlier in your pre-existing $PATH
<clever>
it will also clear it any time PATH is modifies, so i just `export PATH=$PATH`
<clever>
which shows that it didnt look, it remembered
<clever>
on gentoo, it can return this
<clever>
bash is hashed (/bin/bash)
<clever>
clever@c2d ~ $ type bash
<clever>
Lisanna: also, there is "type ls"
<clever>
Lisanna: nixos disables that bash feature automatically
2018-04-03
<clever>
i keep seeing things like 1200 b/sec sorted above 50 kb/sec!
<clever>
the units in iotop are really throwing me off
<clever>
are the heavy loads actually a child of nixos-rebuild?
<clever>
joepie91: what about the process tree?
<clever>
joepie91: nixos-rebuild and any build started by root will generally bypass nix-daemon, so you can just ionice the command directly
<clever>
Dezgeg: its clearly never been io-bound on my end
<clever>
but it drops really slowly, it doesnt even use 2% of my disk bandwidth capacity
<clever>
sphalerite: you can `watch cat /proc/swaps` to see the used swap slowly drop
<clever>
ive profiled it before and the issue is somewhere in the memory management area
<clever>
obadz: it happens even with plaintext swap
<clever>
but to load-balance between them you have to have the same priority, and then the writes are scattered, so perf is murdered on spinning-rust
<clever>
so you can double the swapoff speed if you just use 2 swap partitions on the same device
<clever>
it uses an abnormally large amount of cpu, and it cant multi-thread
<clever>
sphalerite: ive noticed that as well, its a major pain at times
<clever>
Turion: after the rebuild finishes, your nix config will be updated
<clever>
Turion: because your using nix 1.11 config with nix 2.0
<clever>
Turion: its in more of a beta phase right now
<clever>
tilpner: the sshd work-around is gone, and it your install was from 2015, the ssh hostkeys will just change on their own and set off mitm alerts