On Wed, Jan 06, 2010 at 06:20:51AM -0700, Eric Blake wrote:
> According to Jim Meyering on 1/5/2010 2:07 PM:
> >> --- Comment #5 from Ondrej Vasik 2010-01-05 14:29:13
> >> EDT ---
> >> Ah - even the latest gnulib doesn't handle this new recent change - so
> >> touch
> >> from coreutils might be
Eric Blake wrote:
...
> So, how about this NEWS item?
>
> diff --git a/NEWS b/NEWS
...
> + cp -p, install -p, mv, and touch -c could trigger a spurious error
> + message when using new glibc coupled with an old kernel.
> + [bug introduced in coreutils-6.12].
Thanks for the research and summary.
According to Jim Meyering on 1/5/2010 2:07 PM:
>> --- Comment #5 from Ondrej Vasik 2010-01-05 14:29:13
>> EDT ---
>> Ah - even the latest gnulib doesn't handle this new recent change - so touch
>> from coreutils might be affected as well as mentioned in debian bugzilla from
>> comment #4. Theref
Eric Blake wrote:
...
> s/futimes/futimens/ (ChangeLog and commit message)
Thanks!
>> +++ b/lib/utimens.c
>> @@ -264,19 +264,20 @@ fdutimens (char const *file, int fd, struct timespec
>> const timespec[2])
>> }
>> # endif /* HAVE_UTIMENSAT */
>> # if HAVE_FUTIMENS
>> - {
>> -
According to Jim Meyering on 1/5/2010 2:07 PM:
>> https://bugzilla.redhat.com/show_bug.cgi?id=552320
> Thanks for the heads up. Good timing.
> That does indeed look like a bug, and Aurelien Jarno's fix seems right.
I can confirm that the fix is correct.
>
> I expect to push the following to gnu
bugzi...@redhat.com wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=552320
>
> Ondrej Vasik changed:
>
>What|Removed |Added
>
> CC||j..
