diff options
| author | Jerome Charaoui <jcharaoui@cmaisonneuve.qc.ca> | 2015-06-09 15:49:02 +0000 |
|---|---|---|
| committer | Jerome Charaoui <jcharaoui@cmaisonneuve.qc.ca> | 2015-06-09 15:49:02 +0000 |
| commit | 58cfaa32f9de6c38157b2680fbf59da400b8f940 (patch) | |
| tree | af25c8c3452824cb04aed781a715db871c98ba18 /lib | |
| parent | 87bfb868d7625100086a26a81743f5adbabbb988 (diff) | |
| parent | d87876a16fdf6cb710210b1a11572d553dec755a (diff) | |
| download | puppet-apt-58cfaa32f9de6c38157b2680fbf59da400b8f940.tar.gz puppet-apt-58cfaa32f9de6c38157b2680fbf59da400b8f940.tar.bz2 | |
Merge branch 'volatile-backports' into 'master'
allow disabling backports (and volatile in ubuntu)
as the module stands now, there's no way to disable backports.
there are a few reasons why we want to allow this:
* "tools, not policy" - if Debian doesn't ship with backports enabled by default, why should we change that policy?
* too many sources.list entries can cause problems on `apt-get update`, which can run out of memory and require special config
* if the pinning fails, some packages may be updated by mistake
* even if pinning works, some may *want* to keep admins from installing anything from backports as a policy
this keeps backports installed by default (begrudgingly) however. it just allows disabling it.
it also allows disabling volatile in ubuntu, which wasn't possible before.
See merge request !16
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions