On 06/15/2013 12:06 AM, Andres Olarte wrote: > I have an installation that I'm trying to manage with puppet. For some > of the packages we want to have very tight control over the versions. > Since they are critical to our application, we only upgrade them after > testing in our test environment, and we schedule upgrades during low > traffic times. I don't want puppet to upgrade my database whenever a new > package appears. I specified the version in my puppet manifest to > prevent the package from automatically upgrading, however when I went to > generate another instance using the same config, that version of the > package was gone from the Ubuntu repo. Only the more recent ones are there. > > For some of the packages, I've been packing them myself into my own > repo, however packaging the database (postgresql) has proven too be too > much overhead. > > Any solutions or ideas?
You can keep local copy of ubuntu repos, which you could update only when you choose to, or you can have your own local repo in which you will copy only postgresql related pacakges (if it's only postgresql which is being a problem). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
