Closed nervo closed 5 years ago
Experiencing the same thing. Reverting back to vagrant 1.8.6 works. Can't tell if this is a vagrant issue or landrush 😕
Embedded ruby version looks like the same in vagrant 1.8.7 and 1.9.0: 2.2.5p319
Reproduced on Ubuntu 14.04 using vagrant 1.9.0 and landrush 1.1.2
Maybe related to this: https://github.com/vagrant-landrush/landrush/issues/295 ?
For now Landrush is not compatible with Vagrant 1.9.0. Vagrant 1.9.0 made quite some substantial internal changes, which we need to look into. Most importantly it does not rely on Bundler anymore.
I am about to release Landrush 1.2.0 which will make Landrush compatible with Vagrant up to 1.8.6, after that we will be looking into getting a Landrush release which aligns with Vagrant 1.9
Hi,
I'm experiencing the same issue, thanks for the time you put into maintaining this plugin which is cool but would be great to have some kind of visibility into the release of the 1.9 vagrant compatibility on vagrant-landrush side . thanks
I'm not 100% sure what (if any) of these steps fixed this issue, but I was able to get the warning to go away.
vagrant plugin repair
My thought it was the repair command but I can't know for sure. Hopefully that helps someone out.
I think this issue is out of date. The HEAD of Landrush is now on 2.1.4 and I am not able to reproduce this.
I have just tried to install landrush on a fresh vagrant 1.9.0 install on OSX 10.12.1 Nothings to notice in particular except "Building native extensions"
Right after, every vagrant command sends a warning...
... and daemon refuse to start
landrush.log is empty...