1. 04 Oct, 2017 1 commit
    • boklm's avatar
      Bug 23585: fix build with runc version 1.0.0~rc2 · 8c4c05dd
      boklm authored
      Some distributions are packaging runc version 1.0.0~rc2, which seems to
      be half between runc 0.1.1 and runc 1.0.0.
      This version requires the same command line parameters as version 1.0.0,
      however it requires a config.json in the same format as 0.1.1.
      The output from `runc --version` on 1.0.0~rc2 is:
      runc version spec: 1.0.0-rc2-dev
      So we add a var/runc_spec100 function which is true when the runc
      version spec is exactly 1.0.0 (as returned by runc stable 1.0.x
      releases), and use it in projects/common/runc-config.json.
  2. 26 Sep, 2017 1 commit
  3. 22 Sep, 2017 5 commits
  4. 19 Sep, 2017 1 commit
    • boklm's avatar
      Bug 23039: fix detection of runc version · 1f054c59
      boklm authored
      In the previous patch, we wrongly assumed that all runc 0.1.1 versions
      exited with 0 when given an unknown command, and used that to detect the
      version. It seems it is not true on all systems.
      We are now using the 'runc --version' command to find the version of
      We don't support versions older than 0.1.1.
  5. 15 Sep, 2017 1 commit
    • boklm's avatar
      Bug 23039: add support for runc 1.0.0 · 209818fc
      boklm authored
      The var_p/runc100 option is used to detect the version of runc we are
      using. The format of the output of `runc --version` is different in both
      versions, so it is not easy to parse. However I noticed that runc 0.1.1
      does not exit with an error when we try to use a command that does not
      exist while runc >= 1.0.0 does, so we use that to detect the runc
      version we are using.
      When using runc >= 1.0.0, we use `runc run` instead of `runc start':
      In the runc config.json file, the format of the capabilities has been
      changed. Instead of having one list of capabilities, there are now
      separate lists for bounding, effective, inheritable, permitted and
      ambient capabilities (and we use the same list for all of them):
      We also add /proc/timer_list and /sys/firmware to the "maskedPaths", as
      those paths are now listed by default in the config.json file generated
      by `runc spec` with runc 1.0.0.
  6. 11 Sep, 2017 1 commit
    • boklm's avatar
      Bug 23454: restore stderr in build logs · 75af4379
      boklm authored
      In #23425 we redirected the output from runc start to /dev/null to
      avoid annoying messages saying "stdin: is not a tty". However this also
      removes stderr from build logs.
      The command producing the `stdin: is not a tty` message is the `chown -R`
      command from runc/remote_put, so we now only hide stderr from that
      part while keeping it for the runc command running the build script.
  7. 07 Sep, 2017 2 commits
  8. 06 Sep, 2017 1 commit
  9. 05 Sep, 2017 1 commit
  10. 21 Aug, 2017 1 commit
    • boklm's avatar
      Bug 17381: add and adapt the update_responses script · de3f97f3
      boklm authored
      Add the update_responses and incrementals makefile rules.
      The update_responses script is identical to what we have in
      tor-browser-bundle.git, however the config.yml file it is using is now
      generated using the infos from rbm.
  11. 11 Aug, 2017 2 commits
  12. 09 Aug, 2017 2 commits
  13. 07 Aug, 2017 2 commits
  14. 04 Aug, 2017 2 commits
    • boklm's avatar
      Release preparations for 7.5a4 · c29deee7
      boklm authored
      Changelog update and version bumps.
      tor-browser-bundle.git author: Georg Koppen <gk@torproject.org>
      tor-browser-bundle.git commit: 0d192217fc71cccf16bce16e3904460b0991b43d
      tor-browser-bundle.git commit: 6d54b0e2b8cf45fb817e2bbc822c61e5a4ad78de
      tor-browser-bundle.git commit: 1a15760dcb3889417809ab4a38bf4b523ecf74a7
      tor-browser-bundle.git commit: 8b061ed2d5112c006a80723ea63333d0098b94c4
    • boklm's avatar
      Bug 23075: rename RBM_NB_CORES to RBM_NUM_CORES · b466ec4b
      boklm authored
      And buildconf/nb_procs to buildconf/num_procs.
  15. 03 Aug, 2017 2 commits
    • boklm's avatar
      Add var/release, var/alpha, var/nightly options · bec33453
      boklm authored
      Add some options to be able to write things like this in templates:
      [% IF c("var/release") -%]
      do something on release channel
      [% ELSIF c("var/alpha") -%]
      do something on alpha channel
      [% ELSIF c("var/nightly") -%]
      do something on nightly channel
      [% END -%]
    • boklm's avatar
      Bug 22499: build obfsproxy and fteproxy for Windows · 6221fac7
      boklm authored
      Also finish including the Linux build of obfsproxy and fteproxy.
      Based on gitian/descriptors/windows/gitian-pluggable-transports.yml
      from tor-browser-bundle.git.
  16. 02 Aug, 2017 1 commit
  17. 01 Aug, 2017 1 commit
  18. 26 Jul, 2017 1 commit
  19. 24 Jul, 2017 1 commit
  20. 19 Jul, 2017 1 commit
    • boklm's avatar
      Build go-webrtc and snowflake for mac. · 9b591074
      boklm authored
      tor-browser-bundle.git author: David Fifield <david@bamsoftware.com>
      tor-browser-bundle.git commit: 26e0cd44f2886bfad1c3d30844ff7a21eb9d0478
      Commit message from the tor-browser-bundle.git commit:
      Build go-webrtc and snowflake in the mac pluggable-transports descriptor.
      I had to apply two tricks to get a reproducible snowflake-client.
      The first is to use faketime to eliminate some timestamps. There were 11
      variable timestamps in the file. Through experimentation, I found that
      10 of them were dependent on the Go runtime (recompiling Go caused them
      to change) and 1 was dependent on snowflake-client itself (recompiling
      snowflake-client with the same runtime changed only that 1 timestamp).
      The underlying issue has to do with clang 3.8.0 on Darwin embedding
      timestamps, unsolved in the Go issue tracker as of 13 days ago.
      The second is a sed command to clobber embedded paths of the form
      /tmp/go-buildXXXXXXXXX and /tmp/go-link-XXXXXXXXX. Their presence is
      caused by some combination of Clang and Darwin, and there is as yet no
      known workaround upstream.
  21. 18 Jul, 2017 1 commit
  22. 13 Jun, 2017 1 commit
    • boklm's avatar
      Update versions and ChangeLog for 7.5a1 · 48e45a9a
      boklm authored
      tor-browser-bundle.git author: Georg Koppen <gk@torproject.org>
      tor-browser-bundle.git commit: 321ad6021df0b3d55625c5bd88dcfc5acdf112f8
      tor-browser-bundle.git commit: ade53c43e1230a05e0b138b3ade92914e9d9a279
      tor-browser-bundle.git commit: 638da360d67407b2866f0747a5df40d8ae36af78
  23. 05 Jun, 2017 1 commit
  24. 17 May, 2017 1 commit
    • boklm's avatar
      Release preparations for 7.0a4 · 18416a10
      boklm authored
      tor-browser-bundle.git author: 999a7afe0f50c6d6503d99ff3fab3879cd069a85
      tor-browser-bundle.git commit: Georg Koppen <gk@torproject.org>
  25. 11 May, 2017 1 commit
  26. 08 May, 2017 2 commits
  27. 05 May, 2017 1 commit
  28. 10 Apr, 2017 1 commit
  29. 06 Apr, 2017 1 commit