Bug 1054306 - bsd-games install fails due to preinstall script failure
Summary: bsd-games install fails due to preinstall script failure
Keywords:
Status: CLOSED DUPLICATE of bug 1054350
Alias: None
Product: Fedora
Classification: Fedora
Component: bsd-games
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Makey
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-16 15:18 UTC by Bart Wiegmans
Modified: 2014-01-17 22:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-17 22:29:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bart Wiegmans 2014-01-16 15:18:29 UTC
Description of problem:

Trying to install bsd-games for some good old entertainment, but yum can't install it. 

Version-Release number of selected component (if applicable):

2.17.43.fc20 on x86_64

How reproducible:


Steps to Reproduce:
1. Open a terminal
2. Enter sudo yum install bsd-games
3. See it fail

Actual results:
error: %pre(bsd-games-2.17-43.fc20.x86_64) scriptlet failed, exit status 127

Expected results:
bsd-games installed

Additional info:

Comment 1 Jeff Makey 2014-01-17 05:57:32 UTC
Responses to the thread starting at https://lists.fedoraproject.org/pipermail/users/2014-January/445549.html indicate that this failure is caused by SELinux.  If so, there should be a corresponding audit log message.

The responses also say it should be fixed after the selinux-policy-targeted-3.12.1-117.fc20 RPM (currently in testing) is installed.

Another way to work around unwanted interference by SELinux is to switch to permissive mode with a "sudo setenforce Permissive" command and then do the yum install.  Don't forget to return to enforcing mode afterward with a "sudo setenforce Enforcing" command.

Comment 2 Michael Schwendt 2014-01-17 22:29:32 UTC
https://lists.fedoraproject.org/pipermail/users/2014-January/445588.html

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