Bug #1776
closed
I can't reproduce this. Can you try running "yum clean all" and then "yum check-update" and see if that fixes the issue. I've seen something like this before caused by the HTTP caching mechanism in yum (which you can disable in /etc/yum.conf if required).
Indeed, this could be related to yum caches as Sam pointed.
On a clean host I can't reproduce the error. I just bootstrapped a clean EL5 (x86_64) machine and installed the foreman, puppetlabs and EPEL yum repo's:
rpm -ivh http://yum.theforeman.org/releases/1.0/el5/foreman-release.rpm
rpm -ivh http://yum.puppetlabs.com/el/5Server/products/x86_64/puppetlabs-release-5-6.noarch.rpm
rpm -ivh http://mirror.i3d.net/pub/fedora-epel/5/i386/epel-release-5-4.noarch.rpm
Then yum installed foreman without having any issues (see log).
IMO this call can be closed, unless the reporter is still facing the issue and willing to send more output/details.
Siert Z. wrote:
Indeed, this could be related to yum caches as Sam pointed.
On a clean host I can't reproduce the error. I just bootstrapped a clean EL5 (x86_64) machine and installed the foreman, puppetlabs and EPEL yum repo's:
[...]
Then yum installed foreman without having any issues (see log).
IMO this issue can be closed, unless the reporter is still facing the issue and willing to send more output/details.
since that time we've migrated to local repository, where we generate indices ourselves. so, unfortunately, i can't replicate it anymore.
- Status changed from New to Feedback
The repodata for 1.1RC3 and later is generated using --checksum sha, but I'm going to move this to feedback until the new packages and associated repodata are in the stable repo.
- Status changed from Feedback to Closed
Also available in: Atom
PDF
Updated by Sam Kottler 
Updated by 
Updated by 
Updated by