Project

General

Profile

Feature #10285

Feature #5663: Return to Icedove

Add Icedove (and its related packages) to Tails

Added by kytv over 4 years ago. Updated about 4 years ago.

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

100%

Feature Branch:
kytv:feature/5663-return-to-icedove
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Email Client

Related issues

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

Associated revisions

Revision 53e4b336 (diff)
Added by anonym about 4 years ago

Install xul-ext-torbirdy from our APT repo.

A custom (trivial) backport for Debian Wheezy has been uploaded
there. This should fix concerns about builds suddenly breaking due to
the package being removed from testing/sid.

Refs: #10285

Revision d6045ce7
Added by anonym about 4 years ago

Merge branch 'feature/5663-return-to-icedove' into devel

Fix-committed: #6151, #9498, #10285, #10332

History

#1 Updated by kytv over 4 years ago

  • Parent task set to #5663

#2 Updated by kytv over 4 years ago

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

#3 Updated by kytv over 4 years ago

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

#5 Updated by intrigeri over 4 years ago

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

I don't think we'll want a branch per sub-task of #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 over 4 years ago

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

#7 Updated by kytv over 4 years ago

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 #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 over 4 years ago

  • 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 over 4 years ago

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

#10 Updated by kytv over 4 years ago

  • QA Check changed from Dev Needed to Ready for QA

#11 Updated by kytv over 4 years ago

  • Assignee changed from kytv to anonym

#12 Updated by intrigeri over 4 years ago

  • 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 over 4 years ago

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 over 4 years ago

  • 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 over 4 years ago

  • 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 over 4 years ago

  • 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 about 4 years ago

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 602793b. But I apparently b0rked it with a 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 53e4b33.

I think we're good on this ticket now.

#18 Updated by kytv about 4 years ago

  • QA Check changed from Info Needed to Ready for QA

#19 Updated by kytv about 4 years ago

  • Assignee changed from kytv to anonym

#20 Updated by anonym about 4 years ago

  • Status changed from In Progress to 11
  • % Done changed from 30 to 100

#21 Updated by anonym about 4 years ago

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

#22 Updated by anonym about 4 years ago

  • Status changed from 11 to Resolved

Also available in: Atom PDF