CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

textproc/rubygem-elasticsearch-transport-gitlab 7.17.11_1

Ruby client for Elasticsearch

0
unaddressed
0
VuXML only
0
fixed
0
open problem reports

Port info

Maintainer
mfechner@FreeBSD.org
Packages
latest: 7.17.11_1
Upstream
up to date
Last update
to 7.17.11_1 · b4e64ecafd
Quarterly
2026Q4: 7.17.11_1
WWW
https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-transport
Links
cgit · VuXML

Install

Package
# pkg install rubygem-elasticsearch-transport-gitlab
installs 7.17.11_1 from latest; from quarterly (2026Q4) 7.17.11_1
Port
# cd /usr/ports/textproc/rubygem-elasticsearch-transport-gitlab && make install clean
Size
51 KiB download · 340 KiB installed
Depends on
devel/ruby-gems 4.0.21, devel/rubygem-multi_json-gitlab 1.17.0, lang/ruby34 3.4.9_2,1, www/rubygem-faraday-gitlab 2.14.3
License
APACHE20

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 167.17.11_17.17.11_1–
FreeBSD 157.17.11_17.17.11_1–
FreeBSD 147.17.11_17.17.11_17.17.11_1

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 157.17.11_17.17.11_1–
FreeBSD 147.17.11_17.17.11_17.17.11_1

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 7.17.11_1.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (2)

Matthias Fechner (mfechner) · 7.17.11_1
www/gitlab: major upgrade to 18.4.3

Changes:	https://about.gitlab.com/releases/2025/09/18/gitlab-18-4-released/
b4e64ecafd
Matthias Fechner (mfechner) · 7.17.11
www/gitlab: fix regression from 335fc7c38d61142727cb9f01fd9e401c476e4ad8

Gitlab requires net-http 0.4.1:
Because faraday >= 2, < 2.5 could not be found in locally installed gems
  and faraday >= 2.5, < 2.12.1 could not be found in locally installed gems,
  faraday >= 2, < 2.12.1 cannot be used.
And because faraday >= 2.12.1 depends on faraday-net_http >= 2.0, < 3.5,
  faraday >= 2 requires faraday-net_http >= 2.0, < 3.5.
Because faraday-net_http >= 3.4.0 depends on net-http >= 0.5.0
and faraday-net_http >= 2.0, < 3.4.0 could not be found in locally installed
gems,
  faraday-net_http >= 2.0 requires net-http >= 0.5.0.
Thus, faraday >= 2 requires net-http >= 0.5.0.
So, because Gemfile depends on faraday ~> 2
  and Gemfile depends on net-http = 0.4.1,
  version solving has failed.

While fixing the problem, moved gitlab used packages to own package names with a
PKGNAMESUFFIX of `-gitlab`.
This should make the gitlab package much more stable if updates in the ports are done.
edc8d0390e