From owner-freebsd-questions@FreeBSD.ORG  Tue Feb  6 13:19:34 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 84DF016A402
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Feb 2007 13:19:34 +0000 (UTC)
	(envelope-from fbsd06@mlists.homeunix.com)
Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178])
	by mx1.freebsd.org (Postfix) with ESMTP id 5E53913C4B9
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Feb 2007 13:19:34 +0000 (UTC)
	(envelope-from fbsd06@mlists.homeunix.com)
Received: from gumby.homeunix.com (unknown [87.81.140.128])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTP id E7D315194F
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Feb 2007 08:19:32 -0500 (EST)
Date: Tue, 6 Feb 2007 13:19:27 +0000
From: RW <fbsd06@mlists.homeunix.com>
To: freebsd-questions@freebsd.org
Message-ID: <20070206131927.483fe494@gumby.homeunix.com>
In-Reply-To: <907502.10762.qm@web34404.mail.mud.yahoo.com>
References: <907502.10762.qm@web34404.mail.mud.yahoo.com>
X-Mailer: Claws Mail 2.7.2 (GTK+ 2.10.9; i386-portbld-freebsd6.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: Portmanager - not working after ports change
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2007 13:19:34 -0000

On Mon, 5 Feb 2007 09:14:16 -0800 (PST)
White Hat <pigskin_referee@yahoo.com> wrote:

> There was a change in the ports system -
> /usr/ports/UPDATING 20070205 - which now renders
> portmanager unable to run correctly. While it is
> possible to update a single port; i.e., "portmanager
> /path/to-port/", if I attempt to do a general ports
> update; i.e., "portmanager -u", I receive the
> following error message:
> 
> percentDone-=>0 = 100 - ( 100 * ( oldPortsDbQTY-=>6 /
> oldPortsDbTOTALIZER-=>6 ))
> cd: can't cd to /usr/ports/sysutils/portmanager
> rBsdPortMkPatch 0.4.1_7 error: bsd.port.mk
> /usr/ports/Mk unable to restored from back up   cp
> /usr/local/share/portmanager/bsd.port.mk-BACKUP
> /usr/ports/Mk/bsd.port.mk
> 
> I tried deinstalling portmanager and then installing
> it from its new port directory; however, that failed
> to alleviate the problem.
> 
> Has anyone else experienced this problem, and perhaps
> have a solution?

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.