Bug 213260
| Summary: | depsolver "reduced installs:" choosing wrong packages | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Howarth <paul> | ||||||||
| Component: | yum | Assignee: | James Antill <james.antill> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6 | CC: | opensource | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2007-08-03 20:18:05 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Paul Howarth
2006-10-31 15:07:53 UTC
Created attachment 139859 [details] mock root.log with yum-3.0-6 This is the root.log from an attempted build of mod_fcgid using yum 3.0-6 with my regular mock configuration and debugging at level 7. Some useful trace information is missing because of tracebacks caused by Bug #212850. Created attachment 139860 [details] mock root.log with modified yum-3.0-6 This is the root.log from an attempted build of mod_fcgid using a modified version of yum 3.0-6 to fix the tracebacks mentioned in Bug #212850, with my regular mock configuration and debugging at level 7. This log shows the late decision to replace selinux-policy-devel (from updates) by selinux-policy (from core). Created attachment 139861 [details] mock root.log with modified yum-3.0-6 and explicit exclusion of selinux-policy from core repo This is the root.log from a successful build of mod_fcgid using the modified version of yum 3.0-6 to fix the tracebacks mentioned in Bug #212850, with a modified mock configuration excluding the selinux-policy package from the core repo, and debugging at level 7. This is because the selinux-policy package from FC5 has an unversioned obsolete of selinux-policy-devel. Not sure why you're not picking up the newer (and in fc5-updates) selinux-policy package, though... OK, the evil unversioned obsolete partly explains the behaviour them. I note though that the Core FC5 doesn't have a provide to go with that obsolete. So what I think intuitively should happen is that the request for selinux-policy-devel should result in the package of that name from the updates repo being installed. Now yum may realise that on its next run it could replace that selinux-policy-devel with selinux-policy from FC5 core because of the unversioned obsolete, and hence install that instead. However, following that same argument, the selinux-policy package from updates should be installed instead because that one naturally replaces the package from the core repo (as you mentioned). The key difference here I think is that the package in updates doesn't have the obsolete. How about obsoletes only being checked in the latest available package of each name from the selected repos? Would this cause any problems? > How about obsoletes only being checked in the latest available package of each
> name from the selected repos? Would this cause any problems?
I think this is an important feature to make sure that packaging mistakes can be
fixed within a release. This actual beheaviour of yum also causes problems when
an old packages obsolutes foo because a project was renamed from "foo" to "bar"
and there is another, completely different project with name "foo", too. This
happended lately with track (foo := track)
Is this better in the yum in the devel tree? (I think it _shoudl_ be) closing due to no response I must have missed the NEEDINFO somehow. FWIW, this problem is no longer present in yum 3.2.2-1.fc7 |