Fix CI confusion wrt tox %{release}
We were seeing:
No match for argument: tox = 4.12.1-1.fc41
Apparently, standard-test-source does not handle the dist-git history.
Hence, when the SRPM is built in mocktest.sh, %autorelease is set to 1.
However, the available tox from the CI scratchbuild might have a greater Release.
We relax the BuildRequirement.
We assume mock will install the right build anyway.
The CI scratchbuild will either have a different (usually greater) Version
when the PR upgrades or downgrades tox
or a greater Release otherwise, thanks to %autorelease.
This commit is contained in:
+2
-1
@@ -52,7 +52,8 @@ BuildRequires: python3-pytest-xdist
|
||||
BuildRequires: python3.10
|
||||
%if %{with ci_tests}
|
||||
# The CI tests only work if the tested tox is installed :(
|
||||
BuildRequires: tox = %{version}-%{release}
|
||||
# This should technically be the same V-R, but the CI does not handle %%autorelease well
|
||||
BuildRequires: tox = %{version}
|
||||
%endif
|
||||
%endif
|
||||
|
||||
|
||||
Reference in New Issue
Block a user