Proxies are not used during installation

[FedericoCeratto]

Proxies are being used only for some operations e.g. nimble update but not during nimble install:

http_proxy='http://127.0.0.1:9/' https_proxy='http://127.0.0.1:9/' nimble install fswatch

[genotrance]

Nimble only directly uses the proxy when fetching the package list and publishing new packages. All install and update commands are calling git which should be detecting the proxy variable.

Does a git clone work by itself?

[genotrance]

Any update? @FedericoCeratto

[FedericoCeratto]

Nimble is not passing variables to git to use the proxy

[genotrance]

Are you configuring the proxy info in nimble.ini and expecting Nimble to pass it onto git?

[FedericoCeratto]

I have to use environment variables as in the example. Of course Nimble has to pass it correctly to git (or any other VCS).

[genotrance]

I tested this syntax on my Linux system and it worked fine. Nimble calls git with execCmd which allows child processes to inherit such env. variables.

Please share the output of the command if you can. Also, please try a git clone with the same syntax and share that output.

[dom96]

Please elaborate @FedericoCeratto ^^

[genotrance]

@FedericoCeratto

[FedericoCeratto]

I found the issue: git ignores any proxy with the url/insteadOf setting I had. Unfortunately Nimble doesn't have a way to detect this behavior.

Anyhow my endgoal is to have #699 supported, so a flag to disable pulling would be safer.