Github messages for voidlinux
 help / color / mirror / Atom feed
From: damadmai <damadmai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bitcoin: update to 22.0.
Date: Thu, 13 Jan 2022 14:51:09 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35027@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

There is a new pull request by damadmai against master on the void-packages repository

https://github.com/damadmai/void-packages bitcoin22.0
https://github.com/void-linux/void-packages/pull/35027

bitcoin: update to 22.0.
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)

Versioning schema changed 0.21.1 -> 22.0 see also https://bitcoin.org/en/version-history


A patch file from https://github.com/void-linux/void-packages/pull/35027.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bitcoin22.0-35027.patch --]
[-- Type: text/x-diff, Size: 1815 bytes --]

From 34867ceba73dc6114d39cd6937c7fa11a604fc2a Mon Sep 17 00:00:00 2001
From: "Daniel A. Maierhofer" <git@damadmai.at>
Date: Thu, 13 Jan 2022 14:45:31 +0100
Subject: [PATCH] bitcoin: update to 22.0.

---
 srcpkgs/bitcoin/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/bitcoin/template b/srcpkgs/bitcoin/template
index ed8800a1471a..ccc9c4cc5f10 100644
--- a/srcpkgs/bitcoin/template
+++ b/srcpkgs/bitcoin/template
@@ -1,6 +1,6 @@
 # Template file for 'bitcoin'
 pkgname=bitcoin
-version=0.21.0
+version=22.0
 revision=1
 build_style=gnu-configure
 configure_args="--with-incompatible-bdb --disable-ccache --disable-static
@@ -9,13 +9,13 @@ hostmakedepends="automake libtool pkg-config yasm"
 makedepends="db-devel boost-devel miniupnpc-devel qt5-tools-devel
  libevent-devel qrencode-devel libatomic-devel sqlite-devel"
 short_desc="Bitcoin is a peer-to-peer network based digital currency"
-maintainer="Orphaned <orphan@voidlinux.org>"
+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%.*}/debian/bitcoin-qt.desktop
+ https://raw.githubusercontent.com/bitcoin-core/packaging/${version%.*}.x/debian/bitcoin-qt.desktop
  https://raw.githubusercontent.com/bitcoin/bitcoin/v${version}/share/pixmaps/bitcoin128.png"
-checksum="1a91202c62ee49fb64d57a52b8d6d01cd392fffcbef257b573800f9289655f37
+checksum="d0e9d089b57048b1555efa7cd5a63a7ed042482045f6f33402b1df425bf9613b
  0a46bbadda140599e807be38999e6848c89f9c3523d26fede02d34d62d50f632
  ad880c8459ecfdb96abe6a4689af06bdd27906e0edcd39d0915482f2da91e722"
 conflicts="litecoin>=0" # Both provide libbitcoinconsensus.so.0

             reply	other threads:[~2022-01-13 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 13:51 damadmai [this message]
2022-01-13 19:35 ` [PR PATCH] [Merged]: " Piraty

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35027@inbox.vuxu.org \
    --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).