net-mgmt/victoria-metrics1.133.0_13

various: Bump Go ports for Go 1.26.10 / 1.27.3

various: Bump Go ports

many: Bump go ports for 1.26.8 and 1.27.1

various: Bump go ports for go-1.25.14 / 1.26.7

various: Bump go ports for go-1.25.13 / 1.26.6

various: Drop Go 1.25+ version pin

This is a nop since 1.25 is the oldest version we support.

various: Bump go ports for go-1.25.12 / 1.26.5

various: Bump go ports for go-1.25.11 / go-1.26.4

various: Bump ports for Go 1.25.10

various: Bump go ports for go-1.25.9 / 1.26.2

net-mgmt/victoria-metrics: REQUIRE in RC script is wrong

PR:		292407
Approved by:	danfe (maintainer timeout)

various: Bump ports for Go 1.25.8

various: Bump Go ports for 1.25.7

various: Bump Go ports for 1.25.6

net-mgmt/{victoria-metrics,vmutils}: update to version 1.133.0

Reported by:	portscout

net-mgmt/{victoria-metrics,vmutils}: update to version 1.132.0

Also, fix two problems with vmagent startup script:

1) We shouldn't use /tmp for buffered data, since that directory is
typically wiped upon reboot.  The argument name is a bit misleading
(remoteWrite.tmpDataPath), but that directory is used to store a
persistent queue, and /tmp is very much not persistent.  Default to
/var/db/vmagent instead.

2) Previously, vmagent was offloading to itself because remoteWrite.url
in ``vmagent_args'' pointed to port 8429 which is the vmagent port,
leading to a massive load on the machine over time.

PR:		284564
Submitted by:	Jan van der Lugt
Reported by:	Michael Gruner

many: Unpin Go ports

* Ports that were pinned to a deprecated version of Go (1.23 or older)
  have been unpinned.

* Ports that were pinned to a still-supported version of Go (1.24 or
  newer) have been converted to requesting that as their minimum Go
  version.

* Ports that had been forcibly deprecated for pinning an expired Go
  version have been undeprecated.

various: Bump Go ports for 1.25.5

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.131.0

Reported by:	portscout

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.130.0

Reported by:	portscout

net-mgmt/{victoria-metrics,vmutils}: update to version 1.129.1

Reported by:	portscout

various: Bump Go ports for 1.25.4

various: Bump go ports for go-1.25.3

many: Bump dependent ports after go125 update

net-mgmt/{victoria-metrics,vmutils}: update to version 1.126.0

- Required Go[lang] version had been bumped to 1.25
- Garbage-collect no longer needed patch now that date(1)
  is called in a portable way (thanks to Dmytro Kozlov)

Reported by:	portscout

many: Bump go ports for go-1.24.7

net-mgmt/{victoria-metrics,vmutils}: update to version 1.123.0

- Prevent master port from accidentally overriding slave's
  port revision
- Replace naive and fragile date(1) program implementation
  detection with equivalent BSD syntax

Reported by:	portscout

go ports: Bump for 1.24.6

net-mgmt/{victoria-metrics,vmutils}: update to version 1.121.0

Reported by:	portscout

many: Bump PORTREVISION for go-1.24.5 update

various: Bump PORTREVISION after go124-1.24.4 update

net-mgmt/{victoria-metrics,vmutils}: update to version 1.118.0

Reported by:	portscout
PR:		286054

go: Bump go124-dependent ports

Earlier I bumped the default Go to 1.24. Ports that specify a lower
version will still build with those lower version (for now), so they
don't need a bumping. Instead I'm bumping anything that (now) has go124
as a dependency.

net-mgmt/{victoria-metrics,vmutils}: update to version 1.114.0

Previously we had been tracking what seemed to be LTS releases,
but Lapo Luchini had pointed out that they only make sense for
the private enterprise repository (which is not opensource) and
those tags on the public GitHub have nothing to do with that.

This is consistent with the official upstream description which
advises non-enterprise users to regularly upgrade to the latest
available releases.

Another discovery was that the distfile is already vendored, so
we don't need to generate GH_TUPLE with `make gomod-vendor' and
can simply remove it.

PR:	275828

Bump all go ports for yesterday's releases

net-mgmt/victoria-metrics: GC unsupported configuration parameter

In version 1.73.0 config processing was turned to the strict mode
by default.  Strict mode verifies that config file does not contain
unsupported fields, and evaluation_interval is one of such fields.

Reported by:	Oleg Ginzburg

net-mgmt/{victoria-metrics,vmutils}: update to version 1.97.6

This is the latest supported 1.97.x series LTS release.

all: Bump after lang/go121 update

all: Bump after lang/go121 update

all: Bump after lang/go121 update

MFH:		2024Q2

all: Bump after lang/go121 update

MFH:		2024Q2

all: Bump after lang/go121 update

MFH:		2024Q2

lang/go: Change DEFAULT to 1.21

PR:		277776
Approved by:	portmgr (exp-run)

all: Bump PORTREVISION after lang/go* update

PR:		276530

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.93.10

Notably, this fixes the issue of vmagent instances failing to scrape
metrics due to frequent crashes, after Golang update to version 1.20
lead to errors (panics) like:

    panic: BUG: unexpected runtimemetrics.KindBad for
    sample.Name="/gc/gomemlimit:bytes"

PR:	275828, 276639

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.93.9.

all: Bump PORTREVISION after lang/go* update

PR:		274405

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.93.8.

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.93.7.

net-mgmt/victoria-metrics: update VictoriaMetrics to version 1.93.6.