public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Dmitry Belyavskiy <dbelyavs@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/openssl] rebase_40beta: Moving engine-related files to a separate subpackage to be deprecated in future
Date: Tue, 09 Jun 2026 12:45:22 GMT [thread overview]
Message-ID: <178100912228.1.7175691259519988139.rpms-openssl-e67e9d9c40cd@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/openssl
Branch : rebase_40beta
Commit : e67e9d9c40cd2cb9547e539c658e2b63f2736762
Author : Dmitry Belyavskiy <dbelyavs@redhat.com>
Date : 2024-07-01T18:12:40+02:00
Stats : +23/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/openssl/c/e67e9d9c40cd2cb9547e539c658e2b63f2736762?branch=rebase_40beta
Log:
Moving engine-related files to a separate subpackage to be deprecated in future
Resolves: rhbz#2276420
---
diff --git a/openssl.spec b/openssl.spec
index 2733d41..7f8cf85 100644
--- a/openssl.spec
+++ b/openssl.spec
@@ -29,7 +29,7 @@ print(string.sub(hash, 0, 16))
Summary: Utilities from the general purpose cryptography library with TLS implementation
Name: openssl
Version: 3.2.2
-Release: 2%{?dist}
+Release: 3%{?dist}
Epoch: 1
Source: openssl-%{version}.tar.gz
Source2: Makefile.certificate
@@ -203,10 +203,22 @@ OpenSSL is a toolkit for supporting cryptography. The openssl-devel
package contains include files needed to develop applications which
support various cryptographic algorithms and protocols.
+%package devel-engine
+Summary: Files for development of applications which will use OpenSSL and use deprecated ENGINE API.
+Requires: %{name}-libs%{?_isa} = %{epoch}:%{version}-%{release}
+Requires: %{name}-devel%{?_isa} = %{epoch}:%{version}-%{release}
+Requires: pkgconfig
+
+%description devel-engine
+OpenSSL is a toolkit for supporting cryptography. The openssl-devel-engine
+package contains include files needed to develop applications which
+use deprecated OpenSSL ENGINE functionality.
+
%package perl
Summary: Perl scripts provided with OpenSSL
Requires: perl-interpreter
Requires: %{name}%{?_isa} = %{epoch}:%{version}-%{release}
+Provides: deprecated()
%description perl
OpenSSL is a toolkit for supporting cryptography. The openssl-perl
@@ -484,10 +496,16 @@ ln -s /etc/crypto-policies/back-ends/openssl_fips.config $RPM_BUILD_ROOT%{_sysco
%files devel
%doc CHANGES.md doc/dir-locals.example.el doc/openssl-c-indent.el
%{_prefix}/include/openssl
+%exclude %{_prefix}/include/openssl/engine*.h
%{_libdir}/*.so
%{_mandir}/man3/*
+%exclude %{_mandir}/man3/ENGINE*
%{_libdir}/pkgconfig/*.pc
+%files devel-engine
+%{_prefix}/include/openssl/engine*.h
+%{_mandir}/man3/ENGINE*
+
%files perl
%{_bindir}/c_rehash
%{_bindir}/*.pl
@@ -503,6 +521,10 @@ ln -s /etc/crypto-policies/back-ends/openssl_fips.config $RPM_BUILD_ROOT%{_sysco
%ldconfig_scriptlets libs
%changelog
+* Mon Jul 01 2024 Dmitry Belyavskiy <dbelyavs@redhat.com> - 1:3.2.2-3
+- Moving engine-related files to a separate subpackage to be deprecated in future
+ Resolves: rhbz#2276420
+
* Thu Jun 27 2024 Dmitry Belyavskiy <dbelyavs@redhat.com> - 1:3.2.2-2
- As upstream disables TLS 1.0/1.1 on any SECLEVEL > 0, there is no point
keeping the SHA1 permission at SECLEVEL=1 anymore.
reply other threads:[~2026-06-09 12:45 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=178100912228.1.7175691259519988139.rpms-openssl-e67e9d9c40cd@fedoraproject.org \
--to=dbelyavs@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