Change:
<del> { stdenv, fetchFromGitHub, pythonPackages , pkgconfig, autoreconfHook, rsync , swig, qt48Full, fcgi , bitcoin, procps, utillinux }: let version = "0.96.1"; inherit (pythonPackages) buildPythonApplication pyqt4 psutil twisted; in buildPythonApplication { pname = "bitcoinarmory"; inherit version; src = fetchFromGitHub { owner = "goatpig"; repo = "BitcoinArmory"; rev = "v${version}"; sha256 = "0pjk5qx16n3kvs9py62666qkwp2awkgd87by4karbj7vk6p1l14h"; fetchSubmodules = true; }; format = "other"; # FIXME bitcoind doesn't die on shutdown. Need some sort of patch to fix that. #patches = [ ./shutdown-fix.patch ]; nativeBuildInputs = [ autoreconfHook pkgconfig swig pyqt4 qt48Full rsync # used by silly install script (TODO patch upstream) ]; buildInputs = [ qt48Full fcgi ]; propagatedBuildInputs = [ pyqt4 psutil twisted ]; makeFlags = [ "PREFIX=$(out)" ]; makeWrapperArgs = [ "--prefix            PATH : ${bitcoin}/bin"   # for `bitcoind` "--prefix            PATH : ${procps}/bin"    # for `free` "--prefix            PATH : ${utillinux}/bin" # for `whereis` "--suffix LD_LIBRARY_PATH : $out/lib"         # for python bindings built as .so files "--run    cd $out/lib/armory"               # so that GUI resources can be loaded ]; # auditTmpdir runs during fixupPhase, so patchelf before that preFixup = '' newRpath=$(patchelf --print-rpath $out/bin/ArmoryDB | sed -r 's|(.*)(/tmp/nix-build-.*libfcgi/.libs:?)(.*)|13|') patchelf --set-rpath $out/lib:$newRpath $out/bin/ArmoryDB ''; # fixupPhase of mkPythonDerivation wraps $out/bin/*, so this needs to come after postFixup = '' wrapPythonProgramsIn $out/lib/armory "$out $pythonPath" ln -sf $out/lib/armory/ArmoryQt.py $out/bin/armory ''; meta = { description = "Bitcoin wallet with cold storage and multi-signature support"; longDescription = '' Armory is the most secure and full featured solution available for users and institutions to generate and store Bitcoin private keys. This means users never have to trust the Armory team and can use it with the Glacier Protocol. Satoshi would be proud! Users are empowered with multiple encrypted Bitcoin wallets and permanent one-time ‘paper backups’. Armory pioneered cold storage and distributed multi-signature. Bitcoin cold storage is a system for securely storing Bitcoins on a completely air-gapped offline computer. Maintainer's note: The original authors at https://bitcoinarmory.com/ discontinued development. I elected instead to package GitHub user @goatpig's fork, as it's the most active, at time of this writing. ''; homepage = https://github.com/goatpig/BitcoinArmory; license = stdenv.lib.licenses.agpl3Plus; maintainers = with stdenv.lib.maintainers; [ elitak ]; platforms = [ "i686-linux" "x86_64-linux" ]; }; } </del>

Discussion:
After installing , this happens: from — . . System: 17.03.1844. (Gorilla) Nix version: nix-env (Nix) 1.11.14 Nixpkgs version: "17.03.1844." Sandboxing enabled: build-use-sandbox = true
Also, upstream made 2 releases since, one with a critical vuln.
I'm getting the same on 0.96.3, but will look some more. What specifically is the vulnerability, out of curiosity?
The upstream build process in still quite messy, with embedded libraries concretely integrated into build files. I've got a modified nix expression that replaces some of the deps with libs in the store, but with both variants I still get either a SegFault in ArmoryDB or a SIGILL in I don't know if I can invest much more time in fixing this. I suspect the issues originate upstream, FWIW. Personally, I'm running a gcrooted-closure that I've kept unchanged for some months now.
I’m not sure, 0.96.3 works fine with from your original commit, i.e. . The vulnerability was related to fragmented backups. Well, I guess I’ll just stay with Bitcoin Core. I just wanted to try this one. ¯()/¯
Oh, interesting. This isn't the first time I've seen a newer glibc cause segfaults and other nastiness, but I lack the skill to fix these types of problems efficiently. Armory's great for the offline wallet stuff, but the original devs left the source tree in a poor state. I'll eventually get it working on the master branch again, probably.
I don’t get that, really. Is everything compiled from source in this derivation? Does upstream include binary blobs in the repo? :
Both that SIGSEGV at the very beginning, and failure, and SIGILL would suggest a linking error to me. You shouldn’t need to use on programs cleanly built from source. Hmm.
Even less so, to remove a reference? What is this upstream build script doing? :grin: sighs
It's building the lib deps from source. fcgi is a git-submodule and the rest are checked into the repo.

I've already begun to try to excise them during the patch phase: This still yields the same problems, however, along with some new ones (fcgi version mismatch, i think), but it's on the path to getting a cleanly linked binary. I welcome any amendments to get this working reliably and linked properly.
Let me try that, but that upstream repo is a total mess.
:arrow_up: fixed above.