• 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
preferences 3.15 KB