Do not use obsolete %patchN

[jplesnik]

Description

%patchN is obsolete; %patch -P N should be used instead for applying patches.

If a patch is being added to a spec file for the first time, the new %patch -P N format should be used by default. If the spec file already contains existing patches, use whichever format is currently established in that file.

Benefit

Prevents introducing obsolete code into spec files and suppresses warnings such as:

rhpkg defined %patchN compatibility shims to parse the spec file. %patchN is obsolete, use %patch -P N instead.

Importance

No response

Workaround

• There is an existing workaround that can be used until this feature is implemented.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)

[opohorel]

thanks for the report! do you have any example, where this happened?

[jplesnik]

The commit created by Ymir:
https://gitlab.com/redhat/rhel/rpms/perl-Net-DNS/-/merge_requests/1/diffs?commit_id=c7871c6a2498654dfa62de5cf527d8a2c37e59bc