[chef] Re: Re: Re: Re: Vim problem with chef-zero and vagrant


Chronological Thread 
  • From: Anthony Kong < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Vim problem with chef-zero and vagrant
  • Date: Thu, 29 Jan 2015 13:13:16 +1100

Hi Julian,

I did not make my own vim package. I specify the package in Berksfile

# encoding: utf-8


cookbook "apt"
cookbook "python", {}
cookbook "vim", {}
cookbook "git", {}
cookbook "postfix", {}
cookbook 'sensu', '~> 2.3.0'
cookbook "uchiwa"


Chef version

$ chef -v
Chef Development Kit Version: 0.3.6


The vagrant plugin I am using 

$ vagrant plugin list
chef-zero (2.2.1)
vagrant-aws (0.6.0)
vagrant-berkshelf (4.0.2)
vagrant-cachier (1.2.0)
vagrant-chef-zero (0.7.1)
vagrant-omnibus (1.4.1)
vagrant-share (1.1.3, system)


My OS is OSX 10.10.1

The guest OS is "ubuntu/trusty64"

Cheers, Konga



Tony Kong


Don’t EVER make the mistake that you can design something better than what you get from ruthless massively parallel trial-and-error with a feedback cycle. That’s giving your intelligence much too much credit.

- Linus Torvalds


On Thu, Jan 29, 2015 at 12:25 PM, Julian C. Dunn < " target="_blank"> > wrote:
On Thu, 29 Jan 2015, Anthony Kong wrote:

DEBUG: Caught InvalidVersionConstraint. This means that a key in
value_for_platform cannot be interpreted as a Chef::VersionConstraint.

Can you post your vim/recipes/package.rb? What version of Chef are you using? What OS and version is the guest?

- Julian




Archive powered by MHonArc 2.6.16.

§