Package Details: vagrant-git 2.0.0.101.g52824f20b-1

Git Clone URL: https://aur.archlinux.org/vagrant-git.git (read-only)
Package Base: vagrant-git
Description: Build and distribute virtualized development environments
Upstream URL: https://vagrantup.com
Licenses: MIT
Conflicts: vagrant, vagrant-substrate, vagrant-substrate-git
Provides: vagrant
Replaces: vagrant-substrate, vagrant-substrate-git
Submitter: gtmanfred
Maintainer: None
Last Packager: jsteel
Votes: 6
Popularity: 0.000744
First Submitted: 2013-09-03 20:50
Last Updated: 2017-11-02 11:44

Required by (7)

Sources (2)

Latest Comments

1 2 3 Next › Last »

jsteel commented on 2017-11-02 11:44

Upstream have made some changes that means we can ditch the substrate layer and use system binaries/libraries. Please test and let me know of any issues.

zerathidune commented on 2017-10-28 19:31

There seems to be a missing dependency on libyaml. Without libyaml installed I get the following error:

==> Checking buildtime dependencies...
==> Retrieving sources...
-> Cloning vagrant git repo...
Cloning into bare repository '/home/isd/scratch/vagrant-git/vagrant'...
remote: Counting objects: 103007, done.
remote: Compressing objects: 100% (152/152), done.
remote: Total 103007 (delta 88), reused 17 (delta 5), pack-reused 102850
Receiving objects: 100% (103007/103007), 23.68 MiB | 1.39 MiB/s, done.
Resolving deltas: 100% (64572/64572), done.
==> Validating source files with md5sums...
vagrant ... Skipped
==> Extracting sources...
-> Creating working copy of vagrant git repo...
Cloning into 'vagrant'...
done.
==> Starting pkgver()...
==> Updated version: vagrant-git 2.0.0.101.g52824f20b-1
==> Starting build()...
/opt/vagrant/embedded/lib/ruby/2.3.0/yaml.rb:5:in `<top (required)>':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
/opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': libyaml-0.so.2: cannot open shared object file: No such file or directory - /opt/vagrant/embedded/lib/ruby/2.3.0/x86_64-linux/psych.so (LoadError)
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/vagrant/embedded/lib/ruby/2.3.0/psych.rb:7:in `<top (required)>'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/vagrant/embedded/lib/ruby/2.3.0/yaml.rb:6:in `<top (required)>'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems.rb:628:in `load_yaml'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/config_file.rb:327:in `load_file'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/config_file.rb:198:in `initialize'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/gem_runner.rb:75:in `new'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/gem_runner.rb:75:in `do_configuration'
from /opt/vagrant/embedded/lib/ruby/2.3.0/rubygems/gem_runner.rb:40:in `run'
from /opt/vagrant/embedded/bin/gem:25:in `<main>'
==> ERROR: A failure occurred in build().
Aborting...

jsteel commented on 2017-06-13 11:47

That should have been installed as a dep though, so I was a bit confused. Did you make changes to the PKGBUILD?

dmp1ce commented on 2017-06-13 11:38

jsteel: Yes, thank you. It was vagrant-substrate.

jsteel commented on 2017-06-13 11:32

Have you got vagrant-substrate installed?

jsteel commented on 2016-09-23 12:09

Pull and rebuild, without libiconv. Should be OK now.

kozzi commented on 2016-09-22 19:29

please add libiconv to dependencies

jsst commented on 2016-09-18 14:55

> What version of vagrant-substrate have you got?

Using 526.6bb2e80-1 from the community repo.

jsteel commented on 2016-09-13 17:34

I can build it without libiconv. What version of vagrant-substrate have you got? I believe a copy of libiconv is bundled in that. Otherwise try building in a clean chroot.

Dieter_be commented on 2016-09-13 15:33

I can confirm I needed to install libiconv (available in aur).
without it, i was getting build failures: https://gist.github.com/Dieterbe/69bec1c53283d9707f7a12c9e1fe7b33