Skip to main content

· One min read

Week 5 (January 30th – February 5th)

  • packit validate-config now checks whether the Upstream Release Monitoring for the package is correctly configured if pull_from_upstream job is present in the configuration. (packit#2226)
  • There is a new global configuration option parse_time_macros that allows to configure macros to be explicitly defined or undefined at spec file parse time. (packit#2222)
  • We have added additional retries and improvements for task processing. (packit-service#2326)

· One min read

Week 4 (January 23rd – January 29th)

  • pull-from-upstream and propose-downstream commands now have the --sync-acls option that enables syncing the ACLs between dits-git repo and fork. The default behaviour was, however, changed to not sync the ACLs. (packit#2214)
  • Packit now properly handles exceptions when syncing ACLs during release syncing. (packit#2213)
  • allowed_pr_authors and allowed_committers now allow specifying groups and also aliases all_admins and all_committers (corresponding to the access to the repository). (packit-service#2320)
  • ogr now supports 2 new methods for Pagure: one for getting users with specified access rights and one for getting members of a group. (ogr#834)

· One min read

Week 3 (January 16th – January 22nd)

  • Packit now properly handles exceptions when syncing ACLs during release syncing. (packit#2213)
  • We have fixed a bug in handling chroot-specific configuration once the chroots themselves are updated. (packit#2194)
  • We have increased the number of retries of Fedora release syncing for situations where the tarball is uploaded some time after the release happens. (packit-service#2307)
  • There is a new API endpoint /bodhi-updates for getting information about Bodhi updates submitted by Packit. (packit-service#2310)
  • For /packit test command, you can now also use -i and --id aliases for --identifier option. (packit-service#2309)

· One min read

Week 1 (January 2nd – January 8th)

  • We have changed the behaviour of loading Packit configuration for koji_build and bodhi_update jobs. For both of them, the behaviour is the same as for pull_from_upstream - the configuration is taken from the default branch of the dist-git repository (usually rawhide) and other branches are ignored. (packit-service#2295)

· One min read

End of the year in Packit

  • We have hit some issues with the firewall rules on the new cluster hosting our production. We are waiting for the required fix that is done outside of our team which should be deployed around January 11th. We will keep you informed about the current status. At the moment we are aware of the issues related to the:
    • pull-from-upstream jobs that have sources hosted at, and
    • jobs running on the in general
  • We have also fixed an issue that caused some Cockpit releases to fail, others might've been affected too, though there are no reports.

· One min read

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)

· One min read

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: (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!

· One min read

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)