Arch Linux User Repository

https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission I'd like to remember rule #1 especially after the AUR supply chain attacks...

@tiziodcaio: There is actually 3 "packaging variants" of ollama available for ArchLinux, and anyone can choose which one to use based on the speed and willingness to be possibly broken that they have.

ollama and ollama-* on extra: Official ArchLinux packages, goes through that process after a release happens, could be slower to update. They build particular tags from the git repository in ollama's case, although usually official packages will build from source tarballs.

ollama-bin and ollama-*-bin on AUR: This package, downloads the prebuilt binaries from https://github.com/ollama/ollama/releases (as opposed to ArchLinux building them.) We TRY to update this package pretty quickly after a new release, and occasionally we will need to fix the packaging beyond just putting in new SHAs and versions as well. Ollama itself pushes new releases frequently (weekly or so, IIRC) and this package follows that.

ollama-git and ollama-*-git on AUR: That package uses git to pull the CURRENT SOURCE from GitHub from the 'main' branch (not any particular release, just the HEAD commit) at https://github.com/ollama/ollama and builds it, so it's "on the bleeding edge" if you will. If the 'main' branch is broken, the -git packages will be, also, so people using -git packages need to take that into account.

@tiziodcaio: I created this package primarily to provide the 'vulkan' version of ollama, as it didn't exist in the 'extra' section for a while. Now that it's been published there, I don't really see much point in keeping this package. I only continue maintaining it because it costs me almost nothing...

Has it any difference from the package in extra repo? https://archlinux.org/packages/extra/x86_64/ollama/

I can help in maintaining the latest version if you wish.

I want to say "Please give Dominiquini (and I, although he's fast enough I don't do much) 48 or 72 hours before marking it out-of-date, please." There's only so much time in a day, after all, and I have even less, plus ollama pushes new builds up FREQUENTLY.

==> Validating source_x86_64 files with sha256sums...
    ollama-x86_64-0.32.4.tzst ... FAILED

For CUDA 12, I had to patch the libggml-cuda.so library, otherwise the program couldn't find other libraries in the directory. This should be done after installing the program. Here are the commands:

Installing patchelf

sudo pacman -S patchelf

Patching the library to add $ORIGIN to rpath

sudo patchelf --set-rpath '$ORIGIN' /usr/lib/ollama/libggml-cuda.so

Another option is to add /usr/lib/ollama to ldconfig, but this should be considered harmfull and lead to errors with other sofrware.

This error is in upstream ollama binary libs.

I had to roll back to f450a5df747d to rebuild 0.22.1 in order to get it working on my 1070 ti.

Looks good, and thank you!