aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2011-02-06Update debian_release function since Squeeze has been released.intrigeri
2011-01-29updated Ubuntu preferences to include security + updatesvarac
2011-01-23preferences.pp for ubuntu maverickvarac
2011-01-09apt::custom_sources_template to deploy custom sources.list.d/xyz.listnadir
2011-01-08Make sources snippets world-readable.intrigeri
Not doing this breaks big parts of functionality, such as aptitude why.
2010-12-18add -q to the apt-get invocation in upgrade_package.pp, also switch to using ↵Micah Anderson
-y instead of --force-yes. this way we are acting in the same way as the dist_upgrade class
2010-12-18switch aptitude to apt-get, since aptitude will sometimes automatically do ↵Micah Anderson
things that are unrelated to the task at hand, such as deinstalling automatically installed packages, which can be undesirable behavior
2010-12-16Fix apt::upgrade_package when used multiple times.intrigeri
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-15Apply fix from 67dc9a22 to Squeeze template as well.intrigeri
2010-12-15Fix 5237f9da.intrigeri
2010-12-15Merge remote branch 'riseup/master'intrigeri
2010-12-15fix apticron templateMicah Anderson
2010-12-15change $listchanges_* to $apt_listchanges, not nice to clutter up the ↵Micah Anderson
namespace like that
2010-12-15Fix packages dependency.intrigeri
2010-12-15Use line define instead of append_if_no_such_line.intrigeri
The latter is only a wrapper around the former and it seems we want to remove the latter from our shared common module.
2010-12-15apt::upgrade_package: explicitly depend on needed packages.intrigeri
This define was previously broken unless dctrl-tools and apt-show-versions were installed.
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-14(ugly workaround warning) Update packages lists before upgrading a package.intrigeri
... because Exec[update_apt] is currently never run since we set it refreshonly. Better solutions are being thought of, but in the meantime the least we can do is somehow repair apt::upgrade_package.
2010-12-14Make consistent the use of absolute path to apt-get.intrigeri
2010-12-14Factorize.intrigeri
2010-12-13apt::reboot_required_notify: take into account the random sleep time.intrigeri
2010-12-13Merge remote branch 'riseup/master'intrigeri
2010-12-12switch default frontend to 'mail' instead of pager, as most things are done ↵Micah Anderson
non-interactively
2010-12-12Additionally use version number in Lenny default pinning.intrigeri
Lenny's APT does not support pinning like this: Pin: release o=Debian,n=<%= codename %> We therefore switched (in commit ef2ebdffd) to: Pin: release o=Debian,a=<%= release %> With such a pinning setup, when Squeeze is released, systems using this module with $apt_use_next_release set to true would immediately switch to prefer packages from Squeeze. If an automated upgrade process is setup, they would be automatically upgraded to Squeeze. This does not sound safe to me, so let's use the release version number as an additional selection criterion to prevent upgrades to Squeeze to happen behind our back: Pin: release o=Debian,a=<%= release %>,v=<%= release_version %>* Note that the trailing '*' is intentional and necessary to match stable point-releases.
2010-12-11Bypass default APT proxy to access bugs.debian.org.intrigeri
This is needed when using apt-listbugs with an APT proxy that only {wants,can} proxy "normal" APT traffic.
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-11Merge remote branch 'riseup/master'intrigeri
2010-12-11Update comment: Squeeze's unattended-upgrades 0.62 still does not support ↵intrigeri
wildcards.
2010-12-09removed bit from README that is no longer trueMicah Anderson
2010-12-09fix compile syntax error in ubuntu sources.list, closes #2639Micah Anderson
2010-12-09Merge remote branch 'lelutin/master'Micah Anderson
2010-12-08fix syntax errorMicah Anderson
2010-12-08fix template missing <%- end -%>Micah Anderson
2010-12-08fix confusion over lsbrelease / lsbdistcodenameMicah 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-08provide an "03clean" alias for the 03clean_vserver to satisfy dependenciesMicah Anderson
2010-12-08fix typoMicah Anderson
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-07change the name of the custom_keys exec to be "custom_keys" instead of using ↵Micah Anderson
the alias metaparameter. the reason for this change was because the Exec override was not able to find the exec through its alias
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-07switch to archive name for lenny default preferencesMicah Anderson
the templates/Debian/preferences_lenny.erb file checked in with e2f80db7b76171e5945127e2fd42fb35043990fb contains pinning based on codename, which is not supported in lenny (see #433624 - if you look at the version graph, you see, "Fixed in version 0.7.21", and lenny has 0.7.20.2+lenny1.)
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
2010-12-07README update: clarify the site-apt preferences optionsMicah Anderson
The README described a few things that were not true relating to the apt/preferences file. First of all it said you could ship a 'file', but preferences.pp very clearly uses the 'content => $custom_preferences' parameter, which will not take file sources, only templates. Secondly, it seemed to imply that you could just drop the custom preferences into your site-apt and it would work. But you actually need to set the $custom_preferences to indicate the content source. Lastly, it said that you could specify a host-specific file in the site-apt module, but there is no facility for this (nor can you use files). Perhaps this is where this module is going eventually, once we have a preferences.d possibility? Until then, it makes more sense to have it reflect the current situation.
2010-12-07format standardizationMicah Anderson