public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Nicolas Chauvet <kwizart@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/cryptopp] rawhide: Update to 2026.8.1
Date: Wed, 05 Aug 2026 18:54:13 GMT	[thread overview]
Message-ID: <178595605354.1.11064601366565981424.rpms-cryptopp-9192320821f4@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/cryptopp
Branch : rawhide
Commit : 9192320821f4174c177cc3eace0757f035d8d809
Author : Nicolas Chauvet <kwizart@gmail.com>
Date   : 2026-08-05T20:53:56+02:00
Stats  : +3/-9 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/cryptopp/c/9192320821f4174c177cc3eace0757f035d8d809?branch=rawhide

Log:
Update to 2026.8.1

---
diff --git a/cryptopp.spec b/cryptopp.spec
index 8599d19..e45da85 100644
--- a/cryptopp.spec
+++ b/cryptopp.spec
@@ -5,7 +5,7 @@
 %global upstream_url https://github.com/cryptopp-modern/cryptopp-modern
 
 Name:           cryptopp
-Version:        2026.8.0
+Version:        2026.8.1
 Release:        %autorelease
 Summary:        C++ class library of cryptographic schemes
 License:        BSL-1.0
@@ -105,13 +105,7 @@ mv %{__cmake_builddir} build-shared
 mv build-static %{__cmake_builddir}
 
 %check
-# Disabled on s390x
-# https://github.com/cryptopp-modern/cryptopp-modern/issues/65
-%ifarch s390x
-%ctest  || :
-%else
 %ctest
-%endif
 
 
 %files

diff --git a/sources b/sources
index f2fb8ce..810ea47 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (cryptopp-modern-2026.8.0.tar.gz) = dc4825ccba024fcbf9204bba1ff02a278ad51aa79fced05b059268b138fe28a6e7c53c999a874c970a384571111061f299477e86a73e7f25975be6c20273256a
-SHA512 (cryptopp-modern-2026.8.0.tar.gz.sig) = a88923f9b59178e8abfa8d0d732b17fcd25916c48b686db41cd7732896825165238833f7a11a152d775d5f5511cae9c0c012babc596d28014814defe29ea179e
+SHA512 (cryptopp-modern-2026.8.1.tar.gz) = 87c05dc60259531e938c4a950f6a0244cbc9f1a6c5c523493cc999c16d49a9cd45a9e6e4ded517431b41f20ee83e8f5b5cd3e7e2895a4ba16126a576bbde5d92
+SHA512 (cryptopp-modern-2026.8.1.tar.gz.sig) = f5f3d46f99cd18b76e786e3cbe4a3b63565cb167479fe59c1a6bd99ec67086a47007a082704a42687953960638cff6210c490b504a3ced22386c7d2ef9b0b10f
 SHA512 (gpgkey-CoraleSoft-844DCFC44A5DE9C14C3A2F62497A4CFBB700543E.gpg) = 33400c97bbad66de7f6874018f523c2cc1328dcde2dad1171262f5647d2796d119e664c8ebce89da2b209a1be58caff6dbdd88dbaecfbe9c71b242f031832705

                 reply	other threads:[~2026-08-05 18:54 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=178595605354.1.11064601366565981424.rpms-cryptopp-9192320821f4@fedoraproject.org \
    --to=kwizart@gmail.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