textproc/kibana93: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.3.x has ended 04 Aug 2026 - use kibana94 or kibana95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
sysutils/logstash93: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.3.x has ended 04 Aug 2026 - use logstash94 or logstash95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
sysutils/beats93: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.3.x has ended 04 Aug 2026 - use beats94 or beats95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
sysutils/logstash92: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.2.x has ended 05 May 2026 - use logstash94 or logstash95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
sysutils/beats92: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.2.x has ended 05 May 2026 - use beats94 or beats95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
textproc/kibana92: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.2.x has ended 05 May 2026 - use kibana94 or kibana95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
textproc/kibana91: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.1.x has ended 03 Feb 2026 - use kibana94 or kibana95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
sysutils/logstash91: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.1.x has ended 03 Feb 2026 - use logstash94 or logstash95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs (vvd, commit patch)
sysutils/beats91: Deprecate with EXPIRATION_DATE=2026-12-31
Support for 9.1.x has ended 03 Feb 2026 - use beats94 or beats95 instead
Approved by: elastic (implicit, inactive for several months again)
Sponsored by: UNIS Labs
vmd(8): drop packets if tap(4) returns ENOMEM.
If there are no mbufs available to queue a packet on write(2), we
should drop the packet instead of toggling the device reset state.
The virtio network device was inspecting the wrong errno as well.
Also drop packets if EMSGSIZE is set on error. Only in unexpected
cases should we flag the device needs a reset.
Issue reported by Mischa Peters.
ok bluhm@, jan@, mlarkin@ and makes sense to deraadt@
[CIR] Compare access ranges of pointers into the same object (#225166)
Two pointers at different offsets into the same object were previously
reported as MayAlias, because whether they overlap depends on how many
bytes each access touches. This change extends the analysis to use the
access size from the pointee type and compare the byte ranges the two
accesses cover. Disjoint ranges don't alias, overlapping ranges
partially alias. Access to different members of a record are now
reported as NoAlias, while a member compared against the record it
belongs to is reported as PartialAlias.
Accesses whose extent isn't statically known, such as those through a
pointer to void, keep the conservative answer.
Assisted-by: Cursor / various models
In lfs_checkempty(), do not continue looping through partial segments
after an error. Also, do not continue checking all future segments but
confine our attention only to the segment we are trying to verify empty.
Addresses an issue described in PR kern/60746.
[CI] Ignore ';' comments in .ll files in undef deprecator (#225509)
Without this patch, UndefGetFormatHelper matches across ';' comment
markers on added lines in .ll files, flagging false positives whenever
the word 'undef' appears in a test comment.
This patch stops matching at ';' on added lines in .ll files so comments
are ignored while uses of undef in IR instructions are still caught.
Assisted-by: Antigravity
pkg: Fix rpm warnings about not being able to read its database
When building on many debian machines, the RPM database, by default at
/var/lib/rpm/rpmdb.sqlite, does not exist and can not be created when
running as an unprivileged user. This will cause any rpm command that
ties to access the database to print this obnoxious error message:
error: Unable to open sqlite database /var/lib/rpm/rpmdb.sqlite: unable to open database file
error: cannot open Packages index using sqlite - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
It appears as though this doesn't cause any failures and is really a
warning. However, it can be printed more than 20 times when making the
deb-kmod target.
Detect when the database file is not readable at configure time and
setup various rpm and rpmbuild invocations to use the root of the build
directory as the database directory path. The alien program internally
runs various rpm queries, however it provides no good way to tell those
[7 lines not shown]
