On 01/12/2011 11:30 AM, Sven Sporer wrote:
> Hi, I have a simple use case, but can't get the dependency resolution
> to work on first run. This is not critical, but I want to understand
> what's going on. Here's the szenario:
>
> * puppet --version: 2.6.4
> * on the bare system, I have vim 6.4 installed (no vim-base)
> * I first want to upgrade to the latest version in repo, which is 7.1,
> * and then install vim extensions for 7.1 (vim-enhanced, vim-data)
>
> My definition:
>
> class packages::vim {
> $addons = ["vim-enhanced.x86_64", "vim-data.x86_64"]
>
> package { "vim.x86_64":
> ensure => latest,
> require => Class["yum::repos"],
> before => Package[$addons],
> }
>
> package { $addons:
> ensure => present,
> }
> }
>
> The agent complains that vim-base-7.1 is not compatible with the
> installed vim-6.4 (vim-base is needed for the addons). This would not
> be a problem if the vim would be updated to 7.1 "before".
>
> (* I run puppet agent --test to see what happens on every run)
> * So, this fails on first run.
> * On second run, vim updates from 7.1 and installs $addons.
> * Sometimes, a third run is needed to install the $addons.
>
> From the command line, a "yum update vim" shows the following
> dependencies:
> * updating: vim => 7.1
> * installing for dependencies: vim-base => 7.1
>
> So, vim-7.1 has vim-base-7.1 as dependency, which is not compatible
> with the installed vim-6.4. Should I include a package vim-base in the
> manifest? Or is yum (2.4.2) wrong here?
>
So one of your dependencies has a conflict. Does yum not resolve this
for you automatically?
To play it safe, you could ensure the offending vim-6 related packages
be absent before installing vim7.
Cheers,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
