nix-shell doesn't understand the "undeprecate URL literals" flag #523
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#523
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?
Describe the bug
nix-shell admonishes that you should use --extra-deprecated-features=url-literals to evaluate legacy shell.nix files, but doesn't understand that flag.
Steps to reproduce
Attempt to load nextpnr's nix shell (https://github.com/YosysHQ/nextpnr/blob/master/shell.nix)
Expected behavior
nix-shell should understand the flag it recommends, or have a different error message
nix --version
outputnix (Lix, like Nix) 2.92.0-dev-pre20240912-b2fc007
Additional context
Easy to fix by fixing the shell.nix of course, just a minor UI hiccup.
What's deleting the = sign do in there? I have a suspicion it might be the bug you're finding, cuz long options that are config settings do generally work with the legacy commands. also cc @piegames
Yeah, that is a fuckup of mine, though arguably the issue is with this horrible CLI parser not accepting
=
between argument and value. Still, sorry for that. (IIRC pennae noticed and told me some weeks ago, but it kinda fell through the cracks of other stuff I'm doing)yeah no worries i am not blaming you, i just think you want to know of this issue :)
This issue was mentioned on Gerrit on the following CLs: