public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
To: git-commits@fedoraproject.org
Subject: [rpms/intel-ipp-crypto-mb] rawhide: Update to 2.3.0 (rhbz#2504142)
Date: Fri, 31 Jul 2026 13:15:18 GMT [thread overview]
Message-ID: <178550371865.1.2307846888057372431.rpms-intel-ipp-crypto-mb-cda6a4dfbed6@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/intel-ipp-crypto-mb
Branch : rawhide
Commit : cda6a4dfbed6ce6a12a1bd5519280f4f8c3adf3d
Author : Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
Date : 2026-07-31T16:14:57+03:00
Stats : +20/-18 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/intel-ipp-crypto-mb/c/cda6a4dfbed6ce6a12a1bd5519280f4f8c3adf3d?branch=rawhide
Log:
Update to 2.3.0 (rhbz#2504142)
---
diff --git a/intel-ipp-crypto-mb.spec b/intel-ipp-crypto-mb.spec
index 60b0352..0d9edcb 100644
--- a/intel-ipp-crypto-mb.spec
+++ b/intel-ipp-crypto-mb.spec
@@ -1,7 +1,5 @@
-%global debug_package %{nil}
-%global srctag ippcp_2021.10.0
-%global mbx_int_major 11
-%global mbx_int_minor 11
+%global ipp_int_major 13
+%global ipp_int_minor 3
%global desc %{expand: \
Intel IPP Cryptography library provides optimized versions of RSA, ECDSA, ECDH
and x25519 multi-buffer algorithms based on Intel Advanced Vector Extensions
@@ -10,21 +8,21 @@ Intel Advanced Vector Extensions 512 (Intel AVX-512) GFNI and SM3 based on
Intel Advanced Vector Extensions 512 (Intel AVX-512) instructions.}
Name: intel-ipp-crypto-mb
-Version: 1.0.10
-Release: 8%{?dist}
+Version: 2.3.0
+Release: 1%{?dist}
Summary: Intel IPP Cryptography multi-buffer library
License: Apache-2.0
-URL: https://github.com/intel/ipp-crypto
-Source0: %{url}/archive/%{srctag}/%{name}-%{srctag}.tar.gz
+URL: https://github.com/intel/cryptography-primitives
+Source0: %{url}/archive/v%{version}/%{name}-%{version}.tar.gz
# Upstream exclusively uses x86_64-specific intrinsics
-ExclusiveArch: x86_64
+ExclusiveArch: %{x86_64}
BuildRequires: cmake
BuildRequires: gcc
BuildRequires: gcc-c++
-BuildRequires: openssl-devel >= 1.1.0
+BuildRequires: openssl-devel >= 3.5.5
%description
%{desc}
@@ -47,15 +45,16 @@ Requires: %{name}%{?_isa} = %{version}-%{release}
Static library.
%prep
-%autosetup -n ipp-crypto-%{srctag}
-# library path fix
-sed -i 's/"lib\"/"lib64"/g' sources/ippcp/crypto_mb/src/CMakeLists.txt
+%autosetup -n cryptography-primitives-%{version}
+# library path fix and remove PRIVATE_HEADERs
+sed -i 's|MBX_LIB_INSTALL_DIR "lib"|MBX_LIB_INSTALL_DIR "lib64"|g' sources/ippcp/crypto_mb/src/CMakeLists.txt
+sed -i 's|PRIVATE_HEADER "${MBX_ONE_CPU_HEADERS}"|PRIVATE_HEADER ""|' sources/ippcp/crypto_mb/src/CMakeLists.txt
%build
pushd sources/ippcp/crypto_mb
%cmake \
- -DARCH=intel64 \
- -DMERGED_BLD:BOOL=off
+ -DCMAKE_BUILD_TYPE=Debug \
+ -DARCH=intel64
%cmake_build
popd
@@ -69,8 +68,8 @@ popd
%files
%license LICENSE
%doc sources/ippcp/crypto_mb/Readme.md
-%{_libdir}/libcrypto_mb.so.%{mbx_int_major}
-%{_libdir}/libcrypto_mb.so.%{mbx_int_major}.%{mbx_int_minor}
+%{_libdir}/libcrypto_mb.so.%{ipp_int_major}
+%{_libdir}/libcrypto_mb.so.%{ipp_int_major}.%{ipp_int_minor}
%files devel
%{_includedir}/crypto_mb
@@ -81,6 +80,9 @@ popd
%{_libdir}/libcrypto_mb.a
%changelog
+* Fri Jul 31 2026 Ali Erdinc Koroglu <aekoroglu@fedoraproject.org> - 2.3.0-1
+- Update to 2.3.0 (rhbz#2504142)
+
* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.10-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
diff --git a/sources b/sources
index 9771300..2533082 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (intel-ipp-crypto-mb-ippcp_2021.10.0.tar.gz) = f8da170d7e34effc306571b8633331a337c61650f141eb3424892e992fa330c458aa9629661705a0e3214a75e3dbfc6b7f3d4314647d783a40d8f71fb62b1306
+SHA512 (intel-ipp-crypto-mb-2.3.0.tar.gz) = fdae87aabf94c9308197a01b3d971aa38e750dc0d4333a5d7789106ea7103a0743d2217efd0c86980d4bafae039c728b00661e73b411e49d7c903f8b5c0cbe19
reply other threads:[~2026-07-31 13:15 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=178550371865.1.2307846888057372431.rpms-intel-ipp-crypto-mb-cda6a4dfbed6@fedoraproject.org \
--to=ali.koroglu@oss.qualcomm.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