Bug #79382 --verbosity on mysqfrm does't work

Description:
ERROR: Spawn server operation failed. Clone server error: Unable to communicate with new instance. Process id = 1936.. To diagnose, run the utility again and use the --verbosity option to view the messages from the spawned server and correct any errors presented then run the utility again.

root@debian:~# mysqlfrm --basedir=/usr/bin/ bt_account_master.frm --port=3333 --user=mysql --verbosity
Usage: mysqlfrm --server=[user[:<pass>]@host[:<port>][:<socket>]|<login-path>[:<port>][:<socket>]] [path\tbl1.frm|db:tbl.frm]

mysqlfrm: error: no such option: --verbosity

How to repeat:
Run mysqfrm with --verbosity

Hello Miguel,

Thank you for the report.
Verifying for the incorrect option specified in the error message i.e "--verbosity..." instead of "--verbose".

Thanks,
Umesh

//

[root@cluster-repo ~]# mysqlfrm --basedir=/usr/bin/ t1.frm --port=3333 --user=mysql
# Spawning server with --user=mysql.
# Starting the spawned server on port 3333 ...
..

ERROR: Spawn server operation failed. Clone server error: Unable to communicate with new instance. Process id = 26222.. To diagnose, run the utility again and use the --verbosity option to view the messages from the spawned server and correct any errors presented then run the utility again.

[root@cluster-repo ~]# mysqlfrm --basedir=/usr/bin/ t1.frm --port=3333 --user=mysql --verbosity
Usage: mysqlfrm --server=[user[:<pass>]@host[:<port>][:<socket>]|<login-path>[:<port>][:<socket>]] [path\tbl1.frm|db:tbl.frm]

mysqlfrm: error: no such option: --verbosity

-- workaround use --verbose

Posted by developer:
 
Fixed as of the upcoming MySQL Utilities 1.6.5 release, and here's the changelog entry:

The mysqlfrm utility failed when the --verbosity option was used. This
fix replaces the --verbosity option with --verbose, the correct option name, 
and uses it consistently in error messages and code.

Thank you for the bug report.