On 02/08/2021 21.23, George N. White III wrote:
On Sun, 1 Aug 2021 at 23:31, Eyal Lebedinsky <fed...@eyal.emu.id.au 
<mailto:fed...@eyal.emu.id.au>> wrote:


    On 02/08/2021 08.53, Cameron Simpson wrote:
     > On 01Aug2021 08:40, George N. White III <gnw...@gmail.com 
<mailto:gnw...@gmail.com>> wrote:
     >> gzip can store the file date in the archive, and (per
     >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950519 
<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 <c...@cskk.id.au <mailto:c...@cskk.id.au>>

    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?


Dragons hang out at edge cases.  How did /usr/share/licenses/mdevctl/COPYING 
get that timestamp?    I have (Fedora 33):

~ % ls -l /usr/share/licenses/mdevctl/COPYING --full-time
-rw-r--r--. 1 root root 26530 2021-06-10 13:49:09.000000000 -0300 
/usr/share/licenses/mdevctl/COPYING

As I show in another reply in this thread, there are 4 files like this, and my 
other (also f34) machine
also has the same four with the same timestamp. So it is not a local corruption.

--
George N. White III

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to