Bug 1054355 - glibc-headers are uninstallable
Summary: glibc-headers are uninstallable
Keywords:
Status: CLOSED DUPLICATE of bug 1054350
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-16 16:56 UTC by chris desjardins
Modified: 2016-11-24 12:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-16 17:44:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description chris desjardins 2014-01-16 16:56:31 UTC
Description of problem:
glibc-headers package is uninstallable 

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

How reproducible:
100%

Steps to Reproduce:
1. yum update 
2. yum install glibc-headers

Actual results:
[chris@tg-d09 ~]$ sudo yum install glibc-headers
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.18-11.fc20 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================
 Package                     Arch                 Version                    Repository            Size
========================================================================================================
Installing:
 glibc-headers               x86_64               2.18-11.fc20               fedora               647 k

Transaction Summary
========================================================================================================
Install  1 Package

Total download size: 647 k
Installed size: 2.2 M
Is this ok [y/d/N]: y
Downloading packages:
glibc-headers-2.18-11.fc20.x86_64.rpm                                            | 647 kB  00:00:01     
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  

Expected results:
Expect glibc-headers to be installed.

Additional info:

Comment 1 Carlos O'Donell 2014-01-16 17:08:12 UTC
The %pre script for headers is this:

%pre headers
# this used to be a link and it is causing nightmares now
if [ -L %{_prefix}/include/scsi ] ; then
  rm -f %{_prefix}/include/scsi
fi

A status of 127 indicates that the command to be executed could not be found.

That looks like your system is broken, either your shell or test (executed to handle [] in shell) is broken.

Neither of these things look like glibc problems, but rather stability issues on the system you are using.

Can you try run this shell script?
~~~
#!/bin/sh
# this used to be a link and it is causing nightmares now
if [ -L /usr/include/scsi ] ; then
  rm -f /usr/include/scsi
fi
~~~
Then `echo $?' to see the exit status.

Comment 2 chris desjardins 2014-01-16 17:16:31 UTC
[chris@tg-d09 ~]$ #!/bin/sh
[chris@tg-d09 ~]$ # this used to be a link and it is causing nightmares now
[chris@tg-d09 ~]$ if [ -L /usr/include/scsi ] ; then
>   rm -f /usr/include/scsi
> fi
[chris@tg-d09 ~]$ echo $?
0

This is a fresh install off the DVD today. I installed the Cinnamon desktop and have only applied updates + R, R-devel, and some other development packages.

Comment 3 chris desjardins 2014-01-16 17:44:49 UTC
This should be closed. Because it's related to bug 1054350. Updating selinux-policy from updates-testing worked.

Comment 4 Siddhesh Poyarekar 2014-01-17 04:01:14 UTC

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