<clever>
ndowens08: is the ext4 on a partition or lvm or luks?
<clever>
mythmon: pythonPackages.tox builds on my copy of nixos-unstable
<clever>
ndowens08: what is the ext4 fs ontop of?
<clever>
mythmon: did you try libtoxcore?
<clever>
samae: looks like all i did was networking = { wireless.enable = true; enableB43Firmware = true; }; and manualy poppulated /etc/wpa_supplicant.conf
<clever>
samae: when i used wpa_supplicant, i just manualy copied a pre-existing config to /etc/wpa_supplicant.conf, and it just worked
<clever>
yeah, foo has to be replaced with the name of the package you want to override
<clever>
ndowens08: this defines a function for applying overrides, and it will modify the foo package to use clang instead of gcc
<clever>
config.nix doesnt get those argments, and its completely invalid
<clever>
yeah, that wont work at all
<clever>
ndowens08: ah, can you gist the config.nix also?
<clever>
ndowens08: can you gist all of the involved files?
2017-03-10
<clever>
its currently using buildbot, so i cant do concurrent builds, and there is tons of impure state to deal with
<clever>
LnL: i plan to nix-ify it, as we discussed in ##nix-darwin
<clever>
its doing something weird, that allows the dylib files to be within the foo.app "package"
<clever>
ekleog: that project is still building the non-nix way
<clever>
ndowens08: that lets you switch any derivation to clang
<clever>
ndowens08: you can also do foo = foo.override { stdenv = clangStdenv; };
<clever>
it now compiles all the way to a .dmg, but i havent had a chance to test it yet
<clever>
ndowens08: so ive had to redo that project to build protobuf with clang
<clever>
ndowens08: my best guess to the problem is that they did c++ name mangling differently, and now clang cant find the symbols
<clever>
ndowens08: i spent an hour today trying to get clang to link against some protobuf stuff i think was built by gcc
<clever>
yeah
<clever>
you just reference which one you want in the nix expression
<clever>
with nix, you shouldnt install things like gcc or clang
<clever>
ndowens08: there is a clandStdenv.mkDerivation that uses clang by default
<clever>
ndowens08: id say just test the program as normal, and if it works, it works
<clever>
spluko: the ~/.config/nixpkgs/config.nix path was recently added, and has priority, some people have been tripped up by that, when it just ignores ~/.nixpkgs/config.nix
<clever>
spluko: all other commands use ~/.nixpkgs/config.nix or ~/.config/nixpkgs/config.nix
<clever>
spluko: yeah, only nixos-rebuild obeys the config in configuration.nix
<clever>
spluko: that is much slower, so -A is always recomended
<clever>
spluko: without the -A, nix-env will search the .name of every package (in every channel?)
<clever>
spluko: so just add unstable as a channel to your user, and call it nixpkgs
<clever>
spluko: nix-env -iA nixpkgs.foo will use the channel called nixpkgs
<clever>
and there is state that may not be logged at all
<clever>
jeremejevs: are you able to ssh in from another machine?
<clever>
and then all applications claimed they didnt even have pulseaudio support, lol
<clever>
so the new pulseaudio failed to start
<clever>
jeremejevs: i did have an oddity yesterday when i had to restart xorg, and the old pulseaudio refused to die
<clever>
then both nixos and root share the same overrides
<clever>
some people just do nixpkgs.config = import /root/.nixpkgs/config.nix; in configuration.nix
<clever>
jeremejevs: if the config argument isnt set, it will default to ~/.nixpkgs/config.nix
<clever>
jeremejevs: internaly, nixos uses the config argument to force nixpkgs to obey nixpkgs.config
<clever>
jeremejevs: i dont think this part is in any of the manuals
<clever>
jeremejevs: you want let unstable = import <unstable> { config = config.nixpkgs.config; };
<clever>
jeremejevs: that 2nd nixpkgs you loaded ignores the nixpkgs.config specified in configuration.nix
<clever>
jeremejevs: and how is polybar installed?
<clever>
jeremejevs: what file did you put that packageOverrides into?
<clever>
jeremejevs: did you tell nix to build polybar again with the new config?
<clever>
dmj`: i think xen is being referenced in the nixos manual
<clever>
jsgrant-: the grub.conf file only gets updated when you do a nixos-rebuild (switch|boot)
<clever>
shlevy: though being able to default back to a hard-coded version could be usefull
<clever>
shlevy: in the case of NIX_SSL_CERT_FILE, i think that nixos and the nix profile script should setup sane defaults, pointing to either a system copy or a copy installed via nix-env
<clever>
shlevy: using an absolute path to nix, or after sourcing the profile?
<clever>
ah
<clever>
shlevy: and if you dont source the nix profile script, you wont even get access to the nix tools
<clever>
shlevy: the lines i just linked, install the certs to the nix profile using nix-env
<clever>
then it can load bootcode.bin from usb, or even tftp
<clever>
if you can boot it once with a start.elf and a config.txt, you can burn a fuse in the cpu to enable it
<clever>
nope
<clever>
i can probably do it over usb
<clever>
oh wait, i turned on the new bootstack in my rpi3
<clever>
ive located a 16gig uSD card, now i just need a reader
<clever>
but now that i have the build working, i can more quickly make changes on this end
<clever>
no changes yet
<clever>
i'll need to find a spare SD card and a reader, then i can test it on my end
<clever>
and it will download the image i built
<clever>
smw_: if you add that to /etc/nix/nix.conf, you can just run "nix-store -r /nix/store/n5n74pijd3x9jpcz0qrni9cdl7vgn1is-sd-image-armv7l-linux.img"
<clever>
smw_: i added a nix.conf entry to the previous gist
<clever>
smw_: havent had a chance to test that
<clever>
icetan: hydra will also get the entire build-time closure of every dependency, even if it can get the built copy from the cache
<clever>
smw_: that has to go into either configuration.nix or nix.conf (with changes)
<clever>
smw_: but now that i think of it, i can just enable the qemu-user stuff i wrote, and then i can do that step on my desktop
<clever>
smw_: i was able to compile everything, but i dont have enough free space on the SD to build the .img file
<clever>
and if the OS fails to boot, it looses the fight
<clever>
so the 2 parties are forever fighting over what the default should be
<clever>
and then when the OS finishes booting, it restores the default again
<clever>
generaly, its done by grub changing its own default, right before it boots the OS
<clever>
yeah
<clever>
and it would be much harder to brick a remote machine
<clever>
with that, and a bit of panic+reboot on fail, you could get automatic rollbacks
<clever>
ekleog: but this is also something i have been interested in, if a given generation fails to boot, go to the previous generation
<clever>
until you run boot/switch again
<clever>
not really, the boot flag will change the default and leave it like that
<clever>
i have done that on purpose twice, to convert gentoo boxes to nixos
<clever>
ekleog: i have also done even more insane things, if you run "switch-to-configuration boot" on a machine that isnt nixos, and you trick it into thinking it is nixos, it will overwrite grub!
<clever>
next time i boot, the hack is gone
<clever>
i prefer the 2nd fix for cases where i want to temporarily hack an option in, and i dont want nix to remember it
<clever>
nixos-rebuild will undo that, and restore the symlink
<clever>
ekleog: next level, is to go into /etc/nix, copy the contents of the symlink to a new file, delete the symlink, rename the file, and then fix the syntax error
<clever>
ekleog: this will just directly activate any generation you want, without changing the default
<clever>
ekleog: simplest, is something like "/nix/var/nix/profiles/system-268-link/bin/switch-to-configuration test"
<clever>
ekleog: i can think of 2 options
<clever>
my new hydra farms all binary cache access out to build slaves, so its a bit slower
<clever>
my old hydra just downloads from the binary cache directly, and it shows up as localhost in the build steps
<clever>
nope, but i have helped others that turned the binary cache off entirely and had it
<clever>
ive been running the same version of hydra for over a year, so i'm not sure how the new versions behave yet
<clever>
services.hydra.useSubstitutes is a new option i found in nixos
<clever>
icetan: the only solution is to use a binary cache to get a pre-built copy, or to ensure the /bin/sh referenced in nix.conf doesnt depend on the glibc your building
<clever>
icetan: but /bin/sh is linked against glibc
<clever>
icetan: the problem is that it needs to rebuild something like glibc.doc, so it has to omit the entire glibc from the sandbox
<clever>
2.5gig left on mine, and about half of the storepaths are copied
<clever>
Dezgeg: ouch!
<clever>
copying 1198 missing paths (2859.95 MiB) to ‘builder@192.168.2.126’...
<clever>
Dezgeg: looks like my build compiled everything, but is now running out of space making the disk image
<clever>
/nix/store/gjhsysgkl234r95ly2kn1ypmfp704v4v-stdenv/setup: line 500: export: write error: No space left on device
<clever>
building path(s) ‘/nix/store/n5n74pijd3x9jpcz0qrni9cdl7vgn1is-sd-image-armv7l-linux.img’
<clever>
and what Dezgeg said can help also
<clever>
stepcut: nix.buildMachines in configuration.nix is how you configure that on nixos
<clever>
stepcut: and it will ssh into the pi to do the arm builds, but use the x86 ram for the nix expressions, where you are currently having the problems
<clever>
stepcut: with that config and command, i can initiate an arm build on an x86 machine
<clever>
[clever@amd-nixos:~/apps/nixpkgs]$ nix-build nixos/default.nix -I nixos-config=nixos/modules/installer/cd-dvd/sd-image-armv7l-multiplatform.nix --argstr system "armv7l-linux" -k -A config.system.build.sdImage
<clever>
spacekitteh: do you want to manualy build that new git, or let nix build it, and provide a git command in $PATH?
<clever>
for this command
<clever>
nix-shell -A myGit
<clever>
can you pastebin the output of running nix-shell and the prompt that came up?
<clever>
spacekitteh: and -p wont work at all
<clever>
spacekitteh: "nix-shell" and "nix-shell -A myGit" will give you an env for building that git, so you have to run configurePhase and buildPhase
<clever>
spacekitteh: and what nix command did you run?
<clever>
can you gist the command you used and the nix expressions its referencing?
<clever>
spacekitteh: and how do you want to use that custom git?
<clever>
spacekitteh: what have you tried?
2017-03-07
<clever>
or man pags
<clever>
nor where i found the info, i probably just googled it
<clever>
i used it years ago, but cant remember anything about it right now
<clever>
gchristensen: and due to how tmux was configured, $NIXOS_CONFIG didnt exist in half his shells, so it worked half the time, then just didnt obey the commands
<clever>
gchristensen: and related, $NIXPKGS_CONFIG has higher priority then both files, and i ran into a problem with smw_ a few days ago, where $NIXOS_CONFIG was making it ignore -I nixos-config
<clever>
so now you have to play a guessing game every time you help somebody
<clever>
and if you give people the new path, it will either not work (nixpkgs too old), or it will break their existing config.nix
<clever>
if you keep giving people the old path, it will randomly break like this
<clever>
gchristensen: i had a feeling this would happen 3 days ago when i learned of the change
<clever>
yeah
<clever>
the new ~/.config/nixpkgs/config.nix path takes priority over the old ~/.nixpkgs/config.nix
<clever>
oh
<clever>
samae: what command are you running that is giving an error?
<clever>
samae: does ~/.config/nixpkgs/config.nix exist?