-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unzip not found on PATH on Ubuntu 22.04 when using 'deno compile', although unzip has been installed and can be executed on command line #23988
Comments
Outputs of echo $PATH
echo $SHELL
which unzip |
Maybe the temp directory Deno created got deleted before unzip was called. @flo-jan Do you have any background service that deletes The error message can be improved. |
Deno runs as Snap application. There is a |
I would be interested if someone is able to reproduce this issue |
I tried another way of installing deno, not with Snap but with this command: I still encounter the same problem when trying to run deno compile but with a different error message:
I checked the /tmp folder. I can create folders and files in it and they are not removed automatically. I also tried another laptop with Ubuntu 22.04 installed and on that laptop deno compile works without problems. |
Since an Ubuntu clean install of the same version does not trigger any issues, it looks more like an issue with the OS and/or the user env setup. |
Deno.makeTempFile() works correctlty however, on the same computer |
it creates files in the /tmp folder |
It would be helpful if would know the exact location in deno's source code where this
happens. Could someone point me to that? |
I seem to be having a similar issue, |
deno 1.43.6 (release, x86_64-unknown-linux-gnu)
Ubuntu 22.04
When I give the command 'deno compile' it gives the error: "unzip was not found in your PATH, please install unzip".
But unzip is installed. I can use unzip commands in the same terminal as where I try to execute the deno compile command.
Could this be a bug?
The text was updated successfully, but these errors were encountered: