You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.
I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)
Bug is in README.md in master, so no build necessary.
Issue Reproduce Instructions
Follow the install instructions for Ubuntu
Especially sudo pip3 install WoeUSB-ng
Expected Behavior
Collecting WoeUSB-ng … Collecting termcolor … etc.
Current Behavior
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f542d5577c0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/woeusb-ng/
Info of My Environment
I use a proxy, defined in environment variables http_proxy and https_proxy
Solution
any of these:
Invoke sudo with -E
Invoke sudo with --preserve-env
any other means to set the proxy variables so pip can see them.
I suggest we use the -E variant in the install instructions.
The text was updated successfully, but these errors were encountered:
@WaxyMocha
Giving the proxy as explicit argument would probably work as well. However, especially for more complex proxy configs (e.g. with exclude lists), it's waaaay easier to just type -E to have sudo pass the environment. The new command in the readme would thus be sudo -E pip3 install WoeUSB-ng
Good Habit Checklist for Issue Reporting
Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.
Issue Reproduce Instructions
Expected Behavior
Current Behavior
Info of My Environment
http_proxy
andhttps_proxy
Solution
any of these:
-E
--preserve-env
I suggest we use the
-E
variant in the install instructions.The text was updated successfully, but these errors were encountered: