[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:           |
-------------------------+-------------------------------------------------

Comment (by jsha):

 Git submodules are set to a particular sha1 at any given time. You can see
 which submodules have which hashes by running `git submodule`. So, in
 theory, so long as you init and update the submodules in the fetch step,
 you should always get the same content under translations.

 If we can't get the submodule approach to work for reproducible builds,
 I'm open to going back to the old style. My main goal here was to make it
 abundantly obvious that translation happens elsewhere, since we were
 getting occasional patches to change translations in HTTPS Everywhere
 rather than in Transifex.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16909#comment:5>
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