nix upgrade-nix should restart the daemon for you #267
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#267
Loading…
Add table
Add a link
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?
Currently it doesn't, and that requires extra steps in upgrade documents.
Also perhaps
upgrade-nixshould just hit the installer. Unsure.we::horrors are convinced that
upgrade-nixshould not exist and be an installer feature instead. it's too much of a footgun, especially on systems that had nix installed via a different package manager, not the installeryeah, it feels like possible miscommunication that we unbroke it rather than replacing it with an installer feature 🙃 i am very sorry @qyriad.
No problem! We assumed fixing upgrade-nix was temporary/interim while the installer feature wasn't a thing yet, so we knew we were fixing a feature that was not long for this world
nix upgrade-nix#10I just ran
nix upgrade-nixand afterwardsnix --versionreports the new version.I assume that this is expected and I still need to restart the daemon manually to complete the upgrade. But it would be nice if that is specifically documented (i.e. some language to the effect that the daemon restart is necessary even though it looks like it is upgraded).