Re: [Tails-dev] Help needed: Electrum in Debian → Tails

Delete this message

Reply to this message
Autor: intrigeri
Data:  
A: The Tails public development discussion list
Assumpte: Re: [Tails-dev] Help needed: Electrum in Debian → Tails
Hi,

s7r:
> intrigeri wrote:
>> s7r:


> Done. I explained there what we are waiting for:
> https://labs.riseup.net/code/issues/15022


Thanks!

>> Shall we add you as a watcher for all tickets related to Electrum?


> Yes, please. I should be able to provide relevant information and
> clarifications in such cases.


I just did that and I've added Electrum to the "Affected tool"
drop-down list so it's easy to list all these tickets.

>> A backport can be uploaded (and all such uploads will be automatically
>> accepted once a first one has been manually accepted to a given suite)
>> as soon as the package reaches Debian testing, so installing from
>> backports does not add any relevant delay, except in the rare case
>> when the timing of the migration to testing conflicts in the worst
>> possible way with the Tails freeze schedule.
>>
>> Installing from Debian testing can definitely be a sane short-term
>> option *but* this is brittle and can't be relied upon on the long
>> term: at some point it's likely that the package from testing becomes
>> uninstallable on stable due to new/updated versioned dependencies.
>> So we install packages from testing only when we can be fully certain
>> that whenever this happens, someone starts maintaining a backport
>> immediately. I would recommend they start doing it now.


> Ok. Will work on this.


Great :)

On the ticket you wrote "We will include 3.0.2 in the first Tails
release after it lands in testing". I've replaced "in testing" with
"in stretch-backports" to encode more clearly the way forward
I'm proposing.

Note that this update might not be suitable for a bugfix release (that
we release no RC for): we'll need to balance risk of regressions vs.
urgency of supporting SegWit.

>> Are you also interested in maintaining the Electrum integration into
>> Tails (e.g. taking care of whatever needs to be done on incompatible
>> config updates and similar Tails-specific glue)? If you want to commit
>> to this, at some point we should probably add you as the point of
>> contact for Electrum matters on
>> https://tails.boum.org/contribute/#mentors :)


> I can do that. Been replying to emails with questions for this for some
> time now. Just for the record, I don't have commit access upstream, but
> I think I could fix Tails-specific needs because it's a big user base
> that uses this additional software package and also because the main
> developer and entire upstream community takes security and privacy very
> very seriously, just like we do, that is why I support this being
> included in Tails.


Good. Note that Electrum is currently shipped in Tails by default,
and "Additional Software Packages" in the Tails context refers to
a different feature:

https://tails.boum.org/doc/first_steps/persistence/configure/#additional_software

:)

Cheers,
--
intrigeri