Portmanager - not working after ports change
fbsd06 at mlists.homeunix.com
Tue Feb 6 13:19:34 UTC 2007
On Mon, 5 Feb 2007 09:14:16 -0800 (PST)
White Hat <pigskin_referee at 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
> 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'
More information about the freebsd-questions