Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Update Electrum to 4.0.9
Date: Wed, 24 Mar 2021 22:17:34 +0100	[thread overview]
Message-ID: <20210324211734.t_vMyDnQeE5Qhqp5mbjgI8Wu4FvkISmjUqVD-dmjRSo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28305@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

Update Electrum to 4.0.9
https://github.com/void-linux/void-packages/pull/28305

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->

#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl


~This depends on #28272.~

~Using package [libbitcoin-secp256k1](https://github.com/void-linux/void-packages/tree/master/srcpkgs/libbitcoin-secp256k1) as dependency might be possible, but: it is based on this release: https://github.com/libbitcoin/secp256k1/releases/tag/v0.1.0.13 with the last commit included dating to December 2016. Electrum currently [uses](https://github.com/spesmilo/electrum/blob/master/contrib/make_libsecp256k1.sh) a commit from from June 2020 from https://github.com/bitcoin-core/secp256k1.~

--> The old version of `libbitcoin-secp256k1` in Void's repos is is sufficient for now, as per [this Electrum issue](https://github.com/spesmilo/electrum/issues/7014): `if the tests pass, it is considered good enough.`

New dependencies:

    python3-socks-1.2.0
    python3-curio-1.4
    python3-trio-0.18.0
    python3-outcome-1.1.0
    python3-sniffio-1.2.0
    python3-bitstring-3.1.7

Updated dependencies:

    python3-aiohttp_socks: update to 0.5.5.
    python3-dnspython: update to 2.1.0. 

So this is ready; also tested locally.

      parent reply	other threads:[~2021-03-24 21:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 16:42 [PR PATCH] [WIP] " ar-jan
2021-01-29 16:48 ` [PR PATCH] [Updated] " ar-jan
2021-02-01 23:48 ` ar-jan
2021-02-02  0:16 ` ar-jan
2021-02-08 21:48 ` ar-jan
2021-02-10  0:37 ` atweiden
2021-02-10  0:43 ` ar-jan
2021-02-21 18:25 ` [PR PATCH] [Updated] " ar-jan
2021-02-21 19:02 ` ar-jan
2021-02-22 10:20 ` ar-jan
2021-03-08 18:05 ` ar-jan
2021-03-08 18:36 ` ar-jan
2021-03-08 20:26 ` ar-jan
2021-03-08 21:55 ` [PR PATCH] [Updated] " ar-jan
2021-03-08 22:35 ` ar-jan
2021-03-08 23:27 ` [PR PATCH] [Updated] " ar-jan
2021-03-08 23:41 ` ericonr
2021-03-08 23:45 ` ar-jan
2021-03-09  0:18 ` ericonr
2021-03-09  0:34 ` [PR PATCH] [Updated] " ar-jan
2021-03-09  0:47 ` ar-jan
2021-03-09  7:06 ` [PR REVIEW] " ericonr
2021-03-09  7:06 ` ericonr
2021-03-09  7:06 ` ericonr
2021-03-09  7:06 ` ericonr
2021-03-09  7:08 ` ericonr
2021-03-15 19:25 ` ar-jan
2021-03-24 18:56 ` [PR REVIEW] " ericonr
2021-03-24 18:56 ` ericonr
2021-03-24 21:01 ` [PR PATCH] [Updated] " ar-jan
2021-03-24 21:04 ` [PR REVIEW] " ar-jan
2021-03-24 21:14 ` ar-jan
2021-03-24 21:17 ` ericonr [this message]

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=20210324211734.t_vMyDnQeE5Qhqp5mbjgI8Wu4FvkISmjUqVD-dmjRSo@z \
    --to=ericonr@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).