Re: Adding version constraints in dependencies to avoid bugs
On 09/16/2016 10:57 AM, Santiago Vila wrote:
> On Fri, Sep 16, 2016 at 09:40:54AM +0100, Simon McVittie wrote:
>> On Thu, 15 Sep 2016 at 23:50:33 +0200, Thomas Goirand wrote:
>>> Recently, the upload python-cryptography broke pyopenssl, and pyopenssl
>>> had to be upgraded to support the new python-cryptography (I don't have
>>> the exact details, but it doesn't mater much here...).
>>
>> The situation here is that pyopenssl (Build-)Depends on -cryptography and
>> zigos-package Depends on pyopenssl (and possibly -cryptography), right?
>
> More precisely, zigos-package *Build-Depends* on python-openssl, so a
> more appropriate subject for this would have been "Making build-depends
> versioned to avoid *FTBFS* bugs".
I haven't checked, but I suspect there qas also runtime issues. You're
just seeing the FTBFS because it easily exposes the problem (which is
what the unit tests are for).
> I consider this distinction important, as this is not just an "ordinary bug",
> it's a bug which breaks our promise that a source package will build
> from source provided its build-dependencies are fulfilled.
My packages depending on pyopenssl do build well, provided there's the
right matching versions of python-openssl and python-cryptography (and
this, for any version of python-openssl). The issue isn't (and I should
say: wasn't) there, but in the missing Breaks: in python-cryptography
(see other posts in this thread).
Cheers,
Thomas Goirand (zigo)
Reply to: