Oh, I see, I've searched for `%_default_patch_fuzz` but missed
`%{_default_patch_fuzz}` :1st_place_medal:
Thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1405.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1405#event-3897983752___
Rpm-maint mailing list
Current implementation of `%autosetup` applies patches with the default fuzz
factor of the patch binary, which is 2.
I have looked for a way to set it to 0 and discovered that there exists a
`%_default_patch_fuzz` macro, whose value is 0, but it's not taken into account
outside `patchX`
Closed #1404.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1404#event-3897185281___
Rpm-maint mailing list
Sorry but no: a bitfield does not scale for classifying individual file
formats, and that's not what the virtual file attributes are for.
A `file` magic string is attached to most files (RPMTAG_FILECLASS extension)
which can be used for further identification, but it's not terribly reliable as
We've been doing this since RPM 4.14 already, see
66a6082634687e45b321a5ade9887420d5830162.
Either your version of RPM is too old, or the distribution is setting a fuzz of
2 by default.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
