-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rsync folders by Vagrant core code #66
Conversation
So I was able to build the plugin forcing a v1.5.0 and (v1.5.2), and install it into vagrant 1.5.2, but I get an internal error when I try to bring up a machine. Not sure where to look next.
|
I have Windows on my host system, so that's not so easy to test NFS-related issues. |
Matt, |
Hey Michael, I only build your gem and ran my standard machine up. I haven't had a Cheers, On Thu, May 22, 2014 at 9:41 AM, Michael Kuzmin notifications@gh.neting.ccwrote:
|
I've tested this on Mac OS host. It looks like this issue is out of scope of my pull request, but I've reproduced your error, and going to fix it. |
Had to guess at a spec that was failing, but I don't know why it didn't fail without your changes. Happy to hear a suggestion if it's wrong. Thanks. |
As I said, my PR implements RSync, but supporting NFS requires additional code. |
Vagrant 1.5 introduced a common logic for folder synchronization for all plugins (Rsync Synced Folders).
RSync-related code is now moved into Vagrant core, and maintained by Mitchell directly.
In vSphere plugin we need to get new bugfixes, for example hashicorp/vagrant#3804.
So duplicated and outdated Rsync-related code is removed, and inherited from Vagrant core.
Additionally I raise a requirement for minimal compatible Vagrant version to 1.5.