DEBUG: process_cmd failed: can't read "string": no such variable
https://build.macports.org/builders/ports-11_x86_64-builder/builds/30991/steps/install-port/logs/stdio
DEBUG: process_cmd failed: can't read "string": no such variable
while executing
"return $string"
(procedure "wrapline" line 7)
invoked from within
"wrapline $line $maxlen $indent $indentline"
(procedure "wrap" line 15)
invoked from within
"wrap "Follow https://guide.macports.org/#project.tickets if you believe there is a bug." -${len}"
(procedure "print_tickets_url" line 4)
invoked from within
"print_tickets_url"
("uplevel" body line 82)
invoked from within
"uplevel 1 $block"
(procedure "foreachport" line 20)
invoked from within
"foreachport $portlist {
array unset portinfo
# If we have a url, use that, since it's most specific
# otherwise try to map the..."
(procedure "action_target" line 10)
invoked from within
"$action_proc $action $portlist [array get global_options]"
(procedure "process_cmd" line 110)
invoked from within
"process_cmd $remaining_args"
("uplevel" body line 3)
invoked from within
"uplevel 1 $body"
Error: process_cmd failed: can't read "string": no such variable
Change History (3)
Owner: |
set to jmroot
|
Resolution: |
→ fixed
|
Status: |
new →
closed
|
Milestone: |
→ MacPorts 2.7.1
|
Funnily enough this bug has existed since 2008, it was only exposed by more recent changes.