Bug #9066: Use convertkey.py from the python-potr package

Bug #9066

Use convertkey.py from the python-potr package

Added by anonym 2015-03-17 09:23:20 . Updated 2015-07-03 03:41:59 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Test suite

Target version:

Tails_1.4.1

Start date:

2015-03-17

Due date:

% Done:

100%

Feature Branch:

test/9066-use-convertkey-from-Debian

Type of work:

Wait

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

We need Debian bug #780610 resolved. Then rewrite commit:eb4abc9 in test/9062-otr-bot-with-python-potr appropriately.

Subtasks

History

#1 Updated by intrigeri 2015-03-17 09:37:52

> * Target version: Tails_1.3.1

This won’t happen (in a way that allows us to actually use the updated package in our test suite) before 1. Jessie is released (so that jessie-backports opens its doors) and 2. ~~Feature #8165~~ is resolved. So it’s very unlikely that we have all that for 1.3.1.

=> please mark this as blocked by ~~Feature #8165~~, and adjust the target version accordingly. Hint: my current best bet is that Jessie will be out at some point in April.

#2 Updated by anonym 2015-03-17 11:43:21

Target version changed from Tails_1.3.2 to Tails_1.4

intrigeri wrote:
> > * Target version: Tails_1.3.1
>
> This won’t happen (in a way that allows us to actually use the updated package in our test suite) before 1. Jessie is released (so that jessie-backports opens its doors)

Is it because this is not an important bug enough to break the freeze?

> and 2. ~~Feature #8165~~ is resolved. So it’s very unlikely that we have all that for 1.3.1.
> => please mark this as blocked by ~~Feature #8165~~, and adjust the target version accordingly.

This I don’t understand. We have a temporary fix for the problem that works on both Wheezy (+ wheezy-backports) and Jessie, so how is it blocking ~~Feature #8165~~?

> Hint: my current best bet is that Jessie will be out at some point in April.

Woo! Setting the milestone to 1.4 (2015-05-19) then.

#3 Updated by intrigeri 2015-03-17 11:44:42

Subject changed from Include convertkey.sh in python-potr to Use convertkey.py from the python-potr package
Parent task deleted (~~~~Feature #9062~~~~)

This doesn’t block ~~Feature #9062~~ anymore, so reparenting.

#4 Updated by anonym 2015-03-17 11:46:43

anonym wrote:
> intrigeri wrote:
> > This won’t happen (in a way that allows us to actually use the updated package in our test suite) before 1. Jessie is released (so that jessie-backports opens its doors)
>
> Is it because this is not an important bug enough to break the freeze?

Forgot to ask: and since it’s a bug that even violates the package description, won’t the fix end up in Jessie’s python-potr?

#5 Updated by intrigeri 2015-03-17 11:48:35

>> This won’t happen (in a way that allows us to actually use the updated package in our test suite) before 1. Jessie is released (so that jessie-backports opens its doors)

> Is it because this is not an important bug enough to break the freeze?

Exactly.

>> and 2. ~~Feature #8165~~ is resolved. So it’s very unlikely that we have all that for 1.3.1. => please mark this as blocked by ~~Feature #8165~~, and adjust the target version accordingly.

> This I don’t understand. We have a temporary fix for the problem that works on both Wheezy (+ wheezy-backports) and Jessie, so how is it blocking ~~Feature #8165~~?

This is not blocking ~~Feature #8165~~, it is blocked by ~~Feature #8165~~ for the reasons stated above.

#6 Updated by intrigeri 2015-03-17 12:12:15

> Forgot to ask: and since it’s a bug that even violates the package description, won’t the fix end up in Jessie’s python-potr?

I strongly doubt it: I suspect this bug has been there since the initial package upload two years ago, and nobody complained about it. Now, of course it could be argued that violating the package’s description is RC, or that the package description being wrong is RC. Not sure it would work, and not sure it’s less work than maintaining a backport. It can also be argued that introducing a new script now may make the package more buggy than it currently is, in case the script itself is buggy.

In any case, I personally don’t feel like adding to the release team’s workload for that minor an issue, this late in the release process.

#7 Updated by intrigeri 2015-05-09 03:33:47

Assignee changed from anonym to intrigeri
Target version changed from Tails_1.4 to Tails_1.4.1
Type of work changed from Wait to Debian

Pinged on the Debian bug, proposing a solution + NMU. ETOOLAZY to create child tickets to track the status in Debian, and oh well, this should have been done initially anyway, so I won’t bother. I’ll reassign to anonym when it’s fixed in Debian, or when I get bored.