BSD Commit Log Search

   Update binaryen to 132.

   Handle IMSG_CTL_LOG_VERBOSE like bgpd with imsg_get_data instead of an
   unchecked memcpy.

   OK tb@

   Handle IMSG_CTL_LOG_VERBOSE like bgpd with imsg_get_data instead of an
   unchecked memcpy.

   OK tb@

   Handle IMSG_CTL_LOG_VERBOSE like bgpd with imsg_get_data instead of an
   unchecked memcpy.

   OK tb@

   Handle IMSG_CTL_LOG_VERBOSE like bgpd with imsg_get_data instead of an
   unchecked memcpy.

   OK tb@

   Handle IMSG_CTL_LOG_VERBOSE like bgpd with imsg_get_data instead of an
   unchecked memcpy.

   Reported by Shibo, Hugo Systopia Team
   OK tb@

   If writing a file fails, propagate the error to the server via a new
   message. Use a client flag rather than bumping the protocol version.
   GitHub issue 5451.

   Add default terminal features for Rio, GitHub issue 5489 from Raphael
   Amorim.

   geo/gpxsee: update to 16.12

   Remove flags from both keys for menus, GitHub issue 5484.

   update to putty-0.85

   update to putty-0.85
   some small security fixes

   Attach window to session earlier so resize cannot cause customize mode
   to blow up. Reported by Marcel Partap.

   Do not copy too many positions when deleting, GitHub issue 5478 from
   Uzair Aftab.

   Update to mergiraf 0.19

   https://codeberg.org/mergiraf/mergiraf/releases/tag/v0.19.0

   With base-gcc apr-util throws
   error: missing binary operator before token "("

   Move to ports-gcc on base-gcc arches to fix build on sparc64

   update intel microcode to 20260812

   20260811 with 06-aa-04 (Meteor Lake) downgraded from 0000002a back to 00000028
   due to reports of not being able to boot with 0000002a
   https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/112
   not a problem I saw when testing 0000002a on Meteor Lake

   release notes:
   https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
   https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260812

   devel/intellij: update to 2026.2.1

   ourput -> output

   correct test for non-NULL; ok ratchov@

   Update libopenmpt to 0.8.8.

   Ignore various roff(7) requests that are new in groff-1.23 and groff-1.24.
   Most of these only serve debugging purposes, and some are related to
   features that are not relevant in manual pages and that we do not support
   in the first place.

   Two special cases are notable: .msoquiet is ignored because insecure
   (just like .mso already was), and .soquiet is treated as an exact
   alias for .so, without suppressing any diagnostics, because in manual
   pages, missing include files are never harmless.

   List of requests that needed checking provided by G. Branden Robinson.

   net/samba: quotactl() now takes a void* argument

   update to turnserver-4.16.0, thanks to Filip Lax for testing

   regress/lib/libmlgamma: remove no longer needed __POSIX_VISIBLE 201403

   These days we default to POSIX 2024 with XSI extensions. The original define
   was only needed when our default was POSIX 2008 and we needed to advance to
   a newer standard to run this test.

   groff-1.23.0 invented new roff(7) requests .stringup and .stringdown that
   change the case of the named user-defined string in place.  I haven't seen
   them used in any manual page yet and - like for all roff(7) requests - do
   not recommend using them, but i chose to implement them anyway because that
   was almost as trivial as it would have been to mark them as unsupported.

   G. Branden Robinson reminded me of the new feature.

   Update KDE Frameworks 6.29.0

   https://kde.org/announcements/frameworks/6/6.29.0/

   update to rspamd-4.1.5

   update to rspamd-4.1.5

   Stop clobbering the return value of getenv(3) with strtok(3).
   The getenv(3) manual discourages tampering with the returned string.
   Instead, copy the value to the heap such that it can be safely modified.

   This fixes a bug that Luca Del Re <l.osd at ldr.name>
   found on Alpine Linux and reported to bsd.lv.

   The consequence of the bug was likely implementation-dependent, but
   on both OpenBSD and Alpine Linux, the first colon after the first
   byte of the MANPATH variable was set to NUL in the actual environment
   of the man(1) process, and this truncated value would later be
   passed to the pager child process by execv(3).  Hence, while
   MANPATH=:mypath1 worked as expected, the pager would only see
   MANPATH=mypath1 if man(1) saw any of the following:
   MANPATH=mypath1:
   MANPATH=mypath1:mypath2
   MANPATH=mypath1::mypath2