Nikola Forró

I can see that the [packaging](https://github.com/pypa/packaging) project supports [version specifiers](https://packaging.pypa.io/en/stable/specifiers.html), so maybe we could add a new configuration key e.g. `version_update_specifier` or `version_update_spec` as an alternative to `version_update_mask`: ```yaml version_update_specifier:...

> * `%{major_verson}_%{minor_version}_%{patch_version}` (=be able to construct version from parts -- not sure if 3 part schema is generic enough) Anitya (release-monitoring.org) uses a regex, in this case `libunibreak_(\d)_(\d)`, and...

Thanks for the report! I thought we already have an issue for this, but I can't find it. The thing is, most of the top-level options are inherited by all...

Most likely yes.

I think we need to prioritize https://github.com/packit/packit-service/issues/2118, since for downstream jobs we need to be able to filter out v1 tags.

And also https://github.com/packit/packit-service/issues/2051, to be able to react only to PRs open against the `v2` branch.

Spec file is in Fedora: https://src.fedoraproject.org/rpms/awscli2/blob/rawhide/f/awscli2.spec Currently there is also a downstream patch: https://src.fedoraproject.org/rpms/awscli2/blob/rawhide/f/ruamel-yaml-0.17.22.patch Here is a basic `packit.yaml` (nothing special there): ```yaml upstream_package_name: awscli downstream_package_name: awscli2 upstream_project_url: https://github.com/aws/aws-cli issue_repository:...

This is no longer blocked, I've updated the proposed Packit config.

Update: I've set up Packit on my fork: https://github.com/nforro/aws-cli/pull/1, however: - There is a flaky test that seems to fail almost every time in Copr (and almost never in Koji)...

Ok, here is another attempt, this time against the `develop` branch, it looks like it could work: https://github.com/nforro/aws-cli/pull/2 What do you think about doing checkouts and merges in the upstream...