I and my team have found what we consider to be a major bug in yum 2.4.1. Essentially all you have to do to trigger it is a "yum clean metadata", then something like install or even just check-update: $ sudo yum check-update Setting up repositories (works fine) $ sudo yum clean metadata Cleaning up xml metadata 14 metadata files removed $ sudo yum -d 10 check-update Yum Version: 2.4.1 COMMAND: yum -d 10 Installroot: / Setting up repositories Baseurl(s) for repo: ['http://server/yum/5.00/emergency-install/i386'] Cannot open/read repomd.xml file for repository: emergency-install Cannot find repomd.xml file for emergency-install Error: Cannot find repomd.xml file for emergency-install I can remove the emergency-install repo, but it just fails on the first repo it finds. Essentially yum 2.4.1 fails in downloading a *new* repomd.xml file. If it exists but it is old... no problem. However if it is removed from a "clean all" or even just a "clean metadata" yum command, it won't re-create the file... and chokes because of it. Has anyone else seen this with yum 2.4.1 ? https://devel.linux.duke.edu/bugzilla/show_bug.cgi?id=538 -- Joshua Jensen joshua@xxxxxxxx "If God didn't want us to eat animals, why did he make them out of meat?"
