Bug 169623 - %triggerun refers to incorrect version
Summary: %triggerun refers to incorrect version
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kbd (Show other bugs)
(Show other bugs)
Version: 4.0
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Miloslav Trmač
QA Contact:
Depends On: 170567
Blocks: 189992 FAST4.5APPROVED
TreeView+ depends on / blocked
Reported: 2005-09-30 11:18 UTC by Jay Turner
Modified: 2015-01-08 00:10 UTC (History)
1 user (show)

Fixed In Version: RHBA-2006-0672
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-27 06:38:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0672 normal SHIPPED_LIVE kbd bug fix update 2007-05-01 13:54:53 UTC

Description Jay Turner 2005-09-30 11:18:01 UTC
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:
Actual results:

Expected results:

Additional info:

Comment 1 Miloslav Trmač 2005-09-30 13:11:07 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.

Comment 2 Jay Turner 2005-09-30 16:25:21 UTC
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.

Comment 3 Miloslav Trmač 2005-09-30 16:39:29 UTC
(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).

Comment 4 Florian La Roche 2005-10-04 10:51:42 UTC
Triggers are not kept forever, so releasing a fixed package should also
fix this update problem.


Florian La Roche

Comment 5 Jay Turner 2005-10-04 12:25:40 UTC
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"

Comment 17 Red Hat Bugzilla 2006-09-27 06:38:16 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.