Learn more about these different git repos.
Other Git URLs
Currently a hub policy can match on the package name, but cannot check for the package version or release. (Or epoch, I guess.) It would be nice if it were possible to apply matches to those.
The current use case in Fedora is preventing packages from using versions containing a tilde while those are forbidden by packaging policy.
PR: https://pagure.io/koji/pull-request/1135
The data available to a policy varies. Which policy/policies are you thinking of for this request?
Metadata Update from @mikem: - Issue tagged with: feature
Metadata Update from @mikem: - Issue set to the milestone: 1.18
The intention is to use this match in "tag" policy.
Asked on PR #1135, but also asking here:
Is glob matching sufficient here? Will folks need a version compare? (e.g. greater than, less than)
When I started to think about possible real world policies, my mind immediately jumped to version comparisons. Seems like it could be the most likely case.
Or is there any other sort of version/release test I'm not thinking of?
Metadata Update from @mikem: - Custom field Size adjusted to None
To be fair, the reason which prompted me to file this originally has been made moot over the intervening months. It's possible that a similar situation could soon arise, and for that I guess a glob would work. But note that what we wanted to match against (and I guess might want to match against in future) are special characters like ~ or ^.
~
^
New PR: https://pagure.io/koji/pull-request/1513
Commit f49409e fixes this issue
Commit de16162 fixes this issue
Login to comment on this ticket.