2.3.0
Joshua Root
jmr at macports.org
Sat Apr 5 17:36:57 PDT 2014
On 2014-4-6 09:22 , Gustaf Neumann wrote:
> Am 06.04.14 00:56, schrieb Clemens Lang:
>>> I've seen this happen with debug output enabled now:
>>>
>>> DEBUG: Executing org.macports.uninstall (gettext)
>>> DEBUG: Changing to port directory:
>>> /opt/mports/var/macports/registry/portfiles/gettext-0.18.3.2_0/72c2558ef3fd1fb2daab1b5822e6a86e16af7bb3fb559eef213a28c352e493a4-3049
>>>
>>> DEBUG: wrong # args: should be "set varName ?newValue?"
>>> while executing
>>> "set user_options(_portgroup_search_dirs)
>>> /opt/mports/var/macports/registry/portgroups/7bbea60c69221b3e81858a4c11b6740a082d84fa11a3212e202f31720c7e1abc..."
>>>
>>> invoked from within
>>> "$workername eval set user_options($opt) $val"
>>> (procedure "macports::worker_init" line 123)
>>> invoked from within
>>> "macports::worker_init $workername $portpath $porturl
>>> [macports::getportbuildpath $portpath] $options $variations"
>>> (procedure "mportopen" line 39)
>>> invoked from within
>>> "mportopen file://${portfile_dir}/ $options $variations"
>>> (procedure "mportopen_installed" line 26)
>>> invoked from within
>>> "mportopen_installed [$port name] [$port version] [$port revision]
>>> [$port variants] $options"
>>> Warning: Failed to open Portfile from registry for gettext @0.18.3.2_0
>>> ---> Deactivating gettext @0.18.3.2_0
>>>
>>> Can anyone make anything out of that?
> it looks to be as if the $val in "$workername eval set
> user_options($opt) $val"
> needs to be protected (by eg. [list $val]). The command "set" sees three
> arguments.
And I was sure I fixed that. Is this only happening from port_cutleaves,
and not with normal uninstalls?
- Josh
More information about the macports-dev
mailing list