Bug 454096 - yum clean works not as expected in case of moved repository
yum clean works not as expected in case of moved repository
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: James Antill
Depends On:
  Show dependency treegraph
Reported: 2008-07-04 11:46 EDT by Berthold Cogel
Modified: 2009-03-25 01:43 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-25 01:43:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Berthold Cogel 2008-07-04 11:46:26 EDT
Description of problem:
For internal use (some scripts and helpers..) I've created a local repository
for RHEL5 noarch,i386 and x86_64. 

Path: .../yum/i386/ (noarch and x86_64 likewise)
URL: http://.../yum/i386/

I've created a repo file for two repositories with 

[local noarch]


[local binaries]

This worked perfectly. But then I decided to support our RHEL3/4 systems too. So
I created within the yum directory directories 3 4 5 with subdirectories i386
and x86_64


I've created the repositories and a new repo file for RHEL5. And I've created
symlinks '5Server' and '5Client' to '5'. 

[local noarch]


[local binaries]

What happens now on the systems I've used for the tests before is that the repo
data get loaded and parsed. But when yum tries to retrieve a file from the
'local binaries' repository, the URL gets mixed up:

Path to file: .../yum/5/i386/my.rpm
URL called by yum: http://.../yum/i386//my.rpm

yum clean all doesn't help. I had to delete the complete data in /var/cache/yum
for the repository.

Version-Release number of selected component (if applicable):

How reproducible:
The problem occured on two different systems with i386 and x86_64. But I don't
have the time at the moment to redo all from start. So ...

Steps to Reproduce:
1. create new repository
2. connect system to repository
3. move repository
4. retry connect system to repository
Actual results:
Not all repository informations get cleaned.

Expected results:
yum should check/clean paths too

Additional info:
Comment 1 James Antill 2009-03-25 01:43:50 EDT
 If yum still has the database info. cached it'll use it (and thus. not know about the new paths).
 There were also bugs in older yum-rhn-plugin that made yum clean not clean non-rhn repos.

 Likely you hit both of these.

Note You need to log in before you can comment on or make changes to this bug.