spotmg.blogg.se

1. #Tails electrum 3.1.3 not connected install
2. #Tails electrum 3.1.3 not connected update
3. #Tails electrum 3.1.3 not connected software
4. #Tails electrum 3.1.3 not connected iso

Wallet can be recovered from a secret phrase. Losing coins in a backup mistake or computer failure, because your Maintainer: Port Added: 11:29:37 Last Update: 05:38:34 Commit Hash: 2bef34f Also Listed In: python License: MIT Description: Electrum is an easy to use Bitcoin client. Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15) All times are UTCĤ.4.3 finance =0 Version of this port present on the latest quarterly branch. If this is a controversial move, then we can at least delay shipping the updated config until Electrum is updated via stretch-backports.FreshPorts - finance/electrum: Easy to use Bitcoin clientĪs an Amazon Associate I earn from qualifying purchases. I wasn’t trying to add cutting edge features, but rather I was trying to clean up the config file which requires Electrum 3.1.1. Again, I don’t see “missing cutting edge features” = “bug”. > When there’s a bug or regression that makes the version shipped in Tails useless, the new Electrum version that fixes is will be in stable-backports so we should never get there.

#Tails electrum 3.1.3 not connected software

I could be wrong, but I have found backported software to significantly lag behind testing/unstable. This is more closer and in concordance to Tails ~6 weeks estimated release life.

#Tails electrum 3.1.3 not connected update

Also, every Electrum update in unstable will make it to stable-backports after the required time passes. Installing from stable-backports however ensures it is properly install-able. Installing from unstable might not be the best move. When there’s a bug or regression that makes the version shipped in Tails useless, the new Electrum version that fixes is will be in stable-backports so we should never get there. If we take this approach, we might never catch up.

#Tails electrum 3.1.3 not connected install

These will obviously be supported as they come to stable-backports, but until then users that want cutting edge features should take some time to install themselves the preferred version that support them. It is not mandatory to support all cutting edge features of this wallet and support each and every hardware wallet, to its last version. should not have security bugs, or other severe bugs which could affect user’s funds or security should be fully usuable (send, receive, sync with the network)

We go for the idea that Electrum is to be shipped with Tails and:

Then users who want to use Electrum will need to add it to their list of ASP and they’ll have the same UX as currently, except they’ll always be running the latest version (from the Debian dist our APT pinning prefers, which one is best can be discussed from a different perspective once it’s not about a version that’s frozen in an ISO) as you say they should be. keep shipping sane APT pinning, default configuration, and persistence preset to make Tails+Electrum’s life easier.Fine, once we have much improved Additional Software Packages in Tails 3.9 ( Feature #14568) we should then: If I understand this argument correctly, it basically implies that the Electrum software is not suitable for being included in an OS image that’s released every ~6 weeks.

#Tails electrum 3.1.3 not connected iso

So it seems to me that your argument implies the following: any version of Electrum we include in a Tails ISO will be too old and unusable at some point. The lifetime of a Tails release (~6 weeks) is much greater than how long stretch-backports lags behind testing/sid (ideally: 5 days in practice, probably a bit longer). At some point Electrum will be unusable because the backported version is too old. I think that there is more risk of regressions and maintenance costs for keeping an older version of Electrum.