Since bug 867817 was fixed, it is no longer possible to install both Electrum and the current version of bitcoind and/or bitcoin-qt through Portage: the former depends on <dev-libs/libsecp256k1-0.2, while the latter depends on >=dev-libs/libsecp256k1-0.2.0. Electrum and bitcoind (and a local Electrum server, but I don't think there's one in Gentoo) are a desirable combination for those of us who want the enhanced privacy of running our own node while not being stuck with the Core wallet and GUI. Downgrading bitcoind is a possible workaround, but surely it's best to keep it up to date if possible. Or Electrum could be installed outside Portage, along with a suitable version of libsecp256k1 just for it. I hope this whole mess can be resolved soon, whatever solution the maintainers decide on.
We should either allow using bundled libsecp in bitcoin or see if there's a report at least upstream wrt Electrum (if we can't safely patch Electrum to work with newer libsecp).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=033942e7fc7943c2812beee8d3f30a8ab5c5f83a commit 033942e7fc7943c2812beee8d3f30a8ab5c5f83a Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2023-05-09 15:38:36 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2023-05-09 15:53:05 +0000 net-misc/electrum: Allow <libsecp256k1-0.4 Closes: https://bugs.gentoo.org/905984 Closes: https://bugs.gentoo.org/893250 Signed-off-by: Michał Górny <mgorny@gentoo.org> net-misc/electrum/{electrum-4.4.2.ebuild => electrum-4.4.2-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
