Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is luarocks saying : Error: unknown option '-e' when installing luacheck...? #212

Open
HolterPhylo opened this issue Mar 9, 2021 · 2 comments

Comments

@HolterPhylo
Copy link

Why is luarocks saying : Error: unknown option '-e' when installing luacheck...?
Is it a luacheck problem?

from cmd prompt: luarocks install luacheck

Missing dependencies for luacheck 0.24.0-2:
argparse >= 0.6.0 (not installed)

luacheck 0.24.0-2 depends on lua >= 5.1 (5.3-1 provided by VM)
luacheck 0.24.0-2 depends on argparse >= 0.6.0 (not installed)
Installing https://luarocks.org/argparse-0.7.1-1.src.rock

argparse 0.7.1-1 depends on lua >= 5.1, < 5.5 (5.3-1 provided by VM)
argparse 0.7.1-1 is now installed in C:/Lua (license: MIT)

luacheck 0.24.0-2 depends on luafilesystem >= 1.6.3 (1.8.0-1 installed)
Usage: luarocks [-h] [--version] [--dev] [--server ]
[--only-server ] [--only-sources ]
[--namespace ] [--lua-dir ]
[--lua-version ] [--tree ] [--local] [--global]
[--verbose] [--timeout ] [--pin] [] ...

Error: unknown option '-e'
Did you mean '-h'?
Usage: luarocks [-h] [--version] [--dev] [--server ]
[--only-server ] [--only-sources ]
[--namespace ] [--lua-dir ]
[--lua-version ] [--tree ] [--local] [--global]
[--verbose] [--timeout ] [--pin] [] ...

Error: unknown option '-e'
Did you mean '-h'?
luacheck 0.24.0-2 is now installed in C:/Lua (license: MIT)```

@linuxmaniac
Copy link
Contributor

please read #198

@alerque
Copy link

alerque commented Oct 7, 2021

This looks like an issue with luarocks installing the argparse dependency on Windows but it is hard to be sure. If you still have this issue can I ask that you repost this as a new issue on the new official repository. As the previous commenter noted the maintainer of this one passed away and we have no way to resolve issues here any more. It would be appreciated if you close this to help us track what is dealt with and (if applicable) open a new issue on the active repository. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants