gistfile1.txt

>>vagrant provision
the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
falling back to ffi which might work (or might not, no promises)
==> default: Loading Berkshelf datafile...
....
All good...in the run... I think


Is this normal? Same happens on 
>>vagrant up.
   SAME AS ABOVE.
>>chefck
ruby 2.1.4p265 (2014-10-27 revision 48166) [x86_64-darwin12.0]
Vagrant 1.7.2
omnibus (4.0.0)
parseconfig (1.0.6)
vagrant-aws (0.6.0)
vagrant-berkshelf (4.0.3)
vagrant-bindfs (0.4.0)
vagrant-chef-zero (0.7.1)
vagrant-lxc (1.1.0)
vagrant-ohai (0.1.11)
vagrant-omnibus (1.4.1)
vagrant-proxyconf (1.5.0)
vagrant-serverspec (1.0.1)
vagrant-share (1.1.3, system)
vagrant-vbguest (0.10.0)
vagrant-vmware-fusion (3.2.5)
Updating installed plugins...
All plugins are up to date.
Chef Development Kit Version: 0.4.0
Chef: 12.0.3
Test Kitchen version 1.3.1
>>brew list
ansible		bison		docbook		git		lastpass-cli	libxml2		pidof		ruby-build	tree
apple-gcc42	boost		docker		git-flow	lft		libxslt		pinentry	s3cmd		unixodbc
asciidoc	boot2docker	ec2-api-tools	gmp		libevent	libyaml		pkg-config	scala		wemux
autoconf	brew-cask	erlang		gnupg		libgpg-error	maven		protobuf	shellcheck	wget
automake	cabal-install	fig		go		libksba		mercurial	pstree		sphinx		wxmac
awscli		cmake		fortune		htop-osx	libpng		mysql		python		sqlite		xz
bash		cowsay		gdbm		icu4c		libtiff		node		python3		ssh-copy-id
bind		curl		ghc		jpeg		libtool		openssl		readline	tmux

test