1. 16 May, 2016 1 commit
  2. 11 May, 2016 3 commits
    • intrigeri's avatar
      Add explicit APT pinning for libdvd-pkg. · 7f5b9739
      intrigeri authored
      So far, it was magically pulled from jessie-backports merely because we
      forgot to add a general pinning level of -10 for backports in
      config/chroot_apt/preferences, unlike what we've done for all our other
      APT sources. And now it's broken, because in our APT snapshots system,
      backports have o=Debian, and not o=Debian Backports anymore.
      
      So, let's remove this exception, and pin the package explicitly.
      7f5b9739
    • intrigeri's avatar
      APT pinning: with our snapshots system, backports have o=Debian. · 8efc9e33
      intrigeri authored
      ... and here as well, add a sanity check to warn the developer early if
      they used "o=Debian Backports".
      
      We could easily fix that for time-based snapshots, but for tagged
      snapshots it's a different story: when we pull packages from time-based
      snapshots into tagged snapshots, we have no means to know what was
      the Origin they were pulled from initially.
      
      Granted, we *could* handle backports as a different archive (just like
      we have to do for debian-security), but it doesn't feel worth
      the hassle.
      8efc9e33
    • intrigeri's avatar
      APT pinning: use n=sid instead of a=unstable, to be compatible with our... · 984e8543
      intrigeri authored
      APT pinning: use n=sid instead of a=unstable, to be compatible with our time-based APT snapshots system.
      984e8543
  3. 11 Apr, 2016 1 commit
  4. 25 Mar, 2016 3 commits
  5. 15 Mar, 2016 1 commit
  6. 14 Mar, 2016 1 commit
  7. 10 Mar, 2016 1 commit
  8. 12 Feb, 2016 1 commit
  9. 11 Feb, 2016 1 commit
  10. 24 Jan, 2016 1 commit
  11. 11 Jan, 2016 1 commit
  12. 10 Jan, 2016 1 commit
  13. 30 Dec, 2015 1 commit
  14. 17 Dec, 2015 1 commit
    • intrigeri's avatar
      Use codename (stretch) instead of "testing" in APT pinning. · f2df7530
      intrigeri authored
      Since APT allows us to do this, I think we generally use:
      
       * "testing", when we mean we're going to track the package from Debian
         testing, possibly for years
       * $next_Debian_codename, when we merely want something a bit newer,
         and likely once we port Tails to $next_Debian_codename we can just
         take the package from there and stop tracking testing.
      f2df7530
  15. 16 Dec, 2015 1 commit
  16. 14 Dec, 2015 1 commit
    • intrigeri's avatar
      Install Electrum from jessie-backports. · a264618b
      intrigeri authored
      That is, currently: 2.5.4-1~bpo8+1. This is older than what we'll
      be shipping in Tails 1.8 (#9713), and we'll need a patch that's
      in 2.5.4-2, but for now it's still better than Jessie's 1.9.8-4,
      presumably.
      
      refs: #10754
      a264618b
  17. 09 Dec, 2015 1 commit
  18. 07 Dec, 2015 1 commit
  19. 30 Nov, 2015 3 commits
  20. 20 Nov, 2015 1 commit
  21. 11 Nov, 2015 1 commit
  22. 25 Oct, 2015 1 commit
  23. 22 Oct, 2015 2 commits
  24. 21 Oct, 2015 2 commits
  25. 16 Oct, 2015 1 commit
  26. 08 Oct, 2015 2 commits
  27. 07 Oct, 2015 1 commit
  28. 02 Oct, 2015 1 commit
  29. 30 Sep, 2015 1 commit
  30. 05 Jul, 2015 2 commits