Re: [openstack-dev] [OpenStack-Infra] [infra] Jobs failing : "No matching distribution found for "

2016-05-11 Thread Jeremy Stanley 
On 2016-05-11 21:55:28 +1000 (+1000), Joshua Hesketh wrote:
[...]
> Once fixed properly we should undo the workaround so that our
> mirror matches pypi.

Donald's bandersnatch fix has merged and is now available in an
updated release, but as James Blair pointed out in IRC we're
currently running a lightweight fork of bandersnatch with his hash
indexing patch applied so need to make sure that still applies
cleanly and include it in whatever updated version we deploy on the
mirror-update server.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [infra] Jobs failing : "No matching distribution found for "

2016-05-11 Thread Joshua Hesketh 
Thanks for your digging and help with this Ian and Andreas.

I've added an apache rule to redirect -'s to .'s as a quick workaround to
un-wedge the gate https://review.openstack.org/#/c/314898/ (and a few edge
cases https://review.openstack.org/#/c/314956)

If you have a build that has failed due to "No matching distribution found
for " it should be safe to issue a 'recheck' now.

There may be some more edge cases so let us know if you run into any.

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.

Cheers,
Josh

On Wed, May 11, 2016 at 2:07 PM, Ian Wienand  wrote:

> So it seems the just released pip 8.1.2 has brought in a new version
> of setuptools with it, which creates canonical names per [1] by
> replacing "." with "-".
>
> The upshot is that pip is now looking for the wrong name on our local
> mirrors.  e.g.
>
> ---
>  $ pip --version
> pip 8.1.2 from /tmp/foo/lib/python2.7/site-packages (python 2.7)
> $ pip --verbose  install --trusted-host mirror.ord.rax.openstack.org -i
> http://mirror.ord.rax.openstack.org/pypi/simple 'oslo.config>=3.9.0'
> Collecting oslo.config>=3.9.0
>   1 location(s) to search for versions of oslo.config:
>   * http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/
>   Getting page
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/
>   Starting new HTTP connection (1): mirror.ord.rax.openstack.org
>   "GET /pypi/simple/oslo-config/ HTTP/1.1" 404 222
>   Could not fetch URL
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/: 404 Client
> Error: Not Found for url:
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/ - skipping
>   Could not find a version that satisfies the requirement
> oslo.config>=3.9.0 (from versions: )
> ---
>
> (note olso-config, not oslo.config).  Compare to
>
> ---
> $ pip --verbose install --trusted-host mirror.ord.rax.openstack.org -i
> http://mirror.ord.rax.openstack.org/pypi/simple 'oslo.config>=3.9.0'
> You are using pip version 6.0.8, however version 8.1.2 is available.
> You should consider upgrading via the 'pip install --upgrade pip' command.
> Collecting oslo.config>=3.9.0
>   Getting page
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo.config/
>   Starting new HTTP connection (1): mirror.ord.rax.openstack.org
>   "GET /pypi/simple/oslo.config/ HTTP/1.1" 200 2491
> ---
>
> I think infra jobs that run on bare-precise are hitting this
> currently, because that image was just built.  Other jobs *might* be
> isolated from this for a bit, until the new pip gets out there on
> images, but "winter is coming", as they say...
>
> There is [2] available to make bandersnatch use the new names.
> However, I wonder if this might have the effect of breaking the
> mirrors for old versions of pip that ask for the "."?
>
> pypi proper does not seem affected, just our mirrors.
>
> I think probably working with bandersnatch to get a fixed version ASAP
> is probably the best way forward, rather than us trying to pin to old
> pip versions.
>
> -i
>
> [1] https://www.python.org/dev/peps/pep-0503/
> [2]
> https://bitbucket.org/pypa/bandersnatch/pull-requests/20/fully-implement-pep-503-normalization/
>
> ___
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev