Re: posix atime/ctime changes despite mtime being set

[Paul Eggert]

On 2023-07-25 05:13, Sergey Poznyakoff wrote:
> > as you can see on this output the only
> > differences are between timestamps e.g.:
> >
> >                                                                       
> >   7  -rw-r--r--···0········0······· 7  -rw-r--r--···0········0·······
> >      ·0·····7339·2012-02-16·20:24:4    ·0·····7339·2012-02-16·20:24:4
> >      2.000000·./usr/src/debug/acpid    2.515701·./usr/src/debug/acpid
> >      /2.0.34-r0/acpi_ids.c             /2.0.34-r0/acpi_ids.c
>
> Then I'd suppose that first archive (the one shown on the left size) was
> created in ustar, gnu or similar format - the one that stores timestamps
> with a seconds precision.  In contrast, second archive (the one shown on
> the right side) is in POSIX.1-2001 format, which stores timestamps with
> a subsecond precision.
>
> Regards,
> Sergey

The recipe I suggested yesterday should generate tarballs with 
timestamps that are all integer multiples of seconds. Either the recipe 
wasn't followed, or it's buggy.

It's similar to the recipe I've been using to generate tzdb releases 
since 2022a.