github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #9481] [MERGED] fix(install.sh): update lib/ollama directory permissions #44229

New Issue
Closed
opened 2026-04-24 23:45:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-24 23:45:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/9481
Author: @mxyng
Created: 3/3/2025
Status: ✅ Merged
Merged: 3/3/2025
Merged by: @mxyng

Base: main ← Head: mxyng/load-backend

📝 Commits (1)

  • a015625 fix: own lib/ollama directory

📊 Changes

7 files changed (+137 additions, -147 deletions)

View changed files

➖ llama/patches/0015-try-catch-backend-load.patch (+0 -69)
📝 llama/patches/0015-use-std-filesystem-path-instead-of-wstring.patch (+94 -40)
📝 llama/patches/0016-remove-amx.patch (+0 -0)
📝 llama/patches/0017-fix-clip-compiler-error.patch (+0 -0)
📝 llama/patches/0018-add-phi4-support.patch (+0 -0)
📝 ml/backend/ggml/ggml/src/ggml-backend-reg.cpp (+41 -37)
📝 scripts/install.sh (+2 -1)

📄 Description

this change explicitly creates the lib/ollama directory with the correct permissions. since the ollama release tarball does not contain the lib/ollama entry, it's implicitly created when extracting the archive. this can result in a base directory without other read/execute and prevent ollama from accessing the libraries store inside.

expand backend loading error handling to catch more problems and log them instead of panicking

resolves #9466
resolves #9330

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/9481 **Author:** [@mxyng](https://github.com/mxyng) **Created:** 3/3/2025 **Status:** ✅ Merged **Merged:** 3/3/2025 **Merged by:** [@mxyng](https://github.com/mxyng) **Base:** `main` ← **Head:** `mxyng/load-backend` --- ### 📝 Commits (1) - [`a015625`](https://github.com/ollama/ollama/commit/a0156257f32d2ae0712cdc629b06514a2a61a313) fix: own lib/ollama directory ### 📊 Changes **7 files changed** (+137 additions, -147 deletions) <details> <summary>View changed files</summary> ➖ `llama/patches/0015-try-catch-backend-load.patch` (+0 -69) 📝 `llama/patches/0015-use-std-filesystem-path-instead-of-wstring.patch` (+94 -40) 📝 `llama/patches/0016-remove-amx.patch` (+0 -0) 📝 `llama/patches/0017-fix-clip-compiler-error.patch` (+0 -0) 📝 `llama/patches/0018-add-phi4-support.patch` (+0 -0) 📝 `ml/backend/ggml/ggml/src/ggml-backend-reg.cpp` (+41 -37) 📝 `scripts/install.sh` (+2 -1) </details> ### 📄 Description this change explicitly creates the `lib/ollama` directory with the correct permissions. since the ollama release tarball does not contain the `lib/ollama` entry, it's implicitly created when extracting the archive. this can result in a base directory without other read/execute and prevent ollama from accessing the libraries store inside. expand backend loading error handling to catch more problems and log them instead of panicking resolves #9466 resolves #9330 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-24 23:45:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#44229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?