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

textproc/rubygem-google-cloud-artifact_registry-v1 0.11.0_2

Manages artifacts on Google infrastructure

0
unaddressed
0
VuXML only
0
fixed
0
open problem reports

Port info

Maintainer
mfechner@FreeBSD.org
Packages
latest: 0.11.0_2
Upstream
Higher version available: 1.14.1
Last update
to 0.11.0_2 · f097255a9b
Quarterly
2026Q4: 0.11.0_2
WWW
https://googleapis.github.io/google-cloud-ruby/docs/
Links
cgit · VuXML · Report wrong data

Install

Package
# pkg install rubygem-google-cloud-artifact_registry-v1
installs 0.11.0_2 from latest; from quarterly (2026Q4) 0.11.0_2
Port
# cd /usr/ports/textproc/rubygem-google-cloud-artifact_registry-v1 && make install clean
Size
70 KiB download · 915 KiB installed
Depends on
devel/ruby-gems 4.0.21, devel/rubygem-gapic-common-gitlab 0.23.0_2, devel/rubygem-grpc-google-iam-v1-gitlab 1.11.0_1, lang/ruby34 3.4.9_2,1, net/rubygem-google-cloud-errors 1.7.0, net/rubygem-google-cloud-location-gitlab 0.8.1
License
APACHE20

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 160.11.0_20.11.0_2–
FreeBSD 150.11.0_20.11.0_2–
FreeBSD 140.11.0_20.11.0_20.11.0_2

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 150.11.0_20.11.0_2–
FreeBSD 140.11.0_20.11.0_20.11.0_2

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 0.11.0_2.

Fixed (0)

No VuXML entries for this package.

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

None.

Commits (3)

Matthias Fechner (mfechner) · 0.11.0_2
www/gitlab: use gitlab own grpc packages
f097255a9b
Matthias Fechner (mfechner) · 0.11.0_1
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
Matthias Fechner (mfechner) · 0.11.0
www/gitlab-ce: new ports required for 16.9.0
b62e99dd6b