Bug 885159
Summary: | yum don't warning for cert. files with the same basename | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Patrik Kis <pkis> |
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
Status: | CLOSED ERRATA | QA Contact: | Patrik Kis <pkis> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | grajaiya, james.antill, jstodola, jzeleny, ksrot, rcyriac, sgraf, tlavigne, walters, zpavlas |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | yum-3.2.29-37.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:13:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 841211 |
Description
Patrik Kis
2012-12-07 16:01:08 UTC
1) Confirmed regression, the code that checks for duplicated basenames is dead, as _getRepos() is never called with doSetup = True. 2) This probably never worked, UNLESS at least one --enablerepo option was used. Patch BZ-880968-verify-options-before-diiung.patch removes self.base._getRepos(doSetup=True) call when handling --enablerepo option, so it manifests as a regression. 3) This bug is also present in HEAD. Fixing this is probably simple: http://lists.baseurl.org/pipermail/yum-devel/2012-December/009818.html Added the latest patch that's ACKd. Added missing imports and checks to the backport. Fixed in 3.2.29-38. http://bulk-mail.corp.redhat.com/archives/cvs-commits-list/2012-December/msg04653.html *** Bug 887322 has been marked as a duplicate of this bug. *** *** Bug 887241 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0406.html |