Laura Barcziová

Logs for the most recent event of this type (specfile 0.9.0 release): ``` [2022-10-25 17:11:41,685: DEBUG/MainProcess] About to create dist-git pull request from '0.9.0-epel9-update' to 'epel9'. [2022-10-25 17:11:47,822: ERROR/MainProcess] There...

We have discussed via chat that the builds can still be retriggered via dist-git PR comment or via CLI locally as @LecrisUT mentions. Can this issue be closed or do...

> This is unexpected behaviour What part do you consider the unexpected behaviour? (We have the behaviour of the koji builds explained [in the docs](https://packit.dev/docs/fedora-releases-guide/#koji-build-job))

> Otherwise, just to confirm that pushing an empty commit still triggers the build if allowed_commiters is configured?? No, as per the documentation, there needs to be a spec file...

Hi @ljavorsk ! Sorry, totally missed the comment. We haven't planned this issue yet, but I think we should think about the `koji_build` behaviour improvements in general (somehow related is...

Hi again, thanks for the report! I think this might be related to packit/packit#1924 and maybe the behaviour you are proposing should be the default, without requiring additional configuration flag/variable.

hi! have you already tried using [update_release](https://packit.dev/docs/configuration#update_release) configuration option? And could you provide please an example of the version Packit provides and the one you would like to have with...

@mulkieran thanks for the explanation! Keeping this in the backlog for now, if more people would be interested in this.

hi @hroncok ! Thank you for bringing up this issue. Regarding the decision to create a dedicated comment for each syncing, our intention was to maintain transparency, considering that a...

> Think about how to deal with old bugzilla(s), we missed a release so probably something will not be closed? This is related a little bit to #2155, one of...