On 2023-07-21 01:54, Pavel Raiskup wrote:
I think the problems happen because we do do `autoreconf -v` for the GNU tar package in Fedora (we have several patches applied on top of the upstream tarball). Some distributions (not Fedora) do this by default per their policies, so I would eventually view this as a (low-priority?) tarball issue.
If you patch the tarball's files, then it's your responsibility to make sure the resulting files work. To do that, I suggest adding to your patchlist a patch that adds the missing files. This should work around the problem. You can omit this patch once tar 1.36 comes out.
