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] epel9: Update to 30.3
Date: Mon, 20 Jul 2026 13:11:45 GMT	[thread overview]
Message-ID: <178455310568.1.5282466145379532373.rpms-bitcoin-core-e86163e7ac47@fedoraproject.org> (raw)

A new commit has been pushed.

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

Log:
Update to 30.3

---
diff --git a/bitcoin-core.spec b/bitcoin-core.spec
index 2d559fa..673bf21 100644
--- a/bitcoin-core.spec
+++ b/bitcoin-core.spec
@@ -5,7 +5,7 @@
 %bcond_with extended_tests
 
 Name:       bitcoin-core
-Version:    30.2
+Version:    30.3
 Release:    %autorelease
 Summary:    Peer to Peer Cryptographic Currency
 License:    MIT

diff --git a/bitcoin-offline-pubring.gpg b/bitcoin-offline-pubring.gpg
index c104426..7d3b71b 100644
Binary files a/bitcoin-offline-pubring.gpg and b/bitcoin-offline-pubring.gpg differ

diff --git a/sources b/sources
index 4680f74..f2ab27b 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (bitcoin-30.2.tar.gz) = 4fcdb70a016f9ad1b44539f19d61d4c9ce06d92f947be156f8d5de29026aa90a17cea8dcd0bd9bf2f7ad959a4b79d851de95a1c0d2ab87862e04c26cf89f493b
-SHA512 (SHA256SUMS) = 99df424cfe37197df15c3e12890ba0b3e9fa00d75f4466f36e220d5d9a361c472d140ce9e7e050181e2a41d39f1af6f0c8fe87e1db9bea7a2fc6000b228aed12
-SHA512 (SHA256SUMS.asc) = 1bb28324b7807eaf8bd828039954698cfdbb4ac79ae09a58f84f798ed9da1178ce57459fd7586e51ab514983531045b2a33a28361e4ba302c5527104d0474d53
+SHA512 (bitcoin-30.3.tar.gz) = 507fa14bcaaac391fbb223c5379e46f6cb9a34f1a538e447d83facb78715fa52c53fb2dab0238059940d38c9b4bb2e5392e198c9fa90772e6b406eaa91df5437
+SHA512 (SHA256SUMS) = 015da34cdc6a2c33da3c829df0172b267fb5ff28b239f796ed26c8339b6ec0276f6ec4fb42e3f1de3f8eb8e05f9388ac0ab305bdf18177bb33510ea8ce1d29e6
+SHA512 (SHA256SUMS.asc) = 62dc69f23f722c625406b2c4c3ef02f0eeef1c5a7b9261727baf25803ec668824e10e1d3a72ac9cc320d8ed0c454374c24498884d12be6f2a114ceb2c49fe2c7

                 reply	other threads:[~2026-07-20 13:11 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=178455310568.1.5282466145379532373.rpms-bitcoin-core-e86163e7ac47@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