Description of problem:

rpm -q --requires python-qpid-common
/usr/bin/env
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libm.so.6()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libqpidmessaging.so.2()(64bit)
libqpidtypes.so.1()(64bit)
libstdc++.so.6()(64bit)
libstdc++.so.6(CXXABI_1.3)(64bit)
libstdc++.so.6(GLIBCXX_3.4)(64bit)
libstdc++.so.6(GLIBCXX_3.4.11)(64bit)
libstdc++.so.6(GLIBCXX_3.4.15)(64bit)
libstdc++.so.6(GLIBCXX_3.4.20)(64bit)
libstdc++.so.6(GLIBCXX_3.4.9)(64bit)
python(abi) = 2.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
rtld(GNU_HASH)

The libqpidmessaging.so.2 and libqpidtypes.so.1 libraries are part of qpid-cpp-client which requires boost.

These dependencies are bogus, the Python client does not require the C++ client, so should not depend on it, not the C++ runtime libraries.

This means that the Fedora build of the rhpkg tool used to build RHEL unnecessarily depends on Boost even though it only uses the Python qpid bindings. This should be fixed.

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

python-qpid-common-0.32-4.fc22.x86_64


How reproducible:

Always


Additional info:

The bogus dependencies are due to the following section of the spec file:

 %files -n python-qpid-common
 %doc LICENSE
 %doc examples

The examples dir contains C++ examples, including compiled object files that depend on libstdc++.so

These should not be included in the python-qpid-common subpackage, C++ example files are of no interest to users of the Python bindings.