1. 14 Mar, 2017 1 commit
    • intrigeri's avatar
      Ensure /etc/resolv.conf is owned by root:root in the SquashFS. · 3cae08ce
      intrigeri authored
      lb_chroot_resolv will "cp -a" it from the source tree, so it inherits its
      ownership from the whoever cloned the Git repository. This has two problems.
      First, this results in unsafe permissions on this file (e.g. a Vagrant build
      results in the 'amnesia' user having write access to it). Second, building with
      a different user results in a non-deterministic SquashFS.
      
      refs: #5630
      3cae08ce
  2. 20 Dec, 2016 1 commit
  3. 10 Nov, 2016 2 commits
  4. 08 Jun, 2016 1 commit
  5. 16 May, 2016 2 commits
  6. 24 Mar, 2016 1 commit
  7. 10 Mar, 2016 5 commits
  8. 21 Feb, 2016 1 commit
  9. 03 Jan, 2016 1 commit
  10. 01 Jan, 2016 1 commit
    • intrigeri's avatar
      Repair dotfiles persistence feature by adding a symlink from... · 59573b6f
      intrigeri authored
      Repair dotfiles persistence feature by adding a symlink from /lib/live/mount/persistence to /live/persistence.
      
      live-boot's "link" option generates symlinks to /lib/live/mount/persistence.
      
      This is correct in the supported use case (persistence initialized at initramfs
      time), because components/9990-main.sh does "Move all mountpoints below /live
      into /root/lib/live/mount" after setting up persistence. Our own
      config/chroot_local-includes/usr/local/sbin/live-persist, however, mounts stuff
      in /live/persistence instead, so the generated links are wrong.
      
      We have lots of Tails-specific stuff that depends on the /live/persistence path,
      so I'd rather not change that, and instead I'm adding a compatibility symlinks.
      
      Will-fix: #10784
      59573b6f
  11. 13 Dec, 2015 4 commits
  12. 22 Nov, 2015 1 commit
  13. 25 Oct, 2015 1 commit
  14. 12 Oct, 2015 1 commit
    • anonym's avatar
      Simplify ISO image naming rules. · 28d2fddb
      anonym authored
      ... by using the base rule we use for Jenkins all the time, except
      when building from a tag (i.e. building a release).
      
      Will-fix: #10349
      28d2fddb
  15. 14 Aug, 2015 1 commit
  16. 15 May, 2015 1 commit
    • intrigeri's avatar
      Don't modify files in the source tree before having possibly merged the base branch into it. · d81c8c33
      intrigeri authored
      Previously, when building in Jenkins, we refreshed the wiki (twice) and
      translations before merging the base branch. As a result, we're seeing build
      failures with the "Your local changes to the following files would be
      overwritten by merge" error message.
      
      Let's now build the wiki and refresh translations only _after_ having merged the
      base branch, which makes more sense anyway: we want to include changes from the
      base branch into the wiki and translations. And while we're at it, let's refresh
      the wiki only once when building in Jenkins.
      
      Note that Vagrant builds will still build the wiki before setting up the ramdisk
      and running live-build: those builds don't merge the base branch anyway, so they
      can as well keep the wiki build caching mechanism, which is a nice optimization.
      
      Will-fix: #9406
      d81c8c33
  17. 07 May, 2015 2 commits
  18. 08 Apr, 2015 1 commit
    • intrigeri's avatar
      Replace config/APT_overlays with config/APT_overlays.d/*. · 88157c46
      intrigeri authored
      This avoids having to use a special merge driver when building on Jenkins, and
      in general should make most merges "just work" as intended, minimizing both the
      risk of merge conflicts that need to be dealt with manually, and the risk of Git
      wrongly resolving merges automatically.
      88157c46
  19. 01 Apr, 2015 4 commits
  20. 17 Feb, 2015 1 commit
    • Tails developers's avatar
      Zero-pad our ISO images so their sizes are divisible by 2048. · d70b3bf1
      Tails developers authored
      The data part of an ISO image's sectors are 2048 bytes, which implies
      that ISO images should always have a size divisible by 2048. Some
      application, e.g. VirtualBox, use this as a sanity check, treating ISO
      images for which this isn't true as garbage.
      
      Our isohybrid post-processing seems to result in ISO images with sizes
      that are multiples of 1024, so we now pad our ISO images (if needed)
      to ensure divisibility with 2048 to avoid issues with e.g. VirtualBox.
      
      Will-fix: #8891
      d70b3bf1
  21. 06 Feb, 2015 1 commit
  22. 19 Jan, 2015 1 commit
  23. 11 Jan, 2015 1 commit
  24. 03 Jan, 2015 1 commit
  25. 16 Nov, 2014 1 commit
  26. 08 Nov, 2014 1 commit
  27. 31 Jul, 2014 1 commit
    • Tails developers's avatar
      Compress the SquashFS more aggressively (Closes: #7706). · 41a6531d
      Tails developers authored
      In my tests on current experimental branch, this makes the ISO 10% smaller, but
      makes the build take 63% more (real) time, and eat 110% more (user) CPU time.
      It seems worth it for released ISO images.
      
      Likely, most developers that didn't do it yet will now set
      MKSQUASHFS_OPTIONS='-comp gzip' when doing their regular builds... although the
      time gained by gzip (vs. aggressive xz) at build time is compensated, in many
      cases, by faster IO (e.g. when copying the ISO out of the build VM, when booting
      the ISO, when installing the ISO on a USB stick).
      41a6531d