Bug 1330805

Summary:	boost-devel doesn't provide symlink for boost-python3
Product:	[Fedora] Fedora	Reporter:	Suvayu <fatkasuvayu>
Component:	boost	Assignee:	Jonathan Wakely <jwakely>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	23	CC:	dakingun, denis.arnaud_fedora, jwakely, me
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-27 02:02:12 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:

Description Suvayu 2016-04-27 01:57:52 UTC

Description of problem:
boost-devel provides unversioned symlinks for all of Boost's shared libraries.  A symlink for boost-python3 is missing.

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

How reproducible:
Always

Steps to Reproduce:
1. $ dnf install boost-devel
2. $ ls -lh /usr/lib64/libboost_python*
3.

Actual results:
Step (2) shows the following:
lrwxrwxrwx. 1 root root   25 Jan 16 00:39 /usr/lib64/libboost_python.so -> libboost_python.so.1.58.0
-rwxr-xr-x. 1 root root 308K Jan 16 00:42 /usr/lib64/libboost_python.so.1.58.0
-rwxr-xr-x. 1 root root 296K Jan 16 00:42 /usr/lib64/libboost_python3.so.1.58.0


Expected results:
Step (2) should also list a symlink called libboost_python3.so pointing to libboost_python2.so.1.58.0

Additional info:

Comment 1 Suvayu 2016-04-27 02:02:12 UTC

I just discovered boost-python-devel while looking through http://pkgs.fedoraproject.org/cgit/rpms/boost.git/tree/boost.spec.  Closing this bug.  Sorry about the noise.

Comment 2 Jonathan Wakely 2016-04-27 10:00:16 UTC

Instead of looking at the spec file you can just run:

dnf provides /usr/lib64/libboost_python3.so

Comment 3 Suvayu 2016-04-27 12:19:26 UTC

@Jonathan: Since all other symlinks were provided by one package, I didn't expect a separate package for the "missing" symlink.

Why is it separate though, since boost-python and boost-python3 maybe installed in parallel, is there a need for a separate devel package for Python 3?

Comment 4 Jonathan Wakely 2016-04-27 12:24:56 UTC

Because otherwise if you installed boost-python and boost-devel (but not boost-python3) then you'd have a broken symlink for the boost-python3 shared libraries.

I believe the intention is to support installing all of boost and boost-devel, except the python3 parts. If you want Boost.Python for python3 you need the extra packages.

I assume at some point we'll drop the python2 parts and the extra packages for python3 will go away.