Hi,
linux-headers-server are metapackage. They always point to the latest real
package, eg linux-headers-2.6.32-41-server
That will cause puppet to always update the package to the latest version.
To prevent that, always refer to specific package name, eg.
linux-headers-2.6.32-41-server , not metapackage linux-headers-server
2012/4/25 Juan José Presa Rodal <juan...@gmail.com>
> Hi, I've defined this module:
>
> package {['build-essential', "linux-headers-${kernelrelease}", 'dkms',
> 'linux-headers-server']:
> ensure => installed,
> }
>
> and when the package linux-headers-server it's upgraded in the
> repositories puppet tries to upgrade in client too. And as that package has
> a dependency with latest kernel also upgrade it.
>
> I'm defining ensure => installed, not ensure => latest
>
> Anyone has experienced this, or similar, behaviour?
> Thanks in advance.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/06vr9dljjZkJ.
> 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.
>
--
Sharuzzaman Ahmat Raslan
--
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.
