aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-06-25remove unnecessary before dependency on the /etc/apt/preferences file in ↵Micah Anderson
unattended_upgrades.pp
2013-06-20fix for the following: warning: Dynamic lookup of $custom_preferences at ↵Micah Anderson
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.
2013-05-26Merge branch 'master' into leapMicah Anderson
2013-05-03Wheezy was released!intrigeri
2013-03-20Use the main Debian archive's URL as the default URL for backports on Wheezy.intrigeri
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
2013-03-20Move apt class parameters to a ::params class.intrigeri
This brings no behaviour change yet, but will allow to set class parameters' default value depending on system facts.
2013-03-15Revert "deploy /etc/apt/preferences before File['apt_config']"varac
This reverts commit 7e8113b3fcf6f251ca9d5e2f39f43fd024058c97. see https://leap.se/code/issues/1990 for the miserious details.
2013-03-14deploy /etc/apt/preferences before File['apt_config']varac
2013-03-14apt keys: always deploy before Exec[refresh_apt], also with $custom_preferencesvarac
2013-03-05fix #4249: Ubuntu: wrong sources.list entriesvarac
2013-02-16Don't check for a package priority to be set when removing an APT ↵intrigeri
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.
2013-02-01Install unattended-upgrades after Exec[refresh_apt]varac
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
2013-01-30Merge remote-tracking branch 'remotes/shared/master'varac
2013-01-20added custom fact apt_runningvarac
2013-01-08Don't check for source / content to be set when removing an APT source.intrigeri
Else, the sanity checks prevent one from using a simple apt::sources_list { "sid.list": ensure => absent }
2013-01-08Merge remote-tracking branch 'leap/feature/unattended_upgrades' into reviewintrigeri
Conflicts: files/lenny/50unattended-upgrades
2013-01-03replace a missed Concat reference change with File['apt_config']Micah Anderson
2013-01-03lint READMEMicah Anderson
2013-01-03Add dependency back to the README.intrigeri
It was erroneously removed at some point, but this module still depends on the "common" one, at least for the time being.
2013-01-03Fix overzealous linting.intrigeri
We do want to see \n expanded in this string.
2013-01-02forgot ${distro_codename}-updates in 50unattended-upgrades fallbackvarac
2013-01-02Apply code style corrections from puppet-lintGabriel Filion
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
2013-01-02Simplify codename handling.intrigeri
Have the codename class parameter default to $::lsbdistcodename, and derive $release from it.
2013-01-02Lookup next_release in template the same way we lookup next_codename.intrigeri
next_release was forgotten when next_codename was fixed.
2013-01-02Remove duplicated settings, resulting from wrong merge.intrigeri
2013-01-02Fix README formatting.intrigeri
2013-01-02Finish updating README to reflect move to parameterized classes.intrigeri
2013-01-02Merge remote-tracking branch 'riseup/immerda_27_readme' into sharedintrigeri
Conflicts: README manifests/cron/dist_upgrade.pp manifests/cron/download.pp manifests/init.pp manifests/preferences.pp
2013-01-02Merge branch 'master' into issue_3953Gabriel Filion
2012-12-30Merge remote-tracking branch 'riseup/feature/http_debian_net'intrigeri
2012-12-30Merge remote-tracking branch 'riseup/feature/unknown_lsbdistcodename'intrigeri
2012-12-19exec{'apt_dist-upgrade'} just requires Exec['apt_updated'] if ↵nadir
apt::disable_update if false
2012-12-19Merge remote-tracking branch 'riseup/feature/unknown_lsbdistcodename'varac
2012-12-19Merge branch 'master' of git://labs.riseup.net/shared-aptvarac
2012-12-18On a sid system, $lsbdistcodename is reports 'n/a', this doesn't work ↵Micah Anderson
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
2012-12-18switch default $debian_url to use http.debian.net which is more accurate and ↵Micah Anderson
up-to-date than cdn.debian.net
2012-12-18comparing variabled should use double quotes (interestingly, it does work ↵nadir
with only one too)
2012-12-18updated README to explain $apt_disable_updatenadir
2012-12-18added $apt_disable_update to disable "apt-get update" during puppetrunsnadir
2012-12-16use codename instead of archive variable for Debianvarac
2012-12-16squeeze: use colon seperator to be able to include backport updates,varac
also force unattended upgrades
2012-12-16use oldstable for lenny, force unattended upgradesvarac
2012-12-16refactor 50unattended-upgrades default filevarac
The syntax is valid from v0.70 on (Debian Wheezy, Ubuntu Oneiric and later). It includes Unattended-Upgrade::Origins-Patterns both for Debian and Ubuntu, which even work on systems with both package sources enables. On Debian- or Ubuntu-only systems it doesn't hurt to have both Patterns included.
2012-12-16from Ubuntu oneiric (11.10) on, the 50unattended-upgrades default can be usedvarac
2012-12-1550unattended-upgrades: ubuntu quantal, symlink to precisevarac
2012-12-1550unattended-upgrades: ubuntu precise versionvarac
2012-12-1550unattended-upgrades: squeeze versionvarac
2012-12-1550unattended-upgrades: lenny versionvarac
2012-12-15Replaced fallback file for unattended-upgradesvarac
with a decent one for wheezy onwards. The main syntax shouldn't change, hopefully, from now on. It's a very basic generic one, that uses variables for Distribution/Codename and should apply to all coming distributions. Removed from the default 50unattended-upgrades ---------------------------------------------- - APT::Periodic::Update-Package-Lists "1"; - APT::Periodic::Unattended-Upgrade "1"; cause this is not something the unattended upgrades class should set by default. - APT::UnattendedUpgrades::LogDir "/var/log/"; - APT::UnattendedUpgrades::LogFile "unattended_upgrades.log"; Because we shouldn't change the default logdest by default, which is /var/log/unattended_upgrades/*. - Blacklist for linux-image*, because this we shouldn't blacklist packages by default.
2012-12-05fix for $lsbdistcodename regression introduced by ↵Micah Anderson
ac166366d7baa45b74e09974289d9fb2dad38e67 What happened here was the $codename = $::lsbdistcodename was removed from init.pp and replaced with just $::lsbdistcodename whereever $codename was used. Then in the sources.list.erb and preferences files things were changed like this: <pre>+### Debian current: <%= codename = scope.lookupvar('::lsbdistcodename') %> ... -deb <%= debian_url %> <%= codename %> <%= repos %> ... +deb <%= debian_url=scope.lookupvar('apt::debian_url') %> <%= codename %> <%= repos=scope.lookupvar('apt::repos') %> </pre> This meant that the codename was always set to lsbdistcodename, and you because in newer puppet versions you cannot assign a value to a top-level facter variable, it is not possible to change this. Because we cannot change $lsbdistcodename, we have to fix this by allowing the user to pass a different, non-top-level scoped variable to the class as a parameter, which defaults to $::lsbdistcodename, so that upgrades can be triggered. This is documented in the README in an upgrade notice