Bug 165151
Summary: | RFE: yum multi-lib conflict reports should list archs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tony Nelson <tonynelson> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | katzj, nobody+pnasrat |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-19 20:03:46 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: |
Description
Tony Nelson
2005-08-04 18:02:49 UTC
Seth -- what do you think about changing everything that prints out a package name to be name.arch? I think we probably also want to move this to be part of the default rpm query output in lots of cases we don't have that info being handed back from rpm. and if we change it in the default rpmq you better announce it heavily b/c it will break A LOT of scripts. The arch info is only needed when there are conflicts already found. Could RPM be queried a second time in such cases? Then there would be no need to change any default queries, only to add a new query. The problem is we can't know what it is. if I get back foo-1.1-1 from rpm and we have foo-1.1-1.i386 and foo-1.1-1.x86_64 installed yum has no way of knowing which it was asking about. it has to guess. Then if yum can't do any better, it should query RPM to find if there are potential arch conflicts and if so tell the user that the conflict may stem from incompatible archs. conflicts aren't arch-specific. Right, when you get a conflict you have to find out more about it to be useful to the user. Query RPM to find out if the conflict /could/ be from multiple archs, if you can't find out if it /is/. Give the user a clue to work with. When a conflict is reported by RPM, get more info about the installed versions of packages from RPM, including their arch. If the conflicting packages come in different archs, tell the user it may be an arch conflict for those packages. |