<clever>
so you essentialy have zero firewall while booting
<clever>
and you need to actively isolate them with a config command
<clever>
the WAN and LAN ports are bridged on bootup
<clever>
but that part is also slightly misconfigured by defaylt
<clever>
the A20 processor can change the switch IC config over i2c, so its basicaly a managed switch with the mangement software missing
<clever>
copumpkin: the biggest benefit it has, is 5 ethernet ports and a semi-managed switch IC
<clever>
well, that solves that problem, lol
<clever>
error: Package ‘uboot-Bananapi_defconfig-2017.03’ in ‘/nix/store/mwwncy49y4b691wp527a5qh3lj9hv0cw-nixos-17.09pre105118.65be0b3a4b/nixos/pkgs/misc/uboot/default.nix:53’ is not supported on ‘x86_64-linux’, refusing to evaluate.
<clever>
ive skipped both make and cabal for a number of my nix projects
<clever>
gchristensen: yeah, i'm using nix to mutate 643mb worth of pdf's into ~39gig of xml files, and soon it will be parsed down into the data it contains
<clever>
let me gist an example of this insanity
<clever>
so i had to write nix code that re-runs pdftoxml with 1000 page chunks
<clever>
but that needs insane amounts of ram, i think it wants to store the entire xml as a single c string
<clever>
i ran it thru pdftoxml
<clever>
and the 3 pdf files are treated as 1 unit, so records can cross the pdf boundry
<clever>
each record is ~6 lines, and the records can cross the page boundry
<clever>
and i need to parse, filter, sort, and re-pdf it
<clever>
i have about 260,000 pages of data in 3 pdf files
<clever>
and i'm using it for a very similiar thing today
<clever_>
alunduil: and if you import a module, the top level object is likely a function that wants config and pkgs
<clever_>
alunduil: yeah, import doesnt need a module, import just returns the top level object
<clever_>
alunduil: and those modules must be bare paths within the imports list, you dont import them directly
<clever_>
alunduil: the ... allows you to silently drop arguments you didnt name
<clever_>
alunduil: all modules are passed the arguments config, options, pkgs, and a few misc other things
<clever_>
alunduil: imports is a vastly different beast, and it will recursively load any nixos module loaded under imports, and merge them all together
<clever_>
alunduil: import just loads a given file and returns the top level value of the file, whatever it may be
<clever_>
phpfpm: i mainly use unstable, so im not always following what channels are doing
<clever_>
i think 16.09 might have also done it
<clever_>
phpfpm: nix-shell -p uses runCommand, and runCommand is now an alias to runCommandNoCC
<clever_>
gcc has to actualy be in the -p list (or use stdenv.mkDerviation), otherwise, the libs just wont work
<clever_>
its probably a missing setup-hook then
<clever_>
what does this say? "ls -lh /home/sergio/.nix-profile/bin/gcc"
<clever_>
and now "type gcc" should give a storepath to the cc-wrapper
<clever_>
you need "nix-shell -p gcc sqlite"
<clever_>
Sergio965: what did my last nix-shell command do?
<clever_>
phpfpm: by default, nix-shell now lacks a gcc
<clever_>
and now "type gcc" should give a storepath to the cc-wrapper
<clever_>
you need "nix-shell -p gcc sqlite"
<clever_>
yeah, that gcc isnt aware of how to find nix packages
<clever_>
what does 'type gcc' say?
<clever_>
or make a default.nix like above, and then just nix-shell with no args
<clever_>
nix-shell -p sqlite
<clever_>
need more context around that error
<clever_>
including the commands you ran and the prompts
<clever_>
Sergio965: can you gist all of the output from the shell?
<clever_>
and it will never accidentaly be used by another project
<clever_>
i can write a default.nix, that specifies a specific build of sqlite
<clever_>
this solves a lot of conflicts that can potentialy come up
<clever_>
or that
<clever_>
Sergio965: you can also just call it something else, like foo.nix, and then run nix-(shell|build) foo.nix, and now you can put several in the same dir
<clever_>
Sergio965: yeah
<clever_>
Sergio965: or nix-build to make nix build it
<clever_>
Sergio965: put this into a file called default.nix and then run just nix-shell in that dir to get the shell
<clever>
arianvp2: oh, then you need a static copy of glibc
<clever>
arianvp2: i have seen a python program sanitizing the env before
<clever>
arianvp2: when the script runs gcc, is it keeping the env variables intact?
<clever>
arianvp2: glibc should already be in the buildInputs
<clever>
arianvp2: can you gist the nix expression?
<clever>
arianvp2: are you doing that under a nix-shell?
<clever>
i think you just say his @githubhandle in the msg
<clever>
nh2: seems simpler to just use nix-shell for incremental building, and leave nix-build pure and for release style stuff
<clever>
nh2: so you cant giv it the types of something without also giving it the code, and now it has to rebuild even if the types arent changing
<clever>
nh2: yeah, and haskell lacks a header/source separation
<clever>
tilpner: nix-env -f '<nixpkgs>' -iA ffmpeg-full would force it to use the ffmpeg-full attribute from the <nixpkgs> entry in $NIX_PATH
<clever>
benley: but it will also depend on how much the build-time closure changes between versions
<clever>
benley: yeah, but if you compare the time it takes to rebuild 10,000 source files in chromium, to the time it takes to rebuild a dozen of them
<clever>
i currently lack a way to auto-generate the nix expressions, and no way to parse makefiles or configure scripts
<clever>
ah, it does look very similiar
<clever>
nh2: that would allow incremental builds without having to keep timestamps on things
<clever>
nh2: this is a plan i had on making every .o file its own derivation
<clever>
copumpkin: odd, i think the 2 failing builds are referencing eachothers failures
<clever>
copumpkin: with the same message?, got a link to the build?
<clever>
gchristensen: oops, wrong g name
<clever>
goibhniu: i'm free for the next ~8 hours now
<clever>
copumpkin: within the eval, you can tell it to retry all failed builds
<clever>
mg_: ah, or what gchristensen just said
<clever>
mg_: try loading it with callPackage rather then import
<clever>
gchristensen: yeah, i'll also have some time free tonight till about 10 or 11pm
<clever>
gchristensen: my schedule is clear for the next ~5 hours
<clever>
gchristensen: ah
<clever>
gchristensen: pong
2017-04-04
<clever>
and then run nixos-rebuild switch -I nixpkgs=/home/clever/nixpkgs/
<clever>
railswalker: either checkout the same revision nix-channel is using and manualy apply the change, or just checkout the version in the pr
<clever>
railswalker: there is currently no way to override a nixos module, your only option is to checkout a copy of nixpkgs
<clever>
it would probably be better to make your own thing that will check for the existance of /var/lib/mysql/foo and then create the foo db if it doesnt exist
<clever>
but it will only init the mysql engine once, so you would need to blow away /var/lib/mysql to make it re-init and use the new list
<clever>
it can declaratively join all the modules up
<clever>
mojjo: and there is no type set on the option, so nixos will concat each list from every module
<clever>
mojjo: so if you ever add another thing to that option down the road and nixos-rebuild switch, it wont do what you expec
<clever>
mojjo: the biggest problem i have seen with the design of services.mysql.initialDatabases is that it can only ever run once, when /var/lib/mysql doesnt exist yet
<clever>
depends on how fast you want things and how much power your willing to waste
<clever>
wak-work: probably, but your more likely to have half a dozen x86 machines just idling
<clever>
dash: but xargs has some issues under qemu-user, so you need a full vm or native to get some things like a kernel done
<clever>
wak-work: slower then native, yeah, but i believe its faster then emulating an entire arm, kernel&all
<clever>
dash: and if you use the nix on line 10 then you can tell nix-daemon about that
<clever>
dash: with this, you can run unmodified arm ELF files on an x86 machine
<clever>
dash: you can also use qemu-user for most builds
<clever>
philipp[m]: if your using nix-daemon, then it will probably use the root keys
<clever>
ma9e: does running patchSheBangs on the dir with the script fix it?
<clever>
dash, gchristensen: yeah, not-os just uses an arm build slave to handle things
<clever>
gchristensen: i am now
<clever>
makefu: yep, but the current nixos firewall doesnt have options for extending it at runtime
<clever>
makefu: in theory, you could add nixos firewall support to not-os, and then build an arm image from that, but currently, you would need to reflash the device to change a firewall rule
<clever>
makefu: and i do have an x86 router running nixos
<clever>
makefu: i have booted not-os on a raspberry pi (arm)
<clever>
pie_: as for why i picked that name, its an OS based on nix, but its not nixos
<clever>
ah
<clever>
pie_: id say not-os is more of an example right now, something you would want to fork and further customize, to suit your embeded programming needs
<clever>
heh
<clever>
just got back to the laptop
<clever>
gchristensen: *waves*
2017-04-03
<clever>
shout-user: try installing nox and then run "nox chrome"
<clever>
nix-env isnt recursive by default
<clever>
thats probably making things worse
<clever>
ah, and also idea is under an attr
<clever>
that sounds right
<clever>
can you pastebin the config.nix?
<clever>
then ~/.config/nixpkgs/config.nix, and finally "/.nixpkgs/config.nix
<clever>
";
<clever>
so the config argument has top priority, followed by $NIXPKGS_CONFIG
<clever>
shout-user: this is the logic that decides which file to read
<clever>
fXl: that just references a device section declared elsewhere
<clever>
to get the other versions, the one with the highest number is probably the one that you made earlier and didnt get working
<clever>
you will want the one near /nix/var/nix/profiles/system-*-link/etc/lightdm/lightdm.conf
<clever>
the one in /etc is for the current config that is probably working
<clever>
fXl: it should have an xserver-command= that contains the xorg.conf path
<clever>
fXl: ah, lightdm does things differently from slim, you need to check /etc/lightdm/lightdm.conf
<clever>
fXl: and the contents of the start script referenced on line 16
<clever>
fXl: can you put it in a gist?
<clever>
fXl: oops, display-manager.service
<clever>
shout-user: profiles are just a collection of symlinks, and you normaly arent switching them around, just working on generations within a single profile
<clever>
and this would list every version of display-manager.service over time
<clever>
$ ls -lh /nix/var/nix/profiles/system-*-link/etc/systemd/system/display-manager.service
<clever>
fXl: which will have a different xorg.conf path for each generation
<clever>
SovereignBleak: found the problem, line 139 replaces the entire qt5 with an attrset containing only qt5.base
<clever>
SovereignBleak: line 51, it cant be quoted
<clever>
SovereignBleak can you also gist the configuration.nix?
<clever>
SovereignBleak: can you gist your latest attempt?
<clever>
at least, when using the built-in nixos containers
<clever>
vaibhavsagar: which will also include the config and code for every other container
<clever>
vaibhavsagar: part of the issue there, is that every container has full read access to the host /nix/store
<clever>
so you could make a nix expression that defines config for 100 boxes, hit go, and then it just goes out and adds 100 boxes to your bill
<clever>
for cloud providers with a supported API, nixops can just create the entire machine for you
<clever>
vaibhavsagar: and there is also targetEnv = "none";, where you have to manualy setup a nixos box, with root ssh, then nixops will take care of the rest
<clever>
vaibhavsagar: not sure on what the other platforms in nixops will do
<clever>
vaibhavsagar: for other provides like digitalocean, it will ssh into a base ubuntu image, and then reinstall nixos over the rootfs
<clever>
vaibhavsagar: for nixops on aws, it will spin up a VM running a clone of a base image the foundation uploaded to aws
<clever>
yep :)
<clever>
yeah, fetchgitLocal is a bit weird
<clever>
calvertvl: yeah
<clever>
calvertvl: you have no network access in postUnpack
<clever>
calvertvl: depends on how many sub-modules you have