Bug 1055035 - Error in PREIN scriptlet in rpm package glibc-headers-2.18-11.fc20.x86_64
Summary: Error in PREIN scriptlet in rpm package glibc-headers-2.18-11.fc20.x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 1054350
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-18 05:29 UTC by Ian Kelling
Modified: 2016-11-24 12:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-19 08:31:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ian Kelling 2014-01-18 05:29:49 UTC
Description of problem:
glibc-headers fails to install

Version-Release number of selected component (if applicable):
2.18-11.fc20.x86_64

How reproducible:
Very easily. My system was freshly installed.

Steps to Reproduce:
1 yum -y install glibc-headers

Actual results:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
error: %pre(glibc-headers-2.18-11.fc20.x86_64) scriptlet failed, exit status 127
Error in PREIN scriptlet in rpm package glibc-headers-2.18-11.fc20.x86_64
  Verifying  : glibc-headers-2.18-11.fc20.x86_64                                                                                                                            1/1 

Failed:
  glibc-headers.x86_64 0:2.18-11.fc20                                                                                                                                           

Complete!


Expected results:
success

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=844167 is similar and I found a workaround of running "setenforce 0" allowed the install to succeed.

Comment 1 Michael Schwendt 2014-01-19 08:31:41 UTC
https://fedoraproject.org/wiki/Common_F20_bugs#RPM_scriptlets_fail_during_updates

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


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