Bug #10456

Upgrade Tor Browser to 5.0.4

Added by anonym 2015-10-30 05:32:00 . Updated 2015-11-03 11:25:27 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Start date:
2015-10-30
Due date:
% Done:

100%

Feature Branch:
feature/10456-tor-browser-5.0.4
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description


Subtasks


History

#1 Updated by anonym 2015-10-30 05:32:18

  • Assignee set to anonym
  • Priority changed from Normal to Elevated

#2 Updated by anonym 2015-10-30 07:07:18

  • Status changed from Confirmed to In Progress

Applied in changeset commit:74e0f115f1166b175bfaaff14bc04e3a2c0a03d1.

#3 Updated by anonym 2015-10-30 07:10:06

  • Assignee changed from anonym to bertagaz
  • % Done changed from 0 to 40
  • QA Check set to Dev Needed
  • Feature Branch set to feature/10456-tor-browser-5.0.4

So I uploaded the 5.0.4 tarballs via Git annex, and now they have synced to http://torbrowser-archive.tails.boum.org/5.0.4/ but the permissions are screwed up, cause I get “403 Forbidden” for any of the tarballs. Any ideas, bert?

#4 Updated by bertagaz 2015-10-30 08:21:45

  • Assignee changed from bertagaz to anonym

anonym wrote:
> So I uploaded the 5.0.4 tarballs via Git annex, and now they have synced to http://torbrowser-archive.tails.boum.org/5.0.4/ but the permissions are screwed up, cause I get “403 Forbidden” for any of the tarballs. Any ideas, bert?

Dunno what happened, but I fixed the faulty permission there and the tarball are now available.

#5 Updated by anonym 2015-11-02 14:35:08

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

Applied in changeset commit:09fd0405ddf0b4ced3d6c296b413adfe00fd69be.

#6 Updated by anonym 2015-11-02 16:01:47

  • Assignee deleted (anonym)
  • QA Check changed from Dev Needed to Pass

#7 Updated by anonym 2015-11-03 11:25:27

  • Status changed from Fix committed to Resolved