aboutsummaryrefslogtreecommitdiff
path: root/README
AgeCommit message (Collapse)Author
2015-04-17Document unattended_upgrades class parametersGabriel Filion
2015-04-17Add parameter for blacklisting a list of packages.Gabriel Filion
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.
2015-02-07Merge remote-tracking branch 'shared/master' into feature/squeeze-ltsintrigeri
2015-02-07Add support for Squeeze LTS.intrigeri
2014-12-06rephrase documentation of option .listGabriel Filion
as suggested during review
2014-12-06Update the README to show that .list is optional for sourcesGabriel Filion
2013-12-08Adapt documentation to take into account we haven't been supporting Lenny ↵intrigeri
for more than a year.
2013-12-08Drop Debian Etch and Lenny compatibility.intrigeri
Both have been unsupported for ages.
2013-07-27Make custom_sources_list into a class paramterGabriel Filion
and thus remove the last global variable.
2013-06-25Make custom_key_dir a class parameter and not a global variableSilvio Rhatto
Conflicts: manifests/init.pp
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-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-18updated README to explain $apt_disable_updatenadir
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
2012-09-20Precision on file name format in preferences.d directoryGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-09-20Some stylistic corrections in manifest examples in the READMEGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-09-20Make apt::preferences_snippet place files in /etc/apt/preferences.dGabriel Filion
Since Debian Squeeze, apt supports a .d directory for preferences (pinning). Simplify management by just placing files inside this .d directory. This removes the need for concat and concat::fragment resources, so removes the dependency on the concat module. It also removes the need for a moduledir that was needed for the concat module magic, so we also get rid of the dependency on the common module. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-08-22Add upgrade notices about the changes to parameterized classes; add a ↵Micah Anderson
Requirements header; move things that used to be called variables into the appropriate parameterized class section
2012-08-16Merge remote-tracking branch 'shared/master'mh
Conflicts: README manifests/dist_upgrade/initiator.pp manifests/init.pp manifests/preseeded_package.pp manifests/unattended_upgrades.pp
2012-08-08update README to reflect the requirement of the lsb moduleMicah Anderson
2012-06-08Allow passing arbitrary Pin value to apt::preferences_snippet.intrigeri
Closes: Redmine#3467.
2012-06-08Support multiple APT preferences snippets for the same package name pattern.intrigeri
This is implemented by adding a "package" parameter to apt::preferences_snippet, so that define names can be kept unique while the package names are not necessarily. Closes: Redmine#3468.
2012-06-08Migrate - in class names to _mh
In newer puppet releases the old way to name class/modules with a -, won't anymore be supported. Conflicts: manifests/unattended_upgrades.pp
2012-06-05new style for 2.7mh
2012-04-21Apply GPL-v3 licenseGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-04-15Migrate - in class names to _mh
In newer puppet releases the old way to name class/modules with a -, won't anymore be supported.
2012-04-11Fix formatting.intrigeri
2012-04-11Depend on our shared concat module rather than ripienaar's one.intrigeri
Most of us are likely to use and test against the former.
2012-04-11use correct references for new concat usagemh
2012-04-11migrate concatenated_file to the concat modulemh
2011-04-14README fix - we should use template not an urlmh
2011-02-07Starting from Squeeze, Debian Volatile is deprecated in favor of ↵intrigeri
CODENAME-updates. Take this into account in the Debian sources.list template: - go on using volatile.d.o for <= Lenny sources lines - start using CODENAME-updates for Squeeze and newer. Reference: http://lists.debian.org/debian-volatile/2011/01/msg00008.html
2010-12-16New class: apt::dist_upgrade::initiator.intrigeri
This implements the "update initiator" pattern suggested by http://projects.puppetlabs.com/projects/puppet/wiki/Debian_Patterns. This feature is useful when one does not want to setup a fully automated upgrade process but still needs a way to manually trigger full upgrades of any number of systems at scheduled times.
2010-12-16New class: apt::dist_upgrade.intrigeri
2010-12-15Fix 5237f9da.intrigeri
2010-12-15Repair Exec['update_apt'] to run apt-get update when needed.intrigeri
Move this Exec to a dedicated class that is not included by default i.e. we default not to "apt-get update" on every Puppet run. We now make use of this class in the apt::upgrade_package define to make sure APT indexes are up-to-date before attempting package upgrades. One may now use the following to ensure current packages are installed by Package resources: include apt::update Package { require => Exec[apt_updated] }
2010-12-11Allow running cron-apt more than once a day.intrigeri
2010-12-11New class: apt::reboot_required_notifyintrigeri
This class installs a daily cronjob that checks if a package upgrade requires the system to be rebooted; if so, cron sends a notification email to root.
2010-12-11Fix formatting.intrigeri
2010-12-09removed bit from README that is no longer trueMicah Anderson
2010-12-08add apt-listchanges support. this is a nice compliment to using the ↵Micah Anderson
upgrade_package functionality, because you get an email when the package has been upgraded.
2010-12-08add apticron support.Micah Anderson
Why apticron, when we have cron-apt already? Some people have different preferences, we use apticron along with the upgrade_package functionality in this module. I know someone who uses cron-apt to run the upgrades, but apticron for notifications, because apticron's notifications are much nicer (cron-apt just gives you the output of apt-get upgrade)
2010-12-07multiple sources for templates are not allowed (see #1818), so revert it to ↵Micah Anderson
a single source referenced by the README, and clarify the README to indicate how you can pass the preseed contents directly
2010-12-07update apt::preseeded_package template sources to use $lsbdistcodename ↵Micah Anderson
instead of $debian_release, also expand it to allow for site-apt sources
2010-12-07README update: minor typo fixMicah Anderson
2010-12-07README update: clarify that the debian-archive-keyring is managed alreadyMicah Anderson
Just so people are clear that they do not need to specify a $custom_key_dir to manage the debian archive keyring, I've added some clarifying text so you know that this is not necessary