Bug 1012713

Summary: Error removing acpid.x86_64 0:2.0.19-5.fc19
Product: [Fedora] Fedora Reporter: Michael Fischer <fischer-michael>
Component: acpidAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: jkaluza, jskarvad, ted
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-27 09:02:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Fischer 2013-09-27 01:24:56 UTC
Description of problem: During update to acpid-2.0.20-1.fc19.x86_64, yum failed while erasing acpid-2.0.19-5.fc19.x86_64.  Result: Both packages still installed.

Version-Release number of selected component (if applicable): 
acpid-2.0.19-5.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum erase acpid-2.0.19-5.fc19.x86_64
2.
3.

Actual results:
...
Running transaction
/var/tmp/rpm-tmp.1mReSQ: line 1: fg: no job control
error: %preun(acpid-2.0.19-5.fc19.x86_64) scriptlet failed, exit status 1
Error in PREUN scriptlet in rpm package acpid-2.0.19-5.fc19.x86_64
  Verifying  : acpid-2.0.19-5.fc19.x86_64                                  1/1 

Failed:
  acpid.x86_64 0:2.0.19-5.fc19 
                                              
Expected results:
Running transaction
  Erasing    : acpid-2.0.19-5.fc19.x86_64                                  1/1 
  Verifying  : acpid-2.0.19-5.fc19.x86_64                                  1/1 

Removed:
  acpid.x86_64 0:2.0.19-5.fc19 

Additional info:
I'm able to successfully erase acpid-2.0.20-1.fc19.x86_64, but even with it out of the way, an attempt to erase acpid-2.0.19-5.fc19.x86_64 still fails as described above.

Comment 1 Jaroslav Škarvada 2013-09-27 09:02:19 UTC
This is dupe of bug 995158. Unfortunately it is not possible to do anything about it. The problem happened due to some change in the build system and wasn't spotted by the QE. You need to remove the wrong acpid-2.0.19-5.fc19.x86_64 by the following command:
# rpm -e --noscripts acpid-2.0.19-5

Sorry for the inconvenience.

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

Comment 2 Michael Fischer 2013-09-27 18:44:45 UTC
Thank you for the workaround.  Sorry for not finding the dupe myself.