|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper does not respect the environment variable http_proxy, but uses the settings in /etc/sysconfig/proxy | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Richard Bos <richard.bos> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | dmacvicar, dma_k, erico.mendonca, forgotten_xI2C5NvggO, ma, per |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 655483 | ||
| Bug Blocks: | |||
|
Description
Richard Bos
2009-11-25 21:33:43 UTC
This is related to bug #555066. We need to figure out why /etc/sysconfig/proxy overrules the environment. I guess this was done to immediately reflect changes done by the YaST proxy configuration. So we'd need a fix for that usecase. > We need to figure out why /etc/sysconfig/proxy overrules the environment. I
> guess this was done to immediately reflect changes done by the YaST proxy
> configuration. So we'd need a fix for that usecase.
Hmm, that is a good point. You don't want a user to exit YaST and its related shell, to have him or her re-enter the shell and YaST to have the proxy variable reread.
Zypper should not read /etc/sysconfig/proxy, that is more a task for YaST.
As YaST controls and knows when /etc/sysconfig/proxy is changed, and also knows
when the related proxy variables are changed, YaST should instruct zypper how to deal with the proxy. This seems possible with aria2c --http-proxy=HOST:PORT argument.
In normal cases YaST and hence Zypper should always use the environment variables, in the (rare ;) ) situation that the user changes the proxy settings, YaST should overwrite the environment settings and instruct aria2c via the --http-proxy=HOST:PORT how to deal with the proxy. Or perhaps YaST can change the value of the environment variable http_proxy while running?
Hopefully this is can be implemented in YaST?!
I can confirm this bug. This is fatal in a company environent where users are forced to use an authenticating proxy. After 1.) changing the repos von 11.1 to 11.2 2.) zypper refresh 3.) zypper install zypper zypper dup will not work anymore: Failed to download /repodata/repomd.xml from http://download.opensuse.org/repositories/Emulators%3a/Wine/open SUSE_11.2/ Abort, retry, ignore? [a/r/i/?] (a): After reading this and the other bug report I changed the entry HTTP_PROXY=http://USERNAME:PW@proxy-url:PORT This is a workaround only. It worked in openSUSE 11.2. Please fix asap Thank you! In 11.4 we use libproxy (see bug:655483). We wrote a module for libproxy to use /etc/sysconfig/proxy. However libproxy modules do not have order and basically the first module that says "YES" is used. The sysconfig module gets activated if you are running as root, so the behavior will be the same as before. As in SUSE the variables _come_ from sysconfig this should not be a problem. I don't see a better way to know when sysconfig should not be used. We thought about using the YAST_IS_RUNNING variable but it is not a very clean solution. In 11.4 we use libproxy (see bug:655483). We wrote a module for libproxy to use /etc/sysconfig/proxy. However libproxy modules do not have order and basically the first module that says "YES" is used. The sysconfig module gets activated if you are running as root, so the behavior will be the same as before. As in SUSE the variables _come_ from sysconfig this should not be a problem. I don't see a better way to know when sysconfig should not be used. We thought about using the YAST_IS_RUNNING variable but it is not a very clean solution. fixed in 11.4 |