Project

General

Profile

Bug #1776

repodata not readable in centos 5

Added by konrad rzentarzewski over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
easy
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

yum fails with:

http://yum.theforeman.org/releases/1.0/el5/x86_64/repodata/e9674ebe7cce825f6764827e00cc2fd7aea3dc0a92eb29e9fc28a18bf1883482-primary.sqlite.bz2: [Errno -3] Error performing checksum

can you switch to

createrepo --checksum "sha"

which will calculate sha1?

log.txt log.txt 2.72 KB Siert Z., 11/19/2012 03:23 PM

History

#1 Updated by Sam Kottler over 10 years ago

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).

#2 Updated by Siert Z. about 10 years ago

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.

#3 Updated by Siert Z. about 10 years ago

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.

#4 Updated by konrad rzentarzewski about 10 years ago

since that time we've migrated to local repository, where we generate indices ourselves. so, unfortunately, i can't replicate it anymore.

#5 Updated by Sam Kottler almost 10 years ago

  • 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.

#6 Updated by Dominic Cleal over 9 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF