[meta-virtualization] [meta-openstack][PATCH] layer.conf: bump python-requests 2.12 -> 2.13

[Bruce Ashfield]

On 2017-06-16 8:10 AM, Ioan-Adrian Ratiu wrote:
> Meta-oe upreved to 2.13 (present in Pyro) so bump it here also to
> avoid bitbake messages like:
> 
> "NOTE: preferred version 2.12.0 of python-requests not available"

Unless we've tested it, I'd like to keep it with the warning. We
are (slowly) working towards an update of all the core components.

This version was selected/preferred, because it actually works.

And the warning will force us to test and confirm if it is safe to
move on.

Has this been tested ?

Or is the warning popping up in another scenario ? i.e. you are
using some packages from meta-openstack that trigger the warning,
but don't hit the runtime issue ? In that case, I could take the
patch, since we do want the package reuse from the layer and
forcing people to live with that warning will restrict the reuse.

Bruce

> 
> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu at ni.com>
> ---
>   meta-openstack/conf/layer.conf | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-openstack/conf/layer.conf b/meta-openstack/conf/layer.conf
> index 98282e2..61e9fb5 100644
> --- a/meta-openstack/conf/layer.conf
> +++ b/meta-openstack/conf/layer.conf
> @@ -18,7 +18,7 @@ PREFERRED_VERSION_python-futures = "3.0.3%"
>   PREFERRED_VERSION_python-django = "1.8.6"
>   PREFERRED_VERSION_python-netaddr = "0.7.19"
>   PREFERRED_VERSION_python-sqlalchemy = "1.0.16"
> -PREFERRED_VERSION_python-requests = "2.12.0"
> +PREFERRED_VERSION_python-requests = "2.13.0"
>   PREFERRED_VERSION_python-amqp = "1.4.9"
>   PREFERRED_VERSION_python-kombu = "3.0.%"
>   
>