1. 20 Sep, 2016 1 commit
    • anonym's avatar
      Revert "Install Linux 4.7." · e4c35183
      anonym authored
      This reverts commits:
      
      * ab562fd4
      * c0bc655c
      * 80d0667a
      
      The last minute attempt to include it in Tails 2.6 was a bad (too hasty)
      idea, e.g. USB installations don't boot (pre-init results in
      "FAT-fs (sdb1): IO charset ascii not found"). Also it seems that the
      backport of Linux 4.7 hasn't gone through the proper Debian QA process.
      e4c35183
  2. 19 Sep, 2016 2 commits
    • anonym's avatar
      Install the unsigned (w.r.t. Secure Boot) Linux kernel. · c0bc655c
      anonym authored
      I suppose the signed one will the default (without any suffix), but it
      is not available yet from Jessie backports.
      
      It's worth noting that the linux-image-amd64 package is not satisfied by
      the -unsigned packages yet, so we have to explicitly install the exact
      image version we want.
      c0bc655c
    • anonym's avatar
      Install the firmware-nonfree packages from jessie-backports. · 39ec413c
      anonym authored
      For the Tails 2.6 release, where we did a last minute bump of the
      'debian' snapshot, some firmwares have suddenly been removed from
      Debian Sid:
      
      * firmware-amd-graphics
      * firmware-intel-sound
      * firmware-misc-nonfree
      
      resulting in Tails not building any more.
      39ec413c
  3. 26 Aug, 2016 1 commit
  4. 07 Aug, 2016 1 commit
  5. 22 Jul, 2016 1 commit
  6. 21 Jul, 2016 1 commit
  7. 20 Jul, 2016 3 commits
  8. 19 Jul, 2016 1 commit
  9. 05 Jul, 2016 1 commit
  10. 16 Jun, 2016 1 commit
  11. 10 Jun, 2016 1 commit
  12. 09 Jun, 2016 1 commit
  13. 08 Jun, 2016 2 commits
  14. 07 Jun, 2016 1 commit
    • intrigeri's avatar
      Upgrade to Linux 4.5. · 4eb604e7
      intrigeri authored
      This is essentially a squashed version of feature/8415-overlayfs, purged
      of its overlayfs-specific bits, and that fetches the kernel from
      jessie-backports (instead of from sid) to ease compiling out-of-tree and
      dkms modules. At this stage, the resulting ISO won't boot since it'll
      lack both aufs and overlayfs.
      
      refs: #10298
      
      To achieve that:
      
      * Install the 686 kernel flavour instead of the obsolete 586 one.
      
      * Rename the amd64 kernel via binary_local-hooks.
      
        lb_binary_syslinux depends on --linux-flavours, but we can't pass
        amd64 in there anymore (due to lack of multiarch support) so we need
        to rename the second (amd64) kernel ourselves.
      
      * APT, dpkg: add amd64 architecture. The amd64 kernel flavour is not
        built anymore for the i386 architecture, so we need to use
        multiarch now.
      
      * Temporary disable dkms modules building.
      
        Building them for the amd64 kernel requires installing an amd64
        toolchain, that conflicts with the i386 one and with lots of packages
        we need. Let's come back to it later (refs: #9969).
      4eb604e7
  15. 02 Jun, 2016 2 commits
  16. 31 May, 2016 1 commit
    • intrigeri's avatar
      Install jessie-backports version of all binary packages built from src:hplip. · 6232d76b
      intrigeri authored
      This adds support for quite a few new printers.
      
      refs: #10965 (since it makes it more likely that a given printer will be
      supported out-of-the-box, regardless of whether the online lookup works
      or not; and at this point I cannot confirm that torifying
      scp-dbus-service is enough to make it do anything useful for printers
      that need the online lookup.)
      6232d76b
  17. 24 May, 2016 1 commit
  18. 22 May, 2016 1 commit
  19. 21 May, 2016 1 commit
    • intrigeri's avatar
      Pin our custom APT repo to the same level as Debian ones, and explicitly pin... · 38fb2ddf
      intrigeri authored
      Pin our custom APT repo to the same level as Debian ones, and explicitly pin higher the packages we want to pull from our custom APT repo, when needed.
      
      See the "Freeze exceptions" section of the freezable APT repository design for
      the reason behind this.
      
      Note that we don't add explicit pinning for:
      
       * packages that are not available in any other configured APT repository than
         our custom APT one: i2p, i2p-router, libjbigi-jni, tails-iuk, tails-perl5lib,
         tails-persistence-setup, whisperback
      
       * packages that have newer version, in our custom APT repo, than the ones in
         other APT repositories pinned to 990 (Debian Jessie): lib*-mesa*, libgbm1,
         libxatracker2
      
      ... the idea being to rely on sane defaults settings & behaviour as much as
      possible, and to encode only exceptions in this file.
      
      And regarding the packages we do explicitly pin here:
      
       * grub*: if 2.02~beta2-22+deb8u2 ever exists, it would be higher than our
         custom package, so we need to pin ours
      
       * onioncircuits, tails-installer: they are available from Debian
         (jessie-backports) as well, but for now let's always pull them from our
         custom APT repo; this might change some day, depending on the outcome of the
         discussion on #11361
      38fb2ddf
  20. 16 May, 2016 1 commit
  21. 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
  22. 11 Apr, 2016 1 commit
  23. 02 Apr, 2016 1 commit
  24. 25 Mar, 2016 3 commits
  25. 15 Mar, 2016 1 commit
  26. 14 Mar, 2016 1 commit
  27. 10 Mar, 2016 1 commit
  28. 12 Feb, 2016 1 commit
  29. 11 Feb, 2016 1 commit
  30. 24 Jan, 2016 1 commit
  31. 11 Jan, 2016 1 commit