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
In general this is a limitation of the zip format as it stores extremely limited attributes about the original file (as it was originally only designed for MS-DOS file attributes). That said some zip programs allow storing some POSIX/Unix-style permissions in the optional extended attributes that can be saved in zip archives, however, how to set these and how compatible they are across zip clients is undefined (and so may not be compatible across different zip clients).
I am assuming @ezsh is using infozip. Using infozip one can query these extended attributes via unzip -Z tweego.zip (-Z causes infozip unzip to act like infozip zipinfo). This can be limited to specify files within the archive. As an example (and to keep from spamming lots of data here), executing unzip -Z tweego.zip tweego to examine these extended attributes for only the tweego executable within the released zip archive, I get:
It does not appear as if the released archives are storing such extended attribute information--or at least not in a format that infozip seems to understand.
If I use the infozip tools to unzip the archive, set the executable permission bit on the executable file and rezip the files, effectively recreating the zip archive, and then execute the same command, I now get:
For reference if it matters, I am using infozip tools from/on Ubuntu focal in WSL2 on Windows 10.
If this is a concern for the tweego release process, I recommend switching the POSIX/Unix binary releases to different archive formats (e.g., a compressed tar archive, etc.).
I also noticed this on macOS (12.6) with tweego 2.1.1 (64bit). I don't recall having the problem with previous versions of tweego, but it's been a while since I installed one. I also don't have a general issue with executables unzipping to non-executables; this is the first time I've seen it.
Have to apply
chmod +x tweego
The text was updated successfully, but these errors were encountered: