You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search for projects in the service database, which rely on Packit recursively searching for the specfile.
These are projects in which:
The package config (for exmple packit.yaml) doesn't define specfile_path, AND
The package config doesn't define downstream_package_name, AND
There is no <repo_name>.spec file in the root of the repository, AND
The jobs configured a build to happen (not all the jobs are test jobs with skip_build), AND
There is no specfile generated matching <repo_name>.spec when running packit srpm (it might not be necessary to script this check).
For projects not matching the above: recursively search for a specfile and open a PR proposing to update packit.yaml with the specfile_path config option set to the path found. Before opening the PR, make sure packit srpm works with this change. Explain that the reason for this change is that recursively searching for the specfile when building is going to be dropped.
The text was updated successfully, but these errors were encountered:
Search for projects in the service database, which rely on Packit recursively searching for the specfile.
These are projects in which:
packit.yaml
) doesn't definespecfile_path
, ANDdownstream_package_name
, AND<repo_name>.spec
file in the root of the repository, ANDskip_build
), AND<repo_name>.spec
when runningpackit srpm
(it might not be necessary to script this check).For projects not matching the above: recursively search for a specfile and open a PR proposing to update
packit.yaml
with thespecfile_path
config option set to the path found. Before opening the PR, make surepackit srpm
works with this change. Explain that the reason for this change is that recursively searching for the specfile when building is going to be dropped.The text was updated successfully, but these errors were encountered: