Skip to main content

14 posts tagged with "2023"

View All Tags

· One min read

Week 38 (September 19th – September 25th)

  • As part of the effort of implementing release syncing for CentOS Stream, Packit now supports the pkg_tool option in the config (at the top-level or with specific packages when using the monorepo syntax). This option can be used for switching between fedpkg or centpkg. (packit#2085)
  • When updating the Version tag during propose_downstream or pull_from_upstream, Packit now tries to update referenced macros (if any) rather than overwriting the references. (packit#2087)

· One min read

Week 37 (September 12th – September 18th)

  • If you have concerns about Packit uploading new archives to lookaside cache before creating a pull request, you can newly set upload_sources to False to disable this. (packit#2086)
  • We have introduced a new configuration option notifications.failure_comment.message that enables notifying users on failure via a comment using the configured message. (packit-service#2182)

· One min read

Week 36 (September 5th – September 11th)

  • Packit now supports commit-message action that can be used to override the default commit message produced by Packit during propose-downstream or pull-from-upstream. Please pay attention to our documentation with regards to the usage of this action. (packit#2070)
  • Packit CLI now supports testing the pull-from-upstream workflow. Use the packit pull-from-upstream command from the packit RPM package. (packit#2063)
  • Packit now passes initiator context for tmt to the Testing Farm. You can use this option to run or skip certain tests when they're run by Packit. (packit-service#2176)
  • Testing Farm started additionally exposing regexes on top of the exact compose names in the /composes/ endpoints, and we now support this as well when checking the validity of compose. (packit-service#2168)
  • We have disabled the jitter for retrying Bodhi update tasks to prevent race conditions causing not created updates. (packit-service#2170)
  • We have fixed a bug in get_fork method for Pagure about checking the usernames for a match when going through existing forks. (ogr#800)

· One min read

Week 35 (August 29th – September 4th)

  • Now Packit exposes PACKIT_PACKAGE_NAME, PACKIT_UPSTREAM_PACKAGE_NAME and PACKIT_DOWNSTREAM_PACKAGE_NAME env variables to all the actions. (packit#2061)
  • Packit now sets PACKIT_UPSTREAM_REPO and PACKIT_DOWNSTREAM_REPO environment variables for release syncing actions. The variables represent paths where the respective git repositories are cloned (packit-service#2166)
  • We have fixed a bug causing issues with displaying some Project views on our dashboard. (packit-service#2165)

· One min read

Week 34 (August 22nd – August 28th)

  • We have fixed a bug in packit source-git init caused by the changed behaviour in the newer version of rpmbuild. (packit#2048)
  • We have fixed an issue in our API endpoint that could cause DoS until manual intervention from our team. (packit-service#2164)
  • We have fixed a bug causing broken retriggering of Github checks. (packit-service#2161)
  • SRPM build commit statuses, for monorepos projects, are now being correctly updated. (packit-service#2157)
  • We have fixed the bug resulting in incorrect reporting for tests when retriggering a build of a different target that was not configured for tests. (packit-service#2144)
  • We have fixed an issue that caused retriggers of Testing Farm to fail, if you specified any labels in the comment and had one or more test job definitions without any labels specified. (packit-service#2156)
  • Macro definitions and tags gained a new valid attribute. A macro definition/tag is considered valid if it doesn't appear in a false branch of any condition appearing in the spec file. (specfile#276)

· One min read

Week 32 (August 8th – August 14th)

  • Two new configuration options for filtering when getting latest upstream release tag were introduced: upstream_tag_include and upstream_tag_exclude. They should contain a Python regex that can be used as an argument in re.match. (packit#2030, packit-service#2138)
  • Retriggering of pull-from-upstream via a comment will now use the correct configuration file from the default dist-git branch. (packit-service#2140)
  • The pull-from-upstream job can now be used with upstream repos that are not hosted on a supported git forge. (packit-service#2137)

· One min read

Week 27 (July 4th – July 10th)

  • Packit now correctly reloads upstream specfile after running pre-sync action. (packit#2006)

Week 28 (July 11th – July 17th)

  • Packit now includes instructions on how to checkout the dist-git PR locally when syncing the release. (packit-service#2116)
  • We have fixed a bug in processing options of %prep macros in our specfile library. For instance, when a quoted string appeared inside an expression expansion, it could lead to improper parsing, rendering the spec file invalid after accessing the options. (specfile#253)
  • has a new format! As the content has expanded a lot in the recent year, we decided to switch to using Docosaurus: now all the documentation is in one place and this format also enables additional features for our blog posts. (

Weeks 29–30 (July 18th – July 31st)

  • With plenty of team members on vacation, we didn't manage to implement any significant new features during these two weeks.

· 2 min read

Week 22 (May 30th – June 5th)

  • Packit will now filter the pull requests based on the target branch if the branch is specified in the particular job configuration. (packit-service#2074)
  • Packit now supports manual_trigger in the configuration that allows you to make jobs run only when explicitly triggered by a comment. (packit-service#2069)

Week 23 (June 6th – June 12th)

  • Our dashboard now shows projects in a table instead of the cards. (dashboard#267)

  • /packit test command has two new options:

    With --identifier option, Testing Farm will trigger only jobs with that identifier. (packit-service#2079)

    Also, it is now possible to specify labels for a job and trigger tests based on labels using a --labels option of the /packit test command. (packit#1988, packit-service#2088)

  • If the vm_image_build job doesn't have Copr project/owner configured, Copr project used for the latest Copr build of the pull request will be now used. (packit-service#2080)

  • Fixed filters in files_to_sync not being applied properly. (packit#1977)

  • The issue that could've caused inconsistencies when tests from a PR were supposed to be merged during the test runs on the Testing Farm has been fixed. (packit-service#2090)

Week 24 (June 13th – June 19th)

Week 25 (June 21st – June 27th)

  • If you are interested about the manual triggering deployed two weeks ago, David Kornel and Jakub Stejskal published a blog post about this on
  • Copr builds configured as a monorepo job will now be built in one Copr project together. The bug with overwriting the statuses for monorepo jobs has been fixed as well. (packit-service#2097)

Week 26 (June 27th – July 3rd)

  • The bug which prevented errors on Testing Farm request submission from being correctly propagated to the user was fixed. (packit-service#2103)
  • pull_from_upstream jobs can now be retriggered with a comment /packit pull-from-upstream in a dist-git pull request. (packit-service#2087)

· 2 min read

Week 18 (May 4th - May 9th)

We have experienced issues with automatic Bodhi updates that we are investigating. In case you miss a Bodhi update, you can retrigger the job via /packit create-update comment in a dist-git pull request. Besides that, during this short week (another Czech Republic public holiday) we didn't manage to implement any significant new features.

Week 19 (May 9th – May 15th)

  • Packit now doesn't react to its own comments on Pagure and GitLab (on GitHub, this was already implemented). (packit-service#2048)

Week 20 (May 16th – May 22nd)

  • We have implemented a denylisting mechanism allowing us to denylist namespaces/projects to prevent misuse of our service. (packit-service#2046)
  • Packit will now additionally require for each test job requiring build a build job definition to be present in the Packit configuration file. (packit-service#2012)
  • Packit now checks whether the configured architecture for the test target is supported by Testing Farm and in case it's not supported, Packit doesn't submit these test requests. (packit-service#2053)

Week 21 (May 23rd – May 29th)

  • Unsuccessful Image Builder requests now provide error details so you can fix the Image configuration. (packit#1981)
  • Copr projects created by Packit will not follow the Fedora branching from now. This decision has been made to lower the load on Copr from the temporary Copr projects created, mainly, for the PR builds. If you are releasing your packages to the Copr, please use the new setting follow_fedora_branching. Already existing projects are not affected by this change and it is also not enforced with the custom Copr repositories. (packit#1970)
  • Additional artifact(s) passed as artifacts in the tf_extra_params dictionary will be now combined with the artifact passed by Packit instead of rewriting it. (packit-service#2056)
  • Specfile library now handles multiple %changelog sections. (specfile#230)