Jessie's d-i install defaulted to it being enabled until around the rc2->rc3 transition (cf. Debian #764982) so part of the fleet has it enabled.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | yuvipanda | T105720 Labs team reliability goal for Q1 2015/16 | |||
| Resolved | coren | T106479 Ensure that labstore machine is 'known good' hardware | |||
| Resolved | coren | T107038 Switch NFS server back to labstore1001 | |||
| Resolved | coren | T102478 labstore has multiple unpuppetized files/scripts/configs | |||
| Resolved | coren | T107574 Reinstall labstore1001 and make sure everything is puppet-ready | |||
| Resolved | faidon | T107507 Investigate whether to use Debian's jessie-backports | |||
| Declined | faidon | T108941 Make certain that jessie-backports is disabled fleetwide. |
Event Timeline
Comment Actions
::apt now always injects jessie-backports. That has been done on Nov. 11th by https://gerrit.wikimedia.org/r/#/c/252202/ c3888dcbe6e78c53c3f59bbb62e221d2f0fac1d8
apt: enable backports on Debian systems This enables backports across the fleet and relies on the default Debian policy for the apt priority for the repository (i.e. NotAutomatic/ButAutomaticUpgrades). Suffice to say, packages from jessie-backports should be used with care, as they may change to a newer version at any point.
The task was T107507: Investigate whether to use Debian's jessie-backports and now ::apt has:
# enable backports for Debian systems if $::operatingsystem == 'Debian' { apt::repository { 'debian-backports': uri => 'http://mirrors.wikimedia.org/debian', dist => "${::lsbdistcodename}-backports", components => 'main non-free contrib', comment_old => true, } }
So I guess this task is obsolete.