Provisioning fails about trellis

[starise]

Looks like the same dependency problem i'd here: #8
Try to use this command in the guest (using vagrant ssh):

sudo apt-get install -f

then restart provisioning using vagrant provision

[mwalters]

Thanks @starise this got me going in the right direction to get past this. I actually had to vagrant halt then vagrant up again, and then was able to vagrant ssh and run sudo apt-get install -f then exit out of SSH and run vagrant provision and it finally got it to provision correctly. Would definitely be nice to not have to do the extra steps though. Figured I'd leave my comment in case someone else comes across here with the same problem though.

[swalkinshaw]

@mwalters @starise @ionutzp would be helpful to know if you're using the latest version/commit of this playbook. And also if you're using the (now) default base of roots/bedrock, or a default Ubuntu 14.04 Trusty, or the old Ubuntu 12.04.

Also what host you're running Ansible from (Linux or OSX) or if you're using it within a shell script from Windows.

[mwalters]

@swalkinshaw Sorry for the lack of detail in my previous post, hope this helps:

• I'm using OSX
• I just installed for the first time today, so I cloned the repository around 1-2 hours ago. Only changes I made to it were for setting the domain to testing.dev. I'm going super vanilla with this and the roots/bedrock repo just to learn how it works before I try implementing it.
• I am using roots/bedrock for the default base box.

Not sure if it would help/matter, but I am on Vagrant 1.6.1. I also had to install Ansible on the host machine to get this all working, so that was just installed today as well and is on version 1.6.1.

When I initially ssh'd in to the VM to run sudo apt-get install -f I noticed it was saying a system restart was required, so that's why I halted and re-up'd. After the box came back up I tried to reprovision it before SSH'ing in, in case that fixed it, but it failed with the same error that @ionutzp mentions above. I then ssh'd in, ran the apt-get install, and then was able to successfully provision.

[ionutzp]

same as @mwalters here: osx, latest version, default roots/bedrock box

[swalkinshaw]

This was a fairly dumb error looking back. Fixed as of a5962e9 and I also published a new 0.2.0 version.

apt-get upgrade was being run by default as part of the provision but it shouldn't be because it causes errors like this as packages get upgraded to different versions and could cause conflicts. Basically the goal of any project like this should be to have consistent/deterministic package states and upgrading them breaks that.