From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 19:22:38 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 C2D56106564A for ; Sun, 28 Aug 2011 19:22:38 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF858FC13 for ; Sun, 28 Aug 2011 19:22:38 +0000 (UTC) Received: by vxh11 with SMTP id 11so4918993vxh.13 for ; Sun, 28 Aug 2011 12:22:37 -0700 (PDT) Received: by 10.220.9.131 with SMTP id l3mr1194638vcl.148.1314559357826; Sun, 28 Aug 2011 12:22:37 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id fc7sm1356123vdc.0.2011.08.28.12.22.36 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 12:22:36 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rn5bb0lrwz2CG4t for ; Sun, 28 Aug 2011 15:22:35 -0400 (EDT) Date: Sun, 28 Aug 2011 15:22:34 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828152234.54cc9fac@seibercom.net> In-Reply-To: <20110828184542.GE277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.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 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 19:22:38 -0000 On Sun, 28 Aug 2011 14:45:42 -0400 Sahil Tandon articulated: > I am sorry users have had to "intervene" in managing their systems, > but rather than removing the option entirely, I prefer mandree@'s more > structural suggestion of re-prompting the user when defaults change. > In the meantime, a note in UPDATING about explicitly disabling the > GNUTLS option for cups ports is probably appropriate. I have copied > the maintainer in hopes that he will consider it. Sahil, I think you are being a little to flippant regrading this problem. Obviously any end user is responsible for maintaining his/her system. It is apparently that FreeBSD does not test updates as rigorously as other OSs might. Therefore, when the problem was first discovered in regards to "cups" and "GNUTLS" it is obviously that the end user would have to manually correct the problem. However, this is no longer day 0. The particulars of this case are well know. IMHO, a notice should have been inserted into the UPDATING file immediately -- in other words as soon as the phenomena was confirmed. To allow the port to be shipped with a known problem borders on criminal. At the very lest, it displays gross indifference to the users of FreeBSD. Nothing here is specifically blaming your for this problem. It takes more than one individual to screw things up this thoroughly. However, it takes only one person with a set of balls to get a solution implemented. The fact that you are actually going to wait for the maintainer the port in question to give his permission for you to issue a warning and hopefully a fix for this problem is pathetic. Seriously, and I don't mean any disrespect, but what government agency do you work for? :) -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The climate of Bombay is such that its inhabitants have to live elsewhere.