[tbb-bugs] #27539 [Applications/Tor Browser]: Create plan for releasing on F-Droid

[Tor Bug Tracker & Wiki]

#27539: Create plan for releasing on F-Droid
-------------------------------------------------+-------------------------
 Reporter:  sysrqb                               |          Owner:  tbb-
                                                 |  team
     Type:  enhancement                          |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-mobile, TBA-8.5,                 |  Actual Points:
  TorBrowserTeam201903, tbb-8.5                  |
Parent ID:  #26318                               |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor8
-------------------------------------------------+-------------------------

Comment (by sysrqb):

 Okay, update time.

 {{{
 Build log:
 /home/android/fdroiddata/build/org.torproject.torbrowser_alpha/logs
 /release-android-armv7.log
 + mv out/tor-browser/tor-browser-8.5a10-android-armv7-71df5f/tor-
 browser-8.5a10-android-armv7-multi-qa.apk tor-browser-8.5a10-android-
 armv7-multi.apk
 INFO: Successfully built version 60.6.1 of org.torproject.torbrowser_alpha
 DEBUG: > /home/android/.mozbuild/android-sdk-linux/build-tools/27.0.3/aapt
 dump xmltree build/org.torproject.torbrowser_alpha/tor-browser-8.5a10
 -android-armv7-multi.apk AndroidManifest.xml
 DEBUG: Checking build/org.torproject.torbrowser_alpha/tor-browser-8.5a10
 -android-armv7-multi.apk
 DEBUG: > /home/android/.mozbuild/android-sdk-linux/build-tools/27.0.3/aapt
 dump badging build/org.torproject.torbrowser_alpha/tor-browser-8.5a10
 -android-armv7-multi.apk
 INFO: ...retrieving https://dist.torproject.org/torbrowser/8.5a10/tor-
 browser-8.5a10-android-armv7-multi.apk
 DEBUG: Starting new HTTPS connection (1): dist.torproject.org:443
 DEBUG: https://dist.torproject.org:443 "GET /torbrowser/8.5a10/tor-
 browser-8.5a10-android-armv7-multi.apk HTTP/1.1" 200 45132400
 WARNING: Ignoring META-INF/MANIFEST.MF from
 unsigned/org.torproject.torbrowser_alpha_2015615257.apk
 WARNING: Using Java's jarsigner, not recommended for verifying APKs! Use
 apksigner
 DEBUG: JAR signature verified:
 /tmp/tmpnl152ahj/sigcp_org.torproject.torbrowser_alpha_2015615257.apk
 INFO: ...successfully verified
 INFO: compared built binary to supplied reference binary successfully
 INFO: success: org.torproject.torbrowser_alpha
 INFO: Finished
 INFO: 1 build succeeded
 36345.96user 1521.99system 3:34:46elapsed 293%CPU (0avgtext+0avgdata
 4665892maxresident)k
 90255632inputs+212459080outputs (298918major+328486141minor)pagefaults
 0swaps

 real    215m13,620s
 user    606m12,810s
 sys     25m22,220s
 }}}

 I ran the build process locally under `time`, so I know how long it took
 for a full build without cached artifacts. The entire build process took
 215 minutes (3.5 hours). I am still worried this will exceed timeout
 limits on F-Droid (or maybe disk space limits, if any exist), but hey -
 it's working.

 Assuming I'm reading this correctly, the result of this is an apk that has
 a manifest matching the apk we published. This mean we can distribute the
 apk on F-Droid with our signature (instead of F-Droid signing the apk and
 distributing it under their signing key).

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