<clever>
Guest73580: nix-shell itself wont, but teamspeak will create ~/.ts3something
<clever>
Guest73580: the above command stores the paths in /nix/store, and a normal nix-collect-garbage will delete all unused files in there
<clever>
adamt: you would either need to add a subdir in nginx that shares all of /nix/store/ or setup symlinks in www-root every time you finish a build
<clever>
adamt: replace with a server-side scripting language of your choice
<clever>
adamt: that file receives the mac of the machine in the GET params, and it could just nix-build something on the fly, then respond with the path to the result
<clever>
adamt: see the boot.php file in the example i linked above?
<clever>
jophish: i havent done any fpga stuff since getting into nixos and haskell
<clever>
jophish: i had partially implemented dhcp in verilog before deciding to use an ARM
<clever>
shachaf: and my luks device tends to be LVM with swap + zfs
<clever>
shachaf: i always do a cleartext /boot with an encrypted rootfs partition
2018-05-31
<clever>
andrewmiller1: just mount the existing FS's and run that
<clever>
andrewmiller1: it should be enough to just run `nixos-install` from the livecd after mounting, and it will repair nearly all of it
<clever>
andrewmiller1: then everything in /nix is toast and you have to reinstall
<clever>
andrewmiller1: thats the other database, which is safe to delete, `rm /root/.cache/nix/binary-cache-v5.sqlite*`
<clever>
shachaf: they should be
<clever>
andrewmiller1: what signs are saying its corrupt?
<clever>
andrewmiller1: if that db is lost, then everything in /nix/store is toast
<clever>
andrewmiller1: which nixos db?
<clever>
nh2[m]: but in our case, its stack->ghc->gcc.exe
<clever>
nh2[m]: i think we have been dealing with the exact same problem on windows, lol
<clever>
rihards: the 6c064e6b1f3 at the end is a git rev
<clever>
"18.09pre135256.6c064e6b1f3"
<clever>
nix-instantiate '<nixpkgs>' -A lib.nixpkgsVersion --eval
<clever>
maurer: on multi-user installs, its empty, because nix is in roots profile
<clever>
maurer: on single-user installs, the install script has to install nix into that profile
<clever>
yeah, that sounds useful
<clever>
jbaum98: not sure
<clever>
jbaum98: export variable
<clever>
hyper_ch: double-check the settings in the dns registrar
<clever>
the original admin of the site will need to fix their config at the registrar
<clever>
r
<clever>
so you have to know the answer, to find the answer, to be able to ask for the answe
<clever>
hyper_ch: the nameservers behind roleplayer.org are ns6.roleplayer.org and ns5.roleplayer.org, but there are no glue records to say what IP to find them at
<clever>
hyper_ch: they messed up the dns config
<clever>
hyper_ch: ah, the glue records are missing, i see whats wrong
<clever>
and it has dnssec
<clever>
hyper_ch: if i try again with `dig +trace`, i can see the NS records still exist
<clever>
hyper_ch: no response from the dns server
<clever>
hyper_ch: depends on what it is
<clever>
ryantm: yeah
<clever>
ryantm: and are you on nixos?
<clever>
ryantm: does nix-env -q say nix is installed?
<clever>
ryantm: fun things happen when you later try to upgrade the system nix, and the one in nix-env stops it from upgrading
<clever>
ryantm: but dont try to install nix with nix-env on nixos
<clever>
moet: i would also have a nixpkgs-src.json that specifies where to fetch nixpkgs from, and point NIX_PATH to that
<clever>
moet: you can also generally ignore that warning
<clever>
moet: your running a different version of nix then the host
<clever>
and nix-shell -p requires it
<clever>
--pure will clear NIX_PATH
<clever>
rotaerk: ive had to copy the teamspeak client binary because its being too smart about that
<clever>
rotaerk: the problem is when the path to the exe winds up reading symlinks, and looks in the original derivation
<clever>
rotaerk: now your 3rd derivation is just a 2 line bash script, that runs the haskell program, giving it a path to the shaders
<clever>
and both/default.nix just has { runCommand, shaders, haskellthing }:
<clever>
so you can do packages = self: { haskellthing = pkgs.haskellPackages.callPackage ./haskellthing {}; shaders = self.callPackage ./shaders {}; both = self.callPackage ./both {}; };
<clever>
rotaerk: if you do this, then every package defined inside packages, can refer to eachother, as-if they where all in nixpkgs
<clever>
justan0theruser: so the uefi testcase, turned into directions on creating a uefi install
<clever>
justan0theruser: gchristensen had made some code before, that tool the nixos-install tests, and auto-generated directions on how to install nixos
<clever>
ref and/or rev
<clever>
and if its a set, it will contain a url, ref, ref, and name
<clever>
but everything under builtins is part of nix, not nixpkgs
<clever>
palo: (probably as root) do a nix-channel --update on that machine
<clever>
palo: then it will use the nixpkgs for the host that is running nixops
<clever>
palo: did you pin the nixpkgs with `nixops modify -I` (does `nixops info` show a -I nixpkgs=) ?
<clever>
> "${ { outPath = "foobar"; } }"
<clever>
"${ { outPath = "foobar"; } }"
<clever>
adelbertc: treating an attribute set as a string always refers to .outPath automatically
<clever>
> "${hello}"
<clever>
> hello.outPath
<clever>
> hello
<clever>
yeah, and .outPath will still build it normally
<clever>
adelbertc: it will build it as a normal non-root derivation, then pass you the path to the built product
2018-05-30
<clever>
which would let you merge system.build.path with environment.systemPackages
<clever>
i could see apply being used to turn something like a systemPackages list into a buildEnv
<clever>
ah
<clever>
i'm not sure what the differences is between apply and merge on a type
<clever>
and types.comma i think its called
<clever>
and also types.string which was deprecated
<clever>
kreisys: and then the core of nixos, will throw an error if any module have set that special "optino"
<clever>
kreisys: but there is also a module level assertion, which basically acts as a nixos option any module can set, and it gets merged between all modules
<clever>
kreisys: the assert builtin has to deal with lazyness, you need to get it into the codepath, or nix will just silently skip over it
<clever>
fin-ger: if your planning to reboot, you can also do `nixos-rebuild boot`
<clever>
yeah
<clever>
Jetien: its not a string though, its a path to a file
<clever>
Jetien: you need an input on the jobset called ssh-config-file, then <ssh-config-file> will find that input
<clever>
> let x = { repo, domain ? "gitlab.com" }: domain; in x { repo = "foo"; }
2018-05-29
<clever>
depends on if you want the CI systems to silently ignore a major problem and take an hour longer for every build, or to fail and bring attention to it
<clever>
unreleased changes to opensource software?
<clever>
jtojnar: i suspect that soundnode made changes to the electron build and didnt document them, might even be a license issue??
<clever>
jtojnar: soundnode is an electron based app i came across a few months ago, that refuses to work with the nixpkgs electron
<clever>
worldofpeace: i have patched a "mac" electron app for linux before, all i did was extract the JS from the .pkg file, then run the linux build of electron against it via pkgs.electron
<clever>
mjrosenb: the problem is just that nobody has written a nix derivation that runs otool against the darwin build of oraclejdk
<clever>
mjrosenb: the util for patching things on mac is called otool
<clever>
the example even shows xrandr commands
<clever>
sir_guy_carleton: ah, the setupscript will run after X is started, before you login, so that could be better
<clever>
sir_guy_carleton: the display manager will run this after you login but before launching the desktop manager
<clever>
sir_guy_carleton: you can either configure nixos to run it after you login (the login page wont be on the right monitors), or you can somehow configure the DM to run the cmd, or you can configure a default in xorg with xrandrHeads
<clever>
sir_guy_carleton: X isnt running until after the display-manager has started, so xrandr will fail when ran before
<clever>
same
<clever>
overrideAttrs should be the right one
<clever>
very
<clever>
yes
<clever>
and thats based on the nix expressions, and that users config.nix
<clever>
yeah
<clever>
and then its al .drv files from then on
<clever>
Unode: the user running nix-build will eval all expressions, convert them into .drv files, and forward the .drv files to nix-daemon, which puts them into the store
<clever>
Unode: the nix expressions are no longer in the picture once things reach nix-daemon
<clever>
same
<clever>
you should never be modifying any file in nix/store
<clever>
and how did you modify that?
<clever>
Unode: did you tell it to use the new nixpkgs path?
<clever>
Unode: i'm out of ideas then
<clever>
Unode: thats what the above should answer
<clever>
they only ever operate on .drv files
<clever>
nix-daemon and the build users never read nix files
<clever>
can you pastebin the result of `nix-instantiate '<nixpkgs>' -A findutils -vvvvv`
<clever>
does ~/.config/nixpkgs/config.nix exist?
<clever>
Unode: where did you put your config.nix file?
<clever>
and the phase is entirely absent
<clever>
Unode: or just run cat on it
<clever>
what is the output of `nix show-derivation /g/bork3/home/mocat/nix/store/0a8aq0zicr8brd1lvj0swgd3vya0npgy-findutils-4.6.0.drv` ?
<clever>
ah, i see
<clever>
Unode: and why does that not begin with /nix?