On 10/07/2012 11:28 PM, Sandra Schlichting wrote:
I know for that practice, but the problem is that it makes upgrade from
samba to samba3x packages a problem. So I would rather avoid that with
the puppet. And if you know how to add puppetlabs repo to yum, then
you'll know how to choose what version repo to use. Just take a look at
postgresql repositories.
I would very much like how to do that, as it seams to me that "yum
versionlock" locks the current installed package from being upgraded,
which is not really what we want =)
We want that puppet-2.7.* and puppet-server-2.7.* can be upgraded.
Currently the only way I know is to make your own repositories... We
we're chatting about what policy should puppetlabs adopt, and not how to
solve the current problem.
Currently the only way is to go with ensure => present + versionlock,
and to manually change the lock when new version is out :(
--
Jakov Sosic
www.srce.unizg.hr
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
