Github messages for voidlinux
 help / color / mirror / Atom feed
From: nbelikov <nbelikov@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] electrum: update to 4.3.2.
Date: Sat, 12 Nov 2022 11:21:12 +0100	[thread overview]
Message-ID: <20221112102112.ounQoAP9rqLVNN-Ss0VqpZ4_ftrGJd4uHydJSdy1kEM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40229@inbox.vuxu.org>

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

There is an updated pull request by nbelikov against master on the void-packages repository

https://github.com/nbelikov/void-packages electrum
https://github.com/void-linux/void-packages/pull/40229

electrum: update to 4.3.2.
#### Testing the changes
- I tested the changes in this PR: **briefly**

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

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

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

From ae23b065d641f1a297583a729fd3ad952bdf1a97 Mon Sep 17 00:00:00 2001
From: Nikolay Belikov <nb@nbelikov.com>
Date: Sun, 30 Oct 2022 17:42:32 +0300
Subject: [PATCH] electrum: update to 4.3.2.

---
 srcpkgs/electrum/template | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/electrum/template b/srcpkgs/electrum/template
index dcabed755423..d68ac6c75bc6 100644
--- a/srcpkgs/electrum/template
+++ b/srcpkgs/electrum/template
@@ -1,26 +1,25 @@
 # Template file for 'electrum'
 pkgname=electrum
-version=4.2.0
-revision=3
+version=4.3.2
+revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools python3-PyQt5-devel-tools"
 depends="python3-aiohttp python3-aiohttp_socks python3-aiorpcx
- python3-bitstring python3-dnspython python3-ecdsa python3-jsonrpclib
- python3-protobuf python3-pyaes python3-pycryptodomex python3-PyQt5
- python3-qrcode python3-socks python3-cryptography libbitcoin-secp256k1
- python3-certifi"
+ python3-bitstring python3-dnspython python3-protobuf python3-PyQt5
+ python3-qrcode python3-cryptography libbitcoin-secp256k1 python3-certifi
+ libzbar"
 # Optional dependencies:
 #  btchip - BTChip hardware wallet support
 #  trezor - TREZOR hardware wallet support
 #  keepkey - KeepKey hardware wallet support
 #  qdarkstyle - Dark theme
-checkdepends="$depends python3-pytest"
+checkdepends="${depends} python3-pytest python3-pyaes python3-pycryptodomex"
 short_desc="Lightweight Bitcoin wallet"
 maintainer="Charles E. Lehner <cel@celehner.com>"
 license="MIT"
 homepage="https://electrum.org/"
 distfiles="https://github.com/spesmilo/electrum/archive/${version}.tar.gz"
-checksum=3a24c7ed7a2bb47888f308380b8624a3fff3cf3882fd63d904cd9c3ec543fb3b
+checksum=af126f44ccbfbb302695087a70431d7c764b4d487863e8272f0aa88fccf1bacf
 
 post_install() {
 	vsed -i -e 's|electrum %u|electrum|' \

  parent reply	other threads:[~2022-11-12 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 14:45 [PR PATCH] " nbelikov
2022-11-12  9:25 ` ar-jan
2022-11-12 10:21 ` nbelikov [this message]
2023-01-15 23:49 ` gch1p
2023-02-02 19:23 ` [PR PATCH] [Closed]: " nbelikov

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=20221112102112.ounQoAP9rqLVNN-Ss0VqpZ4_ftrGJd4uHydJSdy1kEM@z \
    --to=nbelikov@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).