public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Simone Caronni <negativo17@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/bitcoin-core] epel10.2: Update to 31.1
Date: Mon, 20 Jul 2026 13:12:10 GMT	[thread overview]
Message-ID: <178455313012.1.15779710514536328320.rpms-bitcoin-core-ee81a4e43311@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/bitcoin-core
Branch : epel10.2
Commit : ee81a4e43311d15fcaadea170dd891ce48106eda
Author : Simone Caronni <negativo17@gmail.com>
Date   : 2026-07-20T15:08:00+02:00
Stats  : +4/-5 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/bitcoin-core/c/ee81a4e43311d15fcaadea170dd891ce48106eda?branch=epel10.2

Log:
Update to 31.1

---
diff --git a/bitcoin-core.spec b/bitcoin-core.spec
index c5ae4d4..40e9907 100644
--- a/bitcoin-core.spec
+++ b/bitcoin-core.spec
@@ -5,7 +5,7 @@
 %bcond_with extended_tests
 
 Name:       bitcoin-core
-Version:    31.0
+Version:    31.1
 Release:    %autorelease
 Summary:    Peer to Peer Cryptographic Currency
 License:    MIT
@@ -164,7 +164,6 @@ grep -q $(sha256sum %{SOURCE0}) %{SOURCE2}
 cp -p %{SOURCE12} %{SOURCE13} %{SOURCE14} %{SOURCE15} .
 
 %build
-
 # Bitcoin kernel library used only as part of the testing for now:
 %cmake \
     -DBUILD_CLI=ON \

diff --git a/bitcoin-offline-pubring.gpg b/bitcoin-offline-pubring.gpg
index dd88283..c0183ab 100644
Binary files a/bitcoin-offline-pubring.gpg and b/bitcoin-offline-pubring.gpg differ

diff --git a/sources b/sources
index fac3e01..3123e96 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (bitcoin-31.0.tar.gz) = 3bfbd8155e56c165551af892d47846c92242ebfd70c11c61d7c7dfc457e51216b6ccabddd4eb5a3fe684eba7a69a306cc69767c8efe7bdc0eb19de1a7ddc5100
-SHA512 (SHA256SUMS) = 148292c9f362c98a01514904f28b8ad99d5d7caa1a5af795ab679462f84920170262d2ee355621d732dbb2518cb11869b02b481ba82d3e70066ea983fcb23a69
-SHA512 (SHA256SUMS.asc) = d58f6884a1115315ea7864d13ba6e2944f0ba95397861079e337bb3d9cbfe58da19a29d189cb41c59f8f3c04214ddbe350a7bd497dd17886f18cc081863fa304
+SHA512 (bitcoin-31.1.tar.gz) = df6c197f7290ba12be78f062e0a9f8750936b5ebe0078b93f18d7cf1e9f511f67e437b8cf12d2f57d26bc4ae71d112a071040a09344092bf587d973e76a0460f
+SHA512 (SHA256SUMS) = 0503c1ea78d0407261046622f3eed43e0e7be2818a4d3c71345fee708302533a921d620746d9bec323728282e0d2a5affbd212c3004bbed99c09bf3bbb3127df
+SHA512 (SHA256SUMS.asc) = f85b805d6a4ee43b50545b74167efabbef979339a0c18457ac817a01364f8042818d9a1ad8f4ae6c37a4a3579b1decad4f501969fa47c8715f2548bca136d62c

                 reply	other threads:[~2026-07-20 13:12 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=178455313012.1.15779710514536328320.rpms-bitcoin-core-ee81a4e43311@fedoraproject.org \
    --to=negativo17@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