From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 15:30:31 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 63DAC1065670 for ; Sun, 28 Aug 2011 15:30:31 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s38.blu0.hotmail.com (blu0-omc3-s38.blu0.hotmail.com [65.55.116.113]) by mx1.freebsd.org (Postfix) with ESMTP id 126BE8FC20 for ; Sun, 28 Aug 2011 15:30:30 +0000 (UTC) Received: from BLU0-SMTP182 ([65.55.116.74]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 28 Aug 2011 08:30:31 -0700 X-Originating-IP: [174.109.142.1] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([174.109.142.1]) by BLU0-SMTP182.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 28 Aug 2011 08:30:29 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rn0Rm29HJz2CG4t for ; Sun, 28 Aug 2011 11:30:28 -0400 (EDT) Date: Sun, 28 Aug 2011 11:30:27 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20058.20743.791783.342355@jerusalem.litteratus.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 28 Aug 2011 15:30:30.0145 (UTC) FILETIME=[6B4B0F10:01CC6597] 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 15:30:31 -0000 On Sun, 28 Aug 2011 10:30:31 -0400 Robert Huff articulated: > Leslie Jensen writes: > > > > Following the instructions in /usr/ports/UPDATING I issued the > > command > > > > portmaster -r libnotify-0 > > > > And after a while I get this error > > > > Dependency check complete for print/cups-client > > libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> > > apache-ant-1.8.2 >> jdk-1.6.0.3p4_25 >> cups-client-1.4.6 > > ===> Cleaning for cups-client-1.4.8 > > > > ===> cups-client-1.4.8 is marked as broken: gnutls does not > > support threads yet. > > *** Error code 1 > > > > Stop in /usr/ports/print/cups-client > > Unless you have a specific reason to use GNUTLS: go to > ports/print, run "make config", uncheck the "Use GNUTLS instead of > OpenSSL" setting. (If you do have a specific reason, you probably > know enough to have handled this already.) > Then rebuild. > Worked for me. 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? It is not like we are talking about some niche application(s). 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. -- Carmel ✌ carmel_ny@hotmail.com Never listen to anyone who talks to you for over five minutes about all that things that have happened to them that have left them speechless!