You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i ran into this when installing a ringo package with symbolic links in it - ringo creates the symlinks as empty files.
i found out that this kind of info is stored in extra fields per ZipEntry, which - afaict - we can't access with java.util.zip. github's zip files do contain that extra info: the symbolic links are created correctly if i unzip with "UnZip 6.00 of 20 April 2009, by Debian."
But the returned byte array seems to have a different format than the one specified in the apache ant documentation linked above. The first two bytes are 85 and 84 (0x5554) instead of 117 and 110 (0x756e).
I’m closing this issue because it has been inactive for a long time. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on for so long, then it seems no one has the time to implement this / there is no interest in it.
Please reopen if you still encounter this issue with the current master version or there is a need to address this issue.
i ran into this when installing a ringo package with symbolic links in it - ringo creates the symlinks as empty files.
i found out that this kind of info is stored in extra fields per ZipEntry, which - afaict - we can't access with java.util.zip. github's zip files do contain that extra info: the symbolic links are created correctly if i unzip with "UnZip 6.00 of 20 April 2009, by Debian."
apache ant's zip tools also seems to handle them http://www.jajakarta.org/ant/ant-1.6.1/docs/ja/manual/api/org/apache/tools/zip/AsiExtraField.html
i guess this issue is more of a caveat than fixable.
The text was updated successfully, but these errors were encountered: