When configuring Copr chroot (target in Packit terminology) specific configuration, make sure to specify additional_modules as a string: module names separated with a comma, example: “httpd:2.4,python:4”. (packit#1826)
We have fixed a bug which caused long Copr build end reporting time on a few occurrences. (packit-service#1838)
Users can now re-trigger bodhi_update and koji_build jobs by /packit create-update
and /packit koji-update comments in an issue opened by Packit in the configured issue_repository if anything
went wrong during these jobs. (packit-service#1796)
All Copr projects created by Packit now default to enable_net=False: our documentation stated this, but it
wasn’t the case. This is now corrected. (packit#1825)
You can now specify update_release: false in the configuration to tell Packit not to change the Version and
Release in the spec file. It works the same as --no-update-release (renamed from now deprecated --no-bump) in
the CLI. (packit#1827)
Packit now supports setting module_hotfixes for Copr projects.
Packit now also allows passing in free-form parameters to Testing Farm in order to support all of its
options immediately once they are added. The parameters can be passed through the tf_extra_params config option.
The free-form dictionary must follow the structure of Testing Farm POST requests. See our documentation
and examples for more information. (packit-service#1853)
Fixed a bug in section parsing that caused sections to be ignored when there were macro definitions spread
across the spec file and not cumulated at the top. (specfile#191)
Also fixed the infinite loop that occurred when section options were followed by whitespace.