aboutsummaryrefslogtreecommitdiff
path: root/templates/Debian
AgeCommit message (Collapse)Author
2013-01-02Lookup next_release in template the same way we lookup next_codename.intrigeri
next_release was forgotten when next_codename was fixed.
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-06-18fix auto repo selectionmh
the actual repos are in real_repos as by default we have auto.
2012-06-08refactor things for >2.7mh
2012-06-05new style for 2.7mh
2011-10-06Add apticron.conf template for Debian sid.intrigeri
2011-10-06Add listchanges.conf template for Debian sid.intrigeri
2011-06-20Add preferences, listchanges, apticron templates for Debian Wheezy.intrigeri
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-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-03Remove pinning for backports on Squeeze.intrigeri
This is now done automatically by APT.
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-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-15Apply fix from 67dc9a22 to Squeeze template as well.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-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-08fix template missing <%- end -%>Micah 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-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-11-21Merge remote branch 'immerda/master'.intrigeri
Conflicts: README files/preferences templates/Debian/sources.list.deb-src.erb templates/Debian/sources.list.volatile.erb templates/Ubuntu/sources.list.backports.erb templates/Ubuntu/sources.list.deb-src.erb
2010-11-21Merge commit '1b0bc415977c1c8b49390e0cdb1361769e0fdbae'.intrigeri
Merging one more commit. Conflicts: files/preferences templates/Debian/sources.list.deb-src.erb templates/Debian/sources.list.volatile.erb templates/Ubuntu/sources.list.backports.erb templates/Ubuntu/sources.list.deb-src.erb
2010-10-25Change "brought to you" into "managed" in headersGabriel Filion
File headers are there to indicate that the files should not be touched directly on the server. By changing the first sentence to "This file is managed by Puppet", we reinforce the idea that it is already taken care of by something else. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2010-10-25Add $main_apt_sourceGabriel Filion
Currently, it's either we use the default source that's hardcoded in the sources.list template or we redefine entirely this template. Make it easier to just change the URL of the apt source while using the rest of the default template by adding a $main_apt_source variable. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2010-10-25Add file headers for awareness of puppet presenceGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2010-10-17Bring in a bit of Ubuntu support from Nadir.intrigeri
2010-10-09removed backports template in favor of main sources.listnadir
2009-12-17Increased Ubuntu supportVarac