Bug 474485
Summary: | Yumex unable to download on a corporate network that resolves external addresses on the proxy only. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Stimpson <paul> |
Component: | yumex | Assignee: | Tim Lauridsen <tim.lauridsen> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | jrodary, paul, tim.lauridsen |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-18 07:08:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul Stimpson
2008-12-04 00:42:10 UTC
I yum working with this proxy setup ? yumex is using yum for all the real action, and yum uses urlgrabber to get stuff from the network. Yum only works when the http-proxy (and also the https-proxy but not sure if that is needed) environment variable is set. How does Yumex pass the proxy details to yum? it sets the http_proxy environment variable to the values defined in the preferences. If I enter any of the following into the "use proxy" field in yumex preferences all downloads fail: http://ourproxy.division.ourcompany.com http://ourproxy.division.ourcompany.com:80 ourproxy.division.ourcompany.com ourproxy.division.ourcompany.com:80 If I su - then enter the following: export http_proxy=http://ourproxy.division.ourcompany.com:80 yum install somepackage The transaction succeeds. if you are running F11 now, could you retest with yumex-2.9.x you can find the packages here: http://timlau.fedorapeople.org/files/yumex/ This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |