[CI:BUILD] packit: handle builds for RC releases

[lsm5]

The version_no_tilde rpm macro correctly handles both vX.Y.Z and vX.Y.Z-rcN git tags. Using this macro instead of version will soon allow Packit to handle RC builds correctly.

Accompanying change in Packit to land soon:
packit/packit#2149

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lsm5]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lsm5]

@cevich why does secret scan fail in https://github.com/lsm5/podman/actions/runs/6849732287/job/18622509799 but pass in the task list on the PR?

[lsm5]

@containers/podman-maintainers PTAL. This should be safe to merge.

[Luap99]

LGTM

[rhatdan]

/lgtm

[cevich]

@lsm5 job shows:

12:08PM FTL unable to load gitleaks config, err: open /default/.gitleaks.toml: no such file or directory

That should not be possible, since the /default volume mount always comes from main. I see the job also died trying to send an alert-mail, which is also no good 😕

I'll add investigation of these into a "fix gitleaks" jira card I already have open.

[cevich]

Oh I figured it out! The key is very subtle in the job title:

[CI:BUILD] packit: handle builds for RC releases #7

That job ran against your personal fork of podman. You must have a main branch that's out of sync with the upstream main. This is completely broken though, that job should never run on forks.