Description of problem: Version-Release number of selected component (if applicable): Fedora Beta 3 How reproducible: Always when you need to use a Proxy server. Steps to Reproduce: 1. Set parameter http_proxy="server_name:port" and export the variable In my case I don't need a username/passwd 2. Run up2date -u Actual results: Fetching package list for channel: rawhide... Fetching http://ftp.redhat.com/pub/redhat/linux/rawhide//headers/header.info... ######################################## Traceback (most recent call last): File "/usr/sbin/up2date", line 1183, in ? sys.exit(main() or 0) File "/usr/sbin/up2date", line 761, in main fullUpdate, dryRun=options.dry_run)) File "/usr/sbin/up2date", line 1046, in batchRun batch.run() File "up2dateBatch.py", line 58, in run File "up2dateBatch.py", line 96, in __findPackagesToUpdate File "packageList.py", line 117, in run File "rhnPackageInfo.py", line 315, in getAvailableAllArchPackageList File "rhnPackageInfo.py", line 153, in availablePackageList File "rpcServer.py", line 109, in doCall File "repoDirector.py", line 20, in listPackages File "rpmSource.py", line 226, in listPackages File "/usr/share/rhn/up2date_client/repoBackends/yumRepo.py", line 223, in listPackages (envra, rpmPath) = string.split(line, '=') ValueError: unpack list of wrong size Expected results: To update my system Additional info: This works fine if I run up2date in a machine connected directly to internet
Oops, I forgot to say that up2date fails when the machine is inside a network and you use a proxy for up2date
I also tried to define the proxy server in /etc/wgetrc to see if there was any difference but nothing changed
As additional information. This functionality worked fine in Beta 2
I installed: up2date-4.1.7-1 up2date-gnome-4.1.7-1 And I get: # up2date -u Fetching package list for channel: rawhide... Fetching http://ftp.redhat.com/pub/redhat/linux/rawhide//headers/header.info... There was some sort of I/O error: <urlopen error (110, 'Connection timed out')>
Duplicate of bug 102272 .
*** This bug has been marked as a duplicate of 102272 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.