Summary: | git-2.eclass through Socks proxy | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Bhaavan Merchant <bhaavanmerchant> |
Component: | Core - Configuration | Assignee: | Donnie Berkholz (RETIRED) <dberkholz> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=509138 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info vlc-9999 output |
Description
Bhaavan Merchant
2012-03-02 18:54:55 UTC
Not really sure whether the ebuild or portage should arrange for this. This could be an "egit" bug i guess. Since all ebuild use egit, it might nt be possible to accomodate change in individual ebuilds. (In reply to comment #0) > However, the problem is this: > I am unable to emerge the 9999 packages which pull code through egit. > egit doesnt listen to regular proxy settings. I guess emerge calls git-2.eclass for this, so assigning to relevant maintainers. AFAICS git doesn't support SOCKS. You can either: 1) use http proxy forwarding requests over SOCKS, 2) use GIT_PROXY_COMMAND and an external tool (I guess socat may have such a capability) to forward requests over SOCKS [1], 3) request including SOCKS support in git upstream. [1]:http://www.patthoyts.tk/blog/using-git-with-socks-proxy.html |