Bug 63184 - apmd cannot be removed because of %triggerpostun
Summary: apmd cannot be removed because of %triggerpostun
Status: CLOSED DUPLICATE of bug 62615
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: apmd
Version: skipjack-beta2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: wdovlrrw
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2002-04-10 21:50 UTC by Chris Adams
Modified: 2007-04-18 16:41 UTC (History)
0 users

Clone Of:
Last Closed: 2002-04-10 21:50:35 UTC

Attachments (Terms of Use)

Description Chris Adams 2002-04-10 21:50:31 UTC
Attempting to "rpm -e apmd" results in:

error reading information on service apmd: No such file or directory
error: execution of %trigger scriptlet from apmd-3.0.2-7 failed, exit status 1

The problem is that the %preun does "chkconfig --del apmd", but there is a
%triggerpostun that tries to "chkconfig --add apmd".

This happens because the %trigger is done if the version is less than
3.0final-6, and the apmd in skijack2 is 3.0.2-7 (which compares as less).

Comment 1 Bill Nottingham 2002-04-10 22:31:19 UTC

*** This bug has been marked as a duplicate of 62615 ***

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