in reply to Re^7: Archive::Zip Modify Date Oddity
in thread Archive::Zip Modify Date Oddity
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^9: Archive::Zip Modify Date Oddity
by pmqs (Friar) on Jan 09, 2017 at 16:02 UTC | |
Sure. Starting with a file where the seconds field of the modification time is an odd number.
Now add that file into a zip archive.
unzip in a different directory
And stat the uncompressed file
| [reply] [d/l] [select] |
by hippo (Archbishop) on Jan 11, 2017 at 10:00 UTC | |
(++ for the sample). Interestingly, I see the other reported behaviour where the mtime is rounded down to even seconds:
Versions are:
And this from "unzip -v":
I'm wondering if maybe it's something in the unzip. Is there a simple way to query the entries in the zipfile to see what its contents are to the resolution of seconds? (I never use zip/unzip so this is all beyond my realm) | [reply] [d/l] [select] |
by pmqs (Friar) on Jan 11, 2017 at 11:44 UTC | |
I'm running exactly the same version of unzip & it works fine. To get more details on the zip file, try running
See my first reply dated today for what you need to look for in the output. Also - IO:Compress comes with a script called zipdetails that dumps lots of details on the fip file. If you happen to have available that try running this. The thing to look for is the "Extended Timestamp" entry
| [reply] [d/l] [select] |
by hippo (Archbishop) on Jan 11, 2017 at 12:18 UTC | |
by pmqs (Friar) on Jan 11, 2017 at 15:19 UTC | |
| |
by Anonymous Monk on Jan 13, 2017 at 20:08 UTC | |
I think it's a bug in the unzip utility. Slackware has (prematurely?) enabled the -DIZ_HAVE_UXUIDGID option when compiling the package and this causes the breakage. The option does not show up on "unzip -v" either. In unzip60 sources, process.c:2909 That results in dos time fields being used instead of unix. I have no idea if there's a bugreport or a fix available somewhere. Just my 10 min debug. HtH. | [reply] [d/l] [select] |