summaryrefslogtreecommitdiff
path: root/.mailmap
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2023-07-09 23:48:00 +0200
committerGitHub <noreply@github.com>2023-07-09 17:48:00 -0400
commiteef14ddcadb6af5beec76a2f5a3cb88d4b9eb1ef (patch)
tree2445c57b8b50ddda55681ddc7d7dfa5e0b7e79c7 /.mailmap
parentdb879a567928d3166365861d85dd1f3be4f0b36e (diff)
downloadspack-eef14ddcadb6af5beec76a2f5a3cb88d4b9eb1ef.tar.gz
spack-eef14ddcadb6af5beec76a2f5a3cb88d4b9eb1ef.tar.bz2
spack-eef14ddcadb6af5beec76a2f5a3cb88d4b9eb1ef.tar.xz
spack-eef14ddcadb6af5beec76a2f5a3cb88d4b9eb1ef.zip
openssl: prefer 3.x (#36729)
* openssl: prefer 3.x This PR is not intended to be merged immediately, but it would be good to see what packages fail to build in CI so that we can get proper version constraints on openssl (before all packages update and support both openssl 1 and 3) * Disable assembly for 3.x %oneapi * cmake: depend on spack curl, to deal with curl - openssl compat * also make zlib external * remove overly strict & unsafe requirement on py-cryptographty patch version number * update openssl compat bounds in py-cryptography * smaller diff * Make libssh2 an autotools/cmake package * fix weird upperbound in libssh2 as there is not openssl v2 * libssh2: pc file lists plain -lssl -lcrypto w/o leading -L flag, confusing libgit2 parsing of pkg-config output * Actually fix the issue in libssh2: its pc file looks broken
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions