Description of problem: kbd-1.08-10.1 includes the keytable service, but kbd-1.0.8-11 doesn't so a %triggerun was added to remove the keytable service upon removal of kbd < 1.08-11: triggerun scriptlet (using /bin/sh) -- kbd < 1.08-11 /sbin/chkconfig --del keytable The problem is that we then built kbd-1.08-10.2 which doesn't include the keytable service and is currently the RHEL3 shipping version of kbd (and includes the above %triggerun) Net result is that when upgrading from RHEL3 -> RHEL4 the trigger fires and we get the following error: Upgrading kbd-1.12-2.x86_64. error reading information on service keytable: No such file or directory error: %trigger(kbd-1.08-10.2.x86_64) scriptlet failed, exit status 1 Should probably think about releasing a new kbd version where the trigger is modified to be: triggerun scriptlet (using /bin/sh) -- kbd < 1.08-10.2 /sbin/chkconfig --del keytable Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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