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

[PR #7055] [CLOSED] Fixing generate failure due to global gpgsign setting #12295

New Issue
Closed
opened 2026-04-12 23:54:35 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 23:54:35 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/7055
Author: @wikki01
Created: 10/1/2024
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (1)

  • 640e264 Fixing generate failure due to global gpgsign setting

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 llm/generate/gen_common.sh (+1 -1)

📄 Description

Hi all, first time commit here so please let me know if I'm missing anything.

Found a small issue in the generate script for llama.cpp where the script patches with a placeholder user. Since I have commit.gpgsign enabled globally on my system, this was causing the following error during go generate ./....

$ go generate ./...
<snip>
+ git submodule init
+ git submodule update --force ../llama.cpp
Submodule path '../llama.cpp': checked out '8962422b1c6f9b8b15f5aeaea42600bcc2d44177'
+ apply_patches
+ for patch in ../patches/*.patch
+ git -c user.name=nobody -c 'user.email=<>' -C ../llama.cpp am ../patches/0000-cmakelist.patch
Applying: patch cmakelist
error: gpg failed to sign the data:
gpg: skipped "nobody <>": No secret key
[GNUPG:] INV_SGNR 9 nobody <>
[GNUPG:] FAILURE sign 17
gpg: signing failed: No secret key

fatal: failed to write commit object
llm/generate/generate_linux.go:3: running "bash": exit status 128

Since this happens in a submodule, setting commit.gpgsign to false for the top-level git repository does not have any effect.

A workaround in the meantime is to disable global gpg signing temporarily, I.E.

git config --global commit.gpgsign false
go generate ./...
git config --global commit.gpgsign true

Cheers!

🔄 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/7055 **Author:** [@wikki01](https://github.com/wikki01) **Created:** 10/1/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`640e264`](https://github.com/ollama/ollama/commit/640e2644f2b2d1233e92c340d1c373123e5b2d73) Fixing generate failure due to global gpgsign setting ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `llm/generate/gen_common.sh` (+1 -1) </details> ### 📄 Description Hi all, first time commit here so please let me know if I'm missing anything. Found a small issue in the generate script for `llama.cpp` where the script patches with a placeholder user. Since I have `commit.gpgsign` enabled globally on my system, this was causing the following error during `go generate ./...`. ``` $ go generate ./... <snip> + git submodule init + git submodule update --force ../llama.cpp Submodule path '../llama.cpp': checked out '8962422b1c6f9b8b15f5aeaea42600bcc2d44177' + apply_patches + for patch in ../patches/*.patch + git -c user.name=nobody -c 'user.email=<>' -C ../llama.cpp am ../patches/0000-cmakelist.patch Applying: patch cmakelist error: gpg failed to sign the data: gpg: skipped "nobody <>": No secret key [GNUPG:] INV_SGNR 9 nobody <> [GNUPG:] FAILURE sign 17 gpg: signing failed: No secret key fatal: failed to write commit object llm/generate/generate_linux.go:3: running "bash": exit status 128 ``` Since this happens in a submodule, setting `commit.gpgsign` to `false` for the top-level git repository does not have any effect. A workaround in the meantime is to disable global gpg signing temporarily, I.E. ``` git config --global commit.gpgsign false go generate ./... git config --global commit.gpgsign true ``` Cheers! --- <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-12 23:54:35 -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#12295
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?