If I use "zip -y" to archive a symbolic link in Linux (CentOS 4.3), the date stamp on the symbolic link in the archive appears to be correct (per unzip -v), but if I then extract the symbolic link, the date stamp on the symbolic link is incorrect (it gets the current date and time rather than the one from the archive). This bug appears to date back to zip 2.32 and unzip 5.51 at least.
Logged In: NO
I've confirmed this behavior on Solaris.
This appears to be a more or less conscious design decision (or
omission) in UnZip. Zip (3.0f is what I tried) seems to store the
date-time properly in the archive, but when UnZip creates a symlink on
UNIX (or VMS), it makes no effort to set any of its attributes
accordingly.
Similarly, "unzip -X" restores GID+UID data for plain files and
directories, but not for symlinks.
This behavior continues through the latest internal development
versions of UnZip. I assume that we'll be discussing this among the
developers.
Logged In: YES
user_id=681780
Originator: YES
It would be nice if this could be fixed in unzip 6.0. I wouldn't think it would involve more than a few lines of code. Unzip should make every effort to restore the files exactly as they were.
Logged In: NO
I've confirmed this behavior on Solaris.
This appears to be a more or less conscious design decision (or
omission) in UnZip. Zip (3.0f is what I tried) seems to store the
date-time properly in the archive, but when UnZip creates a symlink on
UNIX (or VMS), it makes no effort to set any of its attributes
accordingly.
Similarly, "unzip -X" restores GID+UID data for plain files and
directories, but not for symlinks.
This behavior continues through the latest internal development
versions of UnZip. I assume that we'll be discussing this among the
developers.
Logged In: YES
user_id=681780
Originator: YES
This is not fixed as of the latest internal release (unz60d05t.zip).