Week 50 (December 12th – December 18th)​

• We have fixed a bug preventing a release from being synced downstream if the changelog to be set is empty. (packit#2183)
• We have fixed a bug of not running Koji builds for Packit dist-git PRs with multiple commits if the last commit of the PR did not contain a spec file change. (packit-service#2275)

Week 49 (December 5th – December 11th)​

• We have introduced new configuration options test_command.default_labels and test_command.default_identifier that are used by default when running /packit test comment command without any arguments (instead of specifying them via --labels/--identifier). (packit-service#2270)

• We have fixed a bug that GithubRelease.url returned an API URL. (ogr#824)

We, the packit team, are happy to invite you to our upcoming workshop about pulling upstream releases to Fedora using Packit.

When: Wed, Jan 10, 9:30 AM - Wed, Jan 10, 12:30 PM (GMT+1)

Where: Online!

Who should attend: Anyone who maintains a package in Fedora or EPEL and would like to automate syncing the upstream releases for it. The automation is most suitable for simple packages with straightforward update processes (e.g. without patches, or need to build in side-tags). It works without access to the upstream repository.

No package? It’s not an issue. The workshop can help you understand the Fedora release process and the services involved. During the workshop, you can help someone else automate their package or ask someone around if you can help with the maintenance (that’s usually very welcome!). You can also bring an orphaned package back to life!

Can’t make it this time? You can also follow our documentation and ask for help in case of any issue: #packit:fedora.im (Matrix).

If you want to join us please fill this form or contact us on Matrix, and we will send you further details!

Looking forward to seeing you!

Week 48 (November 28th – December 4th)​

• Packit now links the information related to upstream events in PRs opened when syncing a release. (packit#2173)

• When accessing tags or macro definitions by name, specfile library now takes validity into account when looking for the best match. For example if there are two instances of Version tag, one in the true and one in the false branch of a condition, Specfile.version will always access the one that is in the true branch. This also applies to Packit when syncing a release and updating value of Version tag. (specfile#328)

Week 47 (November 21st – November 27th)​

• Packit now correctly sets the specfile content (e.g. changelog entry) even if it syncs the specfile from upstream for the first time. (packit#2170)

Week 46 (November 14th – November 20th)​

• Packit now supports pre-release version in propose_downstream and pull_from_upstream. A spec file update might be required, see the documentation for more details. (packit#2149)
  • In relation to that, specfile library has a new method, Specfile.update_version(), that allows updating spec file version even if it is a pre-release. (specfile#317)
• Packit can now check, using the new update_version_mask configuration option, that the proposed version of new release and the current version of the dist-git branch are compatible and sync the dist-git branch only in that case. (packit#2156)
• Packit is now able to get the version from spec file even if the Version tag is not present in the specfile directly, but e.g. imported from another file. (packit#2157)
• PACKIT_COPR_PROJECT env var that is exposed to Testing Farm now includes the Copr project of the additional build specified in comment, if present. (packit-service#2253)

Week 45 (November 7th – November 13th)​

• Now Packit allows ~^+ (special characters) in a tag (used for building the version string). (packit#2154)
• Downstream Koji builds are now shown in a separate table in /jobs/downstream-koji-builds on dashboard and are also accessible via /api/koji-builds API endpoint. (packit-service#2244, packit-service#2249, dashboard#354)

Week 44 (October 31st – November 6th)​

• Dist tag (%{?dist}) is now enforced when updating release during SRPM creation. (packit#2106)

Week 43 (October 24th – October 30th)​

• Packit no longer downloads sources excluded using spec file conditions. (packit#2132)

Week 41 (October 10th – October 16th)​

• (breaking) Packit no longer accepts packit.json or .packit.json as a configuration file name. (packit#2123)
• We have implemented several improvements in syncing the release downstream:
  • Packit now updates ACL of its own dist-git forks to allow users and groups with commit rights to the original dist-git repo to push directly to a fork. (packit#2112)
  • Packit now also properly cleans up the branch after syncing the release which should prevent unwanted files (e.g. tarballs) being committed to dist-git. (packit#2125)
  • We have adjusted the way how Packit includes the resolved bugzillas in the commit messages created when syncing the release downstream so that the resolved bugzillas are included in changelog when using %autochangelog. (packit#2126)
• Packit now reacts to retriggering comments for downstream jobs by commenting on the same issue/PR and providing information about the jobs. (packit-service#2222)
• We have fixed an issue that prevented you from running the jobs on the GitLab.com due to failing resolution of the upstream/downstream relationship for the cloned project. (packit#2120)
• Packit now triggers the build for the /packit test comment command if the last build was not successful. (packit-service#2228)

And special thanks to @SpyTec for multiple wonderful dashboard improvements!