From b95f7591bd83a0e483d2b6db49258d2ea8b44f3d Mon Sep 17 00:00:00 2001 From: Peter Korsgaard Date: Mon, 6 Feb 2023 15:59:29 +0100 Subject: [PATCH] package/gitlab-runner: use LIBCURL_FORCE_TLS to enforce TLS support in curl BR2_PACKAGE_LIBCURL_OPENSSL is part of a "choice" option so it cannot be selected. What seems to be really be needed is HTTPS support in curl, so use the blind LIBCURL_FORCE_TLS option instead (openssl is already selected). Signed-off-by: Peter Korsgaard --- package/gitlab-runner/Config.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/gitlab-runner/Config.in b/package/gitlab-runner/Config.in index 89e3e87b5c..4289613ab9 100644 --- a/package/gitlab-runner/Config.in +++ b/package/gitlab-runner/Config.in @@ -11,7 +11,7 @@ config BR2_PACKAGE_GITLAB_RUNNER select BR2_PACKAGE_GIT # runtime select BR2_PACKAGE_LIBCURL # runtime select BR2_PACKAGE_LIBCURL_CURL # runtime - select BR2_PACKAGE_LIBCURL_OPENSSL # runtime, for ca-certificates. + select BR2_PACKAGE_LIBCURL_FORCE_TLS # runtime select BR2_PACKAGE_OPENSSL # runtime select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL # runtime select BR2_PACKAGE_LIBOPENSSL_BIN # runtime