<clever>
nekroze: i'm mainly using it to boot a configuration.nix under qemu and run some basic tests against it
<clever>
smw_: is console= set in the kernel arguments?
<clever>
and the 17.03 channel currently fails to even unpack my source, need to look into why
<clever>
nekroze: so now hydra is testing against both channels
<clever>
nekroze: i recently setup hydra to test my stuff against 16.09, and when 17.03 came out, i just cloned the entire jobset
<clever>
gchristensen: ah, that email explains why somebody lost sudo a week ago
2017-03-06
<clever>
ali1234: nix builds always lack root, but it can fire up a qemu vm for cases when it does need to edit a filesystem image
<clever>
ali1234: and if root configures qemu-user-arm ahead of time, it can just run the arm compiler in nix builds
<clever>
ali1234: with how nix works, it doesnt need fakeroot or fakechroot
<clever>
dtzWill: the code expects the builder to be -9'd and not have any more output
<clever>
dtzWill: its happening after nix-build has been ctrl+c'd
<clever>
gchristensen: yeah
<clever>
and nix normaly keeps things in a sandbox, so the rm -rf will clean it up anyways
<clever>
it would need to term, sleep 30, then kill
<clever>
anelson_: and the rest is just to keep any naughty programs from ignoring sigterm, and sticking around eating resources
<clever>
anelson_: part of it, is that one of these killUser passes, is meant to sterilize the nixbld1 user, before a build starts, so you can prevent impurities from the last build under that user
<clever>
nice
<clever>
anelson_: for it to impact nix-daemon, it will have to be an override within configuration.nix
<clever>
anelson_: and here is how you can apply a patch to nix easily
<clever>
but i can see the use in having it auto-upload
<clever>
i would have just built them as an img file localy, along with a bash script that initiates the upload
<clever>
anelson_: most of nix expects the builds to be contained and not have network access, so an rm -rf $NIX_BUILD_TOP would be enough to clean it up
<clever>
anelson_: in the daemon case, you could connect to the daemon over localhost + tcp, and if the tcp link is lost at any point, kill all vm's!
<clever>
anelson_: only thing i can think of, is to either route it thru a daemon that will cleanup automaticaly, or to configure the machines to shutdown after 1 hour
<clever>
anelson_: what kind of resources is it allocating, that you want to clean up?
<clever>
copumpkin: and i was upgrading it to nixos without any removable media
<clever>
copumpkin: in my case, i started with half a gentoo install, that included a 2015 build of nix, that couldnt parse nixpkgs
<clever>
i manualy changed things with sqlite3
<clever>
copumpkin: ah, that github issue looks like a better way to fix it
<clever>
Baughn: i have manualy downgraded the db before, and can help with that
<clever>
niksnut: ah, and it sounds like it accepts things in the same format as NIX_REMOTE and the copy command
<clever>
niksnut: what is the new API to configure substituters?
<clever>
copumpkin: from what i saw in the source, yeah
<clever>
niksnut: ah, and that syntax would involve "local?root=/" i'm guessing?
<clever>
niksnut: and if your doing a build under /mnt/nix/store, does it know enough to copy from /nix/store?
<clever>
niksnut: ah, looks simple enough, i'll have to try that next time i get a chance
<clever>
niksnut: ah nice, and what about realizing a derivation within that new root?
<clever>
niksnut: is there a similar command to copy from /nix/store to /mnt/nix/store ?
<clever>
ive seen evidence in the code that it can do that, but not how to trigger it
<clever>
shlevy: oh, do you know how to make the new nix write to a store store at /mnt/nix/store/ ?
<clever>
Dezgeg: now that i know about self, the fix is easy, but i'll need time to compile the kernel
<clever>
i'll fix the expression and test again
<clever>
yeah
<clever>
Dezgeg: the repl did unstable, but the configuration.nix was 16.09
<clever>
Dezgeg: the api for this function differs between unstable and 16.09
<clever>
11290 linuxPackagesFor = kernel: lib.makeExtensible (self: with self; {
<clever>
11329 linuxPackagesFor = kernel: self: let callPackage = newScope self; in rec {
<clever>
Dezgeg: i think i see the problem
<clever>
error: value is a function while a set was expected, at /home/clever/nixpkgs/nixos/modules/tasks/cpu-freq.nix:6:14
<clever>
Dezgeg: hmmm, the above expression works when put into nix-repl, but not in a configuration.nix
<clever>
Dezgeg: applied to the host or guest kernel, looks like guest at a glance
<clever>
Dezgeg: these zfs + 9p bugs are getting pretty anoying
<clever>
server# [ 22.025044] systemd[1134]: mongodb.service: Failed at step EXEC spawning /nix/store/6akfivwijc51a6c767kmaq6l1dm9cy7i-mongodb-3.2.9/bin/mongod: No such file or directory
<clever>
bennofs1: raw hydra serves the nars at exactly their storepath, nix-serve i believe serves them at the hash from the storepath, and nix-push serves the nars at the hash of the nar contents
<clever>
bennofs1: the nar path depends on the binary cache server
<clever>
copumpkin: that sounds like S3 again
<clever>
copumpkin: 404 on what?, 404's are normal for some things
<clever>
and the most recent update cant render buttons of nixos
<clever>
the servers also block all old versions from working
<clever>
so this problem happens every ~2 months, on the most recent version of nixpkgs
<clever>
as an example, teamviewer deletes old versions every time they make a release
<clever>
depends on the source mirror
<clever>
and if the old source is gone from its mirrors, your in trouble!
<clever>
one minor issue with trying to build older nixpkgs revisions though, is that if its not in the binary cache, you need to download the old source
<clever>
so nix cant cheat and build the missing stuff without you noticing
<clever>
and another neat thing, the above command only works if that exact build is in cache.nixos.org
<clever>
c0bw3b: the above command will download the exact build my nixpkgs references, and you dont need a copy of nixpkgs to do that
<clever>
but you can also skip a few steps, and just directly go to the binary cache
<clever>
as long as S3/AWS hasnt lost the data
<clever>
c0bw3b: so if you save the attribute path and the revision of nixpkgs, you can re-download that package again at any point in the future
<clever>
c0bw3b: so if you just grab a random commit from git, there is a chance hydra hasnt built it, and it wont be in the cache
<clever>
c0bw3b: the channels are part of it, only something released in a channel is going to have been built fully by hydra
<clever>
c0bw3b: also keep in mind, you can only compute the hash to download from cache.nixos.org if you use the old nixpkgs that the package was originaly in
<clever>
hence the quotes
<clever>
yeah
<clever>
c0bw3b: i dont think the cache has ANY garbage collection on it, so the answer is currently "forever"
<clever>
and the only storepath i had to specify directly was ${out}
<clever>
no configure, no automake, no cmake
<clever>
fuzzy_id: i recently made a lua based program using just "buildInputs = [ protobuf libressl lua libevent ];" and " -lssl -lprotobuf -llua -levent_pthreads -levent -levent_openssl"
<clever>
fuzzy_id: gcc will always add lib and .so to the name you give it
<clever>
fuzzy_id: the argument is -llua
<clever>
have you played with nix-repl before?
<clever>
you would need something like nix-repl to keep the files loaded in ram
<clever>
yeah
<clever>
but using it directly lets you inspect any attribute of any set
<clever>
MoreTea: this is the internals behind how hello.meta.position works
<clever>
MoreTea: have you seen builtins.unsafeGetAttrPos ?
<clever>
MoreTea: neat
<clever>
qknight: also, "man configuration.nix" shows all options for the nix channel you built against
<clever>
i should automate that, and provide links for every channel
<clever>
i had made a more up to date version of options.html for master, but i havent updated it in ages
2017-03-04
<clever>
gwlan: cant see anything obvious as to why its broken, and its getting late here
<clever>
gwlan: heading off to bed now
<clever>
gwlan: and the full error
<clever>
gwlan: can you pastebin the configuration.nix?
<clever>
Mateon1: from one of your previous pastebins
<clever>
Mar 04 23:17:04 hydra X[3082]: (++) Using config file: "/nix/store/aqcgdqm1z8lnnl6yqx30mxq7gi7wc4y6-xserver.conf"
<clever>
gwlan: all of those symlinks are absolute, and refer to the other /nix/store, so they wont resolve right until you chroot or manualy resolve them in your head
<clever>
ah
<clever>
there are pre-made virtualbox images available for download
<clever>
or a local vm
<clever>
smw_: maybe you should start with a normal x86 machine you have physical access to?
<clever>
Mateon1: if you post your backtrace and some config details, the sddm guys can probably find the problem better
<clever>
Mateon1: last comment is a person claiming ABI problems, but nix cant really have those