<clever>
Alling: do you have a link to kmeans-par?
<clever>
Alling: that likely has to do with the version of metric in the stack.yaml
<clever>
AlexRice[m]: yep
<clever>
Alling: if you want something installed by nix, then it has to be built by nix, which is where tools like nix-tools and stack2nix come into play
<clever>
Alling: the products made by stack are all impure builds, and nix wont know they exist
<clever>
yep
<clever>
nomeata: what about `nix-store --verify --check-contents` ?
<clever>
yep
<clever>
nomeata: what does ls -l ~/.nix-profile report?
<clever>
`nix-env -q` to list the installed things
<clever>
nomeata: find out which thing is adding it, and uninstall it with nix-env -e
<clever>
nomeata: there is a bug in nix-env, if you have dead symlinks in ~/.nix-profile, it cant update the profile
<clever>
nomeata: ahh
<clever>
both should be building the same thing and just working the same way
<clever>
can you pastebin the entire output of nix-build?
<clever>
does nix-build give the same error if ran several times?
<clever>
and the cmd that gave it?
<clever>
nomeata: what was the original error? and the cmd that gave it?
<clever>
and no nix tools will use an invalid path
<clever>
nomeata: nix will also delete the path automatically when trying to build it again
<clever>
nomeata: `nix-collect-garbage --max-freed 1m` may start with that path, you can repeat that until the path in question is gone
<clever>
nomeata: `is not valid` means its not in `--dump-db`, so a normal nix-collect-garbage will automatically delete that path
<clever>
nix would have trouble with that though, due to /nix
<clever>
gchristensen: user data gets mounted to /data, the os to /system, and then it just runs like that
<clever>
gchristensen: of note, android boots with an initrd, but never does pivot_root
<clever>
lol
<clever>
gchristensen: why not?
<clever>
the livecd stuff already does that, purely with fileSystems.
<clever>
would be simpler from the initrd
<clever>
and then overlay things, maybe
<clever>
you would need to mount tmpfs's to directories that already exist
<clever>
ajs124: yeah, that should work
<clever>
Shouou: you want -p, which doesnt accept the . (a path)
<clever>
Shouou: -A is for building the package, not using the package
2019-03-24
<clever>
thats the nixos one
<clever>
$ nix-build '<nixpkgs/nixos/release.nix>' -A manualHTML
<clever>
ah, that the nixpkgs manual, not the nixos manual
<clever>
i believe
<clever>
nix-build '<nixpkgs/doc>'
<clever>
haslersn[m]: its the default.nix in the doc dir of nixpkgs
<clever>
infinisil: i use ratpoison when i need something keyboard drive, but i dont think it has much tiling in it
2019-03-23
<clever>
and yeah, you can also use raw revs like that
<clever>
which uses the nixos-17.09 branch from the nixpkgs-channels repo
<clever>
noonien: the new style is things like channel:nixos-unstable in NIX_PATH, and that downloads the current nixos-unstable every time the cache expires (~30mins)
<clever>
i prefer using nix-channel, because i dont want it updating on its own, and i prefer to have nixpkgs cached
<clever>
dminuoso: ah, then you probably want to just insert ${pkgs.foo}/lib somewhere in your buildPhase
<clever>
dminuoso: so you dont need to know where ${pkgs.foo}/lib is
<clever>
dminuoso: if you add pkgs.foo to buildInputs, then it will be injected into the search path for gcc, and `gcc -lfoo` will find it automatically
<clever>
dminuoso: by putting them into the buildInputs list
<clever>
dminuoso: 90% of the time, you dont want to set the builder attr, you want to use a string like buildPhase = ''...'';
<clever>
gchristensen: some people still need it, to fetch submodules
<clever>
reallymemorable: in whatever is accessing gitlab
<clever>
reallymemorable: are you using fetchGitPrivate?
<clever>
reallymemorable: then thats why it doesnt work, you must run `ssh-add` to add an identity to the agent
<clever>
reallymemorable: does `ssh-add -l` list an ssh key?
<clever>
reallymemorable: can you paste the exact error, and the cmd you ran?
<clever>
reallymemorable: socat must be running, ssh-config must exist, then you can build
<clever>
reallymemorable: yeah
<clever>
sudo rm /tmp/hax
<clever>
root
<clever>
yep
<clever>
you need to delete the old /tmp/hax when restarting it
<clever>
yep
<clever>
the socat in there must be running for the private fetch to work
<clever>
but the GC will clear the outputs, and require you to fetch things again, which does need the socket
<clever>
reallymemorable: the hax socket requires an socat to be running, a GC is mostly unrelated
<clever>
reallymemorable: its safe to delete once you close the socat that had created it
<clever>
reallymemorable: thats not a file, thats a unix socket
<clever>
reallymemorable: ls -l /tmp/max
2019-03-20
<clever>
and so root doesnt steal ownership of your editor state files
<clever>
sphalerite: so your editor uses the right $HOME for its state
<clever>
sphalerite: it copies the file to /tmp, runs $EDITOR on the copy, then copies it back when you exit
<clever>
sphalerite: the whole point of sudoedit, is that it runs $EDITOR without root
<clever>
Orbstheorem: not sure where those land
<clever>
Orbstheorem: ~/.nix-profile/share/ for nix-env
<clever>
Orbstheorem: create $out/share/passff-host/ and then get put into systemPackages
<clever>
noonien: assuming you have root somehow
<clever>
noonien: nixos-rebuild switch, with a change in configuration.nix
<clever>
spacekookie: nix-env solves that by impurely jamming it into ~/.nix-profile/lib/ and then breaking any qt with an incompatible version
<clever>
spacekookie: QT_PLUGIN_PATH must be set, to a path like ${super.qt5.qtbase.bin}/lib/qt-${super.qt5.qtbase.version}/plugins
<clever>
tmpfs on /run/wrappers type tmpfs (rw,nodev,relatime)
<clever>
and recreated on bootup
<clever>
so its lost at shutdown
<clever>
the sudo wrapper, is on a tmpfs
<clever>
noonien: if you reboot, it will fix sudo
<clever>
noonien: nix doesnt allow setuid binaries in /nix/store/, so nixos must create a wrapper on bootup
<clever>
elvishjerricco: only root can view the env vars of another user
<clever>
yep
<clever>
noonien: any path present in an env var will be protected
<clever>
and over time, GC will remove blocks, till its gone
<clever>
so all reads, will bounce off the old mirror-1 vdev, then lookup within a zvol on mirror-0
<clever>
and then it flags that vdev is read/delete only
<clever>
one way to think of that unfinished feature, is that it copies a given device (like mirror-1) to a zvol (that is sepcially flagged to not allocate on mirror-1)
<clever>
there is an unfinished feature, that turns 'removed' vdevs into indirect things
<clever>
sphalerite: yeah, currently, zfs has no (released) way to remove a vdev, so that pool is forever 2 vdevs (the mirrors can be downgraded to non-mirror status though)
<clever>
Myrl-saki: there was an entry on the old wiki, about how to install those utils with nix-env under a rescue env
<clever>
sphalerit: can you pastebin `zpool status -v` ?
<clever>
hyper_ch2: also, zfs attach wont update the boot sectors, so the drive likely wont be bootable on its own
<clever>
hyper_ch2: thats one of the first rules of backup, ive heard a few horror stories where people discover the backup isnt actually readable
<clever>
hyper_ch2: have you confirmed you can import that usb drive on another machine?
<clever>
but today, i would use iscsi to do that
<clever>
hyper_ch2: back when i used lvm on pata, i also used nbd to get the drives from another box back into the array
<clever>
i think it doesnt trigger when detach makes things expandable
<clever>
hyper_ch2: ive found auto-expand never works, but there is a flag for import that solves it
<clever>
then drop one of the 2tb's, and repeat
<clever>
start by using attach to make it into a 3 way mirror, with 2tb, 2tb, 4tb (half wasted)
<clever>
yeah, and the above sounds sane
<clever>
at another point, it was a 3-way mirror with 2 ssd's and an nvme
<clever>
at one point, my system was a mirror between a magnetic and ssd
<clever>
hyper_ch2: ive done exactly that when messing with the drives in my main desktop
<clever>
mkovacs: but if nix-daemon is at play, they run as seperate users
<clever>
mkovacs: if you are using single-user nix, then all builds happen as the current user, and ssh-agent doesnt get upset
<clever>
mkovacs: you must use socat to proxy the unix socket, so ssh-agent cant detect that uid git clone is running as
<clever>
hyper_ch2: none of the tabs are on the tld or any other subdomain
<clever>
hyper_ch2: that was enough to stop them from loading
<clever>
mkovacs: one min
<clever>
Myrl-saki: you dont want to know how many i had open in firefox back then :P
<clever>
Myrl-saki: ^^^
<clever>
Havvy: even with the lazy loading, it crashed the machine :P
<clever>
Havvy: also, i have had enough tabs in firefox, that just loading the dummy about:blank in each tab, would cripple the machine
<clever>
(back)
<clever>
Havvy: too lazy to switch :P
<clever>
hyper_ch2: due to the sheer number of tabs i have open, just restarting chrome can crash the machine, so i sometimes have to blacklist the domain for half of them lol
<clever>
hyper_ch_: strange, its not in any package!
<clever>
bash-completion.out 847 r /nix/store/4va32apahbksvnr1bq3jyy4dqr06ghqk-bash-completion-2.5/share/bash-completion/completions/mii-tool
<clever>
nettools.out 1,466 x /nix/store/5zi0g3ngaf189vp4aabpvpk3pypdq5sw-net-tools-1.60_p20120127084908/share/man/man8/mii-tool.8.gz
<clever>
,locate bin mii-tool
<clever>
hyper_ch_: `link partner` is the key thing thats missing from your pastebin
<clever>
hyper_ch_: `mii-tool -v eth0` what does it say?
<clever>
hyper_ch_: one min
<clever>
palo: look up the nix file the service is defined in, and see what the systemd service is called
<clever>
slack1256: pretty sure journalctl never wrote to that
<clever>
slack1256: anybody with physical access, or write to /proc/sysrq-trigger
<clever>
`_: nixos avoids changing the uid of users, because the files they own wont be updated, youll need to manually fix the uid in /etc/passwd, /var/lib/nixos/uid-map, and also chown every file the user had, to the new uid