On Apr 16, 9:52 pm, Paul Hinze <[email protected]> wrote: > I've run into this too, and worked around it by considering > ruby-shadow as a "prerequisite" for puppet, and therefore taking > responsibility for that package up to my bootstrapping scripts. IOW, > it is one of the short list of packages that need to be there for > puppet to run successfully. In my case, that means adding it to a > Debian pre-seed config. > > I'd be curious to know if there's any other way to work around > provider dependencies like these in a cleaner way though.
probably what I am going to end up doing as well. in my cause just add to my anaconda list (for physical and VMware based machines) or to my openVZ post deployment. -- 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.
