February 7, 2020
Week 6 #
Packit learned how to look for RPM spec files on its own, so specifying
specfile_path in the configuration is not mandatory anymore. Packit will
recursively search the tree and use the first spec file found.
Week 7 #
The default configuration generated by Packit has test jobs enabled from now on. This should simplify configuring Packit in new repositories.
Fixed a bug which was causing SRPM-build failures in Packit Service for projects which had their spec files stored in a subdirectory.
When enabling Packit Service for new GitHub repositories, instead of checking if the requester is a Fedora packager, we’ll check if they signed the Fedora Project Contributor Agreement.
While proposing an update to Fedora, Packit Service will report a failure now when there are no releases found in the upstream GitHub repository.
Week 8 #
Postgresql database was introduced in production environment to improve performance and enable implementation of new features, e.g. storing logs to reduce amount of messages sent directly to pull request (#406), (#420).
Cleanup in configuration files was performed, so no longer needed values were removed from .packit.yaml (#709).
User experience was improved by adding new
--upstrem-ref option to
copr-build command in command-line interface (#718)
and making error reporting more robust by adding new fedpkg clones related error message (#714).
Following bugs were fixed:
- bug in copr-build command fixed (#713)
- get_local_package_config() duplicate entries in ‘directories’ bug fixed (#715)
Week 9 #
- Dist-git patches are now applied in source-git repos with
-p1to resolve an issue when they are generated with git and patch program fails to apply them (#730).
- Fedora 32 was added to ‘fedora-all’ and ‘fedora-development’ aliases (#731).
- We have put more links to our documentation (README, deprecation warning in packit) so that people can easily correct their configuration files (#726).