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 #3327] Module name is out of date and prevents import from other projects #27806

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

Originally created by @smxlong on GitHub (Mar 24, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3327

Originally assigned to: @pdevine on GitHub.

What is the issue?

Attempting to import parts of the ollama tree (such as the api directory) into an external project fails, because the module name declared in go.mod is still github.com/jmorganca/ollama. This apparently doesn't impact building the project itself, but causes errors when attempting to import packages into other projects.

What did you expect to see?

This should have worked:

go get github.com/ollama/ollama/api

Instead, I get this:

$ go get github.com/ollama/ollama/api
go: github.com/ollama/ollama@v0.1.29 (matching github.com/ollama/ollama/api@upgrade) requires github.com/ollama/ollama@v0.1.29: parsing go.mod:
        module declares its path as: github.com/jmorganca/ollama
                but was required as: github.com/ollama/ollama

Steps to reproduce

Run go get github.com/ollama/ollama/api from another project.

Are there any recent changes that introduced the issue?

No response

OS

Linux

Architecture

amd64

Platform

WSL2

Ollama version

main branch

GPU

No response

GPU info

No response

CPU

No response

Other software

No response

Originally created by @smxlong on GitHub (Mar 24, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3327 Originally assigned to: @pdevine on GitHub. ### What is the issue? Attempting to import parts of the ollama tree (such as the `api` directory) into an external project fails, because the module name declared in `go.mod` is still `github.com/jmorganca/ollama`. This apparently doesn't impact building the project itself, but causes errors when attempting to import packages into other projects. ### What did you expect to see? This should have worked: ``` go get github.com/ollama/ollama/api ``` Instead, I get this: ``` $ go get github.com/ollama/ollama/api go: github.com/ollama/ollama@v0.1.29 (matching github.com/ollama/ollama/api@upgrade) requires github.com/ollama/ollama@v0.1.29: parsing go.mod: module declares its path as: github.com/jmorganca/ollama but was required as: github.com/ollama/ollama ``` ### Steps to reproduce Run `go get github.com/ollama/ollama/api` from another project. ### Are there any recent changes that introduced the issue? _No response_ ### OS Linux ### Architecture amd64 ### Platform WSL2 ### Ollama version main branch ### GPU _No response_ ### GPU info _No response_ ### CPU _No response_ ### Other software _No response_
GiteaMirror added the bug label 2026-04-22 05:24:11 -05:00
GiteaMirror commented 2026-04-22 05:24:13 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Mar 25, 2024):

@smxlong sorry about this. We switched over the repo to ollama/ollama from jmorganca/ollama and didn't update all of the code. I have a fix which I'm testing out and I'll send a PR soon. This will have to wait until 0.1.30 goes out anyway though just so it doesn't mess with the release.

<!-- gh-comment-id:2018781384 --> @pdevine commented on GitHub (Mar 25, 2024): @smxlong sorry about this. We switched over the repo to `ollama/ollama` from `jmorganca/ollama` and didn't update all of the code. I have a fix which I'm testing out and I'll send a PR soon. This will have to wait until `0.1.30` goes out anyway though just so it doesn't mess with the release.
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 bug
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#27806
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?