public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jered Floyd <jered@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/trafficserver] trafficserver-9.2.14-1: Don't try to use Crypto Policies on RHEL 7
Date: Wed, 15 Jul 2026 17:21:13 GMT [thread overview]
Message-ID: <178413607389.1.7245874171778347632.rpms-trafficserver-df38be782bf7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/trafficserver
Branch : trafficserver-9.2.14-1
Commit : df38be782bf7a7e2522ac49ef6af63e2f0f2033c
Author : Jered Floyd <jered@redhat.com>
Date : 2022-07-12T01:50:14+00:00
Stats : +7/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/trafficserver/c/df38be782bf7a7e2522ac49ef6af63e2f0f2033c?branch=trafficserver-9.2.14-1
Log:
Don't try to use Crypto Policies on RHEL 7
---
diff --git a/trafficserver.spec b/trafficserver.spec
index 6ec6c94..063c7e2 100644
--- a/trafficserver.spec
+++ b/trafficserver.spec
@@ -4,7 +4,7 @@
Name: trafficserver
Version: 9.1.2
-Release: 8%{?dist}
+Release: 9%{?dist}
Summary: Fast, scalable and extensible HTTP/1.1 and HTTP/2 caching proxy server
License: ASL 2.0
@@ -25,7 +25,10 @@ Source10: %{modulename}.fc
# The new version of the test framework changes some symbols needed for the tests
Patch0: unit_tests.patch
+# Use Crypto Policies where supported
+%if 0%{?fedora} >= 21 || 0%{?rhel} >= 8
Patch1: trafficserver-crypto-policy.patch
+%endif
# fc36 upgrades to gcc 12, which no longer has cstring compatbility in string
# Upsteam PR: https://github.com/apache/trafficserver/pull/8786
Patch2: gcc12-cstring.patch
@@ -313,6 +316,9 @@ fi
%changelog
+* Mon Jul 11 2022 Jered Floyd <jered@redhat.com> 9.1.2-9
+- Don't try to use Crypto Policies on RHEL 7
+
* Mon Jun 13 2022 Jered Floyd <jered@redhat.com> 9.1.2-8
- Cherry-pick OpenSSL 3 compatibility required for RHEL 9
- Switch to OpenSSL 3 on f36+
reply other threads:[~2026-07-15 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178413607389.1.7245874171778347632.rpms-trafficserver-df38be782bf7@fedoraproject.org \
--to=jered@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox