Bug 516972
| Summary: | Unable to update RHEL 5.2 (gecko-libs is needed by ) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jon Solanu <jsolanu> |
| Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.2 | CC: | james.antill, mcepl, stransky |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-12 20:42:49 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
Jon Solanu
2009-08-12 04:32:40 UTC
See the line: There are unfinished transactions remaining. You mightconsider running yum-complete-transaction first to finish them. Anyway, gecko-libs is provided by xulrunner package (no by firefox) so ensure you have the latest xulrunner installed. From the log, it was not downloaded by yum. This must be (In reply to comment #1) > There are unfinished transactions remaining. You mightconsider running > yum-complete-transaction first to finish them. Does it make any difference if you complete yum transactions first? > Anyway, gecko-libs is provided by xulrunner package (no by firefox) so ensure > you have the latest xulrunner installed. From the log, it was not downloaded by > yum. Otherwise this looks more like a problem in yum. Reassigning. if you don't want to run yum-complete-transactions try running: package-cleanup --dupes and package-cleanup --problems Yes, incomplete transactions can cause "weird" behaviour. As Seth says you can do it "by hand" as long as you make sure everything is happy afterwards. Also this is against 5.2, both yum and rpm have had a lot of bug fixes since 5.2 so it's very possible that the "rpm_check_debug vs depsolve" problem would go away if you update. Of course as soon as I say that I realize that the yum in the example isn't the one in 5.2, so what version is it? |