PBR Freeze reports duplicate shas on many packages.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBR |
Confirmed
|
Low
|
Unassigned |
Bug Description
If I install latest python-heatclient in a clean virtualenv running pbr freeze shows duplicate shas for many packages that should not have any shas.
~/src/openstack$ git clone https:/
~/src/openstack$ cd python-heatclient/
~/src/openstack
~/src/openstack
~/src/openstack
Python==2.7
argparse==1.2.1
wsgiref==0.1.2
oslo.i18n==1.1.0
pytz==2014.10
netifaces==0.10.4 # git sha d6d5197
oslo.utils==1.1.0
pip==1.5.4
prettytable==0.7.2 # git sha d6d5197
python-
Babel==1.3
oslo.serializat
setuptools==2.2
netaddr==0.7.12 # git sha d6d5197
PyYAML==3.11 # git sha d6d5197
six==1.8.0
iso8601==0.1.10 # git sha d6d5197
requests==2.5.1
pbr==0.10.7 # git sha aef4f7e
python-
stevedore==1.1.0
oslo.config==1.5.0
See shas on netifaces, prettytable, netaddr, PyYAML, and iso8601. It is the same sha as python-heatclient.
Changed in pbr: | |
status: | New → Confirmed |
importance: | Undecided → Low |
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.