-
-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Description
Nixpkgs version
- Stable (25.05)
Describe the bug
nix-index v0.1.9 changed the behaviour of the nix-locate
command in a breaking way, removing the --top-level
argument to make it the default, and adding the --all
argument to restore the old behaviour, per https://github.com/nix-community/nix-index/releases/tag/v0.1.9
This is a breaking change, and therefore should not have been backported to 25.05.
Steps to reproduce
With an older 25.05 tree:
$ nix shell github:NixOS/nixpkgs/b43c397f6c213918d6cfe6e3550abfe79b5d1c51#nix-index --command nix-locate --top-level /bin/latexmk
texliveMedium.out 1,776 x /nix/store/8g9dvmk0r20mdwminrbrz4wnlwjl9cgz-texlive-2023-env/bin/latexmk
texliveFull.out 1,776 x /nix/store/99r9zgqml63mjnnc1pll5mb3x6w3p67g-texlive-2023-env/bin/latexmk
texliveBookPub.out 1,776 x /nix/store/zwglipcbwx6dshy44f538p7m4rb496jn-texlive-2023-env/bin/latexmk
With a newer tree:
$ nix shell github:NixOS/nixpkgs/fe83bbdde2ccdc2cb9573aa846abe8363f79a97a#nix-index --command nix-locate --top-level /bin/latexmk
error: unexpected argument '--top-level' found
tip: to pass '--top-level' as a value, use '-- --top-level'
Usage: nix-locate [OPTIONS] <PATTERN>
For more information, try '--help'.
Expected behaviour
Breaking changes are not backported to a stable release
Screenshots
No response
Relevant log output
Additional context
No response
System metadata
- system:
"x86_64-linux"
- host os:
Linux 6.6.87.2-microsoft-standard-WSL2, NixOS, 25.05 (Warbler), 25.05.20250629.b43c397
- multi-user?:
yes
- sandbox:
relaxed
- version:
nix-env (Nix) 2.28.3
- nixpkgs:
/nix/store/j95fcik6rzsydwips4m89dmlvfj9hg9y-source
Notify maintainers
nix-index maintainers: @bennofs @figsoda @ncfavier
Folk involved in #426177 that made the update to v0.1.9 in unstable, and #426179 that backported the change to 25.05: @mweinelt @K900
Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE
.)
I assert that this issue is relevant for Nixpkgs
- I assert that this is a bug and not a support request.
- I assert that this is not a duplicate of an existing issue.
- I assert that I have read the NixOS Code of Conduct and agree to abide by it.
Is this issue important to you?
Add a 👍 reaction to issues you find important.