These versions dropped setup.py from the release tarball, breaking
installation on older systems like CentOS. This affects
ironic-python-agent-builder since it uses CentOS 8 by default.
The breaking change has been reverted in
https://github.com/pypa/packaging/pull/367
Change-Id: Idb9e0a70728108b13fc097a74244226a676c97b3
This reverts commit 9ee3854a50.
There are still a couple of tools using this, including things that pbr
depends on [1]
[1] 9257b68435/pbr/tests/test_integration.py (L80-L83)
Change-Id: I575b18220db4b0a2ce677f99df86486d3ab0f150
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
We don't use six anywhere in the requirements code, only in some test
files that are only used for running tests against. This removes six
from our requirements.txt file since it does not need to be installed.
Change-Id: I33687e8935845a606d97deb55dd5573354867e1b
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds a script that will check through all the requirements in
global-requirements for any that are no longer being used.
Change-Id: I9c8fb2c07c794739bcab07a55e68e67d16736acc
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Move packaging and pyyaml from test-requirement.txt to requirements.txt.
Also add requests as it's needed by validate-projects
This is needed as some projects in the gate are pip installing the
requiremets repo and now they're failing with runtime errors.
Change-Id: Ic88cecd6d2664e447a696c58c123de18f35f7cd2
This script when run creates a constraints file with exact pins for
the transitive dependencies of a requirements file.
Change-Id: I1282f8e4010c0ec46c473495bacddf044d06c0af
This required some care. There doesn't seem to be a sane Python3 ready
comment-preserving ini parser around, so I wrote a
minimal-for-our-case one in Parsley. Parsley is already in use in
infra in bindep, but I need to add it to global-requirements as this
is the first use in a managed project of it.
Change-Id: I48de3a2f36e945f75b534f689e3af802bbdc5be9
Depends-On: I7d7e91694c9145fac0ddab8a9de5f789d723c641
Depends-On: I16e967356d5c56f1474ee661b954b3db11a608cb
... and in the darkness bind them.
This moves the contents of requirements.txt and
test-requirements.txt to a single file, global-requirements.txt.
This means that regardless of whether a requirement is in
either file it will get checked. This massively simplifies the
checking and upgrading of req and test-req files.
This also adds in a unit testing framework for the update.py
script to ensure it does what we think it does. This is
accomplished by making a fake tree with a set of req and test-req
files, running update.py, and ensuring the updates were made
that we expected. It includes testing for the oslo url case,
as well as test-requires.
Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
all our tools work fine with jsonschema 2.0, as we run it in the
gate today (and for months) due to the global requirements race.
The real glance requirement is really >= 1.3.0. The !=1.4.0
remains because of a misrelease by the jsconschema of 2.0 as
1.4.0... poorly.
Change-Id: I88ccf6dca223c825ef98eed50e2270694d05955c
Nova (specifically nova migrations) really don't function with
the versions of sqla in requirements. Bump these to the Nova
minimums.
Change-Id: Icaa4cb74576d301e28b23831a8ce7c1511ba8cae
Fixes bug 1205546.
This reverts commit adf074baa9.
Upstream Babel has worked around the pytz versioning issues by
releasing 1.1.
Change-Id: I2298c80ca0291ea6d0797194897ecc79ec50b818
The latest Babel, 1.0, adds a dependency on
pytz. Further, pytz uses date-based versioning which is not
supported by default in the newest pip, 1.4. Adding a fake direct
dependency on pytz with a minimum declared version before installing
Babel works around this issue.
Fixes bug 1205546
Change-Id: Ie52dd85eac595ba8ee35e3342130648010246943
the older version of python-heatclient and python-ceiloclient
actually required an incompatible version of python-keystone client
to the global requirements list. When running devstack without
heat or ceilo enabled (thus no local git trees), horizon becomes
satisified even when you have and old heatclient, which prevents
horizon from installing.
Change-Id: I8480db4a5c3d08a7d739f495920e4b5a442cbb91
This is a prerequisite for the blueprint realtime-communication in Horizon.
Change-Id: I1dddeec13a45949f01f94014a8451d98cb443b4e
Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
Precise ships with 1.0 by default. Until we force everyone on to
1.4, there is no need to express a depend here which is not true.
Change-Id: Id4101fa4fd1c60a6ffef6bef3dcd03522e681231
Although pip does the right thing, there are various proxies and whatnot
that actually can get confused with the case-insensitivity.
Moving forward, we should try to make sure we put things in the files
correctly.
Change-Id: I6eb5eb8a3d11dd009f94f02da32cf9580ac7333a
A prereq to drop horizon's less.js (and thus NodeJS) dependency for
compiling static assets.
See https://review.openstack.org/#/c/37473/
Change-Id: I265b35def7cdd20c2d1c1040b7fb788c2f2a3e8f
Set the minimum version required to run Horizon with
Keystone V3 Auth.
Change-Id: I6df0624cbcc6b08030d48d905603463a8eaafdc7
Implements: blueprint login-domain-support
If we care about a max version of a package, also
specify the min version to have a range to check for.
Specify min version always in a '>=' fashion.
This simplifies a bit of the handling, as the first
given range is always the lower bound.
Also raise websockify to 0.5.1 in preparation of
https://review.openstack.org/#/c/35365/
Change-Id: Ia2672d675446f2ce9932c0c8b09e7b3c2c9cc392
Changes requirement for stevedore to be >=0.10 because
that version of stevedore has the ability to propagate
exceptions up through the map call which is required for
some of the Nova V3 API extensions to work properly
Change-Id: Ic2316e1f0cba28521950f3313652514dd7484378
per mailing list thread, allowing any project to cap one of our
own clients actually prevents us from testing that client's git
version in devstack gate (because there are 2 ways to install a
python client, one from git, one from pip). This can allow bugs
to creep into the clients because they are no longer tested in
the gate.
We need to start with uncapping the global list, then ensuring
we uncap this in all the projects.
Neutron client excluded because of a need for incompatible
changes in v3.
Needed to make progress on bug #1200214
Change-Id: Ice57c9bd9ce2bbd786ca0c80a1b94049a7f63ff8