Using nix flake update no longer uses the registry to resolve flakes #144

New Issue

rarias · 2025-07-18T10:37:17+02:00

rarias commented

2025-07-18 10:37:17 +02:00

This crap:

hut% nix flake update --commit-lock-file
error:
       … while updating the lock file of flake 'git+file:///home/Computational/rarias/bscpkgs?ref=refs/heads/update-ompss-2025-06&rev=8e5b2dc5ccee0bad68d738cca7db2ffffc44c8fd'

       … while updating the flake input 'nixpkgs'

       error: cannot find flake 'flake:nixpkgs' in the flake registries

Is caused by https://github.com/NixOS/nix/pull/12068, as we have properly set the nixpkgs flake in the registry:

hut% nix registry list
system flake:jungle path:/nix/store/rs0xy9dax2w405c3yssscfdi38pc0nkk-source?lastModified=1752598088&narHash=sha256-sZdpMAG9BrAelK6XR1On1/NwJTpmc0u9%2Bh1w9sJPvYE%3D&rev=1211b2376874cdd5ce4806b3d981562a7db63b14
system flake:nixpkgs path:/nix/store/zk8v61cpk1wprp9ld5ayc1g5fq4pdkwv-source?lastModified=1752436162&narHash=sha256-Kt1UIPi7kZqkSc5HVj6UY5YLHHEzPBkgpNUByuyxtlw%3D&rev=dfcd5b901dbab46c9c6e80b265648481aafb01f8

Which apparently is now ignored.

Why we cannot set in the registry an entry with the flake to point to the remote URL with the locked commit is beyond me. Also, what about reporting what the actual issue is?

A workaround is to use:

nix flake update --override-input nixpkgs flake:nixpkgs --commit-lock-file

Not sure what would be the best option for bscpkgs.

This crap: ``` hut% nix flake update --commit-lock-file error: … while updating the lock file of flake 'git+file:///home/Computational/rarias/bscpkgs?ref=refs/heads/update-ompss-2025-06&rev=8e5b2dc5ccee0bad68d738cca7db2ffffc44c8fd' … while updating the flake input 'nixpkgs' error: cannot find flake 'flake:nixpkgs' in the flake registries ``` Is caused by <https://github.com/NixOS/nix/pull/12068>, as we have properly set the nixpkgs flake in the registry: ``` hut% nix registry list system flake:jungle path:/nix/store/rs0xy9dax2w405c3yssscfdi38pc0nkk-source?lastModified=1752598088&narHash=sha256-sZdpMAG9BrAelK6XR1On1/NwJTpmc0u9%2Bh1w9sJPvYE%3D&rev=1211b2376874cdd5ce4806b3d981562a7db63b14 system flake:nixpkgs path:/nix/store/zk8v61cpk1wprp9ld5ayc1g5fq4pdkwv-source?lastModified=1752436162&narHash=sha256-Kt1UIPi7kZqkSc5HVj6UY5YLHHEzPBkgpNUByuyxtlw%3D&rev=dfcd5b901dbab46c9c6e80b265648481aafb01f8 ``` Which apparently is now ignored. Why we cannot set in the registry an entry with the flake to point to the remote URL with the locked commit is beyond me. Also, what about reporting what the actual issue is? A workaround is to use: ``` nix flake update --override-input nixpkgs flake:nixpkgs --commit-lock-file ``` Not sure what would be the best option for bscpkgs.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rarias/jungle#144