Don't unpack HTTPS Everywhere anymore while bundling Tor Browser

We ship support for unpacked HTTPS Everywhere soon. As it does not need to be unpacked anymore (since 5.2.2) we should not do this either in our bundling step.

added GeorgKoppen201609 TorBrowserTeam201609R component::applications/tor bundles/installation owner::tbb-team priority::medium resolution::fixed severity::normal status::closed tbb-usability type::enhancement labels

Trac:
Owner: erinn to tbb-team
Status: new to assigned

bug_20118_v3 in my public tor-browser-bundle repo (https://gitweb.torproject.org/user/gk/tor-browser-bundle.git/commit/?h=bug_20118_v3&id=46a041e6573c0abbc074e7865a700f383edbc8c1) has a proposed fix up for review.

Trac:
Keywords: TorBrowserTeam201609 deleted, GeorgKoppen201609, TorBrowserTeam201609R added
Status: assigned to needs_revision
Cc: N/A to boklm

I did not try building with this patch, but the changes look correct.

r=mcs I did not try to build with these changes either but they look good.

Okay, I finally went with bug_20188_v5 (https://gitweb.torproject.org/user/gk/tor-browser-bundle.git/commit/?h=bug_20118_v5&id=ae5f3f9f9bb12a0e07d268262c6e5b8e3b0baf88) after I found issues while testing. Applied to master as commit ae5f3f9f9bb12a0e07d268262c6e5b8e3b0baf88.

Trac:
Status: needs_revision to closed
Resolution: N/A to fixed

That got picked up for 6.0.6 with commit b373d46c616682000ff07029eaa4a113e29b286e on maint-6.0.

closed