On Mon, Apr 2, 2018 at 8:26 AM, Jim Rollenhagen
wrote:
> On Sat, Mar 31, 2018 at 7:24 PM, Matthew Thode
> wrote:
>
>> Here's the current status. I'd like to ask the projects what's keeping
>> them from removing pycrypto in facor of a maintained library.
>>
>> pyghmi:
>> - (merge conflict) htt
On Sat, 2018-03-31 at 18:24 -0500, Matthew Thode wrote:
> Here's the current status. I'd like to ask the projects what's
> keeping
> them from removing pycrypto in facor of a maintained library.
>
> Open reviews
> barbican:
> - (merge conflict) https://review.openstack.org/#/c/458196
> - (mer
On Sat, Mar 31, 2018 at 7:24 PM, Matthew Thode
wrote:
> Here's the current status. I'd like to ask the projects what's keeping
> them from removing pycrypto in facor of a maintained library.
>
> pyghmi:
> - (merge conflict) https://review.openstack.org/#/c/331828
> - (merge conflict) https:/
Mr. Fire-
> nova-powervm: no open reviews
> - in test-requirements, but not actually used?
> - made https://review.openstack.org/558091 for it
Thanks for that. It passed all our tests; we should merge it early next
week.
-efried
_
Here's the current status. I'd like to ask the projects what's keeping
them from removing pycrypto in facor of a maintained library.
Open reviews
barbican:
- (merge conflict) https://review.openstack.org/#/c/458196
- (merge conflict) https://review.openstack.org/#/c/544873
nova-powervm: no op
