Bug 63184

Summary: apmd cannot be removed because of %triggerpostun
Product: [Retired] Red Hat Public Beta Reporter: Chris Adams <linux>
Component: apmdAssignee: wdovlrrw <brosenkr>
Status: CLOSED DUPLICATE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: skipjack-beta2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-10 21:50:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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 ***