Created attachment 178578 [details] rubygem-winrm-fs 0.3.2 Upgrade gem due to recent update of logging rubygem. Fixes recent problem with sysutils/vagrant not functioning.
The latest version of the winrm-fs gem is 1.0.1. Are you sure you don't want to update to that version? If vagrant won't work with that one, we can always create a port for the 0.3.x version of winrm-fs. And we can test if vagrant works with the winrm-fs 1.0.1 by patching it, and add that to the vagrant port if so.
It may not be worth the effort of creating different ports for this. To the best of my knowledge, Vagrant is the only port that uses this rubygem. As for the version, an upgrade beyond this minor revision would introduce a number of other port upgrades that may introduce instability in Vagrant.
(In reply to joe from comment #2) True, we'd have to update rubygem-winrm, but I notice the latest version of that (2.1.1) supports a newer rubygem-ntlm and drops the requirement for rubygem-uuidtools, while adding a requirement for rubygem-erubis, but we already have a port for that so that's not an issue. So if we patch vagrant to work with the newer winrm-fs and winrm and it works, that would seem like a good idea.
After looking a bit more, I see these issues: https://github.com/mitchellh/vagrant/issues/7526 https://github.com/mitchellh/vagrant/pull/8102 particularly: Due to the above, winrm-fs is orders of magnitude faster and more reliable But it looks like until the next version is out, we have to wait. So I'll go ahead and commit this for now.
The files/patch-gemspec for sysutils/rubygem-winrm-fs can be removed here, correct?
Sorry, the "files/patch-gemspec" should be removed. (Turns out that it is not present in my own repository.)
Updated to 0.3.2 in r430749. Thanks!