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

debugging "Command failed" is tedious #86

Closed
payload opened this issue Feb 23, 2014 · 1 comment
Closed

debugging "Command failed" is tedious #86

payload opened this issue Feb 23, 2014 · 1 comment

Comments

@payload
Copy link

payload commented Feb 23, 2014

Hi.

I ran into command invocation fails. Red text, no more info. After tediously grepping the code of buildozer i learned about show_output as a kwarg for buildozer.cmd. I also found the relevant cmd call and inserted show_output=True.

Now I could finally see the error messages, solve the problem and be done with it.
(I used a - character in the package.name in the spec file)

I propose an environment variable and command line option to activate helpfull output per "build" phase or something like that.

@payload
Copy link
Author

payload commented Feb 23, 2014

meh... --verbose does it... I tried -vvvv blindly and didn't read Usage :(

@payload payload closed this as completed Feb 23, 2014
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

1 participant