On Fri, Sep 16, 2016 at 01:22:12PM +0200, Thomas Goirand wrote:
> On 09/16/2016 01:20 AM, Santiago Vila wrote:
> > Thomas: Would you take care of filing whatever bug is necessary for
> > this solution to be implemented?
>
> That's IMO not needed, as python-cryptography 1.5-2 already has:
>
> Brea
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
On 09/16/2016 01:20 AM, Santiago Vila wrote:
> On Thu, Sep 15, 2016 at 06:04:54PM -0400, Scott Kitterman wrote:
>
>> I think it would be simpler and more correct for python-cryptography to
>> declare a breaks relationship with python-openssl, e.g. (in the binary
>> control
>> stanza for python-
On Fri, Sep 16, 2016 at 09:57:43AM +0100, 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
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 detail
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 pyope
On Thu, Sep 15, 2016 at 10:50 PM, 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...).
for this specific case, it would jus
Santiago Vila writes:
> I was the one who asked for these build-depends to become versioned.
> My rationale for that is in policy when it says that "it must be
> possible to build the package when the build-dependencies are met".
> If this is not the case it may be argued that the source packag
Thomas Goirand writes:
> Someone is insisting that I should set the minimum version of
> python-openssl in my packages, just to avoid the bug of pyopenssl. I
> replied that if we were to do so in Debian, the work would be
> exponential, and that this is not what we should do: the bug in
> pyopens
On Thu, Sep 15, 2016 at 06:04:54PM -0400, Scott Kitterman wrote:
> I think it would be simpler and more correct for python-cryptography to
> declare a breaks relationship with python-openssl, e.g. (in the binary
> control
> stanza for python-cryptography):
>
> Breaks: python-openssl (<< FIRST_
On Thursday, September 15, 2016 11:50:33 PM Thomas Goirand wrote:
> Hi everyone,
>
> 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...).
>
> Someo
11 matches
Mail list logo
