Bug 1323796 - incorrect centos7 repodata - deleted build present
Summary: incorrect centos7 repodata - deleted build present
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: clime
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 18:05 UTC by Petr Vobornik
Modified: 2016-05-05 13:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-05 13:06:24 UTC


Attachments (Terms of Use)

Description Petr Vobornik 2016-04-04 18:05:07 UTC
Description of problem:

Repodata probably contains deleted build which prevents from installing correct packages.


Version-Release number of selected component (if applicable):
current https://copr.fedorainfracloud.org/


How reproducible:
not sure, valid at  @freeipa/freeipa-4-3-centos7 


Steps to Reproduce:
1. build newer version of package in COPR, e.g. 389-ds-base-1.3.5.1-1.el7.centos.x86_64
2. try to install it on vm (probably not relevant)
3. delete the build
4. build older version of the same packages, e.g.  1.3.4.8-1.el7.centos 
5. # yum clean all
6. try to install it `yum install 389-ds-base` - newer build is used

Step 6. tested also on fresh vm (no yum cache).

By looking at: https://copr-be.cloud.fedoraproject.org/results/%40freeipa/freeipa-4-3-centos7/epel-7-x86_64/ I can see that deleted builds are present in the diretory - don't know if relevant.


Actual results:


Expected results:
Install attempt from step 6 will use the package from step 4 (assuming that no other un-deleted build in the repo has higher version)


Additional info:
Maybe related: I've also built package with version 1.3.4.8-1.el7.centos, deleted the build, corrected spec (removed one dependency), rebuild the package with same version 1.3.4.8-1.el7.centos. Result: yum still tries to add the dependency(version of the package specified explicitly in yum install). This issue has workaround - bump the dependency, but it is not applicable for the above.

Comment 1 Petr Vobornik 2016-04-05 15:46:04 UTC
I've worked around the issue by recreating the project. But still it is a bug.

Comment 2 clime 2016-04-08 09:38:18 UTC
Fixed by 3a26ea9d. Thank you.

Comment 3 Miroslav Suchý 2016-05-05 13:06:24 UTC
Package including this fix has been deployed on production instance of Copr.


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