b0d5e455fc
We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver [1] for the release team [2][3]. Removed specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements [4]. This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug. [1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: I6bdfa9830a32ecf36e1931e1bb0afa366f1dfeb9
17 lines
508 B
Plaintext
17 lines
508 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
# hacking should be first
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
|
|
coverage>=5.3 # Apache-2.0
|
|
kombu>=5.0.2 # BSD
|
|
ddt>=1.4.1 # MIT
|
|
gabbi>=2.0.4 # Apache-2.0
|
|
testscenarios>=0.5.0 # Apache-2.0/BSD
|
|
stestr>=3.0.1 # Apache-2.0
|
|
oslotest>=4.4.1 # Apache-2.0
|
|
doc8>=0.8.1 # Apache-2.0
|
|
bandit>=1.6.0 # Apache-2.0
|