<clever>
ToxicFrog: nixpkgs.overlays in configuration.nix
<clever>
ToxicFrog: nixos-rebuild wont load overlays from the path
<clever>
the -v makes things more obvious when it works
<clever>
i always do ln -sv
<clever>
ToxicFrog: then search it for both versions of bitlbee
<clever>
ToxicFrog: find the path for the final .drv file in the tree, then run nix-store -qR on that drv
<clever>
ToxicFrog: what did you modify inside the overrideAttrs ?
<clever>
yeah
<clever>
and dont reference pkgs anywhere
<clever>
it must use super
<clever>
foo = self.foo.override will fail
<clever>
ToxicFrog: ah, make sure an override doesnt refer to self when trying to modify itself
<clever>
ToxicFrog: if you gist what you changed recently i could take a peek
<clever>
ToxicFrog: one of those files is manipulating a function that came from your code, the traces suck
<clever>
yeah, that
<clever>
attempt to call something which is not a function but a set, at
<clever>
joepie91: overrideAttrs needs a function
<clever>
ah, but it should still be a derivation returned
<clever>
but if pluginSupport is false (like in oraclejdk8), it skips that entirely
<clever>
joepie91: appendToName is a function that takes a derivation, and applies an override to its .name field
<clever>
joepie91: oraclejdk8 is an attr that has already done so
<clever>
joepie91: if you pass it the required 2 booleans, it should return a derivation that can be overridden
<clever>
the strbuf_getwholeline in frame 27 is reading up to the first \n in a given FILE*
<clever>
Sonarpulse: try loading the release.nix in nix-repl and eval the job's attribute?
<clever>
that implies it was hung at __read_nocancel for over 3 weeks, and the deadlocking was a side-effect of __read_nocancel not handling signals right
<clever>
hmmm, reading the .bash_history, i sent it 3 signals while debugging, and i see 3 signal handlers in the backtrace
<clever>
though given that opendir returns a DIR*, you can probably expect it to do so
<clever>
so its not safe to do opendir in a signal handler!
<clever>
the man page makes no mention of that
<clever>
opendir calls malloc
<clever>
git is using opendir to implement its rm -rf
<clever>
aha, i think i found an un-documented hole in glibc
<clever>
over 3 weeks
<clever>
this git process has been deadlocked since july 11th
<clever>
x
<clever>
gchristensen: malloc hangs on a mutex, and sending any signal, causes another nested malloc, to hang on the same mute
<clever>
gchristensen: check the backtrace i linked ~10mins ago
<clever>
yes
<clever>
and that involves malloc in the signal context
<clever>
at a glance, i think it will just undo the partial "git clone" upon receiving any signal (maybe even sigchld?)
<clever>
you can also run nix-shell on an ubuntu system that has had nix installed
<clever>
yeah
<clever>
and now you can track the dependencies in git
<clever>
nschoe: if you put this into a file called shell.nix, you can just run nix-shell without an arguments
<clever>
with import <nixpkgs> {}; stdenv.mkDerivation { name = "yourproject"; buildInputs = [ gnome.gtk pkgconfig ]; }
<clever>
you can also create a shell.nix to save the list of packages that will be growing
<clever>
yes
<clever>
so when using nix-shell, it will just work
<clever>
nschoe: gcc should also be in the scope already, and it will change the search path for -I
<clever>
nschoe: by adding pkgconfig to the -p list, a setup hook for pkgconfig gets ran, which will scan over all of your inputs (gnome.gtk pkgconfig), and add each of them to an env variable that changes the pkgconfig search path
<clever>
nschoe: nix will never have a /usr/lib/include directory
<clever>
nschoe: you must still build it under nix-shell, and installing pkgconfig also breaks it
<clever>
nschoe: nix-shell -p gnome.gtk pkgconfig
<clever>
eacameron: i generally use ghcWithPackages, just add all the packages you need to it
<clever>
nschoe: you must use nix-shell when building things, installing build-time stuff just breaks it
<clever>
akiroz: so it gave an invalid value to nixos, as the key to allow in
<clever>
akiroz: that probably stopped it from creating an ssh keypair
<clever>
so its obvious from the args, what your using
<clever>
this is why i was in favor of using pythonPackages.callPackage, and not passing pythonPackages around
<clever>
which licenses does it use?
<clever>
you passed all of pythonPackages to a package, that only wanted 3 attributes
<clever>
Infinisil: and now we have the pythonPackages.callPackage thing i mentioned yesterday
<clever>
but you can at least code it to print unknown things
<clever>
copumpkin: yeah, then you need to fix the iteration loop after you track it down
<clever>
copumpkin: it might be simpler to just run nix-store -qR $(nix-instantiate ...), and then iterate over nixpkgs to map each .drv to an attribute
<clever>
you have absolutely no way to access strace's meta
<clever>
copumpkin: but if i do ${strace}/bin/strace in a string