Running electrum-ltc after emerging it without additional masks breaks the program. It doesn't seem to be compatible with libsecp256k1-0.4.0 which is the latest, unkeyworded release of the lib (at the time of writing). This release ships version libsecp256k1.so.2 instead of libsecp256k1.so.0. When I manually mask >=dev-libs/libsecp256k1-0.2.0 and re-emerge the lib it works again. The correct version libsecp256k1.so.0 will then be built via dev-libs/libsecp256k1-0.1_pre20201028-r1:0/0::gentoo. So perhaps the dependency spec of dev-libs/libsecp256k1 should be restricted accordingly. $ electrum-ltc Error: Failed to load libsecp256k1. E | ecc_fast | libsecp256k1 library failed to load. exceptions: [OSError('/usr/lib/python3.11/site-packages/electrum_ltc/libsecp256k1.so.0: cannot open shared object file: No such file or directory'), OSError('libsecp256k1.so.0: cannot open shared object file: No such file or directory')]
Created attachment 899843 [details, diff] Depend on the correct subslot of libsecp256k1 Here is a patch that I tested locally. It implements my proposed solution of pulling in the correct subslot (libsecp256k1:0/0).
I'm inclined to say WONTFIX, as Electrum LTC has not seen a release in more than two years, and dev-libs/libsecp256k1-0.4.0 is soon to be stabilized, after which all pre-release versions will be dropped from the tree. In any case, I respectfully decline to spend any of my time on altcoins.
