Comment 2 for bug 1704652

The scenario as I recall is this:
1. Set up a private index (e.g. with devpi)
2. Upload an older version of pbr to that index
3. Create a python package with pbr
4. Run pip install -e ./package -i <your index url>

The expected behavior is for the *older* version of pbr to be used -- however what we experienced is that since pbr downloads its egg directly before proceeding, it attempts to take it from the global pypi for some reason.

Having said that it's been 10 months so it's entirely possible this has already been fixed.