https://bugzilla.novell.com/show_bug.cgi?id=696129 https://bugzilla.novell.com/show_bug.cgi?id=696129#c0 Summary: zypper does not download more than the metalink file when behind a proxy (Digest verification failed) Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mfrost@rooville.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=431423) --> (http://bugzilla.novell.com/attachment.cgi?id=431423) zypper.log output with ZYPP_ARIA2C=0 and ZYPP_MEDIA_CURL_DEBUG=2 set User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 We are behind corporate firewall/proxies. Each of us ran openSuSE 11.x where x<4 successfully by setting our proxies in /etc/sysconfig/proxies. In pre 11.4 releases, we would occasionally have timeout issues until we set "ZYPP_ARIA2C=0". After moving to 11.4 and using the same proxy settings, we see that running zypper in/ref/dup we will get output like: # zypper ref Retrieving repository 'Updates for openSUSE 11.4 11.4-0' metadata [\] Digest verification failed for d66f4594760bae56c3bc14f72de3937a17e333c7-susedata.xml.gz. Expected d66f4594760bae56c3bc14f72de3937a17e333c7, found 4609d87ba1b7ca13d718d27d3bfdc518f6e61bd8. Continue? [yes/no] (no): If I go and look at the file it downloaded in /var/cache/zypp, this file is actually the metalink XML file and not a .xml.gz file. So what appears to be happening is that it's getting the metalink file, but then not processing it and picking a link in the metalink file to download the actual target file from. As a workaround, I run zypper and leave it at this "Continue?" prompt while I 1) cd into /var/cache/zypper/... to wherever the downloaded file is 2) open the file in question to locate a valid download link 3) delete the file 4) use wget to grab the file from the link (works every time) 5) go back to the zypper prompt and say "yes" to the continue prompt 6) repeat steps 1-5 for each file that's being downloaded If I did not get/replace the file using wget, but told it to continue anyway, it would really blow up as the file is not the file it's expecting. I'm attaching zypper.log contents of one particular run where I explicitly set ZYPP_ARIA2C=0 ZYPP_MEDIA_CURL_DEBUG=2 before executing. Hostnames and IP address in the output have been changed to fake but consistent substitutes. Reproducible: Always Steps to Reproduce: 1.(be behind a corporate proxy configured in /etc/sysconfig/proxy) 2. "zypper ref" or "zypper in XXX" or "zypper dup" 3. Actual Results: see above Expected Results: Correct installation or update of software. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.