Review whether the ollama-cuda pin can be removed safely #101
Labels
No labels
host:electra
host:fleet
host:lyra
host:vega
host:vega
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:declarative-purity-cleanup
project:external-review
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
service:auto-update
service:mem0
service:sillytavern
No milestone
No assignees
1 participant
Notifications
Due date
Dependencies
No dependencies set
Reference
nimmo/nixos-config#101
Loading…
Reference in a new issue
No description provided.
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?
Context
The repository currently pins
ollama-cudavia the dedicatednixpkgs-ollama-cudaflake input because the mainnixpkgsupdate toe318e6adc497b5e8a5ac433c6c6ed21ecdab9029broke CUDA-backed Ollama builds.Observed failure during Lyra/Electra-related builds:
Could not find nvcc executable in path specified by environment variable CUDAToolkit_ROOT=...CUDA Toolkit not foundTo keep NVIDIA-backed Ollama buildable, only
pkgs.ollama-cudais overlaid from the pinned nixpkgs revision421eebfd0ec7bccd4abe826ce62d7e6e83129493.Review task
pkgs.ollama-cudafrom the mainnixpkgsinput on Lyra.pkgs.ollama-cuda.nixpkgs-ollama-cudapin and overlay.lib/auto-update-policy.nix,flake.nix,flake.lock, and README to remove references to the pin.Exit criteria
pkgs.ollama-cudafrom the mainnixpkgsinput.nixpkgs-ollama-cudainput and overlay are removed cleanly.