Weekly Status

November 2022

November 7, 2022

Week 44 (November 1st – November 7th) # Fixed an issue due to which the repository was never searched for a specfile if specfile_path was not specified, and specfile_path was always set to <repo_name>.spec. (packit#1758) Packit is now able to generate automatic Bodhi update notes including a changelog diff since the latest stable build of a package. (packit#1747) Description of Bodhi updates now contains a changelog diff. (packit-service#1713) Week 45 (November 8th – November 14th) # You can re-trigger a Bodhi update via dist-git PR comment /packit create-update. ...

October 2022

October 10, 2022

Week 40 (October 4th – October 10th) # Packit now correctly selects a Testing Farm compose when it’s specified correctly in the configuration without an architecture suffix. (packit-service#1689) We have fixed an issue that prevented Packit to work correctly on merge requests on GitLab instances. (packit-service#1683) Packit Service will now replace invalid characters for the Copr projects using the default naming scheme. (packit-service#1684) When we report to set Packit allowed forge projects in the Copr projects, the link for the group projects is now correct. ...

September 2022

September 5, 2022

Week 35 (August 30th – September 5th) # SRPMs for Copr builds are built in Copr by default for Packit GitHub app installations since September 6, 2022. For older installations, you can set the srpm_build_deps config option to use Copr as a builder. Let us know if you hit any issue with the new implementation. We are going to slowly decommission the old implementation and are happy to help with the transition. ...

August 2022

August 1, 2022

Week 30 (July 26th–August 1st) # Packit has switched to python-specfile library for handling spec files. This may cause some issues to pop up. (packit#1588) Packit CLI can now build RPMs in mock. For more information see https://packit.dev/docs/cli/build/mock (packit#1662) When using Packit before being allowed, Packit newly links an approval issue where the self-approval can be performed. (packit-service#1596) A downstream koji-build can now be re-triggered by adding a comment containing /packit koji-build into a dist-git pull request with target branch corresponding to the branch the build should be acted upon. ...

July 2022

July 11, 2022

Weeks 26–27 (June 27th–July 11th) # We adjusted the way we check the author of the PR for PRs related to dist-git commits that trigger Koji build jobs. This should fix the race condition causing not creating Koji builds in some cases. (packit-service#1573) Results from Testing Farm are now correctly reported when multiple jobs with different identifier are defined. (packit-service#1565) On a Bodhi authentication error, Packit will retry the task multiple times in ten-minute intervals to be able to fix the issue in the meantime. ...

June 2022

June 6, 2022

Week 22 (May 31st - June 6th) # Packit shows basic information about allowlisting in the status description when your namespace is not allowed. (packit-service#1533) Week 23 (June 7th - June 13th) # The creation of Bodhi updates should not time out anymore, because we no longer get the latest build of a package via Bodhi. (packit#1612) We have fixed a regression where string values for the targets and dist_git_branches configuration keys were not accepted. ...

May 2022

May 2, 2022

Week 17 (April 26th - May 2th) # We have fixed an issue affecting Pipelines view on Dashboard. Currently you should be able to see pipelines again; we are also working on fixing empty rows for propose-downstream jobs. (packit-service#1461) Packit now shows the specific info when it does not have permissions to create a Bodhi update of your package. When you configure issue_repository in your Packit config file, Packit will create an issue in that project and link the dist-git page where you can give Packit FAS user the correct permissions. ...

April 2022

April 4, 2022

Week 13 (March 29th - April 4th) # We have implemented get_contributors function in ogr that can be used for getting contributors to the project on GitHub (set of logins) and GitLab (set of authors). (ogr#692) When multiple propose downstream attempts for the same PR fail, the error messages are sent to to the same issue (as comments), instead of creating multiple new issues. (packit#1427) Downstream synchronization of the Packit configuration file (aka packit. ...

March 2022

March 7, 2022

Week 9 (March 1st - March 7th) # When a specfile is being generated, and both specfile_path and downstream_package_name are not set, Packit now correctly resolves this situation and sets specfile_path to the name of the upstream repo suffixed with ".spec". (packit#1499) A new command packit source-git status has been introduced for checking the synchronization of a source-git and a dist-git repository based on the used git trailers. The command outputs a range of commits which need to be synchronized from dist-git to source-git or the other way around. ...

February 2022

February 8, 2022

Week 5 (January 31th - February 7th) # A new option --no-require-autosetup for source-git init command has been introduced. Please note that source-git repositories not using %autosetup may not be properly initialized. (packit#1470) Packit-service now supports re-triggering against failed task using comment on pull request /packit rebuild-failed and similarly for testing farm: /packit retest-failed. (packit-service#1303) Week 6 (February 8th - February 14th) # Packit now correctly handles colons in git trailer values in source-git commits. ...