On 28 August 2011 18:30, Kostik Belousov <[email protected]> wrote: > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: >> 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. > > Might be, completely ignoring the option 'use gnutls' in cups ports, > until it can be made working, will change everybody life to be easier.
I can see why that might be appealing, but I'd be less than impressed if I'd selected WITH_TLS and found the option silently ignored. Perhaps the IGNORE message could be clarified... Chris _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
