[tor-bugs] #25339 [Applications/Tor Browser]: Install python 3.6 for building HTTPS-Everywhere

[Tor Bug Tracker & Wiki]

#25339: Install python 3.6 for building HTTPS-Everywhere
-------------------------------------------------+-------------------------
 Reporter:  boklm                                |          Owner:  tbb-
                                                 |  team
     Type:  task                                 |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201803,       |  Actual Points:
  boklm201802                                    |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by gk):

 * keywords:  tbb-rbm, TorBrowserTeam201802R, boklm201802 => tbb-rbm,
     TorBrowserTeam201803, boklm201802
 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:3 boklm]:
 > There is a patch for review in branch `bug_25339_v2`, using `buster` to
 build https-everywhere:
 > https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_25339_v2&id=734a41c0f986989163ff7536ff84a2a03e00d5cc
 >
 > However `buster` is not a stable release yet, so I am wondering how
 likely it is that an update, for instance on the `zip` package, would
 break the reproducibility of the build. Ubuntu Artful is a stable release,
 so it might be less likely to have big updates.

 Yes, that's true. However we would need to look for yet another solution
 to this bug in about three months as Ubuntu Artful is EOL in July 2018,
 not ideal. If you feel strongly here I am fine building Python 3.6 from
 source for 64bit Linux in the same container used for HTTPS-Everywhere. I
 feel the risk of breaking the reproducibility of HTTPS-Everywhere with
 `buster` is not very high given that it is "just" an extension. Either way
 I want to test the new process in an alpha anyway first (shipping the
 stable one time with a not up-to-date HTTPS-Everywhere seems to me
 acceptable given that we need to test a new build method in our
 environment first).

 Looking at the patch we don't need the 32bit `buster` in the debootstrap
 config. Could you remove that part? Oh, and we might want to clean that
 config up anyway (in a different bug/commit) as there are still Ubuntu
 Precise things among others in it.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25339#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online