summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-pbr_1.8.1.bb
Commit message (Collapse)AuthorAgeFilesLines
* python-pbr: drop recipeMark Asselstine2017-01-171-30/+0
| | | | | | | | | | | | | We often include our own versions of recipes in meta-virtualization and meta-cloud-services in order to satisfy specific version dependencies, ie. grouping recipes by usecase. Historically python-pbr versions have been extremely flexible (most recipes only specify the very old 1.6 as a minimum version) and python-pbr can arguably be seen as a core python package, so remove our version of the recipe in favor of the one in meta-python. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python: satisfy setup.py 'setup_requires'Mark Asselstine2017-01-171-0/+4
| | | | | | | | | | | | | | | | | | | | | Python setuptools will attempt to satisfy the packages defined as 'setup_requires' in setup.py by first looking for the package availability locally and ultimately by downloading it from PyPI. This is actually a huge security hole and packages should move to using pip instead, but this is another story that the upstream packages have to address. This also disregards BB_NO_NETWORK and may prove to introduce host contamination. The best approach is to ensure we have the -native version of the 'setup_requires' packages present such that setup.py will not attempt to complete the download from PyPI. Make 'pbr' -native available and for packages which we have identified as having 'setup_requires' include 'pbr' add the necessary python-pbr-native DEPENDS. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-*: uprev to versions required for libertyMark Asselstine2016-02-051-0/+26
This is a collection of recipe uprevs that bring various packages up to the version required to support the liberty release. These uprevs are mostly trivial with the expected SRC_URI and CHECKSUM updates along with updates to the list of dependencies. Where possible recipes have been updated to use git to facilitate future uprevs. For python-futures we need to add a PREFERRED_VERSION to ensure the git version will take precedence over a versioned recipe found in another layer. Signed-off-by: Mark Asselstine <asselsm@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>