1. 06 Jan, 2020 2 commits
  2. 31 Dec, 2019 3 commits
  3. 28 Dec, 2019 1 commit
  4. 27 Dec, 2019 2 commits
  5. 26 Dec, 2019 2 commits
    • intrigeri's avatar
      IUK creation: delete temporary directory on success (refs: #15287) · 1501f638
      intrigeri authored
      tails-create-iuk previously left temporary files behind. In particular, even on
      success, the "squashfs_src" directory would remain on the filesystem.
      It's no big deal in general, but our build_IUKs Jenkins job runs
      tails-create-iuk as root with sudo, so the leftover temporary files are owned by
      root, and then the "workspace-cleanup" step (itself run as the "jenkins" user)
      can't delete them, which causes 2 problems:
       - These temporary files would endlessly accumulate on isobuilders,
         without any mechanism to clean them up automatically.
       - Confusing output in the Jenkins console:
            cannot remove path when cwd is /var/lib/jenkins/workspace/build_IUKs/j4gMvgS3wH for /var/lib/jenkins/workspace/build_IUKs/j4gMvgS3wH:  at /usr/share/perl/5.24/File/Temp.pm line 1583.
            Archiving artifacts
            [WS-CLEANUP] Deleting project workspace...
            Cannot delete workspace: null
            Option not to fail the build is turned on, so let's continue
    • intrigeri's avatar
      IUK creation: only pass --xattrs to rsync when using overlayfs · a61ffaae
      intrigeri authored
      On our Stretch isobuilders, passing --xattrs to rsync when generating an
      aufs-based IUK makes it fail: setting xattrs on a file in an aufs filesystem
      raises an "operation not supported" error.
      We only need to preserve xattrs when building overlayfs-based IUKs,
      because aufs will lose them at mount time anyway.
  6. 24 Dec, 2019 3 commits
  7. 23 Dec, 2019 9 commits
  8. 22 Dec, 2019 5 commits
  9. 18 Dec, 2019 1 commit
  10. 02 Dec, 2019 4 commits
  11. 30 Nov, 2019 2 commits
  12. 29 Nov, 2019 1 commit
    • intrigeri's avatar
      Thunderbird: disable automatic fetch of email at login and in the background (refs: #17222) · ca2b6939
      intrigeri authored
      This replicates what Torbirdy did. It's not clear whether the benefits
      of this behavior outweigh the problematic UX impact of not being notified
      of new email automatically. We started discussing this on #17222 but
      we have not reached a clear conclusion/consensus yet, so for now,
      let's stick to the same behavior as previous versions of Tails,
      and come back to this discussion later.
  13. 28 Nov, 2019 5 commits