Bug 1307037

Summary: [libsrtp] wrong naming of shared library: libsrtp.so.1 is not a symbolic link
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: libsrtpAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gryt2, jeff, tcallawa
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: 2016-02-12 14:45:17 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:
Embargoed:

Description Joachim Frieben 2016-02-12 14:22:15 UTC 
Description of problem:
In violation of the Fedora packaging guidelines, libsrtp contains a single shared library libsrtp.so.1 whereas normally this should be the name of a symbolic link to some shared library libsrtp.so.1.X.Y.
This bug causes recurrent complaints of ldconfig namely that libsrtp.so.1 is not a symbolic link.

Version-Release number of selected component (if applicable):
libsrtp-1.5.4-1.fc24

How reproducible:
Always

Steps to Reproduce:
1. Update to latest development build libsrtp-1.5.4-1.fc24.

Actual results:
The only entry in /usr/lib64/ belonging to package libsrtp-1.5.4-1.fc24 is libsrtp.so.1, and ldconfig complains that "libsrtp.so.1 is not a symbolic link".

Expected results:
There are two entries in /usr/lib64/ belonging to package libsrtp-1.5.4-1.fc24, namely libsrtp.so.1.X.Y and a symbolic link libsrtp.so.1.X.Y -> libsrtp.so.1.

Additional info:
None
Comment 1 Tom "spot" Callaway 2016-02-12 14:45:17 UTC 
It was too much to assume that upstream got this right... sorry about that and thanks for the quick bug filing. This is fixed in libsrtp-1.5.4-2.fc24.
Comment 2 Tom "spot" Callaway 2016-02-16 19:21:57 UTC 
*** Bug 1307270 has been marked as a duplicate of this bug. ***