From owner-freebsd-questions@FreeBSD.ORG Mon Feb 5 19:01:14 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6628A16A492 for ; Mon, 5 Feb 2007 19:01:13 +0000 (UTC) (envelope-from gerard@seibercom.net) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0A313C4C2 for ; Mon, 5 Feb 2007 19:01:13 +0000 (UTC) (envelope-from gerard@seibercom.net) Received: by an-out-0708.google.com with SMTP id c24so1008235ana for ; Mon, 05 Feb 2007 11:01:12 -0800 (PST) Received: by 10.100.9.19 with SMTP id 19mr5233117ani.1170702072647; Mon, 05 Feb 2007 11:01:12 -0800 (PST) Received: from ?192.168.0.4? ( [67.189.184.224]) by mx.google.com with ESMTP id 10sm13613963wrl.2007.02.05.11.01.12; Mon, 05 Feb 2007 11:01:12 -0800 (PST) Date: Mon, 05 Feb 2007 14:01:21 -0500 From: Gerard Seibert To: User Questions Organization: Seibercom.NET In-Reply-To: <45C77875.7030200@mikestammer.com> References: <907502.10762.qm@web34404.mail.mud.yahoo.com> <45C77875.7030200@mikestammer.com> X-Face: "\j?x](l|]4p?-1Bf@!wN<&p=$.}^k-HgL}cJKbQZ3r#Ar]\%U(#6}'?<3s7%(%(gxJxxcR nSNPNr*/^~StawWU9KDJ-CT0k$f#@t2^K&BS_f|?ZV/.7Q Message-Id: <20070205135745.B4C2.GERARD@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.30.02 [en] Subject: Re: Portmanager - not working after ports change X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: User Questions List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 19:01:14 -0000 On Monday February 05, 2007 at 01:33:25 (PM) Eric wrote: > i recommend switching to portmaster. its actively maintained and a lot > better than portmanager I tried portmaster once, and found it slower and not as through as portmanager at fully updating a system. I just discovered the same problem as the OP reported. I filled a PR on it immediately as well as notifying the port maintainer. -- Gerard