[PKG-Openstack-devel] python-pyeclib dependencies
Thomas Goirand
zigo at debian.org
Thu Nov 19 20:17:51 UTC 2015
In such a case, this should be considered a bugfix, and therefore,
there's no need to have pyeclib strict dependency. Only liberasurecode
shall be updated to the last version.
Cheers,
Thomas Goirand (zigo)
On 11/19/2015 03:13 PM, Gohad, Tushar wrote:
> Please disregard the message below. There are no API/ABI changes in 1.1.1, only a include path issue that we fixed. Will investigate further and respond to the next message in this thread. Thanks Thomas.
>
> -----Original Message-----
> From: Thomas Goirand [mailto:zigo at debian.org]
> Sent: Thursday, November 19, 2015 1:07 AM
> To: Gohad, Tushar <tushar.gohad at intel.com>; PKG OpenStack <openstack-devel at lists.alioth.debian.org>
> Subject: Re: python-pyeclib dependencies
>
> On 11/19/2015 05:18 AM, Gohad, Tushar wrote:
>> Hi Thomas,
>>
>> Another important one - we need to update "python-pyeclib-1.1.1"
>> dependencies to specify "liberasurecode-1.1.0-2" exactly. The Ubuntu
>> builds seem to have failed because they picked liberasurecode 1.0.8.
>>
>> Thanks
>>
>> Tushar
>
> Hi,
>
> What you ask isn't possible. Either liberasurecode has changed its API/ABI, and therefore, you should bump the SONAME, either it has not, and the old version 1.0.8 is fine. If you choose the former, then please release a new version of liberasurecode, and on the Debian side, it will produce liberasurecode2, not liberasurecode1.
>
> Everything else (I mean by that: the liberasurecodeX dependency in
> pyeclib) is calculated by dh_shlibsdeb.
>
> So, which one do you choose?
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>
More information about the Openstack-devel
mailing list