Bug 1012034 - missing dependency on keyutils-libs >= 1.5.6-2
missing dependency on keyutils-libs >= 1.5.6-2
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: krb5 (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nalin Dahyabhai
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-25 11:12 EDT by Petr Lautrbach
Modified: 2013-09-25 12:21 EDT (History)
2 users (show)

See Also:
Fixed In Version: krb5-1.11.3-17.fc21
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-25 12:21:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Lautrbach 2013-09-25 11:12:42 EDT
The krb5-1.11.3-15 package has build requires on keyutils-libs-devel >= 1.5.6-2 but this is not propagated as Require: to built krb5 packages so there's an undefined symbol:

/lib64/libkrb5.so.3: undefined symbol: keyctl_get_persistent


# rpm -qa krb5\*
krb5-devel-1.11.3-16.fc21.x86_64
krb5-libs-1.11.3-16.fc21.x86_64
krb5-workstation-1.11.3-16.fc21.x86_64
krb5-server-1.11.3-16.fc21.x86_64

# rpm -qa keyutils\*
keyutils-libs-1.5.6-1.fc21.x86_64
keyutils-1.5.6-1.fc21.x86_64
keyutils-libs-devel-1.5.6-1.fc21.x86_64


# yum
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   /lib64/libkrb5.so.3: undefined symbol: keyctl_get_persistent
...

# rpm -Uvh http://kojipkgs.fedoraproject.org//packages/keyutils/1.5.6/2.fc21/x86_64/keyutils{,-libs,-libs-devel}-1.5.6-2.fc21.x86_64.rpm

# yum
You need to give some command
Usage: yum [options] COMMAND
Comment 1 Nalin Dahyabhai 2013-09-25 12:21:07 EDT
Thanks for catching this!  The dependency will be there starting in krb5-1.11.3-17.fc21, and I've filed bug #1012043 to keep other packages from having the same problem.

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