Bug 169623
Summary: | %triggerun refers to incorrect version | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Jay Turner <jturner> |
Component: | kbd | Assignee: | Miloslav Trmač <mitr> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHBA-2006-0672 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-09-27 06:38:16 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: | |||
Bug Depends On: | 170567 | ||
Bug Blocks: | 189992, 201655 |
Description
Jay Turner
2005-09-30 11:18:01 UTC
This is #144434, already fixed in rawhide. kbd-1.08-10.2 contains the same trigger, so it would trigger on _itself_. AFAICS there's no way to fix that except asking the user to rpm -e --notriggers kbd. Correct, there is on way to fix -10.2 but figured it might be worthwhile to release an updated version of the kbd package for RHEL-3 which didn't have the trigger. That would help prevent problems when using anaconda to update to RHEL4. (Bug 144434, comment 12 says even an upgrade wouldn't get rid of the trigger. I don't quite believe that, but if it is so, we could only fix updates from the new version, that never had -10.2.) But yes, we can fix at least upgrades from fixed RHEL3 to fixed RHEL4 (the same change is missing in RHEL4). Triggers are not kept forever, so releasing a fixed package should also fix this update problem. greetings, Florian La Roche Yeah, my intent was to get a package with the correct trigger released so that folks that updated from the new RHEL3 package to RHEL4 wouldn't hit the "bad" trigger. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0672.html |