Feature #10285

Add Icedove (and its related packages) to Tails

Added by kytv 2015-09-27 06:01:28 . Updated 2015-11-03 11:29:53 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.7
Start date:
2015-09-27
Due date:
% Done:

100%

Feature Branch:
kytv:feature/5663-return-to-icedove
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

Subtasks

Related issues

Blocks Tails - Bug #9821: Torbirdy uses Arabic as a default locale Resolved 2015-07-30

History

#1 Updated by kytv 2015-09-27 06:01:55

#2 Updated by kytv 2015-09-27 06:02:50

  • blocks Bug #9821: Torbirdy uses Arabic as a default locale added

#3 Updated by kytv 2015-09-27 06:10:38

  • % Done changed from 0 to 30
  • Feature Branch set to kytv:feature/10285-add-icedove-to-Tails

#4 Updated by intrigeri 2015-09-28 02:08:37

  • blocks #8668 added

#5 Updated by intrigeri 2015-09-28 02:09:04

> Feature Branch set to kytv:feature/10285-add-icedove-to-Tails

I don’t think we’ll want a branch per sub-task of Feature #5663, so please instead call your branch feature/5663-icedove (and consider basing it on the existing feature/icedove, if not done yet).

#6 Updated by kytv 2015-10-02 09:32:14

  • Feature Branch deleted (kytv:feature/10285-add-icedove-to-Tails)

#7 Updated by kytv 2015-10-02 09:36:46

intrigeri wrote:
> > Feature Branch set to kytv:feature/10285-add-icedove-to-Tails
>
> I don’t think we’ll want a branch per sub-task of Feature #5663, so please instead call your branch feature/5663-icedove (and consider basing it on the existing feature/icedove, if not done yet).

I hadn’t done that but will do so now. Building another ISO to test against the newly rebased against feature/icedove branch.

#8 Updated by kytv 2015-10-03 02:48:23

  • Assignee changed from kytv to anonym
  • QA Check set to Ready for QA
  • Feature Branch set to kytv:feature/5663-return-to-icedove

#9 Updated by anonym 2015-10-05 01:46:28

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Dev Needed

#10 Updated by kytv 2015-10-05 02:32:32

  • QA Check changed from Dev Needed to Ready for QA

#11 Updated by kytv 2015-10-05 02:35:45

  • Assignee changed from kytv to anonym

#12 Updated by intrigeri 2015-10-05 15:12:31

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Info Needed

Any reason to fetch xul-ext-torbirdy from sid? So far, the same version is in Jessie and Stretch.

#13 Updated by sajolida 2015-10-07 08:17:13

Maybe kytv got this from my setup where I have xul-ext-torbirdy/sid. But yes, apparently xul-ext-torbirdy/jessie is installable as well.

#14 Updated by kytv 2015-10-07 16:32:28

  • Assignee changed from kytv to anonym
  • QA Check changed from Info Needed to Ready for QA

intrigeri wrote:
> Any reason to fetch xul-ext-torbirdy from sid? So far, the same version is in Jessie and Stretch.

I don’t remember why I went with that back in July. I’ve dropped it to testing.

#15 Updated by anonym 2015-10-08 05:29:27

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Info Needed

kytv wrote:
> intrigeri wrote:
> > Any reason to fetch xul-ext-torbirdy from sid? So far, the same version is in Jessie and Stretch.
>
> I don’t remember why I went with that back in July. I’ve dropped it to testing.

I’m a bit unsure which source is best. It seems to me that, in general, we should prefer:

  • stable releases > sid, for stability reasons, e.g. no sudden build breaking packages due to deps that only work in sid, or just broken packages that were uploaded prematurely.
  • stable releases (and sid) > testing, since the latter has a delay for security upgrades.

So the winner seems to be a stable release, i.e. Jessie in this case. Thoughts?

#16 Updated by intrigeri 2015-10-12 05:43:33

> * stable releases (and sid) > testing, since the latter has a delay for security upgrades.

JFTR, I have concerns with fetching stuff from testing > sid until we get freezable APT repo (because it can break stuff unexpectedly at the worst possible time in a release cycle), but we’ll get that piece of infra soon enough, so I agree.

#17 Updated by anonym 2015-10-22 08:08:14

intrigeri wrote:
> > * stable releases (and sid) > testing, since the latter has a delay for security upgrades.
>
> JFTR, I have concerns with fetching stuff from testing > sid until we get freezable APT repo (because it can break stuff unexpectedly at the worst possible time in a release cycle), but we’ll get that piece of infra soon enough, so I agree.

Good. This was fixed in commit commit:602793b. But I apparently b0rked it with a commit commit:c40f1b3. I decided to just build a backport and upload it to our APT repo for now, so there will be no surprises. That’s commit commit:53e4b33.

I think we’re good on this ticket now.

#18 Updated by kytv 2015-10-26 03:06:48

  • QA Check changed from Info Needed to Ready for QA

#19 Updated by kytv 2015-10-26 03:13:09

  • Assignee changed from kytv to anonym

#20 Updated by anonym 2015-10-26 13:01:11

  • Status changed from In Progress to Fix committed
  • % Done changed from 30 to 100

Applied in changeset commit:d6045ce79f7f72d2658ee5e54097ce24be106d73.

#21 Updated by anonym 2015-10-26 13:03:51

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#22 Updated by anonym 2015-11-03 11:29:53

  • Status changed from Fix committed to Resolved