Local `git clone` fails with `Fetched in submodule path 'llama.cpp', but it did not contain f6ebc35103f77a0e063b86175d5ecdc14d979cf2. Direct fetching of that commit failed.`

[shubham0204]

I am trying to clone the project locally:

git clone --recurse-submodules https://github.com/jegly/OfflineLLM

Cloning into 'OfflineLLM'...
remote: Enumerating objects: 459, done.
remote: Counting objects: 100% (69/69), done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 459 (delta 46), reused 18 (delta 18), pack-reused 390 (from 1)
Receiving objects: 100% (459/459), 1.18 MiB | 5.84 MiB/s, done.
Resolving deltas: 100% (200/200), done.
Submodule 'llama.cpp' (https://github.com/ggerganov/llama.cpp.git) registered for path 'llama.cpp'
Cloning into '/Users/shubhampanchal/Documents/GitHub/OfflineLLM/llama.cpp'...
remote: Enumerating objects: 89905, done.        
remote: Counting objects: 100% (119/119), done.        
remote: Compressing objects: 100% (104/104), done.        
remote: Total 89905 (delta 76), reused 15 (delta 15), pack-reused 89786 (from 3)        
Receiving objects: 100% (89905/89905), 373.87 MiB | 17.32 MiB/s, done.
Resolving deltas: 100% (63886/63886), done.
fatal: remote error: upload-pack: not our ref f6ebc35103f77a0e063b86175d5ecdc14d979cf2
fatal: Fetched in submodule path 'llama.cpp', but it did not contain f6ebc35103f77a0e063b86175d5ecdc14d979cf2. Direct fetching of that commit failed.

The OfflineLLM/llama.cpp directory is still empty with no contents. Following this answer, running,

git submodule update --force --recursive --init --remote

Submodule path 'llama.cpp': checked out '0adede866ddb2e31992b3792eaea31d18ed89acf'

populates the llama.cpp directory with its source code.

Also, in the GitHub view of the repository, clicking on llama.cpp @ <commit-ref> returns a 404:

[jegly]

Thanks for reporting — the llama.cpp submodule is pointing to a commit that was removed upstream. Working on a fix, will push an update shortly.

the new llama handles gemma4 prompt template better, my manual patch is messy

In the meantime your workaround works:

git submodule update --force --recursive --init --remote

[jegly]

Issue has been resolved. Thank you