<div dir="ltr">Thanks for your digging and help with this Ian and Andreas.<div><br></div><div>I've added an apache rule to redirect -'s to .'s as a quick workaround to un-wedge the gate <a href="https://review.openstack.org/#/c/314898/" target="_blank">https://review.openstack.org/#/c/314898/</a> (and a few edge cases <a href="https://review.openstack.org/#/c/314956">https://review.openstack.org/#/c/314956</a>)</div><div><br></div><div>If you have a build that has failed due to "No matching distribution found for <package with "." in name>" it should be safe to issue a 'recheck' now.</div><div><br></div><div>There may be some more edge cases so let us know if you run into any.</div><div><br></div><div>We should, as suggested, fix bandersnatch or perhaps pin pi as soon as possible. Once fixed properly we should undo the workaround so that our mirror matches pypi.</div><div><br></div><div>Cheers,<br>Josh</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 11, 2016 at 2:07 PM, Ian Wienand <span dir="ltr"><<a href="mailto:iwienand@redhat.com" target="_blank">iwienand@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">So it seems the just released pip 8.1.2 has brought in a new version<br>
of setuptools with it, which creates canonical names per [1] by<br>
replacing "." with "-".<br>
<br>
The upshot is that pip is now looking for the wrong name on our local<br>
mirrors. e.g.<br>
<br>
---<br>
$ pip --version<br>
pip 8.1.2 from /tmp/foo/lib/python2.7/site-packages (python 2.7)<br>
$ pip --verbose install --trusted-host <a href="http://mirror.ord.rax.openstack.org" rel="noreferrer" target="_blank">mirror.ord.rax.openstack.org</a> -i <a href="http://mirror.ord.rax.openstack.org/pypi/simple" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple</a> 'oslo.config>=3.9.0'<br>
Collecting oslo.config>=3.9.0<br>
1 location(s) to search for versions of oslo.config:<br>
* <a href="http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/</a><br>
Getting page <a href="http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/</a><br>
Starting new HTTP connection (1): <a href="http://mirror.ord.rax.openstack.org" rel="noreferrer" target="_blank">mirror.ord.rax.openstack.org</a><br>
"GET /pypi/simple/oslo-config/ HTTP/1.1" 404 222<br>
Could not fetch URL <a href="http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/</a>: 404 Client Error: Not Found for url: <a href="http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/</a> - skipping<br>
Could not find a version that satisfies the requirement oslo.config>=3.9.0 (from versions: )<br>
---<br>
<br>
(note olso-config, not oslo.config). Compare to<br>
<br>
---<br>
$ pip --verbose install --trusted-host <a href="http://mirror.ord.rax.openstack.org" rel="noreferrer" target="_blank">mirror.ord.rax.openstack.org</a> -i <a href="http://mirror.ord.rax.openstack.org/pypi/simple" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple</a> 'oslo.config>=3.9.0'<br>
You are using pip version 6.0.8, however version 8.1.2 is available.<br>
You should consider upgrading via the 'pip install --upgrade pip' command.<br>
Collecting oslo.config>=3.9.0<br>
Getting page <a href="http://mirror.ord.rax.openstack.org/pypi/simple/oslo.config/" rel="noreferrer" target="_blank">http://mirror.ord.rax.openstack.org/pypi/simple/oslo.config/</a><br>
Starting new HTTP connection (1): <a href="http://mirror.ord.rax.openstack.org" rel="noreferrer" target="_blank">mirror.ord.rax.openstack.org</a><br>
"GET /pypi/simple/oslo.config/ HTTP/1.1" 200 2491<br>
---<br>
<br>
I think infra jobs that run on bare-precise are hitting this<br>
currently, because that image was just built. Other jobs *might* be<br>
isolated from this for a bit, until the new pip gets out there on<br>
images, but "winter is coming", as they say...<br>
<br>
There is [2] available to make bandersnatch use the new names.<br>
However, I wonder if this might have the effect of breaking the<br>
mirrors for old versions of pip that ask for the "."?<br>
<br>
pypi proper does not seem affected, just our mirrors.<br>
<br>
I think probably working with bandersnatch to get a fixed version ASAP<br>
is probably the best way forward, rather than us trying to pin to old<br>
pip versions.<br>
<br>
-i<br>
<br>
[1] <a href="https://www.python.org/dev/peps/pep-0503/" rel="noreferrer" target="_blank">https://www.python.org/dev/peps/pep-0503/</a><br>
[2] <a href="https://bitbucket.org/pypa/bandersnatch/pull-requests/20/fully-implement-pep-503-normalization/" rel="noreferrer" target="_blank">https://bitbucket.org/pypa/bandersnatch/pull-requests/20/fully-implement-pep-503-normalization/</a><br>
<br>
_______________________________________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
</blockquote></div><br></div></div>