I think this may happen when the virtualenv is in the root dir of a package because pbr's egg info entry point writer is available and finding the git sha for the package being installed. Not sure why this seems to only happen for some packages though.
I think this may happen when the virtualenv is in the root dir of a package because pbr's egg info entry point writer is available and finding the git sha for the package being installed. Not sure why this seems to only happen for some packages though.