BSD Commit Log Search

   Update to 3.51.2.

   Some -D and -U went upstream.

   devel/esbuild: Update to 0.27.2

   From Maintainer Igor Zornik, thanks

   Remove empty patches, pointed out by Brad

   un-ifdef i8259

   We don't need different code variants for the legacy PIC. Just keep the
   default variant and remove lots of #ifdefs

   always defined:
           ICU_HARDWARE_MASK

   never defined:
           ICU_SPECIAL_MASK_MODE
           AUTO_EOI_1
           AUTO_EOI_2
           PIC_MASKDELAY
           MASKDELAY
           REORDER_IRQ

   ok kettenis@ hshoexer@

   Disable KleidiCV on arm64 to unbreak the build on amr64

   OpenCV attempts to use the KleidiCV library for ARM platforms.
   KleidiCV is not part of the release, and CMake attempts to download it during
   the build process, which is not permitted on OpenBSD.

   Update to Boost 1.88, from Brad, ok rsadowski

   https://www.boost.org/releases/1.88.0/

   bcmsdhost: Set bus clock after reset

   The host reset during attach nukes SDCDIV that the bus clock setup has
   initialized right before. Reorder to keep the correct value in SDCDIV.

   ok kettenis@

   Update to icu4c-78.2.

   Update to py3-libvirt-12.0.0.

   Update to libvirt-12.0.0.

   Update to babl-0.1.120.

   Update to gnome-text-editor-49.1.

   Adding the re2 feature I did not add it to WANTLIB

   Ops forget to commit new patch

   Spotted by Josh

   add upstream fix for inode % checks reported by danj
   add upstream fix for summaries

   update to py3-trove-classifiers-2026.1.14.14

   update to py3-alembic-1.18.1

   update to py3-regex-2026.1.15, use MODPY_TEST_LINK_SO

   Missing armv7 adaptation to upstream API changes

   update to php-8.4.17

   update to php-8.3.30

   sync change needed after Makefile.inc change

   sync PHP Makefile.inc changes from -current

   Update to rust-analyzer 2026-01-12, from maintainer

   Unbreaks build after the mdbook update

   In SEV-ES mode, guest userland is allowed to execute the vmgexit
   instruction, although it has no control over the GHCB.  Therefore,
   it is important that the GHCB does not contain a valid request after
   use.

   In all "vmgexit paths" the GHCB is cleared by ghcb_sync_in() (it
   calls ghcb_clear()) after returning from the hypervisor back into
   the guest.

   However, in _ghcb_mem_rw() I missed this when requesting MMIO writes
   from the hypervisor.  The diff below corrects this.

   I want to keep this pattern in all vmgexit paths:

           ghcb_sync_out
           vmgexit
           ghcb_verify_bm
           ghcb_sync_in


    [4 lines not shown]

   As vmd(8) direct kernel launch now uses 32-bit legacy mode (with
   paging disabled) we do not need the 64-bit #VC handling in locore0
   anymore.

   ok mlarkin@

   Update to gdb-17.1

   Tested on amd64 arm64 i386 mips64 riscv64 and sparc64 by tb@ kirill@ and me
   ok tb@

   update to dav1d-1.5.3, from Brad (tests run on BTI amd64)

   update to wireshark-4.4.13

   update to wireshark-4.4.13