aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2011-08-26Merge branch 'master' of git://labs.riseup.net/shared-aptSilvio Rhatto
2011-08-26Backports have just 'main' sectionSilvio Rhatto
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-08-05Merge remote-tracking branch 'shared/master'mh
2011-06-20Add preferences, listchanges, apticron templates for Debian Wheezy.intrigeri
2011-06-07fixing unattended upgrademh
We should use the correct origin archive. Lenny is oldstable.
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-05-07Add empty line at the end of preferences templates.intrigeri
... else the first block added by apt::preferences_snippet is in the same paragraph as the last block provided by the template.
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-23Merge remote-tracking branch 'nadir/master'Micah Anderson
2011-04-23Merge remote-tracking branch 'immerda/master'Micah Anderson
2011-04-23Debian sources: don't use next release's backports.intrigeri
The APT pinning we ship does not support that, and this seems a bit too much of a corner case to me to deserve being supported out-of-the-box. Anyone willing to use current release + next release + next release backports (e.g. Lenny + Squeeze + squeeze-backports) can anyway do so using apt::sources_list and apt::preferences_snippet. https://labs.riseup.net/code/issues/2856 is the bug that triggered this change.
2011-04-14README fix - we should use template not an urlmh
2011-04-03Remove pinning for backports on Squeeze.intrigeri
This is now done automatically by APT.
2011-04-02Possibility to delpoy release related config fileroot
2011-04-02Merge branch 'master' of git://labs.riseup.net/shared-aptroot
2011-02-19Merge branch 'master' of git://labs.riseup.net/shared-aptSilvio Rhatto
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-02-14Merge branch 'master' of git://labs.riseup.net/shared-aptSilvio Rhatto
Conflicts: manifests/init.pp templates/sources.list.backports.erb
2011-02-14Fixing apt_base_dirSilvio Rhatto
2011-02-14Remove assert_lsbdistcodename requirementsSilvio Rhatto
2011-02-14Using the lsb moduleSilvio Rhatto
2011-02-14Debian Squeeze pinning: pin squeeze-updates as much as regular squeeze.intrigeri
The previous template was indeed ensuring no package from squeeze-updates could be easily or automatically installed.
2011-02-07Stop hard-coding Wheezy name in Squeeze's pinning template.intrigeri
Every needed function has been updated since Squeeze was released and we can thus use a nice generic template.
2011-02-07debian_nextcodename: take into account Squeeze was released.intrigeri
2011-02-07debian_release_version: add Squeeze's version number.intrigeri
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
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.