Thanks for your interest in Packit Service! In order to start using the service you need to be whitelisted, which is an action to be done by us. Once we put you on the whitelist, we’ll get in touch with you. We are now on-boarding Fedora contributors (with a Fedora Account System account).
Since packit service builds your PRs in Fedora COPR build service, by using Packit-as-a-service, your software needs to comply with COPR rules. If any of these points are violated, we’ll remove the builds and may put you on a blacklist so you won’t be able to use the service again.
If you encounter a problem while using Packit-as-a-service, please open an upstream issue. In case of any other questions, feel free to contact us: email@example.com.
If you do not want to have the RPM spec file in your upstream repository, you can download it in actions section.
Add actions section to your packit.yaml configuration file and
download the spec file in a hook
Packit service has a limited set of commands available so please use
The configuration file with downloading the RPM spec file now looks like this:
specfile_path: packit.spec synced_files: - packit.spec - .packit.yaml upstream_project_name: packitos downstream_package_name: packit actions: post-upstream-clone: "wget https://src.fedoraproject.org/rpms/packit/raw/master/f/packit.spec"
The solution is, again, actions and hooks. Just render the spec after the upstream repo is cloned:
specfile_path: my-project.spec upstream_project_name: my-project-src downstream_package_name: my-project actions: post-upstream-clone: "make generate-spec"
Where the “generate-spec” make target could look like this:
generate-spec: sed -e 's/@@VERSION@@/$(VERSION)/g' my-project.spec.template >my-project.spec
As a practical example, cockpit-podman project is using this functionality.