Tails

#1 Updated by intrigeri 2018-03-09 08:30:20

• related to Feature #15022: Electrum package update to version 3.0.6 added

#2 Updated by intrigeri 2018-03-23 06:46:04

• related to Bug #15189: Figure out what to do with optional Electrum dependencies on Buster added

#5 Updated by intrigeri 2018-03-26 08:21:37

• Type of work changed from Debian to Discuss

> python3-trezor will be in stable-backports in few days,

Great! So users who need it can install it themselves :)

> so TREZOR hardware wallet support will remain functional.

… once someone does the Tails part of the work that is one of:

• either wait for our next major release (3.9), that will use newer snapshots of the Debian archive which include python3-trezor; and then one “just” needs to add that package to the list of packages we install in the ISO;
• or speed this up using our freeze exception mechanism (requires upload rights to our custom APT repo so that would be for anonym);
• or forget it because in 3.9 we’ll have a much improved “Additional Software Packages” feature: if we stop including python3-trezor by default, the few users who need it will be able to install it easily. We could document this in wiki/src/doc/anonymous_internet/electrum.mdwn and be done with it.

AFAIK nobody complained about this regression so I’m in favour of the last option.
What do you think?

#8 Updated by intrigeri 2018-04-10 08:52:40

• Type of work changed from Discuss to Debian

>> * or forget it because in 3.9 we’ll have a much improved “Additional Software Packages” feature: if we stop including python3-trezor by default, the few users who need it will be able to install it easily. We could document this in wiki/src/doc/anonymous_internet/electrum.mdwn and be done with it.

>> AFAIK nobody complained about this regression so I’m in favour of the last option.

For the record: goupille forwarded us one such complain and that’s not enough to make me change my mind.

>> What do you think?

> I agree. I am in favour of the last option as well.

OK. So, next steps to fix this regression are:

1. ensure python3-trezor and its dependencies are available in stretch-backports by August 10
2. tell sajolida what he should document (presumably it will boil down to “install python3-trezor and agree to make it persistent”), reassign to him and set “Type of work: End-user documentation”

Technically we should set “Target version: Tails_3.9” now. Please do so unless having it on your 3.7 radar helps you keep track of the first step that’s on your plate.

> python3-trezor and other lower level dependencies like python-mnemonic and python-hidapi need to be fixed at Debian package level as proper dependencies. I don’t see it as a Tails related issue.

python3-trezor depends on python3-mnemonic and python3-hid already so we’re good.

#9 Updated by intrigeri 2018-04-14 08:04:39

• Status changed from Confirmed to In Progress

Applied in changeset commit:da2910ba48bc0b30d2608244bde205dfc1128212.

#10 Updated by intrigeri 2018-04-14 09:53:29

• Status changed from In Progress to Confirmed

#11 Updated by bertagaz 2018-05-10 11:09:32

• Target version changed from Tails_3.7 to Tails_3.8

#12 Updated by intrigeri 2018-06-26 16:28:05

• Target version changed from Tails_3.8 to Tails_3.9

#13 Updated by Anonymous 2018-08-16 11:24:55

• Assignee changed from s7r to intrigeri
• QA Check set to Info Needed
• Type of work changed from Debian to End-user documentation

Please tell sajolida what he should document (presumably it will boil down to “install python3-trezor and agree to make it persistent”), reassign to him and set “Type of work: End-user documentation”.

#14 Updated by intrigeri 2018-08-16 16:36:19

• Assignee changed from intrigeri to s7r

> Please tell sajolida what he should document (presumably it will boil down to “install python3-trezor and agree to make it persistent”), reassign to him and set “Type of work: End-user documentation”.

Yes, s7r, please do so.

u: we’ve kept Electrum in Tails only because s7r volunteered to do this kind of work. I never committed to do it myself.

#16 Updated by intrigeri 2018-09-03 09:40:07

• Target version changed from Tails_3.9 to Tails_3.10.1
• QA Check changed from Info Needed to Dev Needed
• Type of work changed from End-user documentation to Debian

> I can get python3-trezor and its dependencies in strectch-backports, but is this our plan?

My understanding of the past discussion here is that this has been the plan since Bug #15390#note-4.

> What I mean is, there are many hardware wallets out there and it’s best for Tails to just support Electrum and document that hardware wallets need additional packages that need to be in stable-backports, otherwise we can’t do anything about it.

I agree. I’m in favor of not reincluding TREZOR support in Tails and instead fix this regression by having the necessary packages in stretch-backports + document how to add it via Additional Software Packages, as I proposed 5 months ago. That is, what we agreed on 5 months ago already. Next step is still the same: get python3-trezor in stretch-backports.

> intrigeri, what do you think we should do here, considering I can politely ask our Debian package maintainer to add / keep maintained some packages we are interested in for Tails, but the longer this list becomes the harder for everyone.

Sure. Thankfully we won’t need this backport anymore once Tails 4.0 (based on Buster) is out, presumably mid-2019. And then I’ll be much more careful when someone suggests we track Electrum from backports: given how it went so far in Tails 3.x (regression introduced 5 months ago, deadlines made clear months in advance, no progress so far and the deadline is now behind us), for Tails 4.x I’m inclined to stick to whatever version is included in Debian Buster, and whatever needs to be fixed in order to keep it working will have to be done via Debian stable updates. And if nothing else works smoothly enough, we can stop including Electrum, ship a working config + persistence settings, and document how to install it with Additional Software Packages.

#18 Updated by intrigeri 2018-10-24 17:03:45

• Target version changed from Tails_3.10.1 to Tails_3.11

#19 Updated by CyrilBrulebois 2018-12-16 14:05:45

• Target version changed from Tails_3.11 to Tails_3.12

#20 Updated by anonym 2019-01-30 11:59:29

• Target version changed from Tails_3.12 to Tails_3.13

#22 Updated by CyrilBrulebois 2019-03-20 14:34:09

• Target version changed from Tails_3.13 to Tails_3.14

#23 Updated by CyrilBrulebois 2019-05-23 21:23:26

• Target version changed from Tails_3.14 to Tails_3.15

#24 Updated by CyrilBrulebois 2019-07-10 10:34:04

• Target version changed from Tails_3.15 to Tails_3.16

#25 Updated by intrigeri 2019-08-30 17:09:48

• Target version deleted (Tails_3.16)

Hi!

We’ve set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

• better reflect your plans;
• bring down your amount of work-in-progress to a sustainable level;
• encourage team work and increase the chances that someone finishes the work;
• avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

• Stalled work-in-progress
• Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on Feature #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I’m doing on this ticket.

You now have a few options, such as:

• Deassign yourself. That’s fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
• If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable “Target version”. This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today’s choice.

Cheers!

#26 Updated by intrigeri 2019-09-08 06:34:09

• Status changed from Confirmed to Resolved
• Type of work changed from Debian to Code

python3-trezor is included in Tails 4.0~beta2 so this should now be fixed.