Bug 1001022
| Summary: | rpm -e kernel doesn't take kernel-uname-r deps into account? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ville Skyttä <ville.skytta> |
| Component: | rpm | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | ffesti, jzeleny, novyjindrich, packaging-team-maint, pknirsch, pmatilai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 16:55:31 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: | |||
|
Description
Ville Skyttä
2013-08-26 10:43:51 UTC
Here's what I see: [root@localhost Downloads]# rpm -Uvh --nodeps kmod-nvidia-3.10.9-200.fc19.x86_64-319.32-2.fc19.5.x86_64.rpm warning: kmod-nvidia-3.10.9-200.fc19.x86_64-319.32-2.fc19.5.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID cd30c86b: NOKEY Preparing... ################################# [100%] Updating / installing... 1:kmod-nvidia-3.10.9-200.fc19.x86_6################################# [100%] [root@localhost Downloads]# rpm -e --test kernel-3.10.9-200.fc19.x86_64 error: Failed dependencies: kernel-uname-r = 3.10.9-200.fc19.x86_64 is needed by (installed) kmod-nvidia-3.10.9-200.fc19.x86_64-1:319.32-2.fc19.5.x86_64 [root@localhost Downloads]# I guess it could be caused by out-of-sync rpmdb indexes (caused by abnormally terminated transaction) - does 'rpmdb --rebuilddb' fix it? (In reply to Panu Matilainen from comment #1) > does 'rpmdb --rebuilddb' fix it? It does, at least trying to remove the final remaining kernel now fails as it should. And yes, there have been some abnormally terminated transactions earlier on this box, I think it's been a while since the last one though. Ok. The actual bug here is that rpm doesn't automatically detect (and rebuild) out-of-sync indexes. It's a relatively rare thing of course but it can happen and optimally rpm should be able to deal with it. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |