From owner-freebsd-questions@FreeBSD.ORG Tue Feb 6 13:37:08 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 A7CAB16A401 for ; Tue, 6 Feb 2007 13:37:08 +0000 (UTC) (envelope-from gerard@seibercom.net) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 6BC4913C4A3 for ; Tue, 6 Feb 2007 13:37:08 +0000 (UTC) (envelope-from gerard@seibercom.net) Received: by an-out-0708.google.com with SMTP id c24so1185625ana for ; Tue, 06 Feb 2007 05:37:07 -0800 (PST) Received: by 10.100.167.7 with SMTP id p7mr5613018ane.1170769027644; Tue, 06 Feb 2007 05:37:07 -0800 (PST) Received: from ?192.168.0.4? ( [67.189.184.224]) by mx.google.com with ESMTP id 38sm2398646wrl.2007.02.06.05.37.04; Tue, 06 Feb 2007 05:37:06 -0800 (PST) Date: Tue, 06 Feb 2007 08:37:15 -0500 From: Gerard Seibert To: User Questions Organization: Seibercom.NET In-Reply-To: <20070206131927.483fe494@gumby.homeunix.com> References: <907502.10762.qm@web34404.mail.mud.yahoo.com> <20070206131927.483fe494@gumby.homeunix.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: <20070206083609.AF2C.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: Tue, 06 Feb 2007 13:37:08 -0000 On Tuesday February 06, 2007 at 08:19:27 (AM) RW wrote: > Probably it's just that someone need to patch it to change > "sysutils/portmanager" to "ports-mgmt/portmanager" in the source. > > As a workaround try linking portmanager's new port directory to where > its old one was. As there will be a MOVED entry it's probably best to > use it with the new origin, but make sure portmanager is up-to-date > before running it on multiple ports, it wont be able to detect a > self-update, and it doesn't like to do that as part of a general ports' > update. I reported this problem around 10 am. yesterday. Sometime around 2 pm. a patch was submitted. An updated version of 'portmanager' was in the port's system by 4 pm. Personally, I consider that a rather quick fix. Yes, you will have to do a regular 'make install' to get the newer version installed. You have to do a 'make deinstall' to remove the older version first though. -- Gerard Mail from '@gmail' is rejected and/or discarded here. Don't waste your time!