BSD Commit Log Search

   www/mozilla-firefox: MFC update to 156.0.1.

   see https://www.firefox.com/en-US/firefox/156.0.1/releasenotes/

   www/mozilla-firefox: update to 156.0.1.

   see https://www.firefox.com/en-US/firefox/156.0.1/releasenotes/

   update to amule-3.1.0

   xmoto no longer hangs so is not BROKEN on sparc64 in
   the base-clang era

   update to py3-numpy-2.5.3

   update to wget2-2.3.0

   update to py3-virtualenv-21.9.1

   update to py3-trove-classifiers-2026.9.21.13

   update to py3-hatchling-1.32.4

   fheroes2 is no longer BROKEN on sparc64 in the base-clang era

   update to libsrtp-2.8.1

   hyperrogue is no longer BROKEN on sparc64 in the base-clang era

   witchblast and lostpixels are both no longer BROKEN on sparc64
   in the base-clang era

   update to librenms-26.9.0

   spatialindex is no longer BROKEN on sparc64 in the base-clang era

   Both emptyclip and bugdom are no longer BROKEN on sparc64 in
   the base-clang era

   frotz is no longer BROKEN on sparc64 in the base-clang era

   ottomatic is no longer BROKEN on sparc64 in the base-clang era

   update to cjose-0.8.1, CVE fix pointed out by Ivo Marino, no reply from maintainer

   update to py3-fsspec-2026.9.0

   update to py3-uvicorn-0.53.0

   update to py3-platformdirs-4.11.12

   update to py3-pipx-1.17.5

   xwelltris is no longer BROKEN on sparc64 in the base-clang era

   update to ap2-mod_wsgi-6.0.6

   bazel may or may not be still BROKEN-sparc64, but it needs at
   least jdk-17 which is not available on sparc64. Remove the
   BROKEN marker

   asterisk: disable parallel build for now, naddy saw an odd build issue
   (failed after pjsua's configure had run during 'make') and I'm wondering
   if it's due to this.

   update volatility3 2.28.0 -> 2.28.2

   update exploitdb 2026-08-19 -> 2026-09-12

   update ruby-ntlm 0.6.5 -> 0.6.8