Paul Eggert wrote on 2019-07-06:
> The string length determination can easily be
> avoided, so I installed the attached which does that.
This patch produces GCC warnings about the use of memcpy().
And mine as well, about the use of strlen().
This patch fixes it:
2019-07-19 Bruno Haible
Hi Bernhard,
> + parse-datetime: avoid "%pure-parser" deprecation warning from Bison 3.4
I've pushed your change.
However, I think it would be good for "make" to behave reasonably when bison
is not found or too old.
Here's a proposed patch (untested so far):
2019-07-19 Bruno Haible
Hi Max,
> $ docker run -it --rm -v $(pwd):/mnt debian:latest tar xvf /mnt/test.tar -C
> /mnt
>
> The last step fails with:
>
> tar: gnulib-bug-symlinks/2: Cannot utime: No such file or directory
>
> The commit that caused this error to occur is
> http://git.savannah.gnu.org/cgit/gnulib.git/comm
Thanks for reporting the problem. This appears to be due to a bug in the macOS
implementation of utimensat; see:
https://github.com/rfjakob/gocryptfs/issues/229
I don't use macOS so it'd be helpful if you could check a possible workaround
(attached). If this patch doesn't work for you, please
* lib/parse-datetime.y: Use "%define api.pure" rather than obsolescent
"%pure-parser". The former is available since Bison 2.3b (2008, [1]),
while the latter is marked as obsolete since version 3.4 (May 2019, [2]):
./lib/parse-datetime.y:568.1-12: warning: deprecated directive, \
use '%defi
HI all,
when using bind mounts and trying to extract a tar archive containing
symlinks to it the extraction fails with "Cannot utime: No such file or
directory". This only appears to happen on macOS (I'm using 10.14.5 and
Docker Desktop 2.0.0.3).
Here are the steps to reproduce this:
$ rm -rf /t
