This reverts commit 3873433da4ae907dd62d449c8b1d01ee73550c86.
There's now a new version of python-coverage that fixes the bug we were previously running into. So I've changed the spec file to reflect that. --- Makefile.am | 1 + anaconda.spec.in | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile.am b/Makefile.am index ff050eb..e92a1e2 100644 --- a/Makefile.am +++ b/Makefile.am @@ -180,6 +180,7 @@ ci: rc-release @sudo $(MAKE) TMPDIR=/var/tmp TESTS=install/run_install_test.sh TEST_ANACONDA_REPO=file://$(abs_builddir)/repo/ COVERAGE_PROCESS_START=$(abs_builddir)/.coveragerc check @rm -f $(USER_SITE_PACKAGES)/usercustomize.py @sudo rm -f $(ROOT_SITE_PACKAGES)/usercustomize.py + $(MAKE) coverage-report
coverage-report: $(COVERAGE) combine tests/.coverage.* diff --git a/anaconda.spec.in b/anaconda.spec.in index 58f569c..786cb5d 100644 --- a/anaconda.spec.in +++ b/anaconda.spec.in @@ -133,7 +133,7 @@ Requires: kexec-tools %endif Requires: python3-pid
-Requires: python3-coverage +Requires: python3-coverage >= 4.0-0.12.b3
# required because of the rescue mode and VNC question Requires: anaconda-tui = %{version}-%{release}