253ea10d26
The current pinning method for pip/setuptools/wheel works for the initial setup of a host or python venv. However, when a python package which has one of these in its requirements is installed onto the host or into the venv and the '--upgrade' option is given to pip, the package will be upgraded to the latest version available within the given constraints. As OpenStack's requirements management process does not cater for the pip, setuptools or wheel packages we need to ensure that all python install tasks prior to the repo being built use our global pins as a constraint in addition to the OpenStack uppser constraints. As pip's --constraints option can only take a file as an argument we have to copy the global pins file to the target which will use it. This file can be removed from the host once the repo is built. Related-Bug: #1658773 Closes-Bug: #1658948 Change-Id: Iccbb2e4a126a1cc7a4c94ab41b7ce8ef54d89990 |
||
---|---|---|
.. | ||
dynamic-grouping.yml | ||
mysql-db-user.yml | ||
os-log-dir-setup.yml | ||
os-lxc-container-setup.yml | ||
package-cache-proxy.yml | ||
rabbitmq-vhost-user.yml | ||
set-pip-upstream-url.yml | ||
set-upper-constraints.yml |