[openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress
davanum at gmail.com
Mon Apr 11 21:27:26 UTC 2016
Looked at current docker-py and came up with this:
On Mon, Apr 11, 2016 at 3:43 PM, Hongbin Lu <hongbin.lu at huawei.com> wrote:
> Hi Thierry,
> Thanks for your advice. I submitted a patch  to downgrade docker-py to 1.7.2. In long term, we will negotiate with upstream maintainers to resolve the module conflicting issue.
>  https://review.openstack.org/#/c/304296/
> Best regards,
>> -----Original Message-----
>> From: Thierry Carrez [mailto:thierry at openstack.org]
>> Sent: April-11-16 5:28 AM
>> To: openstack-dev at lists.openstack.org
>> Subject: Re: [openstack-dev] [magnum][requirements][release] The
>> introduction of package py2-ipaddress
>> Hongbin Lu wrote:
>> > Hi requirements team,
>> > In short, the recently introduced package py2-ipaddress  seems to
>> > break Magnum. In details, Magnum gate recently broke by an error:
>> > "'\xac\x18\x05\x07' does not appear to be an IPv4 or IPv6 address" 
>> > (the gate breakage has been temporarily fixed but we are looking for
>> > permanent fix ). After investigation, I opened a ticket in
>> > Cryptography for help . According to the feedback from
>> > community, the problem is from py2-address, which was introduced to
>> > OpenStack recently .
>> > I wonder if we can get any advice from requirements team in this
>> > regards. In particular, what is the proper way to handle the
>> > problematic package?
>> >  https://review.openstack.org/#/c/302539/
>> >  https://bugs.launchpad.net/magnum/+bug/1568212
>> >  https://bugs.launchpad.net/magnum/+bug/1568427
>> >  https://github.com/pyca/cryptography/issues/2870
>> py2-ipaddress was introduced as a dependency by docker-py 1.8.0.
>> Short-term solution would be to cap <1.8.0 in global-requirements
>> (which will make us fallback to 1.7.2 and remove py2-ipaddress).
>> If the two modules are conflicting we should determine which one is the
>> best and converge to it. ipaddress seems a lot more used and pulled by
>> a lot of packages. So long-term solution would be to make docker-py
>> upstream depend on ipaddress instead...
>> Thierry Carrez (ttx)
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-
>> request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Davanum Srinivas :: https://twitter.com/dims
More information about the OpenStack-dev