On 03/01/18 12:55 +0000, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jan 03, 2018 at 11:43:34AM +0000, Jonathan Wakely wrote:
On 02/01/18 12:45 +0000, Zbigniew Jędrzejewski-Szmek wrote:
>On Mon, Jan 01, 2018 at 10:13:15PM +0000, Fedora Rawhide Report wrote:
>>[python-lmiwbem]
>> python2-lmiwbem-0.7.2-16.fc28.aarch64 requires boost-python >= 0:1.50.0
>Hmm, boost-python was renamed to python2-boost, and then to boost-python2, and
>the Provides for the old name was lost in the second step. Is this intentional?
>/cc jwakely
boost-python[23] is not a Python module, it's a C++ library. The rules
for naming of Python modules do not apply to this package.
But I think it should still provide the old name.
Agreed on both counts ;) I guess Provides:boost-python, boost-python%_isa must
following the same lifecycle as %python_provide, i.e. when %python_provide
switches the unversioned name to point to python3 version, boost-python
should likewise stop pointing to boost-python2.
I'll add the Provides later today.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
