Current ebuild for vagrant has the following code snippet: # remove windows-specific gems sed -e '/wdm\|winrm/d' \ -i ${PN}.gemspec || die Meanwhile, support for WinRM implemented as a pure Ruby library and works perfectly in Linux with Windows guests. I've just create a Windows 10 box with "winrm" communicator and `vagrant up` works pretty fine for me. Unfortunately there is no dev-ruby/winrm package, so I have to install it manually as described here: http://stackoverflow.com/questions/35016414/vagrant-up-fails-with-cannot-load-winrm $ vagrant plugin install winrm --plugin-version 1.8.1 $ vagrant plugin install winrm-fs Sample output from `vagrant up`: ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 5985 (guest) => 55985 (host) (adapter 1) default: 5986 (guest) => 55986 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:55985 default: WinRM username: ci.builder default: WinRM execution_time_limit: PT2H default: WinRM transport: plaintext ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: Mounting shared folders... default: /vagrant => /work/vagrant/ci-base Reproducible: Always
Hello Alex, thanks for the notice, I haven't noticed this change. Would you like to proxy maintain dev-ruby/winrm?
(In reply to Tomáš Mózes from comment #1) > Hello Alex, thanks for the notice, I haven't noticed this change. > > Would you like to proxy maintain dev-ruby/winrm? what does it mean "proxy maintain" ? %) unfortunately I don't know Ruby well enough to make dev-ruby/winrm and dev-ruby/winrm-fs by myself... it is why I've just added this issue. (actually I can... using say some other ruby gen ebuild as a skeleton, but if smth went wrong ... unlikely I can resolve it... and trying to install `winrm` w/o version specification (i.e. 1.8.1, meanwhile the current is 2.x.smth), I'm really in doubt that I can handle this %()
> what does it mean "proxy maintain" ? %) https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers You can try to build up your ebuild and the gentoo devs in the proxy maintainers project can add it to the tree. You can also consult with Gentoo ruby on IRC: https://wiki.gentoo.org/wiki/Project:Ruby At worst it won't be added to the tree, but I'm sure together we can do it :)
Since I don't use it and honestly I'm not interested in maintaining that ruby library, I'm closing this until dev-ruby/winrm* is added to portage. Then we can add support to vagrant.
