How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken

Sahil Tandon sahil at
Sun Aug 28 17:26:58 UTC 2011

On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote:

> My question is what changed? It worked before updating "libnotify". Is
> "libnotify" the culprit or "GNUTLS" or something else and why didn't
> anyone catch this problem sooner?

The chain of dependencies during the libnotify update prompted the
upgrade of cups.  The latter's OpenSSL interfaces are explicitly
thread-safe, which GNU TLS is not.

> There appears to be a lot of material released lately that is either
> broken or requiring a considerable amount of manual intervention.
> Perhaps a moratorium (port freeze) should be considered until all of
> the outstanding problems have been corrected.

We are sorry for the inconvenience which is surely frustrating, but
freezing the tree because of this does not seem appropriate.

Sahil Tandon <sahil at>

More information about the freebsd-ports mailing list