Package Details: vagrant-git 2.2.6.203.ga1abc177b-1

Git Clone URL: https://aur.archlinux.org/vagrant-git.git (read-only, click to copy)
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: architect0
Last Packager: architect0
Votes: 8
Popularity: 0.000228
First Submitted: 2013-09-03 20:50 (UTC)
Last Updated: 2020-01-23 01:03 (UTC)

Latest Comments

1 2 3 4 Next › Last »

mudejar commented on 2022-09-07 16:00 (UTC) (edited on 2022-09-07 16:03 (UTC) by mudejar)

This package is broken now because git no longer supports the git:// protocol so the following addresses result in a timeout:

git://github.com/hashicorp/vagrant-installers.git

git://github.com/hashicorp/vagrant.git

This can be fixed by changing the MAKEPKG code lines referencing these repos so that they point to the following instead:

git+https://github.com/hashicorp/vagrant-installers.git

git+https://github.com/hashicorp/vagrant.git

(lines 19-20 of the MAKEPKG)

newsboost commented on 2021-10-05 08:56 (UTC) (edited on 2021-10-05 08:56 (UTC) by newsboost)

Maybe it's me who don't understand the concept here, but I just tried this:

==> Making package: vagrant-git 2.2.18.15.g82b083e62-1 (2021-10-05T10:54:15 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Starting build()...
WARNING:  open-ended dependency on erubi (>= 0) is not recommended
  use a bounded requirement, such as '~> x.y'
WARNING:  See https://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: vagrant
  Version: 2.2.19.dev
  File: vagrant-2.2.19.dev.gem
go: downloading github.com/mitchellh/osext v0.0.0-20151018003038-5e2d6d41470f
==> Entering fakeroot environment...
==> Starting package()...
cp: cannot stat '/home/user/.cache/yay/vagrant-git/src/vagrant-installers/substrate/common/rgloader': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
error making: vagrant-git

Doesn't look right...

rageltman commented on 2021-01-15 01:25 (UTC)

Needs ruby-net-ssh along with SCP gem:

[2021-01-14T21:18:59.193Z] ==> Starting package()...
[2021-01-14T21:18:59.193Z] ERROR:  While executing gem ... (Gem::DependencyError)
[2021-01-14T21:18:59.193Z]     Unresolved dependency found during sorting - net-ssh (>= 2.6.5) (requested by net-scp-1.2.1)
[2021-01-14T21:18:59.193Z] ==> ERROR: A failure occurred in package().
[2021-01-14T21:18:59.193Z]     Aborting...
script returned exit code 255

yenlegion commented on 2020-11-12 11:02 (UTC)

Same, the main package at https://www.archlinux.org/packages/community/x86_64/vagrant/ is out of date as well. Several versions behind. The Vagrant website specifically mentions not to use a repo, is this package okay to use, once fixed?

magickreeator commented on 2020-11-10 07:36 (UTC) (edited on 2020-11-10 07:39 (UTC) by magickreeator)

I'm having a problem

    ERROR:  While executing gem ... (Gem::DependencyError)
    Unresolved dependency found during sorting - net-ssh (>= 2.6.5) (requested by net-scp-1.2.1)
==> ОШИБКА: Произошел сбой в package().
    Прерывание...
ошибка сборки: vagrant-git

How can I fix this?

wizonesolutions commented on 2020-01-23 20:35 (UTC)

After building with RVM and version 2.6.3:

$ vagrant                                                                                                                                         
Failed to read Vagrant manifest file at /opt/vagrant/embedded/manifest.json: open /opt/vagrant/embedded/manifest.json: no such file or directory

Did I miss something?

Twiki commented on 2019-04-23 16:11 (UTC) (edited on 2019-04-23 16:41 (UTC) by Twiki)

The repo has moved to here : https://github.com/hashicorp/vagrant-installers EDIT: Forgot the second : https://github.com/hashicorp/vagrant-installers Mitchell's company. EDIT 2: And there is a message here : https://github.com/mitchellh/osext "Don't use this anymore! Use the official library at: https://github.com/kardianos/osext"

jsteel commented on 2017-11-02 11:44 (UTC)

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.

1 2 3 4 Next › Last »