The current version of electrum through the Fedora 31 repository is electrum-3.3.4-3.fc31. According to upstream (https://download.electrum.org/?C=M;O=D), that came out ~11 months ago. Would like to see the latest (3.3.8) released as an update to Fedora 31.
It is applicable to the Fedora 32 and rawhide as well. Fedora is the only distribution that didn't update Electrum: https://repology.org/project/electrum/versions
What have been holding back the upgrade have been this requirement: > aiorpcx>=0.18,<0.19 Fedora are still on 0.11 https://src.fedoraproject.org/rpms/python-aiorpcx
I have built 4.0.2 for rawhide and soon Fedora 32. The update needs to be in sync with several other libraries.
We need a newer version of python-aiohttp-socks. See bug 1785253.
Latest version available is 4.0.3 now. Also please note, that old Electrum versions are susceptible to phishing: https://github.com/spesmilo/electrum/issues/4968 # Release 4.0.3 - (Sep 11, 2020) * PSBT: restore compatibility with Bitcoin Core following CVE-2020-14199: we now allow a PSBT input to have both UTXO and WITNESS_UTXO (#6429). (PSBTs created since 4.0.1 already contained UTXO for segwit inputs) * Hardware wallets: - bitbox02: better multisig UX: implement get_soft_device_id (#6386) - coldcard: fix "show address" for multisig (#6517) - all: run all device communication on a dedicated thread (#6561). This should resolve some threading issues. * new feature: "Automated BIP39 recovery" (#6219, #6155) When restoring from a BIP39 seed, add option to scan many known derivation paths for history, and show them to user to choose from. * show derivation path of keystores in Qt GUI Wallet>Information (#4700) * fix "signtransaction" RPC command (#6502) * Dependencies: pyaes is no longer needed (#6563) * The tar.gz source dist now bundles make_libsecp256k1.sh, to help users getting libsecp256k1 (#6323). * A few other minor bugfixes and usability improvements.
Latest version is 4.0.4 now https://github.com/spesmilo/electrum/releases/tag/4.0.4 # Release 4.0.4 - (Oct 15, 2020) * PSBT: fix regression in 4.0.3 where UTXO data was not included in QR codes (#6600) * new feature: "Cancel tx" (#6641). The Qt/kivy GUI allows cancelling an unconfirmed RBF tx by double-spending its inputs to self. * Ledger: fix "The derivation path is unusual" warnings (#6512) (needs Bitcoin app 1.4.8+ installed on device) * A few other minor bugfixes and usability improvements.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.