pmatilai created an issue (rpm-software-management/rpm#3643)
rpm >= 4.18 uses an external rpmuncompress to handle source decompression and
unpacking during build. It was split out of the internal %setup pseudo-macro to
allow direct use in specs, but this causes an issue that we didn't consider at
the time: rpmuncompress relies on macros to do its business, and since it runs
as a new executable, it doesn't inherit the macro context from rpmbuild. So, if
you override eg `%__tar` from rpmbuild command line to an alternative path,
rpmuncompress will still use the system default. Similarly, if a platform macro
were to speficy some alternate locations for tools, rpmuncompress would not see
them because it only knows how to load the default macro set.
Originally reported on rpm-maint by Jean Delvare:
https://lists.rpm.org/pipermail/rpm-maint/2025-March/031464.html
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3643
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
