On 3/31/23 18:49, Ron Olson wrote:
One thing to note is that the new format doesn’t work with EPEL
releases; I had to revert to the %patchN style for them.
The following bit from
https://rpm-software-management.github.io/rpm/manual/spec.html was
already quoted in this thread, but:
On 31. 03. 23 13:58, Petr Menšík wrote:
Is there also documented and preferred way to apply just single patch when
%autosetup -N -S git is used? I mean, if I want to have all patches applied
git-like way, I know I can use -m or -M parameters to %autopatch. But
%autopatch -m 1 -M 1 does not
One thing to note is that the new format doesn’t work with EPEL
releases; I had to revert to the %patchN style for them.
On 29 Mar 2023, at 3:53, Florian Festi wrote:
On 3/29/23 10:31, Michael J Gruber wrote:
Has `%patchN` been deprecated in favour of `%patch N`?
Yes, see %patch section on
I would suggest creating at least self-contained change on Fedora to
describe what has changed and why. Those syntax might be a little weird,
but were used quite often. It would be nice to have some place to read
about it. Because frankly it just started warning when used, but I do
not
Yes, I've figured this out meanwhile. I still see it as the proven packager's
job to give some information before or at least while pushing a change that was
neither announced, nor called for by a change proposal.
As you point out correctly, the new syntax just landed in rpm 4.18 (F37 up), so
On 3/29/23 18:58, Todd Zullinger wrote:
Florian Festi wrote:
On 3/29/23 10:31, Michael J Gruber wrote:
Has `%patchN` been deprecated in favour of `%patch N`?
Yes, see %patch section on
https://rpm-software-management.github.io/rpm/manual/spec.html
Quoting that:
%patch is used to
Florian Festi wrote:
> On 3/29/23 10:31, Michael J Gruber wrote:
>> Has `%patchN` been deprecated in favour of `%patch N`?
>
> Yes, see %patch section on
> https://rpm-software-management.github.io/rpm/manual/spec.html
Quoting that:
%patch is used to apply patches on top of the just
On 29. 03. 23 10:31, Michael J Gruber wrote:
Has `%patchN` been deprecated in favour of `%patch N`?
Yes. However...
I got a push by a proven packager to one of the packages which I maintain, commit subject
and changelog entry "Fix deprecated patch rpm macro". It contains no
explanation and
On 3/29/23 10:31, Michael J Gruber wrote:
> Has `%patchN` been deprecated in favour of `%patch N`?
Yes, see %patch section on
https://rpm-software-management.github.io/rpm/manual/spec.html
> I got a push by a proven packager to one of the packages which I maintain,
> commit subject and
Has `%patchN` been deprecated in favour of `%patch N`?
I got a push by a proven packager to one of the packages which I maintain,
commit subject and changelog entry "Fix deprecated patch rpm macro". It
contains no explanation and no reference whatsoever. I didn't find any heads up
notice, nor
10 matches
Mail list logo
