I know this will probably sound very na?ve, but I have three Dell 1850s recently installed with Fedora FC4 64bit; when I try to run YUM with the proxy environment variable set as this: HTTP_PROXY="http://this.proxy.com:8000/"; YUM doesn't recognize the proxy and fails immediately, but with the environment variable set as follows: http_proxy="http://this.proxy.com:8000/"; Case of the variable name seems to be important. I have no idea why this is working for me (I haven't had the time to actually run through the sources, although I suspect it will track back to the python libs), and I originally thought it had to be something else, but I have the exact same behavior on all three machines even though the three boxes were not configured simultaneously or via a disk image; perhaps you might try setting a lowercase shell variable similarly? -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of mbylander@xxxxxxxxxxxxxxx Sent: Saturday, December 31, 2005 3:30 PM To: yum@xxxxxxxxxxxxxxxxxxxx Subject: RE: [Yum] Yum and proxy seth vidal [mailto:skvidal@xxxxxxxxxxxxxx] wrote: Sent: Friday, December 30, 2005 11:10 PM >On Fri, 2005-12-30 at 13:21 -0500, Jim Perrin wrote: >> On 12/30/05, mbylander@xxxxxxxxxxxxxxx <mbylander@xxxxxxxxxxxxxxx> wrote: >> <snip....proxy....microsoft.... blah /> >> > >> > Any ideas about how to fix this? Thanks in advance. >> >> try exporting the shell variable of HTTP_PROXY=proxy_url, or switch >> to an ftp mirror if possible. >> >or better yet - stop using the mirrorlists and see if the proxy problem >goes away. I bet it will - it's a bug in pulling down the mirrorlists, >it will be fixed soon. >-sv Thanks for the ideas. Unfortunately, no luck. The HTTP_PROXY and FTP_PROXY variables are set and work properly with wget. Commenting out the proxy information in yum.conf to force it to use the shell variable did not work. I also tried an ftp repository, with no luck. I have not been trying the mirrorlists at all -- I have one single server indicated with no alternatives. The failure seems to occur very quickly -- like it is not even trying to get through the proxy (or is being rejected by the proxy), but the returned error message doesn't indicate that it had problems with the proxy. What else can I try? Thank you. Mark Bylander _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
