| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
the rationale of this is that isn't useful for third party modules,
because they cannot inject keys in there without some serious apt
class hijacking
|
|
|
|
unattended-upgrades is run on a daily base by cron, no need to force
an `apt-get update` after changing this file.
|
|
unattended-upgrades is installed
|
|
|
|
wheezy and newer the default
|
|
This functionality was lost because we stopped using a source file for
the 50unattended-upgrades file that would previously let one override
the configuration per release or per host.
|
|
|
|
This combines all files into one template. It should make maintenance
easier.
|
|
Without this, $common::moduledir::module_dir_path is empty.
|
|
Conflicts:
templates/Debian/sources.list.erb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and thus remove the last global variable.
|
|
|
|
This gets us fixes for the unattended_upgrades in wheezy, as well as the custom_key_dir class parameter replacement of the global variable
Conflicts:
manifests/unattended_upgrades.pp
|
|
|
|
|
|
Conflicts:
manifests/init.pp
|
|
unattended_upgrades.pp
|
|
modules/apt/manifests/preferences_snippet.pp:16 is deprecated. For more information, see http://docs.puppetlabs.com/guides/scope_and_puppet.html. To see the change in behavior, use the --debug flag.
|
|
|
|
The backports are now fully integrated with the main archive.
See:
https://labs.riseup.net/code/issues/4270
https://lists.debian.org/debian-devel-announce/2013/03/msg00007.html
|
|
This brings no behaviour change yet, but will allow to set class parameters'
default value depending on system facts.
|
|
This reverts commit 7e8113b3fcf6f251ca9d5e2f39f43fd024058c97.
see https://leap.se/code/issues/1990 for the miserious details.
|
|
|
|
|
|
|
|
preferences snippet.
The problem I'm facing is that the sanity checks prevent one from
using a simple:
apt::preferences_snippet { "bla": ensure => absent }
So, first set a default value for the `priority' parameter, so
that it's not required anymore. Second, add a sanity check to
error out when priority is not set, to get the safe old behaviour.
Then, wrap all sanity checks about arguments within
a "if $ensure == 'present'" block.
|
|
Before, including apt::unattended_upgrades on a host without
the unattended-upgrades package would fail on the first run,
because the module tries to install the package before apt is
finally configured.
This commit does:
- introduce the option $refresh_apt for apt::apt_conf
(Defaults to true). Can be used to not trigger Exec['refresh_apt']
- install the unattended-upgrades package after a final
Exec['refresh_apt']. To not run into a loop, it calls
Apt_conf['50unattended-upgrades'] with the option
refresh_apt => false, which is also not needed for the configuration
|
|
Else, the sanity checks prevent one from using a simple
apt::sources_list { "sid.list": ensure => absent }
|
|
Conflicts:
files/lenny/50unattended-upgrades
|
|
|
|
We do want to see \n expanded in this string.
|
|
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
+ more linting by intrigeri.
Conflicts:
manifests/apticron.pp
manifests/cron/dist_upgrade.pp
manifests/cron/download.pp
manifests/dist_upgrade/initiator.pp
manifests/init.pp
manifests/listchanges.pp
manifests/preferences.pp
manifests/preseeded_package.pp
manifests/proxy_client.pp
manifests/unattended_upgrades.pp
manifests/update.pp
|
|
Have the codename class parameter default to $::lsbdistcodename, and derive
$release from it.
|
|
|
|
Conflicts:
README
manifests/cron/dist_upgrade.pp
manifests/cron/download.pp
manifests/init.pp
manifests/preferences.pp
|
|
|
|
|
|
|
|
apt::disable_update if false
|
|
because the module
looks for a template based on the $lsbdistcodename, so you get this error:
Could not find template 'apt/Debian/preferences_n/a.erb'
The slash in 'n/a' appears to be a path (confusing!)
So I've set an error message when 'n/a' is encountered, encouraging the user to set the $lsbdistcodename.
I was not confident in the idea of pointing any occurrence of 'n/a' to the sid
templates, as I could imagine a case where this might occur on a non-sid system
where the lsbdistcodename isn't properly detected
|
