nix: update flake.lock

[ggerganov]

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'flake-parts':
    'github:hercules-ci/flake-parts/34fed993f1674c8d06d58b37ce1e0fe5eebcb9f5' (2023-12-01)
  → 'github:hercules-ci/flake-parts/07f6395285469419cf9d078f59b5b49993198c00' (2024-01-11)
• Updated input 'flake-parts/nixpkgs-lib':
    'github:NixOS/nixpkgs/e92039b55bcd58469325ded85d4f58dd5a4eaf58?dir=lib' (2023-11-29)
  → 'github:NixOS/nixpkgs/b0d36bd0a420ecee3bc916c91886caca87c894e9?dir=lib' (2023-12-30)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/cfc3698c31b1fb9cdcf10f36c9643460264d0ca8' (2023-12-27)
  → 'github:NixOS/nixpkgs/317484b1ead87b9c1b8ac5261a8d2dd748a0492d' (2024-01-08)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, run:

git branch -D update_flake_lock_action
git fetch origin
git checkout update_flake_lock_action
git commit --amend --no-edit
git push origin update_flake_lock_action --force

[SomeoneSerge]

Some notes:

• The reason this PR didn't trigger the "Nix CI" workflow is that we need bd05a2d (or drop the "paths" from that workflow entirely)
• Just in case that got lost in the preceding conversation, the PR got opened in your, @ggerganov, name because we used the personal access token. And we used that because github doesn't allow "automated" PRs to trigger more jobs
• Idk if this generates any pings for you? I chose the frequency (once per week) arbitrarily. Something like a monthly automated update wouldn't be unreasonable either

EDIT: I'm going to trigger a manual job, https://github.com/ggerganov/llama.cpp/actions/runs/7514627332

[ggerganov]

Ok thanks. It ok for now. I will likely change it to @ggml-bot at some point

[philiptaron]

I built all the packages on x86_64-linux and ran nix flake update myself to gather the most recent changes.