On Wed, Apr 18, 2018 at 12:02 PM, Michel Peterson <michel at redhat.com> wrote: > How can we fix this? There are several ways I can think of the top of my > head: > > > 1. When encountered with edge cases like this one, first install that > dependency with a manual pip run [2] > 2. Modify pbr to handle these situations by handling the installation > of those depenencies differently with a workaround to the current > functionality of pip > 3. Leverage on the work of corvus [3] to not only do what that patch > is doing, but also including the checked out path of the dependency in > PIP_FIND_LINKS, that way pip knows how to solve the issue. > > All these solutions have different set of pros and cons, but I favor #3 as > the long term solution, #1 as short term and I think #2 requires further > analysis by the pbr team. > I forgot to add the reference on where to add the PIP_FIND_LINKS for solution #3, here you go: https://github.com/openstack-dev/devstack/blob/f99d1771ba1882dfbb69186212a197edae3ef02c/inc/python#L362 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180418/ce670a2f/attachment.html>