1. 26 Aug, 2018 1 commit
  2. 12 Aug, 2018 1 commit
  3. 11 Aug, 2018 1 commit
  4. 08 Aug, 2018 1 commit
    • intrigeri's avatar
      Delete supposedly temporary config file we instructed users to create. · 0f99be6a
      intrigeri authored
      On #15692 we instruct users to create preferences/0000tails.js, with the intent
      that it would not be persistent because until 3.8 we have code that deletes that
      file on persistence activation. But as part of the fix for #15693, I've removed
      the code that deletes that file on persistence activation, which was not
      necessary to fix #15693.
      
      So a user who follows these instructions during their last Tails 3.8 session
      with persistence enabled (before upgrading to 3.9) will have that file left in
      persistence once they upgrade to 3.9… and then they'll be stuck forever with an
      obsolete value for extensions.enigmail.configuredVersion. To avoid that, I'm
      hereby re-adding the code that deletes this obsolete file.
      0f99be6a
  5. 01 Jul, 2018 2 commits
    • intrigeri's avatar
      Drop Icedove → Thunderbird migration code. · 0a533354
      intrigeri authored
      We've done the switch a year ago, in Tails 3.0, and #15693 shows
      that this migration code causes issues, so let's get rid of it.
      
      Besides, I have a hunch that this code is the only possible rationale
      explanation for the dreaded "empty persistence.conf file" problem, putting aside
      user intervention: it's the only piece of code we have, apart of the Tails
      Persistence Setup wizard that affected users tell they did not use, that
      modifies persistence.conf (refs: #10976).
      0a533354
    • intrigeri's avatar
      Stop deleting Enigmail's persistent configuredVersion (refs: #15693). · 45925bdb
      intrigeri authored
      Enigmail needs this info to know whether it should display its configuration
      wizard and trigger other post-upgrade operations. We should let it manage
      this value itself, otherwise it will display its configuration wizard
      every time one starts Thunderbird in a freshly booted Tails, even if
      the Thunderbird data is persistent.
      45925bdb
  6. 01 May, 2018 1 commit
  7. 28 Apr, 2018 1 commit
  8. 05 Mar, 2018 2 commits
  9. 27 Jan, 2018 1 commit
  10. 04 Jan, 2018 1 commit
  11. 02 Jan, 2018 1 commit
  12. 15 Sep, 2017 1 commit
    • intrigeri's avatar
      Make regexp match only what it should (refs: #12680). · ddccd730
      intrigeri authored
      "." is a regexp special char. We mean "." literally so it ought to be escaped.
      
      Wrong:
      
       $ echo 'user_pref("extensionsXenigmailYconfiguredVersion",' \
         | sed --regexp-extended \
              '/^(user_)?pref\("extensions.enigmail.configuredVersion",/d'
      
      Right:
      
       $ echo 'user_pref("extensionsXenigmailYconfiguredVersion",' \
         | sed --regexp-extended \
              '/^(user_)?pref\("extensions\.enigmail\.configuredVersion",/d'
       user_pref("extensionsXenigmailYconfiguredVersion",
      ddccd730
  13. 14 Sep, 2017 3 commits
  14. 13 Sep, 2017 1 commit
  15. 17 May, 2017 2 commits
    • anonym's avatar
      Simplify and clarify. · 22573019
      anonym authored
      Note that the backslash in the removed `\_${pattern}_`-style sed
      patterns just says "the next character will be the delimiter", so _
      becomes the delimiter. That allows you to use another delimiter than /
      in compination with d, which is nice when the pattern is a path (that
      tend to include /). It's a little known sed-feature. Just FYI! :)
      22573019
    • anonym's avatar
      Revert "live-persist: simplify." · c73cc472
      anonym authored
      This reverts commit b3abf4e5.
      c73cc472
  16. 15 May, 2017 5 commits
  17. 01 Feb, 2017 3 commits
  18. 03 Jan, 2016 1 commit
  19. 22 Nov, 2015 1 commit
  20. 01 Nov, 2015 2 commits
    • bertagaz's avatar
      Fix for real the logical bug for real-only persistence. · 5666ebcb
      bertagaz authored
      The problem was not that live-persist must error out when read-only
      persistence is activated rather than issue a warning. In the bug raised
      by #10431, the problem was that it *already did* because it tried to
      make the new persistence config anyway. So fixing #10431 by erroring out
      just lead to the same situation.
      
      In this case, we don't want to error out but warn out that the migration did not
      happen, and just go on with the boot without trying to migrate anything.
      
      Will-fix: #10431
      5666ebcb
    • bertagaz's avatar
      Fix identation. · c1b46347
      bertagaz authored
      c1b46347
  21. 27 Oct, 2015 1 commit
  22. 08 Oct, 2015 1 commit
  23. 07 Oct, 2015 1 commit
  24. 03 Oct, 2015 1 commit
  25. 06 Jul, 2015 2 commits
  26. 25 Jun, 2014 2 commits