sftp-server has moved again in gentoo

[hedmo]

hi

today i was running vagrant-sshfs and it did not find /usr/lib/misc/sftp-server.
today in gentoo the sftp-server is in /usr/lib64/misc/sftp-server.i found the problem via #92
and manage to fix it via :

sudo ln -s /usr/lib64/misc/sftp-server /usr/lib/misc/sftp-server

regards hedmo

[gyakovlev]

gentoo vagrant maintainer here.
it did not move, but we no longer carry /usr/lib -> /usr/lib64 symlink so path no longer valid.

vagrant-sshfs/lib/vagrant-sshfs/synced_folder.rb

Lines 113 to 117 in 5cb3943

	ENV['PATH'] += ':/usr/libexec/openssh' # Linux (Red Hat Family)
	ENV['PATH'] += ':/usr/lib/openssh' # Linux (Debian Family)
	ENV['PATH'] += ':/usr/lib/ssh' # Linux (Arch Linux Family)
	ENV['PATH'] += ':/usr/lib/misc' # Linux (Gentoo Family)
	ENV['PATH'] += ':/usr/libexec/' # Mac OS X

since vagrant is only supported on x86_64 it's safe to assume
/usr/lib64/misc/ path on gentoo hosts, it's backwards compatible with old implementation.

there are users of custom filesystem layouts, but they are power users and know what they are doing.

[dustymabe]

Thanks @gyakovlev - I'll try to address this soon.

[hedmo]

@dustymabe how do i install it:

hedmo@mya51 ~ $ vagrant plugin install vagrant-sshfs-1.3.3
Installing the 'vagrant-sshfs-1.3.3' plugin. This can take a few minutes...
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations                                
or transient network issues. The reported error is:                                                

Unable to resolve dependency: user requested 'vagrant-sshfs-1.3.3 (> 0)

hedmo@mya51 ~ $`

[dustymabe]

I only did part of the release last night. Finished it up this morning. Try again :)

[hedmo]

@dustymabe

it is working but i am getting error messages :

hedmo@mya51 ~/proton $ vagrant up                       
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
Platform: 8 CPUs, 15961 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '2.0.6' is up to date...
==> debian10: Clearing any previously set forwarded ports...
==> debian10: Clearing any previously set network interfaces...
==> debian10: Preparing network interfaces based on configuration...
    debian10: Adapter 1: nat
==> debian10: Forwarding ports...
    debian10: 22 (guest) => 2222 (host) (adapter 1)
==> debian10: Running 'pre-boot' VM customizations...
==> debian10: Booting VM...
==> debian10: Waiting for machine to boot. This may take a few minutes...
    debian10: SSH address: 127.0.0.1:2222
    debian10: SSH username: vagrant
    debian10: SSH auth method: private key
==> debian10: Machine booted and ready!
==> debian10: Checking for guest additions in VM...
    debian10: The guest additions on this VM do not match the installed version of
    debian10: VirtualBox! In most cases this is fine, but in rare cases it can
    debian10: prevent things such as shared folders from working properly. If you see
    debian10: shared folder errors, please make sure the guest additions within the
    debian10: virtual machine match the version of VirtualBox you have installed on
    debian10: your host and reload your VM.
    debian10: 
    debian10: Guest Additions Version: 5.1.38
    debian10: VirtualBox Version: 6.1
==> debian10: Rsyncing folder: /home/hedmo/proton/ => /home/vagrant/proton
==> debian10:   - Exclude: [".vagrant/", "vagrant_share"]
The 'sftp-server' executable file can't be found on the host machine but
is required for sshfs mounting to work. Please install the software and 
try again.
hedmo@mya51 ~/proton $ vagrant up
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
Platform: 8 CPUs, 15961 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '2.0.6' is up to date...
==> debian10: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> debian10: flag to force provisioning. Provisioners marked to run always will still run.
hedmo@mya51 ~/proton $ vagrant ssh
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
NOTE: Gem::Specification.default_specifications_dir is deprecated; use Gem.default_specifications_dir instead. It will be removed on or after 2020-02-01.
Gem::Specification.default_specifications_dir called from /usr/lib64/ruby/gems/2.5.0/gems/vagrant-2.2.6/lib/vagrant/bundler.rb:428.
Platform: 8 CPUs, 15961 MB memory
Last login: Sun Jan  5 09:46:09 2020 from 10.0.2.2
vagrant@debian10:~$

[dustymabe]

hmm, not sure where that message is coming from? vagrant itself? Maybe you updated other plugins as part of the vagrant-sshfs update.