-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
[Bug]: Can't shim ollama.exe: file doesn't exist #6213
Comments
Assuming this is not just a local problem on my computer -- it would be nice if the excavator could do some basic validation before checking in random updates that could easily break packages if the archive layout changed. Of course it would also be nice if this did not require additional VM resources. |
|
Ollama is now packaging ARM builds alongside x64. https://github.com/ollama/ollama/releases/tag/v0.3.12 If I try to run |
Uniextract2 handles the files with correct arch after extraction. Have to replace the bundled innounp.exe with innounp unicode though. I manually created 0.3.12 folder this way and it works. |
I encountered the same issue. But I install 2 version of innounp.
|
I have the same issue, and I'm using scoop list inno
Installed apps matching 'inno':
Name Version Source Updated Info
---- ------- ------ ------- ----
innounp-unicode 1.72 versions 2024-07-30 20:25:12 |
Install |
Prerequisites
Package Name
ollama
Expected/Current Behaviour
Extraction of the setup file ends with multiple numbered binaries rather than the normal expected binaries, then fails during shim step because they names are different than expected.
In
~/scoop/apps/ollama/0.3.12
I have these filesdiffering from the expected
ollama app.exe
andollama.exe
.I ran the installer in a sandbox and found that the installed file names are not numbered like this after a regular install.
Steps to Reproduce
Possible Solution
Could be a change in how the inno installer is configured, or some issue with the inno unpacker.
Scoop and Buckets Version
Scoop Config
PowerShell Version
Additional Softwares
The text was updated successfully, but these errors were encountered: