From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Update Electrum to 4.0.9
Date: Mon, 08 Feb 2021 22:48:10 +0100 [thread overview]
Message-ID: <20210208214810.pkztDM6_oNLOCjF6qr3UbTgVHaD5l5NocK2XJuISers@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: 675 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/pull/28305#issuecomment-775485651
Comment:
Hi @atweiden, @CameronNemo, I was wondering if either of you has a suggestion for how to provide an update to `libsecp256k1` for Void (as maintainer and user of the library respectively). ElectronCash uses the package that's currently in Void, which is based on a very old version of `libbitcoin/secp256k1`.
Electrum 4.x uses a more recent version based on `bitcoin-core/secp256k1`, which is also the upstream repo for libbitcoin/secp256k1. I've updated Electrum but I still need a way to provide a more recent version of the library.
next prev parent reply other threads:[~2021-02-08 21:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 16:42 [PR PATCH] " 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 [this message]
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 ` [PR PATCH] [Merged]: " ericonr
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=20210208214810.pkztDM6_oNLOCjF6qr3UbTgVHaD5l5NocK2XJuISers@z \
--to=ar-jan@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).