-
Notifications
You must be signed in to change notification settings - Fork 64
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
catch and ignore subprocess.CalledProcessError when running lsb_relsase
#261
catch and ignore subprocess.CalledProcessError when running lsb_relsase
#261
Conversation
Can this be merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from the linting error I'd say this looks good!
@nir0s Would be really cool if you could take a look at this PR! |
@nir0s I have fixed the lint issue and the tests to fit the new code, any chance this can be reviewed? |
@nir0s Is there a way to get this merged somehow? Is something blocking this PR? |
@nir0s Thanks a lot for merging this! |
@nir0s Thanks a lot, I have been waiting for this one. |
@nir0s Can you please make a new release with this fix included? |
A fix for #260 issue.
Ignore
lsb_release
issues.The other solution that I have is if
lsb_release
installed but the executable is broken, we can just parse/etc/lsb_release
files to get the same information (maybe it can replace thesubprocess.check_output
completely).