aboutsummaryrefslogtreecommitdiff
path: root/manifests
AgeCommit message (Collapse)Author
2012-08-22parameterize the apt::proxy_client classMicah Anderson
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-06-18Make apt::preferences_snippet support Puppet < 2.7 again, when the 'package' ↵intrigeri
parameter is not set. Details: https://labs.riseup.net/code/issues/3467 https://labs.riseup.net/code/issues/3468
2012-06-18fix relations and finally get rid off config_filemh
2012-06-18get rid off config_file wrappermh
2012-06-14migrate away from hiera stuffmh
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-08refactor things for >2.7mh
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-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-15Merge remote-tracking branch 'shared/master'mh
Conflicts: README
2012-04-11use correct references for new concat usagemh
2012-04-11use the correct namemh
2012-04-11migrate concatenated_file to the concat modulemh
2012-04-09Force an apt-get update when changing an apt::sources_listGabriel Filion
sources_list doesn't currently force puppet to run 'apt-get update' after creating/modifying/removing files in sources.list.d. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-04-09Refactor: manage .d directories when using sources_list and apt_confGabriel Filion
The .d directories are only managed by the main 'apt' class. However, both 'sources_list' and 'apt_conf' defines depend on those directories. So in practice, the defines have an implicit need for those directories to be somehow managed. Let's turn this into an explicit relation, and include the directories in the defines. This makes it possible to use both defines without having to include the main 'apt' class. (maybe when using puppet apply?) Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2011-08-05use correct references for new concat usagemh
2011-08-05use the correct namemh
2011-08-05migrate concatenated_file to the concat modulemh
2011-06-05fix unattended upgradesmh
as we use $lsbdistcodename as source we cannot name the sources which should be used to update "stable". -> Fix it by deploying a per lsbdistcodename configfile. This can also be used as a pre- work for the #2681 shared modules bug.
2011-04-25Revert "apt::custom_sources_template to deploy custom sources.list.d/xyz.list"intrigeri
This reverts commit 3c0499b78d1f671fcce13127ef14b1b662a48c5a. This was already provided by sources_list.pp.
2011-04-02Possibility to delpoy release related config fileroot
2011-04-02Merge branch 'master' of git://labs.riseup.net/shared-aptroot
2011-02-18apt::cron::dist-upgrade: silently keep old version of conffiles.intrigeri
This makes this class' behaviour consistent with the apt::dist_upgrade one and prevents stalled upgrades due to dpkg asking questions to a dumb robot.
2011-02-16Merge branch 'master' of git://labs.riseup.net/shared-aptroot
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-15Fix 5237f9da.intrigeri
2010-12-15Merge remote branch 'riseup/master'intrigeri
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-11Allow running cron-apt more than once a day.intrigeri
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-17 20:00:03 +0000