From: damadmai <damadmai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bitcoin: update to 25.0.
Date: Mon, 29 May 2023 11:29:51 +0200 [thread overview]
Message-ID: <20230529092951.U0sXZ7iaX_4HApXM-Kwrcnl3SuJA2cAz-JiQ0KtI6Pg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44133@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
There is an updated pull request by damadmai against master on the void-packages repository
https://github.com/damadmai/void-packages bitcoin25.0
https://github.com/void-linux/void-packages/pull/44133
bitcoin: update to 25.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/44133.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bitcoin25.0-44133.patch --]
[-- Type: text/x-diff, Size: 2096 bytes --]
From a4a494143f9918aff245caebf94c2d7f89a6fcbb Mon Sep 17 00:00:00 2001
From: "Daniel A. Maierhofer" <git@damadmai.at>
Date: Mon, 29 May 2023 10:29:12 +0200
Subject: [PATCH] bitcoin: update to 25.0.
---
srcpkgs/bitcoin/template | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/srcpkgs/bitcoin/template b/srcpkgs/bitcoin/template
index cf464ce35c46..9c4ab073d690 100644
--- a/srcpkgs/bitcoin/template
+++ b/srcpkgs/bitcoin/template
@@ -1,7 +1,7 @@
# Template file for 'bitcoin'
pkgname=bitcoin
-version=22.0
-revision=5
+version=25.0
+revision=1
build_style=gnu-configure
configure_args="--with-incompatible-bdb --disable-ccache --disable-static
--enable-hardening --with-boost=${XBPS_CROSS_BASE}/usr --with-gui"
@@ -11,11 +11,11 @@ makedepends="db-devel boost-devel miniupnpc-devel qt5-tools-devel
short_desc="Bitcoin is a peer-to-peer network based digital currency"
maintainer="Daniel A. Maierhofer <git@damadmai.at>"
license="MIT"
-homepage="https://bitcoin.org/"
-distfiles="https://bitcoin.org/bin/bitcoin-core-${version}/bitcoin-${version}.tar.gz
- https://raw.githubusercontent.com/bitcoin-core/packaging/${version%.*}.x/debian/bitcoin-qt.desktop
+homepage="https://bitcoincore.org/"
+distfiles="https://bitcoincore.org/bin/bitcoin-core-${version}/bitcoin-${version}.tar.gz
+ https://raw.githubusercontent.com/bitcoin-core/packaging/main/debian/bitcoin-qt.desktop
https://raw.githubusercontent.com/bitcoin/bitcoin/v${version}/share/pixmaps/bitcoin128.png"
-checksum="d0e9d089b57048b1555efa7cd5a63a7ed042482045f6f33402b1df425bf9613b
+checksum="5df67cf42ca3b9a0c38cdafec5bbb517da5b58d251f32c8d2a47511f9be1ebc2
0a46bbadda140599e807be38999e6848c89f9c3523d26fede02d34d62d50f632
ad880c8459ecfdb96abe6a4689af06bdd27906e0edcd39d0915482f2da91e722"
conflicts="litecoin>=0" # Both provide libbitcoinconsensus.so.0
@@ -42,10 +42,6 @@ pre_build() {
post_install() {
rm "${DESTDIR}"/usr/bin/{test,bench}_bitcoin
- for b in bitcoind bitcoin-cli bitcoin-tx; do
- vcompletion contrib/${b}.bash-completion bash $b
- done
-
vlicense COPYING
}
next prev parent reply other threads:[~2023-05-29 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 8:32 [PR PATCH] " damadmai
2023-05-29 9:29 ` damadmai [this message]
2023-05-29 16:54 ` [PR PATCH] [Updated] " damadmai
2023-05-29 17:36 ` damadmai
2023-06-26 20:07 ` [PR PATCH] [Closed]: " leahneukirchen
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=20230529092951.U0sXZ7iaX_4HApXM-Kwrcnl3SuJA2cAz-JiQ0KtI6Pg@z \
--to=damadmai@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).