BSD Commit Log Search

   Probe and detect all possible mwx(4) variants that mwx(4) will cover.

   This is MT7920, MT7921, MT7922 and MT7925.
   From a diff shared by kevlo@

   update to 7.0.27; from Mark Patruck

   mcu_fw_pmctrl and mcu_drv_pmctrl are the same on all mwx(4) versions.
   Rename the functions to mwx_mcu_*_pmctrl.

   from kevlo@

   update to py3-virtualenv-21.4.2

   update to py3-trove-classifiers-2026.6.1.19

   audio/musepack: make C types coherent to appease llvm22

   ok tb@

   Disable the pcie5 port in the t14s device tree.  I believe this port is
   used for the LTE modem on models that include that option.  But accessing
   this port on models without triggers a reset of the machine because the
   firmware didn't set up that port for us.

   tested by deraadt@

   update to py3-hatchling-1.30.1

   Improve checking of ELF notes.  This adds checks for overflow when rounding
   sizes up to be a multiple of the ELF word size and adds checks to prevent
   out of bounds access.

   Based on a report and diff from Andrew Griffiths.
   ok jsg@, deraadt@

   update to py3-pip-26.1.2

   update to py3-pip-26.1.2

   Regen

   Add a few more MediaTek ids that will be handled by mwx(4) eventually.
   OK kevlo@

   Update to webkitgtk{41,60}-2.52.4.

   Update to webkitgtk{41,60}-2.52.4.

   libime: fix build with llvm22 by backporting PR #99

   This could really use an update to 1.1.14.

   tested by kevlo

   Default 'announce as-4byte' to 'enforce' for all peers

   After close to 20 years of 4-byte AS support in bgpd it is time to enforce
   it. The fall back code from 2-byte AS to 4-byte AS is non-trivial and
   the RFC is way to optimistic and ignores many possible error conditions.

   All relevant BGP implementations support 4-byte ASnums so it is a
   misconfiguration to not use this by default. Most implementations do this
   by default.

   In the unlikely cases where 2-byte AS support is still needed one can
   fall back to the previous default by using 'announce as-4byte yes'.

   OK tb@ job@

   Reimplement aspath_merge() in a more cynical fashion

   Mergin AS4_PATH into ASPATH can be done a bit simpler by using the fact
   that AS4_PATH must be a subset of ASPATH. The resulting path has the same
   size and layout as the ASPATH. bgpd inflates the 2-byte ASPATH to 4-byte
   representation early on so this simplifies the merge.

   When mering the path be strict and any difference in the two paths triggers
   a treat-as-withdraw error. Something is off so refuse to work with this path.
   This is harsher than RFC 6793 but the concerns then no longer matter.

   Use ibuf for all the buffers to have memory safety during this merge operation.

   OK tb@

   Move the PANE_FLOATING flag into the layout cell and add an accessor.
   From Dane Jensen.

   Update to librsvg-2.62.3.

   Update to py3-libvirt-12.4.0.

   Update to libvirt-12.4.0.

   Prevent daily(8) from deleting /tmp/run/user/* direct subdirectories

   These are directories that are created by
   setusercontext(LOGIN_SETXDGENV) and should be available as long as
   a session with the XDG_RUNTIME_DIR env variable pointing at them exists.
   Since we don't track such sessions, we can't have daily(8) remove such
   directories blindly. This looks like an oversight in the initial commit.

   Diff proposed by dah4ae (at) posteo (dot) de, ok ajacoutot@

   Update to shotwell-0.32.16.

   Update to ibus-typing-booster-2.30.9.

   Fix border colour bug in the floating panes branch where inactive
   floating pane borders incorrectly use the active colour at intersections
   with tiled pane borders. From Michael Grant.

   Update to mutter-49.6.

   update

   refer to RFC9987 instead of I-D

   geo/mapserver: MFC security update to 8.6.4

   see https://mapserver.org/development/changelog/changelog-8-6.html
   fixes https://github.com/MapServer/MapServer/security/advisories/GHSA-xp29-8wp5-wc3p
   and https://github.com/MapServer/MapServer/security/advisories/GHSA-xqj6-vjqr-33vv