Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#33733 - builtin proxy support

Attached to Project: Pacman
Opened by Stefan Majewsky (majewsky) - Wednesday, 06 February 2013, 09:43 GMT
Last edited by Allan McRae (Allan) - Saturday, 09 February 2013, 03:47 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My company uses a VPN, and access to the public internet is only possible through proxies. I have the various proxy environment variables (like $HTTP_PROXY) set up in an /etc/profile.d script, and the only program on my system which does not pick these up immediately is pacman.

I currently work around that through

XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

in pacman.conf, but wget output clutters the command line, thus obscuring potentially important information inbetween. So for usability's sake, it would be nicer if pacman understood the proxy settings in the first place.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 09 February 2013, 03:47 GMT
Reason for closing:  Not a bug
Additional comments about closing:  libcurl has full proxy support
Comment by Allan McRae (Allan) - Wednesday, 06 February 2013, 10:21 GMT
Try using "http_proxy=..." - see http://curl.haxx.se/libcurl/c/libcurl-tutorial.html
Comment by Stefan Majewsky (majewsky) - Thursday, 14 February 2013, 12:52 GMT
I see. The problem was with my sudo dropping the proxy environment variables.

With Defaults env_keep += "http_proxy ..." in sudoers.conf, everything works.

Loading...