From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:26:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE2A3106566B for ; Sun, 28 Aug 2011 17:26:58 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id BD9148FC0C for ; Sun, 28 Aug 2011 17:26:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id 83BD4170FE for ; Sun, 28 Aug 2011 13:27:27 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314552447; bh=Ucsrz/e2ZMGdt2+QADv5yBLk0DinhAZUniWT3/KmtDc=; b=j vkTMNg4Gk/EzCSkXn22R/L/F+omVzzxoCOR59+BofS8va9ZrTxurRyYrAxs6WLpx YEHkqqMBsN7lxJPGo6rkMhzRzzjy78DIwVVPGOjsuyK5MuTgLHQeZUEECvLmcnbS m1vDhKqWXLrsy6uHAl9bVNrGAcJP/z8uW2ux3Yj6aI= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id AAfHZeol8A9N for ; Sun, 28 Aug 2011 13:27:27 -0400 (EDT) Date: Sun, 28 Aug 2011 13:26:51 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828172651.GB277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:26:58 -0000 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