.fmf/version

@@ -0,0 +1 @@
+1

.gitignore

@@ -1 +1 @@
-SOURCES/leapp-0.18.0.tar.gz
+/leapp-0.18.0.tar.gz

.leapp.metadata

@@ -1 +0,0 @@
-6f78400cf9fac51624d105c5be94945bd68e79cf SOURCES/leapp-0.18.0.tar.gz

SOURCES/0001-Update-references-from-master-branch-to-main.patch

@@ -1,525 +0,0 @@
-From 97871166d037fce1029428d369541ec2d6eeeef7 Mon Sep 17 00:00:00 2001
-From: Vojtech Sokol <vsokol@redhat.com>
-Date: Mon, 2 Sep 2024 17:22:11 +0200
-Subject: [PATCH 1/6] Update references from master branch to main
-
-Focus was on making the CI and GitHub actions work after the default
-branch was switched from master to main.
-
-See: OAMG-4907
----
- .github/workflows/pr-welcome-msg.yml          |  4 ++--
- .github/workflows/reuse-copr-build.yml        |  4 ++--
- .github/workflows/unit-tests.yml              | 10 +++++-----
- .packit.yaml                                  |  6 +++---
- Makefile                                      |  8 ++++----
- docs/source/best-practices.md                 | 20 +++++++++----------
- docs/source/build-schema.md                   |  4 ++--
- .../compatibility-with-leapp-repository.md    |  2 +-
- docs/source/contributing.md                   |  6 +++---
- docs/source/dependencies-leapp-repository.md  |  8 ++++----
- docs/source/dependencies.md                   |  2 +-
- docs/source/deprecation.md                    |  2 +-
- docs/source/devenv-install.md                 |  4 ++--
- docs/source/el7toel8/actor-rhel7-to-rhel8.md  | 12 +++++------
- .../source/el7toel8/inhibit-rhel7-to-rhel8.md |  4 ++--
- docs/source/test-actors.md                    |  4 ++--
- docs/source/unit-testing.md                   |  8 ++++----
- packaging/leapp.spec                          |  4 ++--
- 18 files changed, 56 insertions(+), 56 deletions(-)
-
-diff --git a/.github/workflows/pr-welcome-msg.yml b/.github/workflows/pr-welcome-msg.yml
-index af5d543..66d001e 100644
---- a/.github/workflows/pr-welcome-msg.yml
-+++ b/.github/workflows/pr-welcome-msg.yml
-@@ -25,9 +25,9 @@ jobs:
-             - **/packit copr-build** to submit a public copr build using packit
- 
-             To launch regression testing public members of oamg organization can leave the following comment:
--            - **/rerun** to schedule basic regression tests using this pr build and leapp-repository\*master\* as artifacts
-+            - **/rerun** to schedule basic regression tests using this pr build and leapp-repository\*main\* as artifacts
-             - **/rerun 42** to schedule basic regression tests using this pr build and leapp-repository\*PR42\* as artifacts
--            - **/rerun-sst** to schedule sst tests using this pr build and leapp-repository\*master\* as artifacts
-+            - **/rerun-sst** to schedule sst tests using this pr build and leapp-repository\*main\* as artifacts
-             - **/rerun-sst 42** to schedule sst tests using this pr build and leapp-repository\*PR42\* as artifacts
- 
-             Please [open ticket](https://url.corp.redhat.com/oamg-ci-issue) in case you experience technical problem with the CI. (RH internal only)
-diff --git a/.github/workflows/reuse-copr-build.yml b/.github/workflows/reuse-copr-build.yml
-index a935c7e..b0079a1 100644
---- a/.github/workflows/reuse-copr-build.yml
-+++ b/.github/workflows/reuse-copr-build.yml
-@@ -59,7 +59,7 @@ jobs:
-           echo "::set-output name=sha::$(git rev-parse --short HEAD)"
-           echo "::set-output name=ref::refs/pull/${{ steps.pr_nr.outputs.pr_nr }}/head"
- 
--      - name: Get latest leapp-repository master copr build id
-+      - name: Get latest leapp-repository main copr build id
-         id: get_latest_lpr_copr_build_id
-         if: ${{ steps.leapp_repository_pr_regex_match.outputs.match == '' }}
-         run: |
-@@ -73,7 +73,7 @@ jobs:
-           EOF
- 
-           pip install copr-cli
--          REGEX='leapp-repository.*master.*' COPR_REPO='@oamg/leapp' _COPR_CONFIG=copr_fedora.conf python ${{ github.workspace }}/utils/get_latest_copr_build > latest_lpr
-+          REGEX='leapp-repository.*main.*' COPR_REPO='@oamg/leapp' _COPR_CONFIG=copr_fedora.conf python ${{ github.workspace }}/utils/get_latest_copr_build > latest_lpr
-           COPR_ID=$(cat latest_lpr)
-           echo "::set-output name=copr_id::${COPR_ID##*/}"
- 
-diff --git a/.github/workflows/unit-tests.yml b/.github/workflows/unit-tests.yml
-index e67264b..a0a3942 100644
---- a/.github/workflows/unit-tests.yml
-+++ b/.github/workflows/unit-tests.yml
-@@ -2,10 +2,10 @@ name: Unit Tests
- on:
-   push:
-     branches:
--      - master
-+      - main
-   pull_request:
-     branches:
--      - master
-+      - main
- 
- jobs:
-   test:
-@@ -33,9 +33,9 @@ jobs:
-         uses: actions/checkout@v4
-         with:
-           fetch-depth: '0'
--      - name: Set master to origin/master
--        if: github.ref != 'refs/heads/master'
-+      - name: Set main to origin/main
-+        if: github.ref != 'refs/heads/main'
-         run: |
--          git branch -f master origin/master
-+          git branch -f main origin/main
-       - name: ${{matrix.scenarios.name}}
-         run: script -e -c /bin/bash -c 'TERM=xterm podman build --security-opt=seccomp=unconfined -t leapp-tests -f res/container-tests/Containerfile.${{matrix.scenarios.container}} res/container-tests && PYTHON_VENV=${{matrix.scenarios.python}} REPOSITORIES=${{matrix.scenarios.repos}} podman run --security-opt=seccomp=unconfined --rm -ti -v ${PWD}:/payload --env=PYTHON_VENV --env=REPOSITORIES leapp-tests'
-diff --git a/.packit.yaml b/.packit.yaml
-index 2aead86..36a6e16 100644
---- a/.packit.yaml
-+++ b/.packit.yaml
-@@ -19,7 +19,7 @@ jobs:
-     - fedora-all-x86_64
-   actions:
-     post-upstream-clone:
--    # builds from PRs should have lower NVR than those from master branch
-+    # builds from PRs should have lower NVR than those from main branch
-     - sed -i "s/1%{?dist}/0%{?dist}/g" packaging/leapp.spec
-     get-current-version:
-     # get version from spec file instead from git tag
-@@ -27,7 +27,7 @@ jobs:
- - job: copr_build
-   trigger: commit
-   metadata:
--    branch: master
-+    branch: main
-     owner: "@oamg"
-     project: leapp
-     targets:
-@@ -38,7 +38,7 @@ jobs:
-     - fedora-all-x86_64
-   actions:
-     post-upstream-clone:
--    # builds from master branch should have the highest NVR
-+    # builds from main branch should have the highest NVR
-     - sed -i "s/1%{?dist}/100%{?dist}/g" packaging/leapp.spec
-     get-current-version:
-     # get version from spec file instead from git tag
-diff --git a/Makefile b/Makefile
-index 677c748..0c1b805 100644
---- a/Makefile
-+++ b/Makefile
-@@ -23,7 +23,7 @@ _TEST_CONTAINER=$${TEST_CONTAINER:-rhel8}
- 
- # just to reduce number of unwanted builds mark as the upstream one when
- # someone will call copr_build without additional parameters
--MASTER_BRANCH=master
-+MASTER_BRANCH=main
- 
- # In case the PR or MR is defined or in case build is not coming from the
- # MATER_BRANCH branch, N_REL=0; (so build is not update of the approved
-@@ -44,14 +44,14 @@ REQUEST=`if test -n "$$PR"; then echo ".PR$${PR}"; elif test -n "$$MR"; then ech
- # Examples:
- #    0.201810080027Z.4078402.packaging.PR2
- #    0.201810080027Z.4078402.packaging
--#    0.201810080027Z.4078402.master.MR2
--#    1.201810080027Z.4078402.master
-+#    0.201810080027Z.4078402.main.MR2
-+#    1.201810080027Z.4078402.main
- RELEASE="$(N_REL).$(TIMESTAMP).$(SHORT_SHA).$(BRANCH)$(REQUEST)$(_SUFFIX)"
- 
- ifneq ($(shell id -u),0)
- 	ENTER_VENV := . $(VENVNAME)/bin/activate;
- else
--	ENTER_VENV := 
-+	ENTER_VENV :=
- endif
- 
- all: help
-diff --git a/docs/source/best-practices.md b/docs/source/best-practices.md
-index f3387e2..46aedbc 100644
---- a/docs/source/best-practices.md
-+++ b/docs/source/best-practices.md
-@@ -43,17 +43,17 @@ to a shared library function. You can introduce it in one of these two places:
-   writing your actor for, e.g. for an OS in-place upgrade workflow, should go to the `<Leapp repository>/libraries`
-   folder. In this case, we welcome your proposals under the
-   [leapp-repository on GitHub](https://github.com/oamg/leapp-repository).
--  
-+
-   Please note that the name of the library module in this case should be unique and contain
-   the actor name. For example:
-   `repos/system_upgrade/el7toel8/actors/vimmigrate/libraries/vimmigrate.py`
-- 
-+
- 
- ## Discover standard library functions
- 
- Before implementing functionality for your actor, browse through the available functionality provided by:
- 
--- the [Leapp Standard Library](https://github.com/oamg/leapp/tree/master/leapp/libraries/stdlib/),
-+- the [Leapp Standard Library](https://github.com/oamg/leapp/tree/main/leapp/libraries/stdlib/),
- - the shared library of your Leapp repository (`<Leapp repository>/libraries` folder).
- 
- These libraries contain functions that may satisfy your needs. Using them can save you time, lower code complexity and
-@@ -63,7 +63,7 @@ help avoiding duplicate code. Improvement proposals for the library functions ar
- 
- Sources of external functionality to be used in your actor in order of preference:
- 
--1. the [Leapp Standard Library](https://github.com/oamg/leapp/tree/master/leapp/libraries/stdlib/)
-+1. the [Leapp Standard Library](https://github.com/oamg/leapp/tree/main/leapp/libraries/stdlib/)
- 2. the [Python Standard Library](https://docs.python.org/3/library/index.html)
- 3. shell commands
- 
-@@ -81,13 +81,13 @@ As with the Leapp Standard Library mentioned above, it may be beneficial for you
- place in the [leapp-repository](https://github.com/oamg/leapp-repository). You might be interested in the messages they
- produce, for example:
- 
--- [SystemFactsActor](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/systemfacts/actor.py) -
-+- [SystemFactsActor](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/systemfacts/actor.py) -
-   information about kernel modules, yum repos, sysctl variables, users, firewall, SELinux, etc.
--- [OSReleaseCollector](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/osreleasecollector/actor.py) -
-+- [OSReleaseCollector](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/osreleasecollector/actor.py) -
-   system release information
--- [RpmScanner](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/rpmscanner/actor.py) -
-+- [RpmScanner](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/rpmscanner/actor.py) -
-   list of installed packages
--- [StorageScanner](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/storagescanner/actor.py) -
-+- [StorageScanner](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/storagescanner/actor.py) -
-   storage information
- 
- In case you find any message of the existing actors to be incorrect, incomplete or misleading, we encourage you to
-@@ -123,8 +123,8 @@ For more about unit testing, see the [tutorial](unit-testing).
- ## Do not introduce new dependencies
- 
- Ideally, actors shouldn't require any additional dependency on top of the dependencies already in the
--[leapp](https://github.com/oamg/leapp/blob/master/packaging/leapp.spec) and
--[leapp-repository](https://github.com/oamg/leapp-repository/blob/master/packaging/leapp-repository.spec) spec files,
-+[leapp](https://github.com/oamg/leapp/blob/main/packaging/leapp.spec) and
-+[leapp-repository](https://github.com/oamg/leapp-repository/blob/main/packaging/leapp-repository.spec) spec files,
- which are, as of December 2018, just these:
- 
- - dnf
-diff --git a/docs/source/build-schema.md b/docs/source/build-schema.md
-index 053ff0c..7919964 100644
---- a/docs/source/build-schema.md
-+++ b/docs/source/build-schema.md
-@@ -4,7 +4,7 @@ All projects under the OAMG should use the same schema for names of RPM builds,
- to be able to simply and fast find specific builds. The schema itself looks
- like that (NVR without %{dist}):
- 
--- for builds made from the master branch:
-+- for builds made from the main branch:
- ```
- <name>-<version>-100.<timestamp>.<short-hash>.<branch>
- ```
-@@ -25,4 +25,4 @@ Where:
-   of a (S)RPM file; so it is suggested (not required) to to avoid dashes
-   in names of branches
- - **number** is number of a pull-request (alternatively merge-request) to which
--  builds are related
-\ No newline at end of file
-+  builds are related
-diff --git a/docs/source/compatibility-with-leapp-repository.md b/docs/source/compatibility-with-leapp-repository.md
-index 40441ed..13c6123 100644
---- a/docs/source/compatibility-with-leapp-repository.md
-+++ b/docs/source/compatibility-with-leapp-repository.md
-@@ -9,7 +9,7 @@ We rather prefer releasing new versions with changelogs and everything
- when we agree it's worthwhile.
- 
- But we need a mechanism to be able to synchronize with other projects, when we
--provide new functionality in the upstream (master) branch without the need
-+provide new functionality in the upstream (main) branch without the need
- of immediate release of the new version of leapp. For these purposes the
- `leapp-framework` capability is provided in the framework (python[23]-leapp) rpms.
- 
-diff --git a/docs/source/contributing.md b/docs/source/contributing.md
-index f0422ee..65f94a5 100644
---- a/docs/source/contributing.md
-+++ b/docs/source/contributing.md
-@@ -29,7 +29,7 @@ Before you submit your pull request, consider the following guidelines:
- * Fork the repository and clone your fork.
- * Make your changes in a new git branch:
- 
--     ``git checkout -b bug/my-fix-branch master``
-+     ``git checkout -b bug/my-fix-branch main``
- 
- * Include documentation that either describe a change to a behavior or the changed capability to an end user.
- * Commit your changes with message conforming to the [Git Commit Messages](#git-commit-messages) guidelines.
-@@ -39,7 +39,7 @@ Before you submit your pull request, consider the following guidelines:
- 
-     ``git push --set-upstream origin bug/my-fix-branch``
- 
--* When opening a pull request, select the `master` branch as a base.
-+* When opening a pull request, select the `main` branch as a base.
- * Mark your pull request with **[WIP]** (Work In Progress) to get feedback, but prevent merging (for example,
-   [WIP] Update CONTRIBUTING.rst).
- * If you are fixing a GitHub issue, include the issue number you are fixing, e.g. 'Closes issue #xyz'.
-@@ -51,7 +51,7 @@ Before you submit your pull request, consider the following guidelines:
- * Push changes to git (this will update your pull request). For that you can add a new commit or rebase your branch
-   and force push to your GitHub repository like this: ::
- 
--    git rebase -i master
-+    git rebase -i main
-     git push -f origin bug/my-fix-branch
- 
- ### Merge Rules
-diff --git a/docs/source/dependencies-leapp-repository.md b/docs/source/dependencies-leapp-repository.md
-index dc0ed61..cbefca0 100644
---- a/docs/source/dependencies-leapp-repository.md
-+++ b/docs/source/dependencies-leapp-repository.md
-@@ -14,11 +14,11 @@ this document focuses on the leapp-repository specifics only.
- Currently there are two SPEC files for leapp-repository:
- 
- - The
--[leapp-repository.spec](https://github.com/oamg/leapp-repository/blob/master/packaging/leapp-repository.spec)
-+[leapp-repository.spec](https://github.com/oamg/leapp-repository/blob/main/packaging/leapp-repository.spec)
- file is used to build leapp-repository packages and their dependency
- metapackage _leapp-repository-deps_ **for RHEL 7**.
- - The
--[leapp-el7toel8-deps.spec](https://github.com/oamg/leapp-repository/blob/master/packaging/leapp-el7toel8-deps.spec)
-+[leapp-el7toel8-deps.spec](https://github.com/oamg/leapp-repository/blob/main/packaging/leapp-el7toel8-deps.spec)
- file is used to build dependency metapackages _leapp-deps-el8_ and
- _leapp-repository-deps-el8_ **for RHEL 8** whose purpose is to replace the
- RHEL 7 dependency metapackages _leapp-deps_ and _leapp-repository-deps_ during
-@@ -27,10 +27,10 @@ the upgrade.
- ## What to do in leapp-repository when dependencies of leapp change?
- 
- Go to the section below the line `%package -n %{ldname}` in the
--[leapp-el7toel8-deps.spec](https://github.com/oamg/leapp-repository/blob/master/packaging/leapp-el7toel8-deps.spec).
-+[leapp-el7toel8-deps.spec](https://github.com/oamg/leapp-repository/blob/main/packaging/leapp-el7toel8-deps.spec).
- This section creates the RHEL 8 _leapp-deps-el8_ metapackage that replaces the
- RHEL7 _leapp-deps_ metapackage. So when the leapp package dependencies change
--in the [leapp.spec](https://github.com/oamg/leapp/blob/master/packaging/leapp.spec)
-+in the [leapp.spec](https://github.com/oamg/leapp/blob/main/packaging/leapp.spec)
- together with incrementing version of the **leapp-framework-dependencies**
- capability, it's necessary to:
- 
-diff --git a/docs/source/dependencies.md b/docs/source/dependencies.md
-index a94beab..9d0fdca 100644
---- a/docs/source/dependencies.md
-+++ b/docs/source/dependencies.md
-@@ -40,7 +40,7 @@ As a solution, we are using the metapackage that contains those dependencies.
- ## What to do when dependencies needs to be changed
- 
- It's easy to change *outer dependencies* for Leapp. Open the
--[packaging/leapp.spec](https://github.com/oamg/leapp/blob/master/packaging/leapp.spec) file and change the dependencies as needed under
-+[packaging/leapp.spec](https://github.com/oamg/leapp/blob/main/packaging/leapp.spec) file and change the dependencies as needed under
- `%package deps`. The right place is pretty highlighted (you cannot miss it):
- 
- ```spec
-diff --git a/docs/source/deprecation.md b/docs/source/deprecation.md
-index b583758..65cc18a 100644
---- a/docs/source/deprecation.md
-+++ b/docs/source/deprecation.md
-@@ -10,7 +10,7 @@ impact on your code, we introduce the deprecation process described below.
- 
- The following lists cover deprecated functionality in the leapp utility, snactor,
- the leapp standard library, etc. But don't cover deprecated functionalities
--from particular leapp repositories (e.g. the [elt7toel8](https://github.com/oamg/leapp-repository/tree/master/repos/system_upgrade/el7toel8) leapp repository). For
-+from particular leapp repositories (e.g. the [elt7toel8](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8) leapp repository). For
- such information, see [Deprecated functionality in the el7toel8 repository](el7toel8/deprecation.html#deprecated-functionality-in-the-el7toel8-repository).
- 
- ## current upstream development <span style="font-size:0.5em; font-weight:normal">(till the next release + 6months)</span>
-diff --git a/docs/source/devenv-install.md b/docs/source/devenv-install.md
-index 72f2590..84a5bab 100644
---- a/docs/source/devenv-install.md
-+++ b/docs/source/devenv-install.md
-@@ -4,7 +4,7 @@
- 
- If you do not want to modify the framework itself, install it from
- the RPM packages provided by the [Copr](https://copr.fedorainfracloud.org/coprs/g/oamg/leapp/)
--build system, which automatically builds packages with every commit merged into master.
-+build system, which automatically builds packages with every commit merged into main.
- Packages are built for EPEL and Fedora.
- 
- * On CentOS/RHEL:
-@@ -65,7 +65,7 @@ Optional arguments:
-   --debug               Enables debug mode
- 
- Main commands:
--  
-+
-     new-tag             Create a new tag
-     new-model           Creates a new model
-     run                 Execute the given actor
-diff --git a/docs/source/el7toel8/actor-rhel7-to-rhel8.md b/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-index 06bdfae..2cc72f3 100644
---- a/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-+++ b/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-@@ -21,7 +21,7 @@ The leapp framework provides the libraries required to be imported by any actor
- 
- Separate tool provided by Leapp to help the process of creating and executing an actor.
- 
--You can see _snactor_ source code [here](https://github.com/oamg/leapp/tree/master/leapp/snactor).
-+You can see _snactor_ source code [here](https://github.com/oamg/leapp/tree/main/leapp/snactor).
- 
- ## Creating an actor
- 
-@@ -62,7 +62,7 @@ For further information about how create an actor read this [document](../first-
- 
- Until now, you have created boilerplate of a new actor and made it visible to Leapp. But, Leapp needs some more information about what to do with the actor. Specifically, in which **“workflow”** and in which **“phase”** the actor should be executed. A workflow is a sequence of phases. The only workflow available now is the one solving the upgrade of RHEL 7 to RHEL 8. Each phase is a set of actors that will be executed one after another before the next phase starts. To find out in which workflow and phase should the actor be executed, Leapp looks for **“tags”**. To be part of RHEL 7 to RHEL 8 upgrade workflow, an actor needs to be tagged with **IPUWorkflowTag**.
- 
--The phases of the IPUWorkflow (in order) are: **Facts Collection, Checks, Report, Download, Upgrade RamDisk Preparation, Upgrade RamDisk Start, Late Tests, Preparation, RPM Upgrade, Application Upgrade, Third Party Applications, Finalization** and **First Boot**. Each phase has a specific tag that marks an actor as being part of that phase. You can find descriptions of all the phases and their tags [here](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/common/workflows/inplace_upgrade.py) and workflow diagram [here](../inplace-upgrade-workflow).
-+The phases of the IPUWorkflow (in order) are: **Facts Collection, Checks, Report, Download, Upgrade RamDisk Preparation, Upgrade RamDisk Start, Late Tests, Preparation, RPM Upgrade, Application Upgrade, Third Party Applications, Finalization** and **First Boot**. Each phase has a specific tag that marks an actor as being part of that phase. You can find descriptions of all the phases and their tags [here](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/common/workflows/inplace_upgrade.py) and workflow diagram [here](../inplace-upgrade-workflow).
- 
- For example, if an actor is to be executed within the Checks phase, it needs to be tagged both with IPUWorkflowTag and ChecksPhaseTag. The result after updating the boilerplate would be:
- 
-@@ -90,7 +90,7 @@ All communication between actors in Leapp is carried out using **“messages”*
- 
- For further information about messaging see [document](../messaging).
- 
--One of the existing models in Leapp is [ActiveKernelModulesFacts](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/models/activekernelmodulesfacts.py). Messages from this model contain data about the system on which Leapp has been started. For example, it contains installed kernel modules. If an actor wants to perform some action based on existing kernel modules on the system, the actor can get list of these modules by consuming the _ActiveKernelModulesFacts_ messages. By extending the boilerplate, the code could look like this:
-+One of the existing models in Leapp is [ActiveKernelModulesFacts](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/models/activekernelmodulesfacts.py). Messages from this model contain data about the system on which Leapp has been started. For example, it contains installed kernel modules. If an actor wants to perform some action based on existing kernel modules on the system, the actor can get list of these modules by consuming the _ActiveKernelModulesFacts_ messages. By extending the boilerplate, the code could look like this:
- 
- ```python
- from leapp.actors import Actor
-@@ -280,7 +280,7 @@ During development of your new actor, it is expected that you will test your wor
- 
- ### Executing a single actor
- 
--You should use snactor tool to run a single actor and verify its output. Assuming that there are no errors, the actor was placed inside a valid leapp repository and snactor tool is aware of such repository, you can call snactor run to execute it. Below we are executing the existing [OSReleaseCollector](https://github.com/oamg/leapp-repository/tree/master/repos/system_upgrade/el7toel8/actors/osreleasecollector) actor that provides information about operating system release from target system. For the `snactor run` command you can use either the actor’s folder name (osreleasecollector), the actor’s class name (OSReleaseCollector) or the value of the name attribute of the actor’s class (os_release_collector).
-+You should use snactor tool to run a single actor and verify its output. Assuming that there are no errors, the actor was placed inside a valid leapp repository and snactor tool is aware of such repository, you can call snactor run to execute it. Below we are executing the existing [OSReleaseCollector](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8/actors/osreleasecollector) actor that provides information about operating system release from target system. For the `snactor run` command you can use either the actor’s folder name (osreleasecollector), the actor’s class name (OSReleaseCollector) or the value of the name attribute of the actor’s class (os_release_collector).
- 
- ```shell
- # pwd
-@@ -350,7 +350,7 @@ Finally, you can make your actor part of the “leapp upgrade” process and che
- 
- ### Verifying correct communication between actors
- 
--Leapp provides another actor, named [CheckOSRelease](https://github.com/oamg/leapp-repository/tree/master/repos/system_upgrade/el7toel8/actors/checkosrelease), that consumes messages from model _OSReleaseFacts_ and produces an error message in case system OS Release is not supported by Leapp upgrade process. In order to consume such message, _OSReleaseCollector_ actor needs to be executed before _CheckOSRelease_ and its message needs to be stored inside Leapp database. This process is controlled by the framework during the execution of “leapp upgrade” command.
-+Leapp provides another actor, named [CheckOSRelease](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8/actors/checkosrelease), that consumes messages from model _OSReleaseFacts_ and produces an error message in case system OS Release is not supported by Leapp upgrade process. In order to consume such message, _OSReleaseCollector_ actor needs to be executed before _CheckOSRelease_ and its message needs to be stored inside Leapp database. This process is controlled by the framework during the execution of “leapp upgrade” command.
- 
- But, if you want to execute it manually, for test purposes, you can also use snactor for it. First we need to make sure that all messages that will be consumed are generated and stored. For this example, this means running _OSReleaseCollector_ actor with the _--save-output_ option of snactor:
- 
-@@ -412,7 +412,7 @@ This [pull request](https://github.com/oamg/leapp-repository/pull/186) gives a g
- 
- ### In which existing workflow phase should I place my new actor?
- 
--You can decide that based on the description of the phases this information is available in the [code](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/workflows/inplace_upgrade.py) and diagram [here](../inplace-upgrade-workflow). Please note that if your actor depends on some message generated by another actor, it cannot be executed in a phase before the phase of such actor. In a similar way, if your actor produces data, it needs to be executed before the actor consuming the data.
-+You can decide that based on the description of the phases this information is available in the [code](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/workflows/inplace_upgrade.py) and diagram [here](../inplace-upgrade-workflow). Please note that if your actor depends on some message generated by another actor, it cannot be executed in a phase before the phase of such actor. In a similar way, if your actor produces data, it needs to be executed before the actor consuming the data.
- 
- ### How to stop the upgrade in case my actor finds a problem with the system setup?
- 
-diff --git a/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md b/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-index 5e97c78..a31208f 100644
---- a/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-+++ b/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-@@ -56,7 +56,7 @@ $ snactor run CheckSystemArch --verbose
- If, instead of only adding a message to the log, the actor writer wants to make
- sure that the upgrade process will be stopped in case of unsupported arch, the
- actor needs to produce a [Report](/pydoc/leapp.reporting.html#leapp.reporting.Report)
--message using one of the `report_*` functions from the [reporting](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/libraries/reporting.py)
-+message using one of the `report_*` functions from the [reporting](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/libraries/reporting.py)
- shared library with the `'inhibitor'` group.
- 
- ```python
-@@ -131,7 +131,7 @@ This is all that an actor needs to do in order to verify if some condition is
- present on the system and inhibit the upgrade process based on that check.
- 
- After all the system checks are executed by different actors, an existing actor
--named [VerifyCheckResults](https://github.com/oamg/leapp-repository/tree/master/repos/system_upgrade/el7toel8/actors/verifycheckresults)
-+named [VerifyCheckResults](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8/actors/verifycheckresults)
- is scheduled to run in the Leapp upgrade workflow. If some [Report](/pydoc/leapp.reporting.html#leapp.reporting.Report)
- message with the `'inhibitor'` group was generated by some previous execution of
- another actor in any previous phase of the workflow, like the sample one we just
-diff --git a/docs/source/test-actors.md b/docs/source/test-actors.md
-index 322fe77..967c2ad 100644
---- a/docs/source/test-actors.md
-+++ b/docs/source/test-actors.md
-@@ -21,13 +21,13 @@ Test module names should match the following regex:
- - These tests deal with individual actor's functions/methods.
- - It's not possible to unit test any method/function within the *actor.py*. You can write unit tests only for functions/methods within the actor's libraries.
- - Thus, to be able to write unit tests for an actor, ideally the only thing in the _actor.py_'s _process()_ method is calling the entry-point function of the actor's library python module.
--- [Example of unit tests](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/checkbootavailspace/tests/unit_test_checkbootavailspace.py)
-+- [Example of unit tests](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/checkbootavailspace/tests/unit_test_checkbootavailspace.py)
- 
- ### Component tests
- 
- - These tests provide fabricated input messages for the actor, check the outputs stated in the actor's description.
- - These tests should not be written based on the actor's code but rather based on the behavior stated in the actor's description. They could be written by somebody who didn't write the code.
--- [Example of component tests](https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/checknfs/tests/test_checknfs.py)
-+- [Example of component tests](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/actors/checknfs/tests/test_checknfs.py)
- 
- ## End to end (e2e) tests
- 
-diff --git a/docs/source/unit-testing.md b/docs/source/unit-testing.md
-index d4feec9..52310e1 100644
---- a/docs/source/unit-testing.md
-+++ b/docs/source/unit-testing.md
-@@ -11,7 +11,7 @@ Tests are considered being part of the actor and we do not only encourage but
- basically require you to write tests if you want the actors to be accepted into
- the git repository. To read more about what we ask from you when submitting
- your work for our review, see
--[Contributing guidelines for writing actors](https://github.com/oamg/leapp-repository/blob/master/CONTRIBUTING.md).
-+[Contributing guidelines for writing actors](https://github.com/oamg/leapp-repository/blob/main/CONTRIBUTING.md).
- 
- Tests for an actor are to be placed within the actor's directory, in a
- subdirectory called `tests`. The layout for an actor `MyActor` in the
-@@ -111,7 +111,7 @@ supposed to be unit tested is necessary to move into the actor's private
- library. Modules from the private library can then be imported not only from
- the `actor.py` but also from the test modules.
- 
--Let's assume your actor has a private library module called 
-+Let's assume your actor has a private library module called
- `private_{actor_name}.py`.
- 
- ```
-@@ -173,7 +173,7 @@ install-deps:
- Note: Dependencies defined the way mentioned above is for test execution only.
- If your actor requires any package when executed as part of a workflow, it
- needs to be specified in a
--[leapp-repository specfile](https://github.com/oamg/leapp-repository/blob/master/packaging/leapp-repository.spec).
-+[leapp-repository specfile](https://github.com/oamg/leapp-repository/blob/main/packaging/leapp-repository.spec).
- 
- ## Running the tests
- 
-@@ -209,7 +209,7 @@ It is also possible to run only selected tests based on their name:
- pytest -k "vim"    # to run all tests contains vim in name
- pytest -k "not vim"    # to run all tests, which not contains vim in name
- ```
--More examples could be found in the 
-+More examples could be found in the
- [pytest documentation](https://docs.pytest.org/en/latest/example/markers.html#using-k-expr-to-select-tests-based-on-their-name)
- 
- ### Shared libraries' tests
-diff --git a/packaging/leapp.spec b/packaging/leapp.spec
-index 2352bf0..ab38d20 100644
---- a/packaging/leapp.spec
-+++ b/packaging/leapp.spec
-@@ -1,9 +1,9 @@
- # IMPORTANT:
- # Please read the documentation on how to deal with dependencies before adding a new one.
--# https://github.com/oamg/leapp/blob/master/docs/source/dependencies.md
-+# https://github.com/oamg/leapp/blob/main/docs/source/dependencies.md
- 
- %global debug_package %{nil}
--%global gittag master
-+%global gittag main
- 
- # IMPORTANT: this is for the leapp-framework capability (it's not the real
- # version of the leapp). The capability reflects changes in api and whatever
--- 
-2.47.0
-

SOURCES/0002-docs-Update-docs-engine-and-dependencies.patch

@@ -1,509 +0,0 @@
-From 7565b5c8cd5a098522565ff0ed5278eb2b04b7a8 Mon Sep 17 00:00:00 2001
-From: Matej Matuska <mmatuska@redhat.com>
-Date: Mon, 4 Mar 2024 13:49:18 +0100
-Subject: [PATCH 2/6] docs: Update docs engine and dependencies
-
-Changes with version 3.5.4:
-- The biggest change is the replacement of recommonmark with MyST for markdown
-parsing. The recommonmark library is no longer maintained and is also deprecated
-in sphinx. The recommended replacement is MyST library. In our case it seems
-like a drop-in replacement with only errors being "non-consecutive header level
-increment", which shouldn't be a problem and the docs build successfully.
-
-Changes with version 4.5.0
-- No major changes, just some deprecated APIs are replaced.
-
-Changes with version 5.3.0
-- Instead of linking to autodoc generated HTML files (in the pydoc dir), use cross
-references. Also fix some of the ambiguous references and repair some of
-the broken ones.
-
-Changes with version 6.2.1
-- No breaking changes.
-- This version requires Python 3.10 for deps to correctly install,
-otherwise the version of sphinx-autobuild and sphinxcontrib-* packages
-would have to pinned.
-
-Changes with version 7.2.6
-- No breaking changes.
-- Works properly on Python >= 3.10. On Python 3.12 requires manual upgrade
-of the six package until the version is bumped in requirements.txt.
----
- .readthedocs.yaml                             |  2 +-
- docs/Makefile                                 |  5 ++--
- docs/source/best-practices.md                 | 18 +++++------
- docs/source/conf.py                           | 30 +++++++++----------
- docs/source/debugging.md                      |  2 +-
- docs/source/deprecation.md                    |  7 ++---
- docs/source/devenv-install.md                 |  2 +-
- docs/source/dialogs.md                        |  4 +--
- docs/source/el7toel8/actor-rhel7-to-rhel8.md  |  2 +-
- docs/source/el7toel8/deprecation.md           |  2 +-
- docs/source/el7toel8/envars.md                |  2 +-
- .../source/el7toel8/inhibit-rhel7-to-rhel8.md |  8 +++--
- docs/source/faq.md                            | 16 +++++-----
- docs/source/messaging.md                      |  2 +-
- docs/source/terminology.md                    |  2 +-
- docs/source/unit-testing.md                   |  4 +--
- leapp/libraries/actor/__init__.py             |  2 +-
- leapp/libraries/common/__init__.py            |  2 +-
- leapp/utils/__init__.py                       |  4 +--
- requirements-docs.txt                         | 10 ++++---
- 20 files changed, 64 insertions(+), 62 deletions(-)
-
-diff --git a/.readthedocs.yaml b/.readthedocs.yaml
-index 5b892d8..f78af83 100644
---- a/.readthedocs.yaml
-+++ b/.readthedocs.yaml
-@@ -8,7 +8,7 @@ version: 2
- build:
-   os: ubuntu-22.04
-   tools:
--    python: "2.7"
-+    python: "3.10"
-     # You can also specify other tool versions:
-     # nodejs: "20"
-     # rust: "1.70"
-diff --git a/docs/Makefile b/docs/Makefile
-index 8750d07..709c35b 100644
---- a/docs/Makefile
-+++ b/docs/Makefile
-@@ -15,12 +15,11 @@ BUILDDIR      = build
- help:
- 	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
- livehtml:
--	@$(SPHINXAUTOBUILD) -z ../leapp "$(SOURCEDIR)" "$(BUILDDIR)/html" $(SPHINXOPTS) $(0)
--
--.PHONY: help Makefile
-+	@$(SPHINXAUTOBUILD) --watch ../leapp "$(SOURCEDIR)" "$(BUILDDIR)/html" $(SPHINXOPTS) $(0)
- 
- # Catch-all target: route all unknown targets to Sphinx using the new
- # "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
- %: Makefile
- 	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
- 
-+.PHONY: all help Makefile
-diff --git a/docs/source/best-practices.md b/docs/source/best-practices.md
-index 46aedbc..7951290 100644
---- a/docs/source/best-practices.md
-+++ b/docs/source/best-practices.md
-@@ -30,10 +30,10 @@ See the [tutorial on basic usage of snactor](first-actor).
- Part of your actor's functionality might end up being rather generic or abstract. In that case, consider converting it
- to a shared library function. You can introduce it in one of these two places:
- 
--- The [Leapp Standard Library](pydoc/leapp.libraries.stdlib)
-+- The [Leapp Standard Library](leapp.libraries.stdlib)
- 
-   The most generic functionality which actors of any workflow can use, e.g. function for exectuting a shell command,
--  should go to the [Leapp Standard Library](pydoc/leapp.libraries.stdlib).
-+  should go to the [Leapp Standard Library](leapp.libraries.stdlib).
-   For that, please submit proposals through issues or pull requests under the
-   [leapp GitHub repository](https://github.com/oamg/leapp/).
- 
-@@ -146,16 +146,16 @@ For more details about dependencies and how to modify them, see the [How to deal
- 
- If you encounter unexpected input or any other error during execution of an actor and want to stop it, use these exceptions:
- 
--- [StopActorExecution](pydoc/leapp.html#leapp.exceptions.StopActorExecution) - raising this exception is a convenient to stop actor's execution with no side effect - it has the same effect as returning `None` from the main `process()` method in the `actor.py`
--- [StopActorExecutionError](pydoc/leapp.html#leapp.exceptions.StopActorExecutionError) - raising this exception will stop actor's execution and notify the framework that an error has occurred and can influence the result of the workflow execution.
-+- [StopActorExecution](leapp.exceptions.StopActorExecution) - raising this exception is a convenient to stop actor's execution with no side effect - it has the same effect as returning `None` from the main `process()` method in the `actor.py`
-+- [StopActorExecutionError](leapp.exceptions.StopActorExecutionError) - raising this exception will stop actor's execution and notify the framework that an error has occurred and can influence the result of the workflow execution.
- 
--In case of [StopActorExecutionError](pydoc/leapp.html#leapp.exceptions.StopActorExecutionError) the execution of the workflow will stop or not according to the [policy](pydoc/leapp.workflows.html?highlight=FailPhase#module-leapp.workflows.policies) defined in the workflow, there are three possibilities:
-+In case of [StopActorExecutionError](leapp.exceptions.StopActorExecutionError) the execution of the workflow will stop or not according to the [policy](leapp.workflows.policies) defined in the workflow, there are three possibilities:
- 
--- [FailImmediately](pydoc/leapp.workflows.html?highlight=FailPhase#leapp.workflows.policies.Policies.Errors.FailImmediately) - end the workflow execution right away
--- [FailPhase](pydoc/leapp.workflows.html?highlight=FailPhase#leapp.workflows.policies.Policies.Errors.FailPhase) - end the workflow execution after finishing the current phase
--- [ReportOnly](pydoc/leapp.workflows.html?highlight=FailPhase#leapp.workflows.policies.Policies.Errors.ReportOnly) - do not end the workflow execution at all and continue with logging the issue only
-+- [FailImmediately](leapp.workflows.policies.Policies.Errors.FailImmediately) - end the workflow execution right away
-+- [FailPhase](leapp.workflows.policies.Policies.Errors.FailPhase) - end the workflow execution after finishing the current phase
-+- [ReportOnly](leapp.workflows.policies.Policies.Errors.ReportOnly) - do not end the workflow execution at all and continue with logging the issue only
- 
--You can also use the [StopActorExecution](pydoc/leapp.html#leapp.exceptions.StopActorExecution) and [StopActorExecutionError](pydoc/leapp.html#leapp.exceptions.StopActorExecutionError) exceptions inside a private or shared library.
-+You can also use the [StopActorExecution](leapp.exceptions.StopActorExecution) and [StopActorExecutionError](leapp.exceptions.StopActorExecutionError) exceptions inside a private or shared library.
- 
- ## Use the LEAPP and LEAPP\_DEVEL prefixes for new envars
- 
-diff --git a/docs/source/conf.py b/docs/source/conf.py
-index 4b1b4bc..d8551f4 100644
---- a/docs/source/conf.py
-+++ b/docs/source/conf.py
-@@ -25,8 +25,6 @@ sys.path.insert(0, os.path.abspath(os.path.dirname(os.path.dirname(os.path.dirna
- 
- import sphinx_rtd_theme  # noqa
- import leapp  # noqa
--from recommonmark.parser import CommonMarkParser  # noqa
--from recommonmark.transform import AutoStructify  # noqa
- 
- # -- General configuration ------------------------------------------------
- 
-@@ -37,9 +35,12 @@ from recommonmark.transform import AutoStructify  # noqa
- # Add any Sphinx extension module names here, as strings. They can be
- # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
- # ones.
--extensions = ['sphinx.ext.autodoc',
--              'sphinx.ext.githubpages',
--              'autosectionlabelext']
-+extensions = [
-+    'sphinx.ext.autodoc',
-+    'sphinx.ext.githubpages',
-+    'autosectionlabelext',
-+    'myst_parser',
-+]
- 
- # Add any paths that contain templates here, relative to this directory.
- templates_path = ['_templates']
-@@ -50,6 +51,9 @@ templates_path = ['_templates']
- source_suffix = ['.md', '.rst']
- # source_suffix = '.rst'
- 
-+# how many level of headings in markdown should linkable anchors be generated for
-+myst_heading_anchors = 3
-+
- # The master toctree document.
- master_doc = 'index'
- 
-@@ -72,7 +76,8 @@ release = leapp.FULL_VERSION
- #
- # This is also used if you do content translation via gettext catalogs.
- # Usually you set "language" from the command line for these cases.
--language = None
-+language = 'en'
-+# highlight_language = "python"
- 
- # List of patterns, relative to source directory, that match files and
- # directories to ignore when looking for source files.
-@@ -165,11 +170,6 @@ texinfo_documents = [
-      'Miscellaneous'),
- ]
- 
--
--source_parsers = {
--    '.md': CommonMarkParser,
--}
--
- autoclass_content = 'both'
- autodoc_default_flags = ['members', 'undoc-members', 'inherited-members', 'show-inheritance']
- 
-@@ -185,9 +185,7 @@ def filter_unwanted_leapp_types(app, what, name, obj, skip, options):
- 
- 
- def setup(app):
--    app.add_config_value('recommonmark_config', {}, True)
--    app.add_transform(AutoStructify)
-     app.connect('autodoc-skip-member', filter_unwanted_leapp_types)
--    app.add_stylesheet('css/asciinema-player.css')
--    app.add_stylesheet('css/custom.css')
--    app.add_javascript('js/asciinema-player.js')
-+    app.add_css_file('css/asciinema-player.css')
-+    app.add_css_file('css/custom.css')
-+    app.add_js_file('js/asciinema-player.js')
-diff --git a/docs/source/debugging.md b/docs/source/debugging.md
-index b01d156..b1e222e 100644
---- a/docs/source/debugging.md
-+++ b/docs/source/debugging.md
-@@ -4,7 +4,7 @@
- 
- The snactor tool is used to debug your actors. You can execute actors
- and save their output, so that it can be consumed by other actors.
--See [Storing messages in the repository data for reuse](messaging.html#storing-messages-in-the-repository-data-for-reuse).
-+See [Storing messages in the repository data for reuse](messaging.md#storing-messages-in-the-repository-data-for-reuse).
- 
- Snactor checks for the `LEAPP_DEBUG` environment variable and has also
- the --debug parameter which sets the environment variable to '1' when it is
-diff --git a/docs/source/deprecation.md b/docs/source/deprecation.md
-index 65cc18a..142d884 100644
---- a/docs/source/deprecation.md
-+++ b/docs/source/deprecation.md
-@@ -11,7 +11,7 @@ impact on your code, we introduce the deprecation process described below.
- The following lists cover deprecated functionality in the leapp utility, snactor,
- the leapp standard library, etc. But don't cover deprecated functionalities
- from particular leapp repositories (e.g. the [elt7toel8](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8) leapp repository). For
--such information, see [Deprecated functionality in the el7toel8 repository](el7toel8/deprecation.html#deprecated-functionality-in-the-el7toel8-repository).
-+such information, see [Deprecated functionality in the el7toel8 repository](el7toel8/deprecation.md#deprecated-functionality-in-the-el7toel8-repository).
- 
- ## current upstream development <span style="font-size:0.5em; font-weight:normal">(till the next release + 6months)</span>
- 
-@@ -106,7 +106,7 @@ the deprecation of derived classes.*
- In case of a class deprecation, all derived classes are considered to be deprecated
- as well. However, the current reporting could be a little bit confusing. To
- improve that, the `stack_level_offset` option can be specified.
--See [examples of the use of the @deprecated decorator for classes](deprecation.html#classes).
-+See [examples of the use of the @deprecated decorator for classes](deprecation.md#classes).
- 
- When you mark any entity as deprecated and this entity is then used
- in the code, users will be notified about that via a terminal and report
-@@ -290,9 +290,8 @@ before the definition of the `produce_answer` function. But if we do the same
- for the test function, we will get an error (see that we have now just one
- deprecation warning now):
- 
--```python
-+```
- | 21:59:57 | conftest | INFO | conftest.py | Actor 'foo_producer' context teardown complete
--
- repos/system_upgrade/el7toel8/actors/fooproducer/tests/test_unit_fooproducer.py::test_process FAILED
- 
- ====================================================== FAILURES ======================================================
-diff --git a/docs/source/devenv-install.md b/docs/source/devenv-install.md
-index 84a5bab..210e48f 100644
---- a/docs/source/devenv-install.md
-+++ b/docs/source/devenv-install.md
-@@ -49,7 +49,7 @@ $ pip install git+https://github.com/oamg/leapp
- ```
- 
- Once the framework is installed, you can use the snactor tool.
--```shell
-+```
- $ snactor --help
- usage: snactor [-h] [--version] [--logger-config LOGGER_CONFIG]
-                [--config CONFIG] [--verbose] [--debug]
-diff --git a/docs/source/dialogs.md b/docs/source/dialogs.md
-index 391b37f..d863fab 100644
---- a/docs/source/dialogs.md
-+++ b/docs/source/dialogs.md
-@@ -4,9 +4,9 @@ Leapp framework uses dialogs to ask user for any additional information an actor
- automatically.
- Dialogs contain Components which represent individual questions.
- Complete list of component types can be found in
--[documentation](pydoc/leapp.dialogs.html#module-leapp.dialogs.components).
-+[documentation](leapp.dialogs.components).
- 
--As an example we will change [IpResolver](messaging.html#creating-a-message-consuming-actor) actor in a way that user
-+As an example we will change [IpResolver](messaging.md#creating-a-message-consuming-actor) actor in a way that user
- will decide which hostnames will be resolved.
- 
- 
-diff --git a/docs/source/el7toel8/actor-rhel7-to-rhel8.md b/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-index 2cc72f3..32b371f 100644
---- a/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-+++ b/docs/source/el7toel8/actor-rhel7-to-rhel8.md
-@@ -420,7 +420,7 @@ The process of inhibiting the upgrade is done by the VerifyCheckResult actor, ex
- 
- ### How to stop execution of my actor in case of an unexpected error?
- 
--It’s good practice to code defensively so the code is robust. The actor should detect unexpected input or result of some operation and exit gracefully instead of tracebacking. In case you detect an unexpected behavior, let the framework know about it by raising [StopActorExecutionError](pydoc/leapp.html#leapp.exceptions.StopActorExecutionError). Framework will act based on the [setting of the upgrade workflow](pydoc/leapp.workflows.html?highlight=FailPhase#module-leapp.workflows.policies) in one of the following three ways:
-+It’s good practice to code defensively so the code is robust. The actor should detect unexpected input or result of some operation and exit gracefully instead of tracebacking. In case you detect an unexpected behavior, let the framework know about it by raising [StopActorExecutionError](leapp.exceptions.StopActorExecutionError). Framework will act based on the [setting of the upgrade workflow](leapp.workflows.policies) in one of the following three ways:
- 
- - end the upgrade process right away, or
- - end the upgrade process after finishing the current phase, or
-diff --git a/docs/source/el7toel8/deprecation.md b/docs/source/el7toel8/deprecation.md
-index 37bef8f..243972f 100644
---- a/docs/source/el7toel8/deprecation.md
-+++ b/docs/source/el7toel8/deprecation.md
-@@ -8,7 +8,7 @@ after which the related functionality can be removed at any time.
- 
- *Note* The lists cover just the functionality provided inside the el7toel8
- repository only. For the functionality deprecated in the leapp
--framework, see [List of deprecated functionality in leapp](../deprecation.html#list-of-deprecated-functionality-in-leapp)
-+framework, see [List of deprecated functionality in leapp](../deprecation.md#list-of-the-deprecated-functionality-in-leapp)
- 
- ## current upstream development <span style="font-size:0.5em; font-weight:normal">(till the next release + 6months)</span>
- 
-diff --git a/docs/source/el7toel8/envars.md b/docs/source/el7toel8/envars.md
-index 86190ad..6eeb81f 100644
---- a/docs/source/el7toel8/envars.md
-+++ b/docs/source/el7toel8/envars.md
-@@ -2,7 +2,7 @@
- 
- Actors in the el7toel8 repository use environment variables specified below.
- All these envars use the suggested prefixes specified in
--[the best practices document](../best-practices#use-the-leapp-and-leapp-devel-prefixes-for-new-envars)
-+[the best practices document](../best-practices.md#use-the-leapp-and-leapp_devel-prefixes-for-new-envars)
- for the leapp project to distinguish their purpose: _production_ or _devel_ use.
- 
- If the argument for envars below is not specified, it is expected to set `0`
-diff --git a/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md b/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-index a31208f..c2c592f 100644
---- a/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-+++ b/docs/source/el7toel8/inhibit-rhel7-to-rhel8.md
-@@ -5,7 +5,7 @@
- With latest changes on Leapp and with new actors added to the el7toel8 Leapp
- repository, any actor can inhibit the upgrade process by producing a specific
- message when a problem is found. The message model to use in this case is
--[Report](pydoc/leapp.reporting.html#leapp.reporting.Report).
-+[Report](leapp.reporting.Report).
- If there is at least one Report message with the `'inhibitor'` group produced before
- the Report phase, the upgrade will be stopped in the Reports phase, in which the
- messages are being collected. It means that any Report message produced
-@@ -55,7 +55,7 @@ $ snactor run CheckSystemArch --verbose
- 
- If, instead of only adding a message to the log, the actor writer wants to make
- sure that the upgrade process will be stopped in case of unsupported arch, the
--actor needs to produce a [Report](/pydoc/leapp.reporting.html#leapp.reporting.Report)
-+actor needs to produce a [Report](leapp.reporting.Report)
- message using one of the `report_*` functions from the [reporting](https://github.com/oamg/leapp-repository/blob/main/repos/system_upgrade/el7toel8/libraries/reporting.py)
- shared library with the `'inhibitor'` group.
- 
-@@ -131,8 +131,10 @@ This is all that an actor needs to do in order to verify if some condition is
- present on the system and inhibit the upgrade process based on that check.
- 
- After all the system checks are executed by different actors, an existing actor
--named [VerifyCheckResults](https://github.com/oamg/leapp-repository/tree/main/repos/system_upgrade/el7toel8/actors/verifycheckresults)
-+==== BASE ====
-+named [VerifyCheckResults](https://github.com/oamg/leapp-repository/tree/master/repos/system_upgrade/el7toel8/actors/verifycheckresults)
- is scheduled to run in the Leapp upgrade workflow. If some [Report](/pydoc/leapp.reporting.html#leapp.reporting.Report)
-+==== BASE ====
- message with the `'inhibitor'` group was generated by some previous execution of
- another actor in any previous phase of the workflow, like the sample one we just
- wrote, the following output will be displayed to the user:
-diff --git a/docs/source/faq.md b/docs/source/faq.md
-index 66de4e0..4e00583 100644
---- a/docs/source/faq.md
-+++ b/docs/source/faq.md
-@@ -8,12 +8,12 @@
- - [What do I have to do in order to execute actor I just wrote?](#what-do-i-have-to-do-in-order-to-execute-actor-i-just-wrote)
- - [What should I do if I need to execute multiple actors? Can I somehow ensure the dependencies between them?](#what-should-i-do-if-i-need-to-execute-multiple-actors-can-i-somehow-ensure-the-dependencies-between-them)
- - [How can I specify what run time dependencies will my actor have?](#how-can-i-specify-what-run-time-dependencies-will-my-actor-have)
--- [How can I distinguish between actors that I depend on directly (I need to consume their output) and indirectly (I just need them to be executed as part of the upgrade as I don’t handle the upgrade of that specific piece; think PHP vs. Apache - upgrade of Apache is independent of the upgrade of PHP but it needs to be done to enable its upgrade)?](#how-can-i-distinguish-between-actors-that-i-depend-on-directly-i-need-to-consume-their-output-and-indirectly-i-just-need-them-to-be-executed-as-part-of-the-upgrade-as-i-don-t-handle-the-upgrade-of-that-specific-piece-think-php-vs-apache-upgrade-of-apache-is-independent-of-the-upgrade-of-php-but-it-needs-to-be-done-to-enable-its-upgrade)
-+- [How can I distinguish between actors that I depend on directly (I need to consume their output) and indirectly (I just need them to be executed as part of the upgrade as I don’t handle the upgrade of that specific piece; think PHP vs. Apache - upgrade of Apache is independent of the upgrade of PHP but it needs to be done to enable its upgrade)?](#how-can-i-distinguish-between-actors-that-i-depend-on-directly-i-need-to-consume-their-output-and-indirectly-i-just-need-them-to-be-executed-as-part-of-the-upgrade-as-i-dont-handle-the-upgrade-of-that-specific-piece)
- - [Once I write an actor that consumes data from some other actors, how can I be sure that the format will not change on the producing side in the future?](#once-i-write-an-actor-that-consumes-data-from-some-other-actors-how-can-i-be-sure-that-the-format-will-not-change-on-the-producing-side-in-the-future)
- - [What are the best practices for writing actors?](#what-are-the-best-practices-for-writing-actors)
- - [What are the requirements for actors to be accepted by upstream?](#what-are-the-requirements-for-actors-to-be-accepted-by-upstream)
- - [How can I debug my actor? Is there a standard/supported way how to log and get logs from actors/channels?](#what-are-the-requirements-for-actors-to-be-accepted-by-upstream)
--- [Are there some technical limitations for an actor? E.g. maximum time execution, size of the input/output, libraries I can use… In case there are, is it possible to specify that the actor needs e.g. longer time for execution?](#are-there-some-technical-limitations-for-an-actor-e-g-maximum-time-execution-size-of-the-input-output-libraries-i-can-use-in-case-there-are-is-it-possible-to-specify-that-the-actor-needs-e-g-longer-time-for-execution)
-+- [Are there some technical limitations for an actor? E.g. maximum time execution, size of the input/output, libraries I can use… In case there are, is it possible to specify that the actor needs e.g. longer time for execution?](#are-there-some-technical-limitations-for-an-actor-eg-maximum-time-execution-size-of-the-inputoutput-libraries-i-can-use-in-case-there-are-is-it-possible-to-specify-that-the-actor-needs-eg-longer-time-for-execution)
- - [Are there some actions that are either forbidden or not recommended to be done in actors?](#are-there-some-actions-that-are-either-forbidden-or-not-recommended-to-be-done-in-actors)
- - [I got an error about PES data/ Repositories mapping where I find such files?](#i-got-an-error-about-pes-data-repositories-mapping-where-i-find-such-files)
- 
-@@ -49,19 +49,21 @@ Source: [How to create a Leapp actor for RHEL 7 to 8 upgrade](el7toel8/actor-rhe
- ## What should I do if I need to execute multiple actors? Can I somehow ensure the dependencies between them?
- 
- To be sure that your ActorA runs before your ActorB, produce a specific message in ActorA and let ActorB consume it. By doing this you create a dependency of ActorB on ActorA.
--To run just your actors during development, use snactor run --save-output ActorA to save the message of ActorA to the Leapp repository database and then snactor run ActorB. This way, the ActorB will be able to consume the ActorA's saved message. Read more about that in the [tutorial about messaging](messaging).
-+To run just your actors during development, use snactor run --save-output ActorA to save the message of ActorA to the Leapp repository database and then snactor run ActorB. This way, the ActorB will be able to consume the ActorA's saved message. Read more about that in the [tutorial about messaging](messaging.md).
- 
- ## How can I specify what run time dependencies will my actor have?
- 
--See the section about dependencies in the [Best practices document](best-practices.html#do-not-introduce-new-dependencies)
-+See the section about dependencies in the [Best practices document](best-practices.md#do-not-introduce-new-dependencies)
- 
--## How can I distinguish between actors that I depend on directly (I need to consume their output) and indirectly (I just need them to be executed as part of the upgrade as I don't handle the upgrade of that specific piece; think PHP vs. Apache - upgrade of Apache is independent of the upgrade of PHP but it needs to be done to enable its upgrade)?
-+## How can I distinguish between actors that I depend on directly (I need to consume their output) and indirectly (I just need them to be executed as part of the upgrade as I don't handle the upgrade of that specific piece)?
-+
-+An example of this is PHP vs. Apache - upgrade of Apache is independent of the upgrade of PHP but it needs to be done to enable its upgrade.
- 
- In the case of actors you depend on directly because you consume their message, you don't need to do anything extra, the Leapp framework will make sure that the actors that produce the messages you consume are executed before your actor.
- In case of the actors you depend on indirectly you may approach it in various ways:
- 
- - Talk to the developers of the actors you depend on indirectly and agree on sending a message between their actors and your actor. This will cause a direct dependency described above.
--- Talk to the [Engineering Lead](contributing.html#contact) of the OS and Application Modernization group and tell them to coordinate development, testing and release of your actor and the actors you depend on indirectly, targeting the same milestone.
-+- Talk to the [Engineering Lead](contributing.md#contact) of the OS and Application Modernization group and tell them to coordinate development, testing and release of your actor and the actors you depend on indirectly, targeting the same milestone.
- 
- ## Once I write an actor that consumes data from some other actors, how can I be sure that the format will not change on the producing side in the future?
- 
-@@ -85,7 +87,7 @@ Source: [How to create a Leapp actor for RHEL 7 to 8 upgrade](el7toel8/actor-rhe
- There are no technical limitations but rather conceptual:
- 
- - Libraries to use:
--  - See the section about actor dependencies in the [Best practices document](best-practices.html#do-not-introduce-new-dependencies)
-+  - See the section about actor dependencies in the [Best practices document](best-practices.md#do-not-introduce-new-dependencies)
- 
- Execution time:
- 
-diff --git a/docs/source/messaging.md b/docs/source/messaging.md
-index 73b76c1..f1f5636 100644
---- a/docs/source/messaging.md
-+++ b/docs/source/messaging.md
-@@ -1,7 +1,7 @@
- ## Using messaging to send data between actors
- 
- The Leapp framework uses messages to send data to other actors that are executed afterward.
--Messages are defined through the models declared [earlier](first-actor.html#creating-a-model). Actors can consume these messages and produce data based on their input.
-+Messages are defined through the models declared [earlier](first-actor.md#creating-a-model). Actors can consume these messages and produce data based on their input.
- 
- As an example, the actors consume Hostname messages, resolve IPs for those
- hostnames, and create the ResolvedHostname model to send a new type of message.
-diff --git a/docs/source/terminology.md b/docs/source/terminology.md
-index 42a823f..b1754dc 100644
---- a/docs/source/terminology.md
-+++ b/docs/source/terminology.md
-@@ -1,4 +1,4 @@
--## Terminology
-+# Terminology
- 
- ### Actor
- 
-diff --git a/docs/source/unit-testing.md b/docs/source/unit-testing.md
-index 52310e1..f721d55 100644
---- a/docs/source/unit-testing.md
-+++ b/docs/source/unit-testing.md
-@@ -49,7 +49,7 @@ def test_actor_execution(current_actor_context):
-     current_actor_context.run()
- ```
- 
--This example makes use of the [current_actor_context](pydoc/leapp.html#leapp.snactor.fixture.current_actor_context)
-+This example makes use of the [current_actor_context](#leapp.snactor.fixture.current_actor_context)
- fixture and will execute the `MyActor` actor.
- 
- Now if you would want to check that it produced an imaginary model called
-@@ -92,7 +92,7 @@ The unit testing support was first implemented with the help of
- [pytest fixtures](https://docs.pytest.org/en/latest/fixture.html).
- Nowadays, we encourage you to use only the `current_actor_context` fixture
- mentioned above. However the other fixtures have been preserved and are
--still possible to use - see their [documentation](pydoc/leapp.html#module-leapp.snactor.fixture).
-+still possible to use - see their [documentation](#leapp.snactor.fixture).
- 
- #### Testing actors that modify the OS
- 
-diff --git a/leapp/libraries/actor/__init__.py b/leapp/libraries/actor/__init__.py
-index a0662c5..e63b5e1 100644
---- a/leapp/libraries/actor/__init__.py
-+++ b/leapp/libraries/actor/__init__.py
-@@ -5,7 +5,7 @@ are placed in the actor's libraries folder.
- 
- Example:
-       If you actor has a libraries folder with a module.py python module, import it
--      from the actor like this::
-+      from the actor like this:
- 
-       from leapp.libraries.actor import module
- 
-diff --git a/leapp/libraries/common/__init__.py b/leapp/libraries/common/__init__.py
-index d14c19e..a983cfa 100644
---- a/leapp/libraries/common/__init__.py
-+++ b/leapp/libraries/common/__init__.py
-@@ -4,7 +4,7 @@ are placed in the repository's libraries folder.
- 
- Example:
-       If any of the repositories has a libraries folder with a module.py python module, import it
--      from the actor like this::
-+      from the actor like this:
- 
-       from leapp.libraries.common import module
- 
-diff --git a/leapp/utils/__init__.py b/leapp/utils/__init__.py
-index 68a5f38..1f5dde1 100644
---- a/leapp/utils/__init__.py
-+++ b/leapp/utils/__init__.py
-@@ -13,8 +13,8 @@ def get_api_models(actor, what):
- 
-     :param what: A string which either is 'consumes' or 'produces'
-     :type what: str
--    :param actor: Actor type/instance or ActorDefinition instance to retrieve the information from
--    :type actor: Actor or ActorDefinition
-+    :param actor: type/instance or ActorDefinition instance to retrieve the information from
-+    :type actor: leapp.actors.Actor or ActorDefinition
-     :return: Tuple of all produced or consumed models as specified by actor and APIs used by the actor.
-     """
- 
-diff --git a/requirements-docs.txt b/requirements-docs.txt
-index 54d5ba1..93096c4 100644
---- a/requirements-docs.txt
-+++ b/requirements-docs.txt
-@@ -1,7 +1,9 @@
- -r requirements-tests.txt
- 
--CommonMark==0.7.5
--sphinx>=1.5,<1.6
--sphinx_rtd_theme==0.4.3
-+sphinx==7.2.6
-+sphinx_rtd_theme
-+sphinxcontrib-jquery
-+docutils
-+CommonMark
-+myst-parser
- sphinx-autobuild
--git+https://github.com/leapp-to/recommonmark.git@master
--- 
-2.47.0
-

SOURCES/0004-pylint-ignore-too-many-params-lines-yield-from.patch

@@ -1,43 +0,0 @@
-From 45c1b35fb5cc5ec43288a4318c904bc5ae997638 Mon Sep 17 00:00:00 2001
-From: Michal Hecko <mhecko@redhat.com>
-Date: Tue, 29 Oct 2024 22:16:09 +0100
-Subject: [PATCH 4/6] pylint: ignore too many params/lines, yield from
-
-Ignore pylint's options:
-* too-many-lines
-* too-many-positional-arguments
-* use-yield-from
-
-Some of these options cannot be used (python2.7 compat) or configured.
-See: https://github.com/oamg/leapp-repository/pull/1299
----
- .pylintrc | 5 ++++-
- 1 file changed, 4 insertions(+), 1 deletion(-)
-
-diff --git a/.pylintrc b/.pylintrc
-index fd73083..459933a 100644
---- a/.pylintrc
-+++ b/.pylintrc
-@@ -28,7 +28,9 @@ disable=
-  too-few-public-methods,
-  too-many-ancestors,
-  too-many-branches,
-+ too-many-lines,
-  too-many-locals,
-+ too-many-positional-arguments,
-  too-many-public-methods,
-  too-many-statements,
-  print-statement,
-@@ -42,7 +44,8 @@ disable=
-  no-absolute-import,  # XXX FIXME nice to have one day
-  unspecified-encoding,  # XXX FIXME May be a good thing to have one day though
-  deprecated-class,  # We still have < 3.9 to support
-- use-dict-literal
-+ use-dict-literal,
-+ use-yield-from
- 
- [FORMAT]
- # Maximum number of characters on a single line.
--- 
-2.47.0
-

SOURCES/0005-packaging-bump-leapp-framework-version.patch

@@ -1,37 +0,0 @@
-From 607be4cd18dd24695e8fad827e7484bed36f7dce Mon Sep 17 00:00:00 2001
-From: Michal Hecko <mhecko@redhat.com>
-Date: Mon, 4 Nov 2024 11:29:00 +0100
-Subject: [PATCH 5/6] packaging: bump leapp-framework version
-
-Increase the provided leapp-framework version to 6.0 (from 5.0).
-Similarly, framework_dependencies are bumped to 6.0. These changes
-are done as introducing actor configuration presents a major feature,
-and, therefore, any codebases using the framework might want to
-require leapp with config support. Bumping the version number, thus,
-allows to distinguish between leapp-framework versions that provide
-configs and those that do not.
----
- packaging/leapp.spec | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/packaging/leapp.spec b/packaging/leapp.spec
-index 29ece53..7efe596 100644
---- a/packaging/leapp.spec
-+++ b/packaging/leapp.spec
-@@ -13,11 +13,11 @@
- # This is kind of help for more flexible development of leapp repository,
- # so people do not have to wait for new official release of leapp to ensure
- # it is installed/used the compatible one.
--%global framework_version 5.0
-+%global framework_version 6.0
- 
- # IMPORTANT: everytime the requirements are changed, increment number by one
- # - same for Provides in deps subpackage
--%global framework_dependencies 5
-+%global framework_dependencies 6
- 
- # Do not build bindings for python3 for RHEL == 7
- # # Currently Py2 is dead on Fedora and we don't have to support it. As well,
--- 
-2.47.0
-

SOURCES/0006-spec-Introduce-etc-leapp-actor_conf.d-directory.patch

@@ -1,35 +0,0 @@
-From ee6bf5aa0608723528caaf9e6fd2edd67258dcc8 Mon Sep 17 00:00:00 2001
-From: Petr Stodulka <pstodulk@redhat.com>
-Date: Thu, 14 Nov 2024 16:28:57 +0100
-Subject: [PATCH 6/6] spec: Introduce /etc/leapp/actor_conf.d/ directory
-
-The directory should be owned by the leapp rpm so leapp actors
-could already use it - or existing leapp repositories packages could
-install some config files inside already.
----
- packaging/leapp.spec | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/packaging/leapp.spec b/packaging/leapp.spec
-index 7efe596..8bb4102 100644
---- a/packaging/leapp.spec
-+++ b/packaging/leapp.spec
-@@ -184,6 +184,7 @@ install -m 0755 -d %{buildroot}%{_datadir}/leapp/report_schema
- install -m 0644 -p report-schema-v110.json %{buildroot}%{_datadir}/leapp/report_schema/report-schema.json
- install -m 0700 -d %{buildroot}%{_sharedstatedir}/leapp
- install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp
-+install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp/actor_conf.d/
- install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp/repos.d
- install -m 0600 -d %{buildroot}%{_sysconfdir}/leapp/answers
- # standard directory should have permission set to 0755, however this directory
-@@ -209,6 +210,7 @@ install -m 0644 -p man/leapp.1 %{buildroot}%{_mandir}/man1/
- %config(noreplace) %{_sysconfdir}/leapp/leapp.conf
- %config(noreplace) %{_sysconfdir}/leapp/logger.conf
- %dir %{_sysconfdir}/leapp
-+%dir %{_sysconfdir}/leapp/actor_conf.d
- %dir %{_sysconfdir}/leapp/answers
- %dir %{_sysconfdir}/leapp/repos.d
- %{_bindir}/leapp
--- 
-2.47.0
-

SPECS/leapp.spec

@@ -1,518 +0,0 @@
-# IMPORTANT: this is for the leapp-framework capability (it's not the real
-# version of the leapp). The capability reflects changes in api and whatever
-# functionality important from the point of repository. In case of
-# incompatible changes, bump the major number and zero minor one. Otherwise
-# bump the minor one.
-# NOTE: we do not use this capability in the RHEL official rpms. But we provide
-# it. In case of upstream, dependencies are set differently, but YUM is not
-# capable enough to deal with them correctly all the time; we continue to use
-# simplified deps in RHEL to ensure that YUM can deal with it.
-%global framework_version 6.0
-
-# IMPORTANT: everytime the requirements are changed, increment number by one
-# - same for Provides in deps subpackage
-%global framework_dependencies 6
-
-# Do not build bindings for python3 for RHEL == 7
-# # Currently Py2 is dead on Fedora and we don't have to support it. As well,
-# # our current packaging is not prepared for Py2 & Py3 packages in the same
-# # time. Instead of that, make Py2 and Py3 exclusive. Possibly rename macros..
-%if 0%{?rhel} == 7
-  %define leapp_python 2
-  %define leapp_python_sitelib %{python2_sitelib}
-  %define leapp_python_name python2
-  %define leapp_py_build %{py2_build}
-  %define leapp_py_install %{py2_install}
-
-%else
-  %define leapp_python 3
-  %define leapp_python_sitelib %{python3_sitelib}
-  %define leapp_python_name python3
-  %define leapp_py_build %{py3_build}
-  %define leapp_py_install %{py3_install}
-  # we have to drop the dependency on python(abi) completely on el8+ because
-  # of IPU (python abi is different between systems)
-  %global __requires_exclude ^python\\(abi\\) = 3\\..+|/usr/libexec/platform-python|/usr/bin/python.*
-%endif
-
-Name:       leapp
-Version:    0.18.0
-Release:    2%{?dist}
-Summary:    OS & Application modernization framework
-
-License:    ASL 2.0
-URL:        https://oamg.github.io/leapp/
-Source0:    https://github.com/oamg/%{name}/archive/v%{version}.tar.gz#/%{name}-%{version}.tar.gz
-
-# NOTE: Our packages must be noarch. Do no drop this in any way.
-BuildArch:  noarch
-
-Requires: %{leapp_python_name}-%{name} = %{version}-%{release}
-%{?python_disable_dependency_generator}
-
-%if 0%{?rhel} == 7
-# The leapp tool doesn't require the leapp-repository anymore. However for the
-# compatibility purposes, we keep it here for RHEL 7 at least for a while.
-# The dependency on leapp is expected to be set by packages providing the
-# final functionality (e.g. conversion of system, in-place upgrade).
-# IOW, people should look for rpms like leapp-convert or leapp-upgrade
-# in future.
-
-# Just ensure the leapp repository will be installed as well. Compatibility
-# should be specified by the leapp-repository itself
-Requires: leapp-repository
-%endif # !fedora
-
-# PATCHES HERE
-# Patch0001: filename.patch
-Patch0001:  0001-Update-references-from-master-branch-to-main.patch
-Patch0002:  0002-docs-Update-docs-engine-and-dependencies.patch
-Patch0003:  0003-configs-implement-actor-configuration-support.patch
-Patch0004:  0004-pylint-ignore-too-many-params-lines-yield-from.patch
-Patch0005:  0005-packaging-bump-leapp-framework-version.patch
-Patch0006:  0006-spec-Introduce-etc-leapp-actor_conf.d-directory.patch
-
-%description
-Leapp utility provides the possibility to use the Leapp framework via CLI.
-The utility itself does not define any subcommands but "help". All leapp
-subcommands are expected to be provided by other packages under a specific
-directory. See the man page for more details.
-
-
-##################################################
-# snactor package
-##################################################
-%package -n snactor
-Summary: %{summary}
-Requires: %{leapp_python_name}-%{name} = %{version}-%{release}
-%{?python_disable_dependency_generator}
-
-%description -n snactor
-Leapp's snactor tool - actor development environment utility for creating and
-managing actor projects.
-
-##################################################
-# the library package (the framework itself)
-##################################################
-%package -n %{leapp_python_name}-%{name}
-
-Summary: %{summary}
-%{?python_provide:%python_provide %{leapp_python_name}-%{name}}
-
-%if %{leapp_python} == 2
-# RHEL 7 only
-BuildRequires:  python-devel
-BuildRequires:  python-setuptools
-Conflicts:      python3-%{name}
-%else
-BuildRequires:  python3-devel
-BuildRequires:  python3-setuptools
-Conflicts:      python2-%{name}
-
-%{?python_disable_dependency_generator}
-%define __provides_exclude_from ^.*$
-%endif
-
-Provides: leapp-framework = %{framework_version}
-Requires: leapp-framework-dependencies = %{framework_dependencies}
-
-%description -n %{leapp_python_name}-%{name}
-Python %{leapp_python} leapp framework libraries.
-
-
-##################################################
-# DEPS package for external dependencies
-##################################################
-%package deps
-Summary:    Meta-package with system dependencies of %{name} package
-
-# IMPORTANT: everytime the requirements are changed, increment number by one
-# same for requirements in main package above
-Provides: leapp-framework-dependencies = %{framework_dependencies}
-##################################################
-# Real requirements for the leapp HERE
-##################################################
-%if 0%{?rhel} && 0%{?rhel} == 7
-Requires: python-six
-Requires: python-setuptools
-Requires: python-requests
-Requires: PyYAML
-%else # <> rhel 7
-# for Fedora & RHEL 8+ deliver just python3 stuff
-# NOTE: requirement on python3 refers to the general version of Python
-# for the particular system (3.6 on RHEL 8, 3.9 on RHEL 9, ...)
-# Do not use python(abi) deps, as on RHEL 8 it's provided by platform-python
-# which is not helpful for us
-Requires: python3
-Requires: python3-six
-Requires: python3-setuptools
-Requires: python3-requests
-Requires: python3-PyYAML
-%endif
-Requires: findutils
-##################################################
-# end requirements here
-##################################################
-
-%description deps
-%{summary}
-
-
-##################################################
-# Prep
-##################################################
-%prep
-%setup -n %{name}-%{version}
-
-
-# APPLY REGISTERED PATCHES HERE
-%patch -P 0001 -p1
-%patch -P 0002 -p1
-%patch -P 0003 -p1
-%patch -P 0004 -p1
-%patch -P 0005 -p1
-%patch -P 0006 -p1
-
-
-##################################################
-# Build
-##################################################
-%build
-%{leapp_py_build}
-
-
-##################################################
-# Install
-##################################################
-%install
-
-install -m 0755 -d %{buildroot}%{_mandir}/man1
-install -m 0644 -p man/snactor.1 %{buildroot}%{_mandir}/man1/
-
-# This block of files was originally skipped for fedora. Adding now
-install -m 0755 -d %{buildroot}%{_datadir}/leapp
-install -m 0755 -d %{buildroot}%{_datadir}/leapp/report_schema
-install -m 0644 -p report-schema-v110.json %{buildroot}%{_datadir}/leapp/report_schema/report-schema.json
-install -m 0700 -d %{buildroot}%{_sharedstatedir}/leapp
-install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp
-install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp/actor_conf.d/
-install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp/repos.d
-install -m 0600 -d %{buildroot}%{_sysconfdir}/leapp/answers
-# standard directory should have permission set to 0755, however this directory
-# could contain sensitive data, hence permission for root only
-install -m 0700 -d %{buildroot}%{_sysconfdir}/leapp/answers
-# same for this dir; we need it for the frontend in cockpit
-install -m 0700 -d %{buildroot}%{_localstatedir}/log/leapp
-install -m 0644 etc/leapp/*.conf %{buildroot}%{_sysconfdir}/leapp
-install -m 0644 -p man/leapp.1 %{buildroot}%{_mandir}/man1/
-
-%{leapp_py_install}
-
-
-##################################################
-# leapp files
-##################################################
-
-%files
-%doc README.md
-%license COPYING
-%{_mandir}/man1/leapp.1*
-%config(noreplace) %{_sysconfdir}/leapp/leapp.conf
-%config(noreplace) %{_sysconfdir}/leapp/logger.conf
-%dir %{_sysconfdir}/leapp
-%dir %{_sysconfdir}/leapp/actor_conf.d
-%dir %{_sysconfdir}/leapp/answers
-%dir %{_sysconfdir}/leapp/repos.d
-%{_bindir}/leapp
-%dir %{_sharedstatedir}/leapp
-%dir %{_localstatedir}/log/leapp
-%dir %{_datadir}/leapp/
-%dir %{_datadir}/leapp/report_schema/
-%{_datadir}/leapp/report_schema
-%{leapp_python_sitelib}/leapp/cli
-
-
-##################################################
-# snactor files
-##################################################
-%files -n snactor
-%license COPYING
-%{leapp_python_sitelib}/leapp/snactor
-%{_mandir}/man1/snactor.1*
-%{_bindir}/snactor
-
-
-##################################################
-# python[23]-leapp files
-##################################################
-%files -n %{leapp_python_name}-%{name}
-%license COPYING
-%{leapp_python_sitelib}/*
-# These are delivered in other subpackages
-%exclude %{leapp_python_sitelib}/leapp/cli
-%exclude %{leapp_python_sitelib}/leapp/snactor
-
-
-%files deps
-# no files here
-
-%changelog
-* Mon Nov 18 2024 Petr Stodulka <pstodulk@redhat.com> - 0.18.0-2
-- Bump leapp-framework to 6.0
-- Bump leapp-framework-dependencies to 6
-- Require python3-PyYAML
-- [Technical preview] Introduce configurability for leapp actors
-- Resolves: RHEL-67622
-
-* Fri Aug 16 2024 Toshio Kuratomi <toshio@fedoraproject.org> - 0.18.0-1
-- Rebase to new upstream version 0.18.0.
-- Properly close file descriptors for executed shell commands.
-- Resolves: RHEL-27848
-
-* Wed Jul 24 2024 Toshio Kuratomi <toshio@fedoraproject.org> - 0.17.0-3
-- Fix broken leapp db queries on rerun
-- Port all code to be Python-3.12 compatible.
-- Resolves: RHEL-40363
-
-* Mon May 13 2024 Toshio Kuratomi <toshio@fedoraproject.org> - 0.17.0-2
-- Minor improvement of the summary overview in the console output.
-- Store metadata about the LEAPP plugins inside leapp audit db.
-- Prevent leapp from starting if an instance is already runnning.
-- Resolves: RHEL-27848, RHEL-25407
-
-* Tue Feb 13 2024 Toshio Kuratomi <toshio@fedoraproject.org> - - 0.17.0-1
-- Rebase to upstream version v0.17.0.
-- Resolves: RHEL-21451
-
-* Fri Jan 12 2024 Petr Stodulka <pstodulk@redhat.com> - 0.16.0-3
-- Add external links to the text version of the generated report file
-- Resolves: RHEL-21451
-
-* Wed Aug 23 2023 Petr Stodulka <pstodulk@redhat.com> - 0.16.0-2
-- Bump leapp-framework to 5.0
-- Resolves: #2223312
-
-* Wed Aug 23 2023 Petr Stodulka <pstodulk@redhat.com> - 0.16.0-1
-- Rebase to v0.16.0
-- Bump leapp-framework to 5.0
-- Improve the report overview to include also information about errors
-- Distinguish errors from valid reports in the generated txt report file
-- Resolves: #2223312
-
-* Mon Jul 17 2023 Petr Stodulka <pstodulk@redhat.com> - 0.15.1-2
-- Bump leapp-framework to 4.0
-- Improve the report summary output to make it more visible
-- Fix processing data in remediation instructions with non-ascii characters
-- Fix creation of Dialog for Component without choices
-- Store tracebacks from actors in leapp.db
-- Resolves: #2223312
-
-* Tue Feb 21 2023 Petr Stodulka <pstodulk@redhat.com> - 0.15.1-1
-- Rebase to v0.15.1
-- Change DAC for /var/lib/leapp to 0700 to make it accessible for root only
-- Propagate error messages from leapp actors to the main leapp process
-- Prevent unicode errors when printing error messages
-- Resolves: rhbz#2162710
-
-* Thu Sep 08 2022 Petr Stodulka <pstodulk@redhat.com> - 0.15.0-2
-- Fix the check of missing required answers
-- Resolves: rhbz#2124332
-
-* Wed Aug 24 2022 Petr Stodulka <pstodulk@redhat.com> - 0.15.0-1
-- Rebase to v0.15.0
-- Bump leapp-framework to 3.1
-- Deprecate `reporting.(Tags|Flags)` replaced by `reporting.Groups`
-- Fix crashes when processing invalid FQDNs
-- Fix the error msg when a leapp CLI command does not exist
-- Introduce new report JSON schema v1.2.0 (default: 1.1.0)
-- Resolves: rhbz#2090992, rhbz#2106065
-
-* Mon Mar 14 2022 Petr Stodulka <pstodulk@redhat.com> - 0.14.0-1
-- Rebase to v0.14.0
-- Bump leapp-framework to 2.2
-- Bump leapp-framework-dependencies to 5
-- Add depency on python3 (distribution python)
-- Added possibility to specify the report format version
-- Check the answerfile upon loading and prevent creation of invalid answerfile
-- Dialogs: print the reason field for question in the answerfile
-- Fix the JSON serialization in Dialogs on Python3
-- Introduced new functions in the leapp standard library
-- Updated man page
-- Resolves: rhbz#1997075
-
-* Thu Sep 30 2021 Petr Stodulka <pstodulk@redhat.com> - 0.13.0-10
-- Rebase to v0.13.0
-- Bump the provided leapp-framework capability to 2.0
-- The commands for the leapp tool (e.g. preupgrade, upgrade) are now
-  defined in the leapp-repository component
-- The leapp tool scans the available CLI commands dynamically
-- First build for the IPU 8 -> 9
-- Resolves: #1997075
-
-* Fri Apr 23 2021 Petr Stodulka <pstodulk@redhat.com> - 0.12.1-1
-- Rebase to v0.12.1
-- Added rerun command for experimental purposes to be able to re-run manually
-  the last phase when needed (experimental)
-- Resolves: #1952885
-
-* Thu Feb 04 2021 Dominik Rehak <drehak@redhat.com> - 0.12.0-1
-- Rebase to v0.12.0
-- Bump leapp-framework capability to 1.4
-- Add JSON schema of leapp reports for validation
-- Add a stable report identifier for each generated report
-- Resolves: #1915508
-
-* Wed Oct 21 2020 Dominik Rehak <drehak@redhat.com> - 0.11.1-1
-- Rebase to v0.11.1
-- Fix conversion of deprecation messages to reports
-- Fix various issues regarding suppressing of deprecation
-- Remove pytest residuals in spec file
-- Update documentation and manpages
-- Resolves: #1887913
-
-* Tue Aug 18 2020 Michal Bocek <mbocek@redhat.com> - 0.11.0-1
-- Rebase to v0.11.0
-- Bump leapp-framework capability to 1.3
-- Preserve verbose/debug options during the whole upgrade workflow
-- Print the informative error block to the STDOUT instead of STDERR
-- Add new reporting tags: `PUBLIC_CLOUD` and `RHUI`
-- Add the possibility to skip actor discovery to improve performance of tests when an actor context is injected directly
-- Introduce the `deprecated` and `suppress_deprecation` decorators to support the deprecation process
-- Store dialog answers in the leapp.db
-- Update and improve man pages
-- Raising a missing exception with tests failing under py3
-- Adde the --actor-config option to `snactor run` to specify a workflow configuration model that should be consumed by actors
-- The `call` function has been improved to be working on MacOS
-- Known issue: the `suppress_deprecation` decorator causes a traceback in certain cases
-
-* Thu Jul 30 2020 Michal Bocek <mbocek@redhat.com> - 0.10.0-3
-- A temporary build to run TPS tests against
-- Relates: #1860373
-
-* Mon Apr 20 2020 Michal Bocek <mbocek@redhat.com> - 0.10.0-2
-- Make debug/verbose setting persistent across the upgrade
-- Relates: #1821712
-
-* Thu Apr 16 2020 Petr Stodulka <pstodulk@redhat.com> - 0.10.0-1
-- Rebase to v0.10.0
-- Add the --enablerepo option for Leapp to use an existing custom yum/dnf
-  repository during the upgrade
-- Add the --no-rhsm option for Leapp for use without subscription-manager
-  (#622)
-- Add `leapp answer` to answer Dialog questions in CLI (#592)
-- Add `stdin` and `encoding` parameters in the run function (#583, #595)
-- Add new dependency on python-requests
-- Add the DESKTOP tag for the leapp report (#612)
-- Display a warning when leapp is used in an unsupported (devel/testing) mode
-  (#577)
-- Drop dependency on python-jinja2
-- Error messages are now part of the preupgrade report
-- Fix json export capabilities using serialization (#598)
-- Introduce DialogModel that could be processed by actors to add related
-  information into the report (#589)
-- Introduce Workflow API (#618)
-- Move all leapp and snactor files into related rpms instead of python2-leapp
-  (#591)
-- Print errors on stdout in pretty format (#593)
-- Report inhibitors separately from errors on stdout (#620)
-- Show progress in non-verbose executions (#621)
-- The verbosity options (--verbose | --debug) are available for leapp commands
-  as well
-- Resolves: #1821712
-
-
-* Thu Oct 24 2019 Petr Stodulka <pstodulk@redhat.com> - 0.9.0-1
-- Rebase to v0.9.0
-- Add sanity-check command for snactor
-- Add the /var/log/leapp directory to the leapp RPM
-- Handle string types in compatible way
-- Introduce answerfile generation & usage
-- Introduce report composability, remove renders (#543)
-- Show help message for proper subcommand of leapp
-- Stop adding 'process-end' audit entry (#538)
-- Various fixes in displaying of generated reports
-- Resolves: #1753583
-
-* Wed Jul 24 2019 Petr Stodulka <pstodulk@redhat.com> - 0.8.1-1
-- Rebase to v0.8.1
-  Relates: #1723113
-- Fix issue undefined ReportReference
-
-* Mon Jul 15 2019 Petr Stodulka <pstodulk@redhat.com> - 0.8.0-1
-- Rebase to v0.8.0
-  Relates: #1723113
-- add the preupgrade subcommand to be able check system and generate report for
-  upgrade without run of the upgrade itself
-- add checks of arguments for cmdline parameters
-- log output of commands to logfile (#520)
-- avoid spurious output about missing logger
-- exit non-zero on unhandled exceptions and errors
-- fix actor library loading, so libraries do not have to be imported in
-  lexicographical order
-- log on the ERROR level by default instead of DEBUG
-- create a dynamic configuration phase that allows creation of configuration
-  for repository workflow
-- add JSON report generation
-- stdlib: add option to `run()` to ignore exit code
-
-* Sun Jun 23 2019 Vojtech Sokol <vsokol@redhat.com> - 0.7.0-3
-- Rebuild
-  Resolves: #1723113
-
-* Mon Apr 29 2019 Petr Stodulka <pstodulk@redhat.com> - 0.7.0-2
-- load checkpoints ordered by 'id' instead of timestamp
-  Relates: #1636478
-
-* Wed Apr 17 2019 Vojtech Sokol <vsokol@redhat.com> - 0.7.0-1
-- Rebase to v0.7.0
-  Relates: #1636478
-- add the ability to stop and resume workflow in any phase
-- fix incompatibilities with Python3
-- store logs in one place and support archiving of previous logs
-- fix handling of Unicode in the run function of leapp stdlib
-
-* Mon Apr 08 2019 Vojtech Sokol <vsokol@redhat.com> - 0.6.0-2
-- Fix specfile
-  Relates: #1636478
-
-* Mon Apr 08 2019 Vojtech Sokol <vsokol@redhat.com> - 0.6.0-1
-- Rebase to v0.6.0
-  Relates: #1636478
-- snactor
-  - `repo new` subcommand: display message if directory with same name exists
-  - `discover subcommand`: fix wrong path
-  - `workflow run` subcommand: introduce `--save-output` parameter
-  - fix cryptic message without user repo config
-  - show global repos in repo list
-  - fix trace on topic creation
-- stdlib
-  - make api directly available in stdlib
-  - external program exec function - audit data generation and storage
-- models
-  - introduction of the JSON field type
-- new debug and verbose modes
-- new reporting capabilities
-- change default loglevel to ERROR
-
-* Thu Jan 24 2019 Petr Stodulka <pstodulk@redhat.com> - 0.5.0-1
-- Rebase to v0.5.0
-  Relates: #1636478
-- Models has been refactored to be more comprehensible and reliable
-- Introduced standard library
-- Introduced the actor convenience api for actors and repository libraries
-- Added localization support
-- Extended serialization support
-- Added exception to be able to stop actor execution
-- Packaging: Move system dependencies into the metapackage
-
-* Fri Nov 23 2018 Petr Stodulka <pstodulk@redhat.com> - 0.4.0-1
-- Rebase to v0.4.0
-  Relates: #1636478
-
-* Wed Nov 07 2018 Petr Stodulka <pstodulk@redhat.com> - 0.3.1-1
-- Rebase to v0.3.1
-  Relates: #1636478
-
-* Wed Nov 07 2018 Petr Stodulka <pstodulk@redhat.com> - 0.3-1
-- Initial rpm
-  Resolves: #1636478

gating.yaml

@@ -0,0 +1,7 @@
+--- !Policy
+product_versions:
+  - rhel-9
+decision_context: osci_compose_gate
+rules:
+  - !PassingTestCaseRule {test_case_name: osci.brew-build.tier0.functional}
+

leapp.spec

@@ -0,0 +1,250 @@
+# IMPORTANT: this is for the leapp-framework capability (it's not the real
+# version of the leapp). The capability reflects changes in api and whatever
+# functionality important from the point of repository. In case of
+# incompatible changes, bump the major number and zero minor one. Otherwise
+# bump the minor one.
+# NOTE: we do not use this capability in the RHEL official rpms. But we provide
+# it. In case of upstream, dependencies are set differently, but YUM is not
+# capable enough to deal with them correctly all the time; we continue to use
+# simplified deps in RHEL to ensure that YUM can deal with it.
+%global framework_version 5.0
+
+# IMPORTANT: everytime the requirements are changed, increment number by one
+# - same for Provides in deps subpackage
+%global framework_dependencies 5
+
+# Do not build bindings for python3 for RHEL == 7
+# # Currently Py2 is dead on Fedora and we don't have to support it. As well,
+# # our current packaging is not prepared for Py2 & Py3 packages in the same
+# # time. Instead of that, make Py2 and Py3 exclusive. Possibly rename macros..
+%if 0%{?rhel} == 7
+  %define leapp_python 2
+  %define leapp_python_sitelib %{python2_sitelib}
+  %define leapp_python_name python2
+  %define leapp_py_build %{py2_build}
+  %define leapp_py_install %{py2_install}
+
+%else
+  %define leapp_python 3
+  %define leapp_python_sitelib %{python3_sitelib}
+  %define leapp_python_name python3
+  %define leapp_py_build %{py3_build}
+  %define leapp_py_install %{py3_install}
+  # we have to drop the dependency on python(abi) completely on el8+ because
+  # of IPU (python abi is different between systems)
+  %global __requires_exclude ^python\\(abi\\) = 3\\..+|/usr/libexec/platform-python|/usr/bin/python.*
+%endif
+
+Name:       leapp
+Version:    0.18.0
+Release:    3%{?dist}
+Summary:    OS & Application modernization framework
+
+License:    ASL 2.0
+URL:        https://oamg.github.io/leapp/
+Source0:    https://github.com/oamg/%{name}/archive/v%{version}.tar.gz#/%{name}-%{version}.tar.gz
+
+# NOTE: Our packages must be noarch. Do no drop this in any way.
+BuildArch:  noarch
+
+Requires: %{leapp_python_name}-%{name} = %{version}-%{release}
+%{?python_disable_dependency_generator}
+
+%if 0%{?rhel} == 7
+# The leapp tool doesn't require the leapp-repository anymore. However for the
+# compatibility purposes, we keep it here for RHEL 7 at least for a while.
+# The dependency on leapp is expected to be set by packages providing the
+# final functionality (e.g. conversion of system, in-place upgrade).
+# IOW, people should look for rpms like leapp-convert or leapp-upgrade
+# in future.
+
+# Just ensure the leapp repository will be installed as well. Compatibility
+# should be specified by the leapp-repository itself
+Requires: leapp-repository
+%endif # !fedora
+
+# PATCHES HERE
+# Patch0001: filename.patch
+
+%description
+Leapp utility provides the possibility to use the Leapp framework via CLI.
+The utility itself does not define any subcommands but "help". All leapp
+subcommands are expected to be provided by other packages under a specific
+directory. See the man page for more details.
+
+
+##################################################
+# snactor package
+##################################################
+%package -n snactor
+Summary: %{summary}
+Requires: %{leapp_python_name}-%{name} = %{version}-%{release}
+%{?python_disable_dependency_generator}
+
+%description -n snactor
+Leapp's snactor tool - actor development environment utility for creating and
+managing actor projects.
+
+##################################################
+# the library package (the framework itself)
+##################################################
+%package -n %{leapp_python_name}-%{name}
+
+Summary: %{summary}
+%{?python_provide:%python_provide %{leapp_python_name}-%{name}}
+
+%if %{leapp_python} == 2
+# RHEL 7 only
+BuildRequires:  python-devel
+BuildRequires:  python-setuptools
+Conflicts:      python3-%{name}
+%else
+BuildRequires:  python3-devel
+BuildRequires:  python3-setuptools
+Conflicts:      python2-%{name}
+
+%{?python_disable_dependency_generator}
+%define __provides_exclude_from ^.*$
+%endif
+
+Provides: leapp-framework = %{framework_version}
+Requires: leapp-framework-dependencies = %{framework_dependencies}
+
+%description -n %{leapp_python_name}-%{name}
+Python %{leapp_python} leapp framework libraries.
+
+
+##################################################
+# DEPS package for external dependencies
+##################################################
+%package deps
+Summary:    Meta-package with system dependencies of %{name} package
+
+# IMPORTANT: everytime the requirements are changed, increment number by one
+# same for requirements in main package above
+Provides: leapp-framework-dependencies = %{framework_dependencies}
+##################################################
+# Real requirements for the leapp HERE
+##################################################
+%if 0%{?rhel} && 0%{?rhel} == 7
+Requires: python-six
+Requires: python-setuptools
+Requires: python-requests
+%else # <> rhel 7
+# for Fedora & RHEL 8+ deliver just python3 stuff
+# NOTE: requirement on python3 refers to the general version of Python
+# for the particular system (3.6 on RHEL 8, 3.9 on RHEL 9, ...)
+# Do not use python(abi) deps, as on RHEL 8 it's provided by platform-python
+# which is not helpful for us
+Requires: python3
+Requires: python3-six
+Requires: python3-setuptools
+Requires: python3-requests
+%endif
+Requires: findutils
+##################################################
+# end requirements here
+##################################################
+
+%description deps
+%{summary}
+
+
+##################################################
+# Prep
+##################################################
+%prep
+%setup -n %{name}-%{version}
+
+
+# APPLY REGISTERED PATCHES HERE
+
+
+##################################################
+# Build
+##################################################
+%build
+%{leapp_py_build}
+
+
+##################################################
+# Install
+##################################################
+%install
+
+install -m 0755 -d %{buildroot}%{_mandir}/man1
+install -m 0644 -p man/snactor.1 %{buildroot}%{_mandir}/man1/
+
+# This block of files was originally skipped for fedora. Adding now
+install -m 0755 -d %{buildroot}%{_datadir}/leapp
+install -m 0755 -d %{buildroot}%{_datadir}/leapp/report_schema
+install -m 0644 -p report-schema-v110.json %{buildroot}%{_datadir}/leapp/report_schema/report-schema.json
+install -m 0700 -d %{buildroot}%{_sharedstatedir}/leapp
+install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp
+install -m 0755 -d %{buildroot}%{_sysconfdir}/leapp/repos.d
+install -m 0600 -d %{buildroot}%{_sysconfdir}/leapp/answers
+# standard directory should have permission set to 0755, however this directory
+# could contain sensitive data, hence permission for root only
+install -m 0700 -d %{buildroot}%{_sysconfdir}/leapp/answers
+# same for this dir; we need it for the frontend in cockpit
+install -m 0700 -d %{buildroot}%{_localstatedir}/log/leapp
+install -m 0644 etc/leapp/*.conf %{buildroot}%{_sysconfdir}/leapp
+install -m 0644 -p man/leapp.1 %{buildroot}%{_mandir}/man1/
+
+%{leapp_py_install}
+
+
+##################################################
+# leapp files
+##################################################
+
+%files
+%doc README.md
+%license COPYING
+%{_mandir}/man1/leapp.1*
+%config(noreplace) %{_sysconfdir}/leapp/leapp.conf
+%config(noreplace) %{_sysconfdir}/leapp/logger.conf
+%dir %{_sysconfdir}/leapp
+%dir %{_sysconfdir}/leapp/answers
+%dir %{_sysconfdir}/leapp/repos.d
+%{_bindir}/leapp
+%dir %{_sharedstatedir}/leapp
+%dir %{_localstatedir}/log/leapp
+%dir %{_datadir}/leapp/
+%dir %{_datadir}/leapp/report_schema/
+%{_datadir}/leapp/report_schema
+%{leapp_python_sitelib}/leapp/cli
+
+
+##################################################
+# snactor files
+##################################################
+%files -n snactor
+%license COPYING
+%{leapp_python_sitelib}/leapp/snactor
+%{_mandir}/man1/snactor.1*
+%{_bindir}/snactor
+
+
+##################################################
+# python[23]-leapp files
+##################################################
+%files -n %{leapp_python_name}-%{name}
+%license COPYING
+%{leapp_python_sitelib}/*
+# These are delivered in other subpackages
+%exclude %{leapp_python_sitelib}/leapp/cli
+%exclude %{leapp_python_sitelib}/leapp/snactor
+
+
+%files deps
+# no files here
+
+%changelog
+* Thu Sep 19 2024 Petr Stodulka <pstodulk@redhat.com> - 0.18.0-3
+- Rebuild to apply changes for gating
+- Resolves:  RHEL-57042
+
+* Thu Sep 12 2024 Petr Stodulka <pstodulk@redhat.com> - 0.18.0-2
+- Initial build for el9
+- Resolves:  RHEL-57042

plans/tier0.fmf

@@ -0,0 +1,66 @@
+# These test plans were created manually based on information taken from
+# https://gitlab.cee.redhat.com/oamg/leapp-tests/-/blob/main/config.yaml. The tmt definitions can be simplified, once
+# https://github.com/teemtee/tmt/issues/1770 is implemented.
+
+summary: Internal Tier0 tests
+
+environment:
+    SOURCE_RELEASE: '9.6'
+    TARGET_RELEASE: '10.0'
+
+context:
+    distro: rhel-9.6
+    distro_target: rhel-10.0
+
+adjust:
+    enabled: false
+    when: distro == centos-stream-9
+
+/customrepos_upgrade_happy_path:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/destructive/customrepos/basic_upgrade/upgrade_happy_path
+            ref: main
+
+/oamg3661_two_reboots:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/destructive/customrepos/oamg/oamg3661_two_reboots
+            ref: main
+
+/oamg9299_devtmpfs_in_fstab:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/destructive/customrepos/oamg/oamg9299_devtmpfs_in_fstab
+            ref: main
+
+/rhsm_upgrade_happy_path:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/destructive/rhsm/upgrade_happy_path
+            ref: main
+
+/customrepos_tier0only:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/nondestructive/customrepos/tier0only
+            ref: main
+
+/none_tier0only:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/nondestructive/none/tier0only
+            ref: main
+
+/rhsm_tier0only:
+    plan:
+        import:
+            url: https://gitlab.cee.redhat.com/oamg/leapp-tests
+            name: /plans/nondestructive/rhsm/tier0only
+            ref: main

sources

@@ -0,0 +1 @@
+SHA512 (leapp-0.18.0.tar.gz) = 9539d4fed20f3a5e6772a1365bbd8fdbf6b9246c75d64f937b9048010704d66936e994bd421c466200393bf10b437370bc46aff1684c88c57dbed2695df93a68