Bug 444948 - repodiff doesn't delete old data in the repos. it creates
Summary: repodiff doesn't delete old data in the repos. it creates
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum-utils   
(Show other bugs)
Version: 5.2
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: James Antill
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-02 09:31 UTC by Jan Hutař
Modified: 2018-10-20 03:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 22:05:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0227 normal SHIPPED_LIVE yum-utils bug fix update 2009-01-20 16:06:29 UTC

Description Jan Hutař 2008-05-02 09:31:49 UTC
Description of problem:
repodiff do not outputs expected changes.

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

How reproducible:

Steps to Reproduce:
1. # yum list available --disablerepo=\* --enablerepo=test1
2. # yum list available --disablerepo=\* --enablerepo=test2
3. # repodiff --old=file:///tmp/test1/ --new=file:///tmp/test2/

Actual results:
# yum list available --disablerepo=\* --enablerepo=test1
somepackage.i386                         0.2-2                  test1           
test-exclude.i386                        0.2-2                  test1           
test-obsoleted.i386                      0.1-1                  test1           
test-obsoletes.i386                      0.1-1                  test1           
test-only-new.i386                       0.2-2                  test1           
test-regular.i386                        0.2-2                  test1
# yum list available --disablerepo=\* --enablerepo=test2
somepackage.i386                         0.1-1                  test2           
test-exclude.i386                        0.1-1                  test2           
test-obsoleted.i386                      0.1-1                  test2           
test-obsoletes.i386                      0.1-1                  test2           
test-regular.i386                        0.1-1                  test2
# repodiff --old=file:///tmp/test1/ --new=file:///tmp/test2/
setting up old repo file:///tmp/test1/
0 packages excluded due to repository protections
setting up new repo file:///tmp/test2/
0 packages excluded due to repository protections
performing the diff
0 packages excluded due to repository protections
0 packages excluded due to repository protections

Expected results:
should show differences between these two repos

Comment 3 RHEL Product and Program Management 2008-09-25 13:25:52 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 12 James Antill 2008-09-29 05:08:45 UTC
 Sorry, I didn't spot this in your comment #9. From repodiff --help:

          -a ARCHLIST, --archlist=ARCHLIST
                In addition to src.rpms, any arch you want to include

...so with the above two repos. (which just have .noarch packages) you want:

repodiff -a noarch \
-o http://honeypot.usersys.redhat.com/yum/ \
-n http://honeypot.usersys.redhat.com/yum2/

...you still need the patch in yum-utils-1.1.16-8.el5.noarch or the time comparison does weird things, but the above should clear the confusion up, no?:)

Comment 20 errata-xmlrpc 2009-01-20 22:05:52 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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