[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #16909 [Tor Browser]: Adapt Tor Browser bundling to new HTTPS-Everywhere ID beginning with 5.1.0

#16909: Adapt Tor Browser bundling to new HTTPS-Everywhere ID beginning with 5.1.0
-------------------------+-------------------------------------------------
     Reporter:  gk       |      Owner:  gk
         Type:           |     Status:  needs_information
  enhancement            |  Milestone:
     Priority:  normal   |    Version:
    Component:  Tor      |   Keywords:  tbb-gitian, TorBrowserTeam201509,
  Browser                |  GeorgKoppen201509
   Resolution:           |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------
Changes (by gk):

 * cc: jsha (added)
 * status:  new => needs_information


Comment:

 Replying to [ticket:16909 gk]:
 > The other change although orthogonal to the AMO signing is moving to a
 submodule for the translations. We should verify that our build process
 picks this up.

 This is actually problematic I think. Aside from the fact that the Gitian
 build itself should not need network connectivity (which we could fix if
 we initialized and updated all the submodules in the fetch step) there is
 no guarantee anymore that two builders starting the build tagged as
 `tbb-5.5a3-build1` would get identical builds as builder 2, starting at a
 later time, could get the `https_everyhwere` branch in the translations
 repo being at a later state: the translations are not subject to the
 https-e tag anymore. Or am I missing something here?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16909#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs