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

[GH-ISSUE #2777] Request: change the default sha256 hash file seperator for blobs to - (minus) instead of : #1674

New Issue
Closed
opened 2026-04-12 11:38:48 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 11:38:48 -05:00
Owner
Copy Link

Originally created by @LumiWasTaken on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2777

Heya,
I have a setup where I'd like to use two systems, one testing on Windows and one active on Linux use the same path for model and manifest to save storage.
The issue I have is: Linux deployment creates blob files with the name sha256:SHATHATHASBEENGENERATED and on Windows sha256-SHATHATHASBEENGENERATED this makes their filenames incompatible with each other and troublesome on Windows since any file with a : inside it is considered "non-existent"

Desired resolution:
A Patch where it'll be backwards-compatible with files that have : but the new default to be - so it will even work when the storage is on a NTFS or exFAT file system.

Thank you!

Originally created by @LumiWasTaken on GitHub (Feb 27, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2777 Heya, I have a setup where I'd like to use two systems, one testing on Windows and one active on Linux use the same path for model and manifest to save storage. The issue I have is: Linux deployment creates blob files with the name `sha256:SHATHATHASBEENGENERATED` and on Windows `sha256-SHATHATHASBEENGENERATED` this makes their filenames incompatible with each other and troublesome on Windows since any file with a : inside it is considered "non-existent" Desired resolution: A Patch where it'll be backwards-compatible with files that have `:` but the new default to be `-` so it will even work when the storage is on a NTFS or exFAT file system. Thank you!
GiteaMirror commented 2026-04-12 11:38:49 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 13, 2024):

Let's track this separator cleanup via #2032

<!-- gh-comment-id:1994895442 --> @dhiltgen commented on GitHub (Mar 13, 2024): Let's track this separator cleanup via #2032
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
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#1674
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?