On 04/27/2018 05:22 AM, Christian Weisgerber wrote:
I don't know at which level this should be fixed
Simplest, I think, would be for tar to stop using the progname module
and to assume only getprogname instead. The progname module is
problematic for reasons discussed in this thread:
https:/
Sergey Poznyakoff:
> > For GNU tar 1.30, the regression tests remfiles01.at and remfiles02.at
> > (175 176) fail.
>
> Pretty strange, but both tests work for me (the release would have been
> impossible if they woudn't). Any specific conditions in order to
> reproduce that?
It fails for me on Op
Hi Christian,
> For GNU tar 1.30, the regression tests remfiles01.at and remfiles02.at
> (175 176) fail. The immediate problem is that tar's child process
> fails to identify itself as "tar (child)" in the error message.
Pretty strange, but both tests work for me (the release would have been
imp
For GNU tar 1.30, the regression tests remfiles01.at and remfiles02.at
(175 176) fail. The immediate problem is that tar's child process
fails to identify itself as "tar (child)" in the error message.
The underlying cause is a change in gnulib, specifically this commit:
https://git.savannah.gnu.o
