<clever>
slabity: and then `nixops deploy -d networkname` will remember that `-I nixpkgs=/anything` for you
<clever>
slabity: if you `nixops modify -d networkname deployment.nix -I nixpkgs=/anything`, it will get baked into the sqlite state
<clever>
nicolas[m]1: can you paste the part of the expr using trace?
<clever>
but the language is pure and shouldnt work like that
<clever>
bqv: the commit doesnt seem to exist within any branch, which implies they used a force-push to undo it
<clever>
slabity: *facepalm*
<clever>
wnklmnn: use an overlay to override the derivation in question
<clever>
immae: the problem is that the cargoSha256 is just the hash of whatever `cargo fetch` created, so it depends on which version of cargo you used
<clever>
bbigras: if your not using IFD, you can just use nix-instantiate or `nixos-rebuild --dry-run` to eval it
<clever>
zangi: yes
<clever>
adisbladis: propagatedBuildInputs would also do that automatically
<clever>
adisbladis: why do you want the deps from several?
<clever>
reactormonk: you can also `nix-shell -A valgrind`, it will import . by default
<clever>
reactormonk: you want -E not -A
<clever>
mvnetbiz_: that makes the installPhase fail fatally, and then keeps the result of the failure
<clever>
reactormonk: run `unpackPhase ; cd $sourceRoot ; configurePhase` inside a `nix-shell '<nixpkgs>' -A valgrind`
<clever>
oops, was thinking of `nix build -L`
<clever>
reactormonk: run `nix-store -L /nix/store/foo` to see the log of how something was built, `nix log` may also work for things on a cache
2020-07-08
<clever>
then you can just ignore nearly everything, but you must generate the arg list properly yourself (or copy/paste)
<clever>
KarlJoad: for a real dirty solution, `services.xserver.displayManager.xserverArgs = lib.mkForce [ ... ];`
<clever>
yes
<clever>
KarlJoad: for example, monitorSection for the first monitor, and xrandrHeads for the extra ones
<clever>
KarlJoad: you need to look at the string interpolation on 713-808, and set the right settings to make it generate the right config
<clever>
robodojo: nixos-generate-config handles that step
<clever>
KarlJoad: compare the generated xorg.conf to the one nixos is creating, how do they differ, what needs to be changed?
<clever>
colemickens: --option substituters "list goes here" to temporarily skip it
<clever>
KarlJoad: how are the defaults conflicting?
<clever>
KarlJoad: but!, line 713-808 is also setting services.xserver.config, so nixos is merging the 2 strings
<clever>
KarlJoad: this shell script is used to generate the config file, lines 122-139 generate the `Section "Files"` part, and line 141 will print the config (from 118) which is your services.xserver.config
<clever>
patagonicus: you usually dont use ccache with nix, since nix can already cache things
<clever>
patagonicus: linuxPackages_latest isnt a single package, its a set of every optional kernel module
<clever>
KarlJoad`: read the xorg.conf file and logs that both nixos and ubuntu are using
<clever>
KarlJoad`: that implies xorg cant see the card, and nothing xrandr does can change things
<clever>
robodojo: availableKernelModules can also be auto-loaded by udev, when the relevant device is detected
<clever>
mostly up to personal preference
<clever>
yep
<clever>
robodojo: you can choose to just never run nixos-generate-config again, and edit it all you want
<clever>
robodojo: any time you run nixos-generate-config, the file gets overwritten
<clever>
yorick: you may want to run `nix-store --verify --check-contents` after it is working again
<clever>
yorick: yeah, try slabity'd trick above, but your FS may have other corruption due to an improper shutdown
<clever>
mine is also "10"
<clever>
yorick: and ls -l reports the size as what?
<clever>
yorick: what are the contents of that file?
<clever>
slabity: it only works if , is the first character of the msg
<clever>
selfsymmetric-mu: yeah, just add it to the inputs or the -p param
<clever>
selfsymmetric-mu: the stdenv should just auto-detect the right output when you put `builtInputs = [ postgresql ];`
<clever>
so /mnt goes before /mnt/boot and /mnt/home
<clever>
robodojo: basically, sort all things by the length of the path your mounting to (in terms of number of /'s), and then mount from shortest to longest
<clever>
robodojo: no, boot has to be mounted after root
<clever>
robodojo: because when you mount to /mnt, it hides anything that was previously at /mnt, such as /mnt/boot/
<clever>
robodojo: root should be mounted first
<clever>
only the order of mounting really matters
<clever>
robodojo: i would always create boot first, swap 2nd, and root last
<clever>
64mb for /boot is a bit too low, i often have trouble getting 2 generations to fit
<clever>
i was thinking it would be defined at the nixops layer
<clever>
some one-time setup commands, that cant be changed after the fact
<clever>
robodojo: it gets the sizes from another configuration.nix, that is used to build the livecd
<clever>
robodojo: this shell script will partition, format, mount, and install nixos, in a single command
<clever>
makefu: try using pkgs.fetchFromBitbucket ?
<clever>
makefu: where is the repo hosted?
<clever>
makefu: builtins.fetchGit is impure, and can use host config
<clever>
since they are already validating the final hash of the product
<clever>
makefu: most of the fetch functions also ignore how valid ssl certs are
<clever>
AlpineLlama: it creates that after it mounts the main filesystem on the disk
<clever>
AlpineLlama: if you boot with the kexec method, then you have a livecd-like env running entirely from ram, and can poke at the usb more with the benefit of the whole OS working
<clever>
AlpineLlama: this lets you switch from any distro to nixos, without rebooting
<clever>
patagonicus: its an attribute set containing a name and patch i believe
<clever>
yep
<clever>
i can mess with it later, still waking up now
<clever>
where did i put that older usb code...
<clever>
thanks
<clever>
wireless
<clever>
i tried to get that from the older headset, but all i could do was read the buttons
<clever>
battery level would be useful
<clever>
ashkitten: whats there to control? it has fewer options then the older headset i have
<clever>
ashkitten: logitech g533
<clever>
gueorgui: its just vendor lockin, adding special features that only their hw can use
<clever>
gueorgui: main downside of the G533, is that you need the usb dongle to make it work, and the headset is a big large for travel
<clever>
gueorgui: its not bluetooth, so it can just ignore the limits
<clever>
gueorgui: ive been using a logitech g533 for a while now, and its got good quality for both directions
<clever>
you may even need a special bluetooth controller to even use them
<clever>
and they havent documented how to use them
<clever>
it could be custom bluetooth profiles
<clever>
gueorgui: that lets you hear the cpu fan and every keystroke!
2020-07-07
<clever>
and the bash installed on the system, doesnt depend on the bash-dev
<clever>
the stdenv changes the SHELL to a non-interactive build of bash
<clever>
`nix-build /nix/store/d43v6bx7r6fcaq3fbbfd5mwh1f5s7rmg-bash-interactive-4.4-p23-dev -o bash-root` i think
<clever>
you can just run nix-build against it to make your own roots
<clever>
nix-shell impurely grabs bashInteractive from the host <nixpkgs>
<clever>
which package?
<clever>
i'm not sure either on that part
<clever>
it comes up when cross compiling
<clever>
Guest7: that wont get nativeBuildInputs, you may want just `env > $out` to get everything
<clever>
typetetris: some poorly made scripts will use that to change how they behave, causing surprises
<clever>
typetetris: the value of lib.inNixShell changes when your in nix-shell, even if its in an expr being evaled by nix-build
<clever>
> pkgs.stdenv.system
<clever>
hexo: if you comment out everything from 10-18, and `nixos-rebuild build`, what happens?
<clever>
`python3-3.7.5-env` is likely the result of calling pkgs.buildEnv, and you gave it 2 conflicting versions of sip
<clever>
hexo: builder for '/nix/store/n4g06d8fmvpigddx970waiaqm2rifsj5-python3-3.7.5-env.drv'` this line here
<clever>
hexo: further down, it should tell you what derivation failed to build
<clever>
hexo: its creating a new directory, that has the contents of both of the inputs
<clever>
maybe get the dockerTools from it too
<clever>
mariatsji: you need to `import <nixpkgs> { system = "x86-64-linux"; }` and get hello from that
2020-07-06
<clever>
it might be a child-proc, a `git clone`, check `ps -eH x`
<clever>
do `ls -l /proc/PID/fd/10` to see what that is
<clever>
yep, so its waiting for something from fd 10
<clever>
ctrl+c will detatch safely
<clever>
wpcarro: you can also use `strace -p PID` to attach to something after the fact
<clever>
wpcarro: the git repo is rather large, how long did you wait?
<clever>
the sandbox will copy all inputs to /nix/store/ first, and make them world readable
<clever>
builtins.fetchGit doesnt define a derivation, it just runs git at eval time, immediately
<clever>
when nix-daemon then builds that derivation (at a later time), it will run git in a sandbox, possibly with network enabled
<clever>
__monty__: fetchFromGithub isnt directly running git, its defining a derivation
<clever>
about all you could do is make it an alias to builtins.fetchGit
<clever>
__monty__: doesnt exist
<clever>
> lib.impureFetchGit
<clever>
more a closure size issue
<clever>
__monty__: the impure ones, just have nix impurely run a command as the current user, and the nix binary would have to depend on those commands, for every user
<clever>
__monty__: the pure ones cant access secrets, but dont rely on something being installed
<clever>
__monty__: the impure ones via builtins, can access secrets (like ssh keys) while fetching
<clever>
that one isnt bad, for reasons, lol
<clever>
srhb: pkgs.fetchgit
<clever>
yes, there is a fetchgit
<clever>
simon: try using fetchhg instead?
<clever>
that is not the result of loading the overlay
<clever>
that is a list containing 3 elements, a function, a path, and a set
<clever>
overlays = [
<clever>
import ./client.nix { inherit ghcjs; }
<clever>
yep, theres your problem
<clever>
how did this overlay get applied?
<clever>
the problem is not in the overlay itself
<clever>
Graypup_: and what is the --show-trace output?