notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
The safest procedure: change your FreshPorts password. Anything you had set before Friday March 24 2023 09:49:20 UTC should be changed. You can read more here: SQL inejection issues fixed and FreshSource code fixes Sorry about the extra work for you.
All known SQL injection issues patched. There is no evidence it was exploited. That doesn’t mean it wasn’t. Please change your password.
non port: devel/valgrind/files/patch-coregrind-vg_proxylwp.c

Number of commits found: 3

Fri, 25 Sep 2009
[ 14:43 stas search for other commits by this committer ] Original commit  (Only the first 10 of 16 ports in this commit are shown above. View all ports for this commit)
- Update to version 3.5.0.

Feature safe:   yes
Tue, 15 Nov 2005
[ 11:22 barner search for other commits by this committer ] Original commit 
Fix build on FreeBSD 6 and above.

PR:                     ports/89056
Submitted by:           "Andrei V. Shetuhin" <>
Also reported by:       kris via pointyhat
Thu, 9 Dec 2004
[ 23:08 pav search for other commits by this committer ] Original commit 
- Starting from some point after FreeBSD 5.2.1, valgrind did not terminate
  correctly, but got stuck in state ``umtx''. This was mentioned on the lists
  and in kern/68992 [closed], but I was never able to fix the problem.

  On FreeBSD >= 502120, the kernel's and valgrind's definition of
  UMTX_CONTESTED flag were out of sync, which is why valgrind did not terminate
  on these systems.

PR:             ports/74903
Submitted by:   Simon Barner <> (maintainer)

Number of commits found: 3