From 5d1630d56dfe6b6d0c1f24ad857a2fe13258d74d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miro=20Hron=C4=8Dok?= Date: Tue, 27 Feb 2024 10:10:15 +0100 Subject: [PATCH] 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. --- python-tox.spec | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/python-tox.spec b/python-tox.spec index 7c6d7e5..dcbf474 100644 --- a/python-tox.spec +++ b/python-tox.spec @@ -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