sysutils/vagrant-gitlab: mark unsupported for i386 platformff29c9bc4a
Port details
sysutils/vagrant-gitlab 2.4.9_2
Vagrant Virtual Machine Manager
- Maintainer
- mfechner@FreeBSD.org
- Packages
- latest: 2.4.9_2
- Upstream
- up to date
- Last update
- to 2.4.9_2 · ff29c9bc4a
- Quarterly
- 2026Q4: 2.4.9_2
- WWW
- https://www.vagrantup.com/
- Links
- cgit · VuXML
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 2.4.9_2.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (7)
sysutils/vagrant-gitlab: fix regression from 5efa5ed133f6d472ae214a295700f93e2908c1736e8127cef3
sysutils/vagrant-gitlab: fix compatibility with gitlab 18.4.3bda5366f7d
sysutils/vagrant-gitlab: update to 2.4.9 Changes: https://github.com/hashicorp/vagrant/blob/main/CHANGELOG.md3a847871f5
sysutils/vagrant-gitlab: fix conflict with rubyzip update Fixes a regression by 2697faef19d70068fb20396be2040cbdf43848c619f04aa807
sysutils/vagrant-gitlab: update to 2.4.7 Changes: https://github.com/hashicorp/vagrant/blob/main/CHANGELOG.mdd0c6233e8c
sysutils/vagrant: split into vagrant-gitlab that can be used together with gitlab Added a new port vagrant-gitlab that can be installed with gitlab on the same host. Currently I do not see another solution as other rubygem version that are installed by some ports are breaking gitlab and that was the reason to split this. Some maintainers to do test their changes against all ports which made this step necessary. You can also install gitlab in a jail to fix these problems. PR: 2879262df3bbf530