Compile error on newer Lix in libcmd #977
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
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
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#977
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?
Describe the bug
Lix fails to build using the hashes published on https://lix.systems/add-to-config/.
Steps To Reproduce
Add the following to Nix config imports:
Then run a regular
nixos-build switch --upgrade
.Expected behavior
Lix successfully builds.
Actual behavior
nix --version
outputnix (Lix, like Nix) 2.91.1
Additional context
I can't rebuild 2.91.1, 2.92.0-3, or 2.93.0 because of the following error:
this is a duplicate of .. something, the root cause of this bug is nixpkgs breakages causing burnout that causes not releasing a 2.93.4 with fixes that are already in a branch. please use nixosModules.lixFromNixpkgs or switch both module and lix to release-2.93 or use the running main guide at wiki.lix.systems.
see lix-project/nixos-module#61 for fixing the burnout inducing urgent releases problem