Skip to main content

8 posts tagged with "January"

View All Tags

· One min read
Matej Focko

Weeks 3–4 (January 14th – January 27th)​

danger

This is also a breaking release that includes changes from the Packit 1.0.0, we have opened PRs that should help you with migration if you are affected.

For more details please see the following blog post.

  • Added support for detached (open)SUSE style changelogs (specfile#444, contributed by Dan Čermák)

· One min read
Matej Focko

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
František Lachman

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
Nikola Forró

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)