From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b3) Gecko/20050827 Fedora/1.1-0.2.8.deerpark.alpha2 Firefox/1.0+ Description of problem: When Yum is run it takes roughly one minute per repository to set up. This is running yum-2.4.0-1 from rawhide 20050829. Version-Release number of selected component (if applicable): kernel-2.6.12-1.1519_FC5 How reproducible: Always Steps to Reproduce: 1. Run command "sudo yum update" from shell. 2. Note length of time to get and process data. Actual Results: Yum runs but takes about four minutes in all to check for updates. Expected Results: Nice and fast grabbing of repodata and processing with expected result depending on whether packages exist that need updating. Additional info: [chris@kilimanjaro ~]$ date && sudo yum -y update && date Mon Aug 29 17:04:55 BST 2005 Setting up Update Process Setting up repositories development 100% |=========================| 1.1 kB 00:00 livna 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 extras-development 100% |=========================| 1.1 kB 00:00 freshrpms 100% |=========================| 951 B 00:00 Reading repository metadata in from local files No Packages marked for Update/Obsoletion Mon Aug 29 17:07:14 BST 2005
I'm betting you have a failing name server and/or ipv6 name resolution going on when it shouldn't be. try disabling ipv6 support as described here: http://www.fedorafaq.org/fc2/#mozillaipv6 and see if it all speeds up.
Disabling ipv6 doesnt help and even if it did, it would just be another bug. Workarounds are called as such because they do not resolve the underlying problem.
...however you are spot on with regards to the failing name server. Is this an error on my part and yum should not have to cope with dns that do not exist/respond.....?
the disabling ipv6 question wasn't about a workaround - but it would be another bug filed against python, not yum. That's why I asked. If your network card were flaking out and you were getting a slow connection would that be yum's responsibility to know that? no. it can't be.