BSD Commit Log Search

   vmd(8): unbreak arm64 build

   net/iamb: update to 0.0.12

   leave -beta

   Update to parallel 20260922.

   Update to upplay 1.9.13.

   mail/mlmmj: revise to depend on new devel/kyua

   ok sthen@

   devel/atf: update to 0.26

   ok sthen@

   devel/lutok: update to 0.6.3

   This update is needed to build the new devel/kyua.

   ok sthen@

   hook and add quirks for devel/kyua

   ok sthen@

   Initial revision

   remove and unhook devel/kyua-{cli,testers}

   These ports have been merged into one[0]: devel/kyua. An import of
   the merged port follows.

   [0] https://github.com/freebsd/kyua/blob/33d348582c677ba63daa301d802aefea7aca52af/NEWS#L318

   ok sthen@

   Stop using non-standard UID_MAX and GID_MAX because a variety of code
   uses inclusive comparisons such that the UINT_MAX value aliases on top
   of -1 and causes issues.  First instance of this reported by Acts1631.
   joint work with millert

   Stop using non-standard UID_MAX and GID_MAX because a variety of code
   uses inclusive comparisons such that the UINT_MAX value aliases on top
   of -1 and causes issues.  First instance of this reported by Acts1631.
   joint work with millert

   Fix vvdec and vvenc build on sparc64

   Path from Brad Smith

   Thanks!

   use UNVEIL_WRITE for acct; from Acts1631

   remove UID_MAX and GID_MAX defines.  base no longer uses them.  The
   few cases in ports will be purged sometime today.

   Stop using non-standard UID_MAX and GID_MAX because a variety of code
   uses inclusive comparisons such that the UINT_MAX value aliases on top
   of -1 and causes issues.  First instance of this reported by Acts1631.
   joint work with millert

   update to resiprocate-1.14.0, unbreaks build with newer asio

   I had to disable building tests due to some errors around sdp and
   auto_ptr. Didn't investigate further as wanted to unbreak it quickly.

   sysutils/pftop: handle removal of UID_MAX und GID_MAX

   The UID_MAX and GID_MAX macros are not portable, their use is prone
   to errors, and they will be removed from the OpenBSD headers shortly.

   Mirror a corresponding change to pfctl(8).

   */*: handle removal of UID_MAX und GID_MAX

   The UID_MAX and GID_MAX macros are not portable, their use is prone
   to errors, and they will be removed from the OpenBSD headers shortly.

   Correct related mistakes in range handling: UINT_MAX is not a valid
   user or group ID.

   update to vlc-3.0.24, from Brad (maintainer)

   update to 154.0.8037.57

   update to 154.0.8037.57

   Update to 1.161.0

   OK sthen@

   update to borgmatic-2.1.9

   devel/crush: update to 0.96.1

   Diff from David Uhden Collado

   lang/ecl: update to 26.5.5

   Diff from Timo Myyra (maintainer)

   build with clang on mips64, from Brad

   update to mupdf-1.28.5

   Do not write multiple assignment of the same value to multiple cmmu registers
   as nested assignment in a single statement.

   This used to work in the gcc 2 days, but from gcc 3 onwards, because these
   registers are declared volatile, this caused register reloads to propagate
   the assignment value.

   This had been noticed and fixed in arch/luna88k/luna88k/machdep.c 1.135, but
   the similar constructs in this file were missed.

   Noticed by tsutsuii at netbsd