xmlsec: use latest nss

The issues mentioned seem to be fixed in the latest xmlsec release
This commit is contained in:
Yureka 2021-09-06 13:59:16 +02:00 committed by Martin Weinelt
parent ffbac21daa
commit 4f93f4b82b
No known key found for this signature in database
GPG key ID: 87C1E9888F856759

View file

@ -1,7 +1,5 @@
{ stdenv, fetchurl, libxml2, gnutls, libxslt, pkg-config, libgcrypt, libtool
# nss_3_53 is used instead of the latest due to a number of issues:
# https://github.com/lsh123/xmlsec/issues?q=is%3Aissue+is%3Aopen+nss
, openssl, nss_3_53, lib, runCommandCC, writeText }:
, openssl, nss, lib, runCommandCC, writeText }:
lib.fix (self:
stdenv.mkDerivation rec {
@ -24,11 +22,11 @@ stdenv.mkDerivation rec {
nativeBuildInputs = [ pkg-config ];
buildInputs = [ libxml2 gnutls libxslt libgcrypt libtool openssl nss_3_53 ];
buildInputs = [ libxml2 gnutls libxslt libgcrypt libtool openssl nss ];
enableParallelBuilding = true;
doCheck = true;
checkInputs = [ nss_3_53.tools ];
checkInputs = [ nss.tools ];
preCheck = ''
substituteInPlace tests/testrun.sh \
--replace 'timestamp=`date +%Y%m%d_%H%M%S`' 'timestamp=19700101_000000' \