Add ollama to eget packages

[kenorb]

Summary by Sourcery

New Features:

• Add Ollama to the supported eget package list for local large language model execution.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d15d48-ab52-4058-b90a-cbbac6ca20ac

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Add Ollama as a supported eget-managed package, including download arguments and example configuration entry.

File-Level Changes

Change	Details	Files
Introduce eget configuration for installing the Ollama package with architecture-specific assets and ML/ROCm filters.	Add an 'ollama' entry to the Ansible eget task mapping with architecture-dependent asset selection between amd64 and arm64. Configure Ollama download to use .tar.zst assets and exclude mlx and rocm variants via asset filters. Reference the ollama/ollama repository as the source for the package.	.ansible/playbooks/tasks/eget.yml
Document Ollama as an available eget package in the example variables configuration.	Add 'ollama' to the eget_packages list in the example Ansible variables file. Document Ollama with a short description and upstream repo hint for reviewers/users.	.ansible/variables-example.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

⛔ Workflow Failures Detected

The following job errors and annotations were found:

• Check / check / Pre-commit at .ansible/variables-example.yml:176: Line too long (125 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/zed.yml:72: Use failed_when and specify error conditions instead of using ignore_errors.
• Check / check / Pre-commit at .ansible/playbooks/tasks/zed.yml:65: Use failed_when and specify error conditions instead of using ignore_errors.
• Check / check / Pre-commit at .ansible/playbooks/tasks/zed.yml:57: Use failed_when and specify error conditions instead of using ignore_errors.
• Check / check / Pre-commit at .ansible/playbooks/tasks/zed.yml:23: Line too long (143 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:121: Line too long (122 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:116: Line too long (122 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:111: Line too long (131 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:95: Line too long (327 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:88: Line too long (139 > 120 characters)
• Check / check / Pre-commit at .ansible/variables-example.yml:176: 176:121 [line-length] line too long (125 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:121: 121:121 [line-length] line too long (122 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:116: 116:121 [line-length] line too long (122 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:111: 111:121 [line-length] line too long (131 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:95: 95:121 [line-length] line too long (327 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/eget.yml:88: 88:121 [line-length] line too long (139 > 120 characters)
• Check / check / Pre-commit at .ansible/playbooks/tasks/zed.yml:23: 23:121 [line-length] line too long (143 > 120 characters)
• Check / check / Link Checker at .github:163: Process completed with exit code 2.
• Check / check / Link Checker at .github:162: Summary report available at: https://github.com/kenorb/dotfiles/actions/runs/32164716285#summary-95801500328

🛠️ Run Links

• Check