From: Hans-Christoph Steiner <hans@eds.org>
Date: Tue, 30 Aug 2016 20:56:06 +0000 (+0200)
Subject: buildserver: force a known-good version of chef
X-Git-Tag: 0.8~165^2~4
X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=b717271c6147731b5be611aed482a1757d6f9b0b;p=fdroidserver.git

buildserver: force a known-good version of chef

This forces the release channel and version of chef-solo to install on the
guest VM.  I was getting really massive, odd stacktraces without specifying
this, and chef is only used for Kivy now anyway.
---

diff --git a/buildserver/Vagrantfile b/buildserver/Vagrantfile
index a7b1745f..3e04fbc1 100644
--- a/buildserver/Vagrantfile
+++ b/buildserver/Vagrantfile
@@ -49,6 +49,8 @@ Vagrant.configure("2") do |config|
     args: [configfile['debian_mirror']]
 
   config.vm.provision :chef_solo do |chef|
+    chef.channel = "stable"
+    chef.version = "12.10.24"
     chef.cookbooks_path = "cookbooks"
     chef.log_level = :debug
     chef.add_recipe "kivy"