1. 02 Dec, 2018 3 commits
  2. 27 Nov, 2018 6 commits
  3. 12 Nov, 2018 1 commit
  4. 16 Aug, 2018 1 commit
  5. 01 Jul, 2018 2 commits
  6. 01 Mar, 2018 1 commit
  7. 23 Feb, 2018 1 commit
  8. 22 Feb, 2018 1 commit
    • anonym's avatar
      Build system: bump builder VM's RAM. · b94b0172
      anonym authored
      On some systems 768 MB is not enough for a disk build. We have not
      seen any corresponding issue for RAM builds, so let's just "move" the
      RAM requirement around.
      Refs: #15310
  9. 05 Jan, 2018 1 commit
  10. 01 Jan, 2018 1 commit
    • bertagaz's avatar
      Add APT_SNAPSHOT_SERIAL build option. · aafdf8da
      bertagaz authored
      It enables to specify which time-based APT snapshot repositories will be
      used as 'latest' during the build, and will set it accordingly in the
      resulting ISO image. Useful to reproduce another ISO image.
      Refs: #15107, #14944, #14924
  11. 12 Dec, 2017 1 commit
    • anonym's avatar
      Vagrant: never build the wiki early. · 3a622350
      anonym authored
      This has caused several issues throughout the years, the lastest
      instance being the reopening of #14933, so let's just remove this
      feature. The optimization this allows for when rebuilding the same
      branch frequently (together with the keeprunning option) was probably
      only used by me, and rarely at that, so I'd argue it is not worth the
      maintenance cost.
      Will-fix: #14933
  12. 10 Nov, 2017 1 commit
    • intrigeri's avatar
      Fix reproducibility of builds of topic branches that lag behind their base... · 0c043dbf
      intrigeri authored
      Fix reproducibility of builds of topic branches that lag behind their base branch with the mergebasebranch build option enabled (refs: #14946)
      Two otherwise identical merge commits done at different times get different IDs,
      and we happen to embed in the ISO the ID of the commit we're building from.
  13. 09 Nov, 2017 2 commits
    • anonym's avatar
      Vagrant: move code to where it makes more sense. · 7f0a1f0e
      anonym authored
      Since the disk cache shrinking is here to ensure that we don't run out
      of disk space, it should actually be done before *each* build.
    • anonym's avatar
      Vagrant: stop feeding ELF binary code to the Perl interpreter. · c4bd3ad8
      anonym authored
      So in a recent apt-cacher-ng (probably the one we upgraded to when
      migrating to Stretch) expire-caller.pl was turned into a symlink to
      acngtool, which is pretty stupid given the extension (which makes one
      think it *should* be fed to Perl), and since it is not a drop-in
      replacement (something like `acngtool shrink -f` is needed).
      With acngtool we're able to specify how much to clean the cache disk,
      so let's try to something intelligent there.
  14. 21 Oct, 2017 2 commits
  15. 15 Sep, 2017 1 commit
  16. 02 Aug, 2017 1 commit
    • bertagaz's avatar
      Lower BUILD_SPACE_REQUIREMENT by 256M. (refs: #13480) · 084f057f
      bertagaz authored
      We've raised the required memory for on-disk build, so let's lower this
      so that we can keep on building in RAM with the same amount of memory
      than before the bump and don't need to allocate more memory to our
  17. 29 Jul, 2017 5 commits
  18. 23 Jul, 2017 1 commit
  19. 14 Jul, 2017 1 commit
  20. 25 Jun, 2017 2 commits
    • intrigeri's avatar
    • intrigeri's avatar
      Vagrant: track the latest debian-security archive for the corresponding APT... · e1dd7080
      intrigeri authored
      Vagrant: track the latest debian-security archive for the corresponding APT sources, and not for the unrelated jessie-updates (refs: #12829).
      Interestingly, this bug wasn't noticed earlier because our
      tails-update-time-based-apt-snapshots-* cronjobs are set up in a way that if
      everything goes fine, we're guaranteed that a snapshot of the debian archive
      corresponding to the debian-security archive's latest serial always exists.
      But when tails-update-time-based-apt-snapshots-* cronjobs start failing, which
      is the case currently due to #12725 and/or #13134, then it may happen that this
      doesn't hold true, and then the ISO build fails because we're trying to use
      a snapshot that doesn't exist for the jessie-updates suite.
      So, in this commit:
      1. do not modify the serial used for the jessie-updates suite; this should fix
         the ISO build;
      2. do update the serial used for the jessie/updates (security) suite; this
         ensures we actually install security updates in the build VM, as
         intended initially.
  21. 09 Jun, 2017 1 commit
  22. 01 Jun, 2017 1 commit
  23. 24 May, 2017 2 commits
  24. 22 May, 2017 1 commit