From f51b6d0708ee8baa221ffa3a596e9ee6acc6255e Mon Sep 17 00:00:00 2001
From: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sun, 5 Jan 2014 15:27:20 -0800
Subject: [PATCH] Lock to log4r < 1.1.11 because we got fucked

1.1.11 was released today and seriously broke backwards compatibility.
While they never officially made any promise to follow semver, it is
almost expected at this point, but log4r decided to just fuck that.

1.1.11 changed the arity of Log4r::Logger.initialize. That seriously
breaks _everything_.

Darwin awarddddddddd goes to...
---
 vagrant.gemspec | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vagrant.gemspec b/vagrant.gemspec
index 6c2a1ae28..f720fb50b 100644
--- a/vagrant.gemspec
+++ b/vagrant.gemspec
@@ -17,7 +17,7 @@ Gem::Specification.new do |s|
   s.add_dependency "childprocess", "~> 0.3.7"
   s.add_dependency "erubis", "~> 2.7.0"
   s.add_dependency "i18n", "~> 0.6.0"
-  s.add_dependency "log4r", "~> 1.1.9"
+  s.add_dependency "log4r", "~> 1.1.9", "< 1.1.11"
   s.add_dependency "net-ssh", ">= 2.6.6", "< 2.8.0"
   s.add_dependency "net-scp", "~> 1.1.0"