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
{{ message }}
This repository has been archived by the owner on May 14, 2021. It is now read-only.
If you have a Zipped file with internal symlinks, for example
./
├ A (~> ./B)
├ B
└ ...
Where A is a symlink to the file B, when decompressing the files, and attempting to restore the original permissions, if A is processed (extracted) before B, then it will throw an ENOENT error
================================================================================
Error executing action `unpack` on resource 'poise_archive[/tmp/file-name.zip]'
================================================================================
Errno::ENOENT
-------------
No such file or directory @ chmod_internal - /path/to/be/unzipped/to/A
This can potentially be remedied by running the File#chmod method after extracting all file instead of after each file, as it's implemented now.
Not sure if this issue also affects other archive providers, since we only experienced this with Zip archives.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If you have a Zipped file with internal symlinks, for example
Where
A
is a symlink to the fileB
, when decompressing the files, and attempting to restore the original permissions, ifA
is processed (extracted) beforeB
, then it will throw an ENOENT errorThis can potentially be remedied by running the
File#chmod
method after extracting all file instead of after each file, as it's implemented now.Not sure if this issue also affects other archive providers, since we only experienced this with Zip archives.
The text was updated successfully, but these errors were encountered: