[MacPorts] #27188: Unable to execute port: wrong # args
MacPorts
noreply at macports.org
Sat Nov 6 20:52:04 PDT 2010
#27188: Unable to execute port: wrong # args
-----------------------------+----------------------------------------------
Reporter: junk@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: High | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port:
-----------------------------+----------------------------------------------
Hello,
I just did a 'sudo port selfupdate', and now I can't install any ports.
Here is an example:
{{{
$ sudo port install pwlib
Error: Unable to execute port: wrong # args: should be
"macports::_deptypes_for_target target"
To report a bug, see <http://guide.macports.org/#project.tickets>
$
}}}
The selfupdate updated my version from 1.9.1 to 1.9.2. Here is the output
when I run 'sudo port -v selfupdate' now:
{{{
$ sudo port selfupdate
---> Updating the ports tree
---> Updating MacPorts base sources using rsync
MacPorts base version 1.9.2 installed,
MacPorts base version 1.9.2 downloaded.
---> MacPorts base is already the latest version
The ports tree has been updated. To upgrade your installed ports, you
should run
port upgrade outdated
$
}}}
When I try running 'sudo port -v upgrade outdated', I get this:
{{{
$ sudo port -v upgrade outdated
Error: Unable to exec port: wrong # args: should be
"macports::_deptypes_for_target target"
To report a bug, see <http://guide.macports.org/#project.tickets>
$
}}}
When I do it with a -d instead, I get a ton of stuff including this
pertinent text:
{{{
DEBUG: Starting logging for gnome-common
DEBUG: wrong # args: should be "macports::_deptypes_for_target target"
while executing
"macports::_deptypes_for_target $target $workername"
(procedure "mportexec" line 17)
invoked from within
"mportexec $workername activate"
Error: Unable to exec port: wrong # args: should be
"macports::_deptypes_for_target target"
To report a bug, see <http://guide.macports.org/#project.tickets>
}}}
It looks like $workername is being passed, and it's not expected. Is this
something that changed in 1.9.2? Any idea how to fix or work around this?
I'm running OS X 10.6.4.
Thanks,
Stephen
--
Ticket URL: <https://trac.macports.org/ticket/27188>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list