Andreas Rammhold 4543ae95a3 globalplatform: stick with openssl 1.0.2 ... While upstream has patches in tree that support newer versions of OpenSSL those haven't been released and picking them doesn't seem to be trivial without risking breakage that I can not test. After talking to the previous maintainer of the package this also seems like the sanest approach for the time being.		2019-07-29 21:25:15 +02:00
..
applications	golden-cheetah: 3.4 -> 3.5-DEV1903	2019-07-29 21:25:15 +02:00
build-support	Merge staging-next into staging	2019-07-26 14:45:31 +02:00
common-updater
data	Merge master into staging-next	2019-07-25 11:52:18 +02:00
desktops	pin some packages to openssl 1.0.2 for now	2019-07-29 21:25:10 +02:00
development	globalplatform: stick with openssl 1.0.2	2019-07-29 21:25:15 +02:00
games	Merge staging-next into staging	2019-07-28 09:10:03 +02:00
misc	Merge staging-next into staging	2019-07-26 14:45:31 +02:00
os-specific	Merge staging-next into staging	2019-07-28 09:10:03 +02:00
servers	postgresql: build < 9.5 with openssl 1.0.2	2019-07-29 21:25:10 +02:00
shells	oh-my-zsh: 2019-07-13 -> 2019-07-22	2019-07-23 08:36:18 -04:00
stdenv	stdenv: MACOSX_DEPLOYMENT_TARGET 10.10 -> 10.12	2019-07-08 21:56:40 +02:00
test
tools	tpm-luks: add openssl1.1 patch	2019-07-29 21:25:15 +02:00
top-level	openssh_hpn: pin to openssl 1.0.2	2019-07-29 21:25:14 +02:00