<clever>
domenkozar: oh, and do you have virtualbox enabled in nixos?
<clever>
pie_: but thats sort of the original problem nix was meant to solve, and relying on things being in a common directory goes against nix
<clever>
pie_: i think the first step would be to rename the qt-5.9 directory in lib to qt-5.9.1, so that the versions that it complains about, cant conflict
<clever>
pie_: it works best if you only install QT programs via systemPackages, then they always share the same nixpkgs version
<clever>
domenkozar: and without pulseaudio managing the difference between the speaker and headphone mutes, you may also want to manualy manage that in alsamixer
<clever>
pie_: the QT stuff in nix is a bit of a mess, and the one thing ive found that breaks all the rules
<clever>
pie_: nix-shell works purely thru env variables, and wont set it up right
<clever>
pie_: a lot of QT things assume that the propagated-user-env-packages land in $HOME/.nix-profile/ and configure their search paths to match that
<clever>
domenkozar: yep
<clever>
pie_: this is also the second time ive seen this bug crash plasma
<clever>
domenkozar: next thing i was thinking of testing, disable pulseaudio, and then use an old alsa test application to see if the alsa drivers are even working
<clever>
which is the oposite of what nix-env normally does
<clever>
so when things ask for both 5.9.1 and 5.9.2, it just gives one and doesnt tell you
<clever>
propagated-user-env-packages will also silently ignore collisions
<clever>
keep searching the --tree for any other things depending on QT
<clever>
pie_: something else you have is silently adding it
<clever>
pie_: plasma runs as your user, and obeys the search path that points into ~/.nix-profile
<clever>
but anything you got from unstable is going to be breaking the os
<clever>
ah
<clever>
pie_: and how did you tell nix-env to upgrade?
<clever>
how did you upgrade things?
<clever>
are there multiple channels on either user?
<clever>
pie_: does the user have its own nix-channel?
<clever>
pie_: so you need to either get all of nix-env on 5.9.1, or just remove all qt from nix-env
<clever>
pie_: aha, so i was backwards in assuming 5.9.2 was the right one
<clever>
pie_: nix-store -qR $(which plasmashell) i think
<clever>
pie_: now double-check what version of QT plasma was linked against
<clever>
pie_: but the storepath behind those names does
<clever>
pie_: and does the 5.9 contain 5.9.1 or 5.9.2?
<clever>
pie_: do you have a directory matching ~/.nix-profile/lib/qt*
<clever>
pie_: but the runtime assertion is more strict then that namespacing
<clever>
pie_: double-check in ~/.nix-profile/lib/ and you should see a qt directory, that is partially namespaced on version
<clever>
pie_: i dont think 5 can ever load 4 by mistake
<clever>
i use imports = [ ./nixcfg/agh.nix ]; and keep the repo in /etc/nixos/nixcfg
<clever>
or better, uninstall them, and add them to systemPackages so they remain in sync
<clever>
pie_: it should result in you having only QT 5.9.2 in the tree
<clever>
pie_: check nix-store --query --tree ~/.nix-profile/ for anything refering to QT 5.9.1, and upgrade those
<clever>
pie_: firefox doesnt use QT, so it shouldnt matter
<clever>
pie_: if you do upgrade your nix-env stuff, it will cause the same problem 6 months down the road, when you update nixos again
<clever>
pie_: entire make sure every single QT program in nix-env is on the same QT version as nixos, or remove all QT programs from nix-env
<clever>
coconnor: yeah, ~/.nix-profile has priority over systemPackages
<clever>
which just break everything :P
<clever>
and that has conflicting versions of the libraries
<clever>
the system plasma obeys the env vars that say to look in ~/.nix-profile/
<clever>
and/or remove them and let systemPackages keep them in sync
<clever>
pie_: the only solution, is to upgrade every QT package in nix-env to the same nixpkgs
<clever>
pie_: the problem is that you mixed QT versions inside nix-env
<clever>
pie_: reboot wont fix that, i have an issue open for it
<clever>
pie_: aha
<clever>
mbrock: but if things are just interupted, it will restart on another slave
<clever>
mbrock: and things getting stuck in limbo is either a case of the retry timeout not being visible, or require features not being met, and the GUI cant tell you what its waiting on
<clever>
mbrock: i have noticed poor scheduling before, where it will do 2 steps of a build on different slaves, and have to transfer the closure twice, once to each slave
<clever>
mbrock: only issue, would be the interuption of something that was in-progress at reboot
<clever>
mbrock: so complete loss of the store on a slave has little impact
<clever>
mbrock: hydra makes no attempts to track what a slave has previously downloaded and to optimize things around that
<clever>
mbrock: you can set a weight for each jobset, and there is a queue within hydra and you can bump some things up
<clever>
mbrock: it doesnt involve nix-build at all, but rather, directly calls ssh and talks to the remote nix-daemon
<clever>
each machine has its own root that it starts at, and all of them include core.nix at some point
<clever>
then i just git clone nixcfg, and put a tree of modules in there
<clever>
coconnor: similar here, my configuration.nix only contains what is required to make the machine boot, and imports = [ ./nixcfg/amd.nix ];
<clever>
ottidmes: then if an OS starts a partition on block 3, and the FS deals with groups of 4 blocks, it will always overlap between 2 hardware blocks, which destroys performance
<clever>
ottidmes: when hardware started to go beyond 512 byte blocks, it broke many OS's, so the hardware lies and claims its still 512 bytes
<clever>
ottidmes: there is also the fun of finding the block size of the hard-drives
<clever>
and can be nested wherever a value is expected
<clever>
pie_: both of the above, are equivelant to just a raw value or expression
<clever>
pie_: with value; value
<clever>
pie_: let foo = bar in value
<clever>
yeah
<clever>
pie_: with pkgs; [ lyx texmaker texlive.combined.scheme-full ]
<clever>
ottidmes: aha, so the system-product-name isnt always accurate
<clever>
hakujin: that will tell you how much is in the nix language, and how much is just building
<clever>
hakujin: as a test, you can compare how long it takes to nix-instantiate an expression, vs how long it takes to `nix-store -r /nix/store/foo.drv` the derivation it produced
<clever>
hakujin: there is also some overhead in nix setting up sandboxes
<clever>
ottidmes: sounds like your just on baremetal, so it would be up to either the BMC/IPMI or a physical serial cable
<clever>
hakujin: nix has to build ghc1 with ghc2 which was built with ghc3, and it has to eval the closure of every ghc thru nixpkgs
<clever>
hakujin: there is also some more layers of overhead in how ghc gets bootstrapped
<clever>
pie_: if you can get root, systemctl restart display-manager
<clever>
pie_: it has been disabled on some systems
<clever>
hakujin: callCabal2nix involves import from derivation, so it has to run cabal2nix every time the source changes, to generate the nix expressions
<clever>
pie_: ctrl+alt+backspace is a hotkey in xorg, that just kills xorg
<clever>
ottidmes: what does `dmidecode -s system-product-name` say?
<clever>
and then the presense of the mysql dataDir will prevent it from happening again in the future
<clever>
gilligan_: then after the daemon has started, it checks the the existance of mysql_init, does some one-time stuff, and deletes mysql_init
<clever>
gilligan_: if the mysql dataDir doesnt exist before starting the daemon, it creates /tmp/mysql_init
<clever>
nextos: oh, because its called hardeningDisable, lol
<clever>
github search is being derpy and finding all but the most important reference to it
<clever>
nextos: disableHardening has to be set to a special string
<clever>
nextos: one min
<clever>
jack[m]: the biggest benefit of that method, is that you can audit your expressions, by confirming they build with NIX_PATH unset, then you know that you dont care what the value is in the future
<clever>
and also via running `env` around postInstall
<clever>
bgamari: if you eval it in nix-repl, can you confirm the presense of that attribute?
<clever>
bgamari: ah, so the setupHook attribute was defined on the derivation, and its trying to create $out/nix-support/setup-hook, for future sourcing
<clever>
bgamari: can you gist the derivation that is having this failure?
<clever>
bgamari: i think only for setup hooks will the stdenv source things
<clever>
bgamari: so you need to ensure you dont have those if $out is a file
<clever>
bgamari: propagated build inputs work via $out/nix-support/something
<clever>
./result/bin/reaper5: symbol lookup error: /nix/store/0xkvp0ngxxr46psic51fp84aqynk362c-reaper/bin/libSwell.so: undefined symbol: gdk_init_check
<clever>
dontStrip fixes the above error
<clever>
./result/bin/reaper5: ./result/bin/reaper5: no version information available (required by ./result/bin/reaper5)
<clever>
erlandsona: i can just throw it into a gist when i'm done
<clever>
/nix/store/j4vcckdcbim2qqyr0kjw9dcvlcm9as12-reaper-derivation/reaper5: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
<clever>
but that doesnt include the contents of the reaper bash script
<clever>
erlandsona: you dont need to use a builder.sh, pkgs.runCommand would do the same thing
<clever>
erlandsona: can you gist that bash script?
<clever>
erlandsona: if you run `file` on reapter5, what does it say?
2018-01-27
<clever>
nice
<clever>
x86_64-unknown-linux-gnu
<clever>
boomshroom: gcc has clever@c2d ~ $ gcc -dumpmachine
<clever>
something is broken
<clever>
cinimod: there is no libmariadb.2.dylib in that directory
<clever>
[clever@amd-nixos:~]$ ls -lh /nix/store/wbbxlsnyp1vpwj7rp9d0l0m4d4z425gl-mariadb-connector-c-2.3.4/lib/
<clever>
cinimod: i'm guessing that rgdal is just failing to build
<clever>
cinimod: can you add the default.nix file to that?
<clever>
cinimod: can you gist that as well?
<clever>
cinimod: is there a default.nix or shell.nix file in that directory?
<clever>
cinimod: you didnt tell nix-shell what to load, so its probably trying to build every single package in the universe
<clever>
and thats just what is in the house
<clever>
3 servers, 1 desktop, 1 laptop, plus a laptop i no longer use but it works and has nixos
<clever>
srhb: it takes me a while to count them too :P
<clever>
GNU ld (GNU Binutils) 2.23.51.20121030 has -z in the man page
<clever>
CapsAdmin: -z accepts another argument, that tells ld to do something