aboutsummaryrefslogtreecommitdiff
path: root/manifests/apticron.pp
AgeCommit message (Collapse)Author
2015-05-11Replace debian_*() parser functions with factsJerome Charaoui
* Removes dependency on lsb-release and/or Facter >1.7 (values are based on $::lsbdistcodename, when available) * Simplifies maintenance: only lib/facter/util/* require updates as new releases are made Caveats: * apt::codename is removed; to override debian_* facts, set the FACTER_debian_codename environment variable for puppet * If tracking unstable, make sure lsb-release is installed, as other methods can't tell between testing and unstable
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
2012-06-14migrate away from hiera stuffmh
2012-06-05new style for 2.7mh
2010-12-08fix confusion over lsbrelease / lsbdistcodenameMicah Anderson
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)