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

Re: [tor-bugs] #9444 [Tor bundles/installation]: Create deterministic TorBrowserBundles with Pluggable Transports

#9444: Create deterministic TorBrowserBundles with Pluggable Transports
------------------------------------------+--------------------------
     Reporter:  bastik                    |      Owner:  erinn
         Type:  task                      |     Status:  needs_review
     Priority:  normal                    |  Milestone:
    Component:  Tor bundles/installation  |    Version:
   Resolution:                            |   Keywords:  flashproxy
Actual Points:                            |  Parent ID:
       Points:                            |
------------------------------------------+--------------------------

Comment (by dcf):

 I merged with the upstream tag [https://gitweb.torproject.org/builders
 /tor-browser-bundle.git/tag/refs/tags/tbb-3.0rc1-build1
 tbb-3.0rc1-build1]; surprisingly it wasn't difficult. That means the
 pluggable transport bundles are now up to date with the
 [https://blog.torproject.org/blog/tor-browser-bundle-30rc1-released most
 recent 3.0-rc-1] released on the blog.

 Builds using [https://gitweb.torproject.org/user/dcf/tor-browser-
 bundle.git/commit/00789049873753d931fec3803c9ccae75a5c5267
 00789049873753d931fec3803c9ccae75a5c5267] are here:
  * https://people.torproject.org/~dcf/pt-bundle/3.0-rc-1-pt20131207-1/
 This time I included the whole mess of vanilla bundles and localizations
 for the PT bundles.

 I wrote a mailing list post asking for advice on what to do next.
  * [https://lists.torproject.org/pipermail/tor-
 dev/2013-December/005913.html tor-dev: Merge of Gitian PT build with
 3.0-rc-1; next steps]
 My goal is to have pluggable transports bundles built in the course of
 normal bundle building. I want to get rid of the `gitian-ptbundle.yml`
 files, which are near-duplicates of `gitian-bundle.yml`, the only
 differences being some additional files copied and the bundle file names.
 The options I put in the mailing list post are:
  1. Add a conditional variable, something like the
 [https://gitweb.torproject.org/builders/tor-browser-
 bundle.git/blob/b575c59a33367af3366d0461cd5815acf1217ef7:/gitian/descriptors/linux
 /gitian-firefox.yml#l65 ${TORBROWSER_VERSION::3} != "3.0"] in `linux
 /gitian-firefox.yml`, that controls whether a vanilla or a PT build is
 underway. When the variable is set, the descriptor would just copy in a
 few additional files and change the output file name.
  2. Build the pluggable transports bundles unconditionally, and just do
 all the dtars in gitian-bundle.yml twice: once for tor-browser and once
 for tor-pluggable-transports-browser.

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