1. 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
  2. 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
  3. 14 Aug, 2015 1 commit
  4. 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
  5. 07 May, 2015 2 commits
  6. 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
  7. 01 Apr, 2015 4 commits
  8. 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
  9. 06 Feb, 2015 1 commit
  10. 19 Jan, 2015 1 commit
  11. 11 Jan, 2015 1 commit
  12. 03 Jan, 2015 1 commit
  13. 16 Nov, 2014 1 commit
  14. 08 Nov, 2014 1 commit
  15. 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
  16. 28 May, 2014 1 commit
  17. 09 May, 2014 1 commit
    • Tails developers's avatar
      Configure the keyboard model and layout used in the GNOME session, accordingly... · 9f73d4b3
      Tails developers authored
      Configure the keyboard model and layout used in the GNOME session, accordingly to what the user chose in the Greeter.
      
      This depends on Tails Greeter to save the relevant environment variables
      to /var/lib/tails-user-session/keyboard.
      
      Note that we don't set layouts to [chosen one, US] anymore, as I could not make
      it work properly: in this case, regardless of the order in which we set it, the
      US layout wins and is applied by default in the session. Anyway, it's easy
      enough to either directly choose US in the greeter (when one wants the GUI in
      their preferred language, and a US keyboard layout), or to add the US layout in
      the GNOME settings (when using both layouts in the same session). So, this seems
      like an acceptable regression to me.
      9f73d4b3
  18. 17 Apr, 2014 1 commit
  19. 29 Nov, 2013 1 commit
    • WinterFairy's avatar
      Remove no longer used variable. · 20387fce
      WinterFairy authored
      According to git log it has been used to decide
      which languages to display in a syslinux menu,
      and which languages to generate mo-files for.
      
      Both uses are deprecated already.
      20387fce
  20. 27 Sep, 2013 1 commit
  21. 03 Sep, 2013 1 commit
  22. 02 Sep, 2013 1 commit
  23. 23 Jun, 2013 4 commits
  24. 23 May, 2013 1 commit
    • Tails developers's avatar
      Add /live/overlay -> /lib/live/mount/overlay symlink, for real this time. · 3233da6c
      Tails developers authored
      The live-boot changes (commit d2b2a461) brought to fix Debian bug#696495 revert
      some of our previous changes (commit 77dab1cb), and as a result, at the time
      live-persist runs, no tmpfs is mounted on /live/overlay while this command is
      run:
      
        mount -t aufs -o noatime,noxino,dirs=/live/overlay//home/amnesia/Persistent=rw:/live/persistence/sda2_unlocked/Persistent=rr+wh aufs /home/amnesia/Persistent
      
      ... and dmesg therefore reads:
      
        aufs test_add:264:mount[4677]: unsupported filesystem, /live/overlay//home/amnesia/Persistent (aufs)
      
      So, let's just ensure /live/overlay points to a tmpfs.
      3233da6c
  25. 03 Feb, 2013 1 commit
    • Tails developers's avatar
      Workaround build failure in lb_source, after creating the ISO. · 06c156ef
      Tails developers authored
      At `lb source` time, when `lb chroot_sources install` wants to run `apt-get
      upgrade`, it fails the build with `The value 'wheezy' is invalid for
      APT::Default-Release as such a release is not available in the sources` (due to
      the APT proxy not being configured at this time, the last `apt-get update`
      failed and the package indices are empty). If one simply removes
      `APT::Default-Release`, then the pinning is broken when indices are
      not available.
      06c156ef
  26. 13 Mar, 2012 1 commit
  27. 29 Nov, 2011 1 commit
  28. 28 Nov, 2011 3 commits
  29. 19 Oct, 2011 1 commit
  30. 15 Sep, 2011 2 commits