From owner-freebsd-ports@FreeBSD.ORG Tue Jan 29 18:13:36 2008 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 E45DD16A419 for ; Tue, 29 Jan 2008 18:13:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 8734813C46E for ; Tue, 29 Jan 2008 18:13:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 12377 invoked by uid 399); 29 Jan 2008 18:13:36 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 29 Jan 2008 18:13:36 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <479F6CCF.1000203@FreeBSD.org> Date: Tue, 29 Jan 2008 10:13:35 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (X11/20080126) MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20080129061621.GA40834@oberon.njm.f2s.com> In-Reply-To: <20080129061621.GA40834@oberon.njm.f2s.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: portmaster: upgrade failed for security/sudo X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2008 18:13:37 -0000 N.J. Mann wrote: > Good morning, > > > I am using portmaster v2.0 and very good it is to, except... > > This morning among the ports that needed updating following my > over-night CVSup was security/sudo (1.6.9.6 -> 1.6.9.12). I am using > portmaster's new feature SU_CMD. I am also using the new HIDE_BUILD > feature which I really like! Thanks, so do I. :) That was another suggestion from a user, btw. > All went well until the install phase, > when portmaster could no longer find sudo. It looks like portmaster got > into a chicken and egg situation: it needed to uninstall sudo in order > to complete the upgrade, but it needed to run sudo to perform the actual > install. Oh, dear. I thought it went without saying that this couldn't possibly work, but I'll update the man page in this regard. Thanks, Doug -- This .signature sanitized for your protection