On 02/08/2021 08.53, Cameron Simpson wrote:
On 01Aug2021 08:40, George N. White III <gnwiii@xxxxxxxxx> wrote:
gzip can store the file date in the archive, and (per
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950519)
supports dates from 1970-01-01 00:00:01 UTC through 2106-02-07 06:28:15
UTC. As the Debian
bug report notes, gzip may be hitting a limit in the kernel or a library.
Likely gzip has a fixed size binary field for the timestamp, which some
timestamp value from afio's data is exceeding.
Can you use gzip's -n option?
-n, -‐no‐name This option stops the filename and timestamp from
being stored in the output file.
That might mangle dates on restore, depending on how afio does that.
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
Took me a while but in the end I tracked down some of the files.
$ ls -l /usr/share/licenses/mdevctl/COPYING --full-time
-rw-r--r-- 1 root root 26530 1970-01-01 10:00:00.000000000 +1000 /usr/share/licenses/mdevctl/COPYING
And the proof
$ gzip -c /usr/share/licenses/mdevctl/COPYING >gzip-test.1.gz
gzip: /usr/share/licenses/mdevctl/COPYING: warning: file timestamp out of range for gzip format
So I guess that some recent gzip or lib has an issue here. '>' vs '>=' maybe?
--
Eyal Lebedinsky (fedora@xxxxxxxxxxxxxx)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
