lix-project/lix
22
79
Fork 54
Code Issues 516 Code Review (Gerrit) Projects 8 Releases Packages Wiki Activity

feat: enable use-xdg-base-directories by default #796

New issue
Open
opened 2025-04-09 16:31:40 +00:00 by kfearsoff · 4 comments
kfearsoff commented 2025-04-09 16:31:40 +00:00
Member
Copy link

XDG Base Directory support has been stalled in CppNix for years. Let's see what is left to do, and fix it.

The setting is currently used in a few places: nix-channel, nix-env, eval settings, profiles. Eval setting is also used in default NIX_PATH, nix-channel and nix-env.

This internal API is error-prone: it expects the user to handle the migration manually, which can come with many caveats. We need to carefully handle this in a centralized manner.

Centralizing User Files

First, we need to move getNixDefExpr from eval settings to libutil/users.cc, which is already used by getNixDefExpr. Similar getNixChannels and getNixProfile functions should be created there, and should be used in previous places where useXDGBaseDirectory was mentioned explicitly.

Then, the functionality of getNixDefExpr and similar functions should be refactored. Right now, getNixDefExpr is a simple conditional on useXDGBaseDirectory. We need more:

  1. Check useXDGBaseDirectory; write relevant subpaths (depending on the function) to usedPath and possibleUnusedPath variables
  2. Check if usedPath exists on disk and write the result to a variable
  3. Check if possibleUnusedPath exists on disk and write the result to a variable
  4. Do a match on usedPath and possibleUnusedPath:
    5. If usedPath doesn't exist and possibleUnusedPath also doesn't exist: call createNixStateDir with relevant subpath
    6. If usedPath doesn't exist and possibleUnusedPath exists: move possibleUnusedPath to usedPath. This is the migration path
    7. If usedPath exists and possibleUnusedPath doesn't exist: do nothing. This is backwards compat flow
    8. If usedPath exists and possibleUnusedPath also exists: TBD, also backwards compat flow
  5. Return usedPath

Migration Path and Backwards Compat

There are a few options here. What's described above is remove old, use new option.

A potentially better flow is symlink old to new option. This would write a symlink to old location that points to new location. It needs testing to see if this option works for the ecosystem. I suggest starting with this one and testing the ecosystem. The major benefit, aside from potentially better backwards compat, is that it might support Lix downgrade operations. This, too, needs to be tested.

The least preferred flow is keep both. This will potentially break UX in awful ways when doing downgrades or using some of the ecosystem options.

Known Issues

There are several things that are already reported to be broken with use-xdg-base-directories.

nix-build is busted. More accurately, this seems to be a NIX_PATH issue, seems to originate here.

fish completions are busted - seems to be resolved.

nix-collect-garbage issues - not actually related.

HM issues: the HM logic is faulty in those lines. First logic branch applies when HM is a NixOS/nix-darwin module, second if Nix impl is managed with HM. If Nix is not managed with HM, then HM defaults to legacy path and doesn't consider XDG paths at all, which is a bug.

Testing

This is a large change that needs extensive testing. There are several use cases that need to be checked on VMs. Like mentioned above, symlink old to new approach is ideal; so this approach should be taken first and discarded if related tests fail and it's a major issue:

  • Generic Linux, use-xdg-base-directories false -> true
  • Generic Linux, use-xdg-base-directories true -> false
  • Generic Linux, use-xdg-base-directories true on a patched Lix version -> downgrade to non-patched and verify that it works
  • Generic Linux, use-xdg-base-directories false on a patched Lix version -> downgrade to non-patched and verify that it works
  • (symlink old to new) Generic Linux, use-xdg-base-directories true on a patched Lix version -> downgrade to non-patched and verify that it works
  • (symlink old to new) Generic Linux, use-xdg-base-directories true -> see if HM standalone works
  • Generic Linux, use-xdg-base-directories true -> see if nix-build works
  • Generic Linux, use-xdg-base-directories true -> see if Hydra and lix-eval-jobs work
  • Generic Linux, use-xdg-base-directories true -> see if packages that use nixForLinking work
  • Generic Linux, use-xdg-base-directories true -> see if packages that can be built with Lix dependency work
  • NixOS, use-xdg-base-directories true -> see if commands like nixos-rebuild, nix-env, nix-channel work
  • (symlink old to new) NixOS, use-xdg-base-directories true -> downgrade to non-patched and see if commands like nixos-rebuild, nix-env, nix-channel work
XDG Base Directory support has been stalled in CppNix for years. Let's see what is left to do, and fix it. The setting is currently used in a few places: [nix-channel](https://git.lix.systems/lix-project/lix/src/branch/main/lix/legacy/nix-channel.cc#L182), [nix-env](https://git.lix.systems/lix-project/lix/src/branch/main/lix/legacy/nix-env.cc#L1335), [eval settings](https://git.lix.systems/lix-project/lix/src/branch/main/lix/libexpr/eval-settings.cc#L102), [profiles](https://git.lix.systems/lix-project/lix/src/branch/main/lix/libstore/profiles.cc#L330). Eval setting is also used in [default NIX_PATH](https://git.lix.systems/lix-project/lix/src/branch/main/lix/libexpr/eval-settings.cc#L66), [nix-channel](https://git.lix.systems/lix-project/lix/src/branch/main/lix/legacy/nix-channel.cc#L183) and [nix-env](https://git.lix.systems/lix-project/lix/src/branch/main/lix/legacy/nix-env.cc#L1442). This internal API is error-prone: it expects the user to handle the migration manually, which can come with many caveats. We need to carefully handle this in a centralized manner. ## Centralizing User Files First, we need to move `getNixDefExpr` from [eval settings](https://git.lix.systems/lix-project/lix/src/branch/main/lix/libexpr/eval-settings.cc#L102) to `libutil/users.cc`, which is [already used](https://git.lix.systems/lix-project/lix/src/commit/fb0ef6ca6bfea368e594e9ae2714858030f66bc6/lix/libutil/users.cc#L92-L96) by `getNixDefExpr`. Similar `getNixChannels` and `getNixProfile` functions should be created there, and should be used in previous places where `useXDGBaseDirectory` was mentioned explicitly. Then, the functionality of `getNixDefExpr` and similar functions should be refactored. Right now, `getNixDefExpr` is a simple conditional on `useXDGBaseDirectory`. We need more: 1. Check `useXDGBaseDirectory`; write relevant subpaths (depending on the function) to `usedPath` and `possibleUnusedPath` variables 2. Check if `usedPath` exists on disk and write the result to a variable 3. Check if `possibleUnusedPath` exists on disk and write the result to a variable 4. Do a match on `usedPath` and `possibleUnusedPath`: 5. If `usedPath` doesn't exist and `possibleUnusedPath` also doesn't exist: call `createNixStateDir` with relevant subpath 6. If `usedPath` doesn't exist and `possibleUnusedPath` exists: move `possibleUnusedPath` to `usedPath`. This is the *migration path* 7. If `usedPath` exists and `possibleUnusedPath` doesn't exist: do nothing. This is *backwards compat* flow 8. If `usedPath` exists and `possibleUnusedPath` also exists: TBD, also *backwards compat* flow 9. Return `usedPath` ## Migration Path and Backwards Compat There are a few options here. What's described above is *remove old, use new* option. A potentially better flow is *symlink old to new* option. This would write a symlink to old location that points to new location. It needs testing to see if this option works for the ecosystem. I suggest **starting with this one** and testing the ecosystem. The major benefit, aside from potentially better backwards compat, is that it *might* support Lix downgrade operations. This, too, needs to be tested. The least preferred flow is *keep both*. This will potentially break UX in awful ways when doing downgrades or using some of the ecosystem options. ## Known Issues There are several things that are already reported to be broken with `use-xdg-base-directories`. [nix-build is busted](https://github.com/NixOS/nix/issues/8580). More accurately, this seems to be a `NIX_PATH` issue, seems to originate [here](https://git.lix.systems/lix-project/lix/src/commit/9c2dba4ee2f54e54f3e8be89e06eeec54f62e31e/lix/libexpr/eval-settings.cc#L53-L71). [fish completions are busted](https://github.com/NixOS/nix/issues/8573) - seems to be resolved. [nix-collect-garbage issues](https://github.com/NixOS/nix/issues/8508) - not actually related. [HM issues](https://github.com/nix-community/home-manager/issues/2544#issuecomment-1507852884): the HM logic is faulty in [those lines](https://github.com/nix-community/home-manager/blob/542efdf2dfac351498f534eb71671525b9bd45ed/modules/home-environment.nix#L563-L569). First logic branch applies when HM is a NixOS/nix-darwin module, second if Nix impl is managed with HM. If Nix is not managed with HM, then HM defaults to legacy path and doesn't consider XDG paths at all, which is a bug. ## Testing This is a large change that needs extensive testing. There are several use cases that need to be checked on VMs. Like mentioned above, *symlink old to new* approach is ideal; so this approach should be taken first and discarded if related tests fail and it's a major issue: - Generic Linux, `use-xdg-base-directories` false -> true - Generic Linux, `use-xdg-base-directories` true -> false - Generic Linux, `use-xdg-base-directories` true on a patched Lix version -> downgrade to non-patched and verify that it works - Generic Linux, `use-xdg-base-directories` false on a patched Lix version -> downgrade to non-patched and verify that it works - (symlink old to new) Generic Linux, `use-xdg-base-directories` true on a patched Lix version -> downgrade to non-patched and verify that it works - (symlink old to new) Generic Linux, `use-xdg-base-directories` true -> see if HM standalone works - Generic Linux, `use-xdg-base-directories` true -> see if `nix-build` works - Generic Linux, `use-xdg-base-directories` true -> see if Hydra and lix-eval-jobs work - Generic Linux, `use-xdg-base-directories` true -> see if [packages that use nixForLinking](https://github.com/NixOS/nixpkgs/pull/384099/files) work - Generic Linux, `use-xdg-base-directories` true -> see if packages that can be built with Lix dependency work - NixOS, `use-xdg-base-directories` true -> see if commands like `nixos-rebuild`, `nix-env`, `nix-channel` work - (symlink old to new) NixOS, `use-xdg-base-directories` true -> downgrade to non-patched and see if commands like `nixos-rebuild`, `nix-env`, `nix-channel` work
kfearsoff commented 2025-04-09 17:54:39 +00:00
Author
Member
Copy link

Discussed in Matrix: supposedly, this flag also screws up profiles by changing symlink structure from ~/.nix-profile -> /nix/var/nix/profiles/per-user/foo/bar -> /nix/store/... to ~/.local/share/nix/something -> /nix/store/...

Also, while checking each other's setups, we might have found a lot of differences in when and how the setup is done...

Sigh, the list of things to do grows ever larger. Things to check:

  1. CppNix 2.3 installation
  2. CppNix 2.4 installation
  3. CppNix 2.18 installation
  4. CppNix latest installation
  5. DetSys installation of CppNix (non-DetSys version, latest)
  6. Lix installation

Additionally, the feature matrix between (nix-env or nix profile, non-XDG or XDG) symlink trees needs checking.

Need to also investigate on what this CL is about: https://gerrit.lix.systems/c/lix/+/1101

Discussed in Matrix: supposedly, this flag also screws up profiles by changing symlink structure from `~/.nix-profile -> /nix/var/nix/profiles/per-user/foo/bar -> /nix/store/...` to `~/.local/share/nix/something -> /nix/store/...` Also, while checking each other's setups, we might have found a lot of differences in when and how the setup is done... Sigh, the list of things to do grows ever larger. Things to check: 1. CppNix 2.3 installation 2. CppNix 2.4 installation 3. CppNix 2.18 installation 4. CppNix latest installation 5. DetSys installation of CppNix (non-DetSys version, latest) 6. Lix installation Additionally, the feature matrix between (`nix-env` or `nix profile`, non-XDG or XDG) symlink trees needs checking. Need to also investigate on what this CL is about: https://gerrit.lix.systems/c/lix/+/1101
kfearsoff commented 2025-04-10 00:12:34 +00:00
Author
Member
Copy link

Okay, totally unscientific research here is done. Methodology:

  1. Provision an Ubuntu-24.04 Server VM, install the OS, shut down
  2. Clone VM with disk to a new VM+disk with descriptive name
  3. Boot up a clone
  4. wget https://releases.nixos.org/nix/nix-<version>/install && chmod +x install && ./install --daemon for script installs
  5. Look at results
  6. Relog into user and look at results
  7. Restart the daemon and look at results

I used "vanilla releases" (ending on .0, like 2.3.0), because keeping up with minor patches is too much of a pain. Results:

  • CppNix 2.3: sets up /root/.nix-channels and /root/.nix-defexpr, /root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels, nothing in user homedir. Relog sets up ~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels and ~/.nix-profile -> /nix/var/nix/profiles/per-user/user/profile. Trying to run nix-env gives error error: opening lock file '/nix/var/nix/db/big-lock': Permission denied. This isn't fixed with trusted-users or reboot, lol
  • CppNix 2.3.13 (because plain 2.3 is broken): same, but /root/.nix-profile-> /nix/var/nix/profiles/default. Relog also sets up ~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels, but homedir setup requires reboot, and running nix-env gives error error: could not set permissions on '/nix/var/nix/profiles/per-user' to 755: Operation not permitted. And it is actually 755 already, just owned by root:root. Gross.
  • CppNix 2.4 is exactly the same
  • CppNix 2.11 (arbitrary version to test 2.4-like before 2.14): same setup like before, but homedir is not set up with login scripts. Instead, running nix-env -iA nixpkgs.hello sets everything up. Channels are a bit weird: it sets up ~/.nix-defexpr/root_channel but ~/.nix-defexpr/channels exists and point to /nix/var/nix/profiles/per-user/user/channels (which doesn't exist). This should resolve itself when running nix-channel --add, though.
  • CppNix 2.18: same setup like before, but now ~/.nix-profile -> ~/.local/state/nix/profiles/profile -> ~/.local/state/nix/profiles/profile-1-link -> /nix/store/...-user-environment. Bizarrely enough, /root/.nix-profile -> /nix/var/nix/profiles/per-user/root/profile, with /nix/var/nix/profiles/default also pointing to it
  • CppNix latest: identical to CppNix 2.18
  • DetSys CppNix latest: identical to CppNix 2.18, except it doesn't set up root channels? sudo nix-channel gives "no command found"? wtf? Reboot doesn't fix it
  • Lix latest: identical to DetSys CppNix

I'll write a summary of what this means in practice later in a separate comment, because this drained life out of me.

Okay, totally unscientific research here is done. Methodology: 1. Provision an Ubuntu-24.04 Server VM, install the OS, shut down 2. Clone VM with disk to a new VM+disk with descriptive name 3. Boot up a clone 4. `wget https://releases.nixos.org/nix/nix-<version>/install && chmod +x install && ./install --daemon` for script installs 5. Look at results 6. Relog into user and look at results 7. Restart the daemon and look at results I used "vanilla releases" (ending on `.0`, like `2.3.0`), because keeping up with minor patches is too much of a pain. Results: - CppNix 2.3: sets up `/root/.nix-channels` and `/root/.nix-defexpr`, `/root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels`, nothing in user homedir. Relog sets up `~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels` and `~/.nix-profile -> /nix/var/nix/profiles/per-user/user/profile`. Trying to run `nix-env` gives error `error: opening lock file '/nix/var/nix/db/big-lock': Permission denied`. This isn't fixed with `trusted-users` or reboot, lol - CppNix 2.3.13 (because plain 2.3 is broken): same, but `/root/.nix-profile-> /nix/var/nix/profiles/default`. Relog also sets up `~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels`, but homedir setup requires **reboot**, and running `nix-env` gives error `error: could not set permissions on '/nix/var/nix/profiles/per-user' to 755: Operation not permitted`. And it is actually 755 already, just owned by `root:root`. Gross. - CppNix 2.4 is exactly the same - CppNix 2.11 (arbitrary version to test 2.4-like before 2.14): same setup like before, but homedir is not set up with login scripts. Instead, running `nix-env -iA nixpkgs.hello` sets everything up. Channels are a bit weird: it sets up `~/.nix-defexpr/root_channel` but `~/.nix-defexpr/channels` exists and point to `/nix/var/nix/profiles/per-user/user/channels` (which doesn't exist). This should resolve itself when running `nix-channel --add`, though. - CppNix 2.18: same setup like before, but now `~/.nix-profile -> ~/.local/state/nix/profiles/profile -> ~/.local/state/nix/profiles/profile-1-link -> /nix/store/...-user-environment`. Bizarrely enough, `/root/.nix-profile` -> `/nix/var/nix/profiles/per-user/root/profile`, with `/nix/var/nix/profiles/default` also pointing to it - CppNix latest: identical to CppNix 2.18 - DetSys CppNix latest: identical to CppNix 2.18, except it doesn't set up root channels? `sudo nix-channel` gives "no command found"? wtf? Reboot doesn't fix it - Lix latest: identical to DetSys CppNix I'll write a summary of what this means in practice later in a separate comment, because this drained life out of me.
kfearsoff commented 2025-04-10 14:51:47 +00:00
Author
Member
Copy link

Pre-2.14 layout looks like this:

  • /root/.nix-channels
  • /root/.nix-defexpr (directory)
    • /root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels
  • /root/.nix-profile -> /nix/var/nix/profiles/default -> /nix/var/nix/profiles/per-user/root/profile
  • ~/.nix-defexpr (directory)
    • ~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels
    • ~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels
  • ~/.nix-profile -> /nix/var/nix/profiles/per-user/user/profile -> /nix/var/nix/profiles/per-user/user/profile-1 -> /nix/store/...-user-environment

Post-2.14:

  • /root/.nix-channels
  • /root/.nix-defexpr (directory)
    • /root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels
  • /root/.nix-profile -> /nix/var/nix/profiles/default -> /nix/var/nix/profiles/per-user/root/profile
  • ~/.nix-defexpr (directory)
    • ~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels
    • ~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels
  • ~/.nix-profile -> ~/.local/state/nix/profiles/profile -> ~/.local/state/nix/profiles/profile-1 -> /nix/store/...-user-environment

To revert 2.14 change (@qyriad CL at https://gerrit.lix.systems/c/lix/+/1101 , CppNix PR: https://github.com/NixOS/nix/pull/5226 ), we need to change daemon stuff, probably nix-collect-garbage, and we need to do something equivalent to mkdir -p /nix/var/nix/profiles/per-user/user && cp ~/.local/state/nix/profiles/* /nix/var/nix/profiles/per-user/user/ && ln -s /nix/var/nix/profiles/per-user/user/profile ~/.nix-profile when running commands.

Additional consideration: we need to figure out root channels, because modern installers don't even set them up. Some middle ground needs to be found, where it's impossible to footgun yourself with rootless/rootful nix-channel usage, yet other stuff doesn't break.

After that, we can actually get to doing this issue, which works as documented.

Pre-2.14 layout looks like this: - `/root/.nix-channels` - `/root/.nix-defexpr` (directory) - `/root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels` - `/root/.nix-profile -> /nix/var/nix/profiles/default -> /nix/var/nix/profiles/per-user/root/profile` - `~/.nix-defexpr` (directory) - `~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels` - `~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels` - `~/.nix-profile -> /nix/var/nix/profiles/per-user/user/profile -> /nix/var/nix/profiles/per-user/user/profile-1 -> /nix/store/...-user-environment` Post-2.14: - `/root/.nix-channels` - `/root/.nix-defexpr` (directory) - `/root/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/root/channels` - `/root/.nix-profile -> /nix/var/nix/profiles/default -> /nix/var/nix/profiles/per-user/root/profile` - `~/.nix-defexpr` (directory) - `~/.nix-defexpr/channels_root -> /nix/var/nix/profiles/per-user/root/channels` - `~/.nix-defexpr/channels -> /nix/var/nix/profiles/per-user/user/channels` - `~/.nix-profile -> ~/.local/state/nix/profiles/profile -> ~/.local/state/nix/profiles/profile-1 -> /nix/store/...-user-environment` To revert 2.14 change (@qyriad CL at https://gerrit.lix.systems/c/lix/+/1101 , CppNix PR: https://github.com/NixOS/nix/pull/5226 ), we need to change daemon stuff, probably `nix-collect-garbage`, and we need to do something equivalent to `mkdir -p /nix/var/nix/profiles/per-user/user && cp ~/.local/state/nix/profiles/* /nix/var/nix/profiles/per-user/user/ && ln -s /nix/var/nix/profiles/per-user/user/profile ~/.nix-profile` when running commands. Additional consideration: we need to figure out root channels, because modern installers don't even set them up. Some middle ground needs to be found, where it's impossible to footgun yourself with rootless/rootful `nix-channel` usage, yet other stuff doesn't break. After that, we can actually get to doing this issue, which works as documented.
kfearsoff commented 2025-04-10 14:56:09 +00:00
Author
Member
Copy link

Related: #151 #215

Related: #151 #215
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci-config
release-2.91
release-2.92
release-2.93
sb/raito/darwin-kqueue-disablement
sb/raito/hydra-merge
sb/pennae/ci-config
sb/raito/phantom-referrers-gc
repl-overlay-example
reuse-compliance
release-2.90
sb/pennae/io-rewrite
git-series/activity-cleanup
sb/tom-hubrecht/primops.cc-v2
sb/bacchanalia/cache-strlen%topic=substr-perf
sb/qyriad/beta-1
sb/qyriad/2.90-beta.0
sb/rbt/test-branch
sb/rbt/justfile
sb/rbt/repl-overlays
sb/qyriad/maint-meson
sb/qyriad/maint/meson
sb/puck/meson-c-api
sb/jade/burn-it-all
dependabot/github_actions/zeebe-io/backport-action-2.4.1
dependabot/github_actions/cachix/install-nix-action-25
dependabot/github_actions/actions/labeler-5
dependabot/github_actions/cachix/cachix-action-14
2.93.3
2.92.3
2.93.2
2.91.3
2.92.2
2.91.2
2.93.1
2.93.0
2.92.0
2.91.1
2.91.0
2.90.0
2.90.0-rc1
2.90-beta.1
2.90-beta.0
Labels
Clear labels   
Affects/CppNix

Probably affects CppNix. This is a best-effort tag for troubles in old code; it exists to inform the CppNix team about problems they might care about also.

  
Affects/Nightly

Found in Lix nightly.

  
Affects/Only nightly

Tag for regressions in Lix nightly. We intend to fix all of these prior to releases.

  
Affects/Stable

Affects the stable release of Lix. Usually such issues affect nightly too but there is no guarantee.

  
Area/build-packaging

regarding the building or packaging of Lix itself

  
Area/cli

The command line interface of Lix

  
Area/evaluator

libexpr and anything else related to the evaluation of Nix expressions

  
Area/fetching

Fetching sources or other materials from the World Wide Web in Lix

  
Area/flakes

   
Area/language

language design, features, extensions, etc

  
Area/lix ci

Lix's own CI and deployment pipeline

  
Area/nix-eval-jobs

nix-eval-jobs for Lix

  
Area/profiles

profiles: nix-env, nix profile, and installer flavors all alike

  
Area/protocol

The protocol, used for communicating between the client and the daemon

  
Area/releng

Release engineering

  
Area/remote-builds

remote builds

  
Area/repl

nix repl

  
Area/repl/debugger

The --debugger that brings up a Lix repl

  
Area/store

libstore and anything else relating to the Nix store

  
bug

it's a bug

  
Context
contributors
This issue might require some context that isn't written down. It might be possible to handle as a person who already worked on this area.

  
Context
drive-by
This issue contains all the necessary information to do a drive-by contribution: that is, you don't have to talk with anyone at all to successfully solve it!

  
Context
maintainers
This issue requires a lot of know-how. Attention from maintainers is needed to proceed.

  
Context
RFD
This issue needs discussion from multiple maintainers and interested parties: it's a Request For Discussion.

  
crash 💥

Lix crashes (possibly bad error handling)

  
Cross Compilation

   
devx

development experience issues

  
docs

requires or is about documentation changes

  
Downstream Dependents

regarding an external tool's usage with Lix (e.g. nix-eval-jobs)

  
E/easy

bug is relatively simple and could simply be fixed with some minor effort

  
E/hard

this issue should probably be solved with close involvement of an expert

  
E/help wanted

maintainers may not get to this soon, but we want it fixed

  
E/reproducible

This bug is reproducible and obvious.

  
E/requires rearchitecture

this bug cannot be fixed properly without fixing a known architectural flaw

  
imported

Issue imported from upstream nix (please do not remove this label, it will cause dupes if import is rerun)

  
Language/Bash

   
Language/C++

   
Language/NixLang

   
Language/Python

   
Language/Rust

   
Needs Langver

We can't get to this until we implement language versioning

  
OS/Linux

Affects specifically Lix on Linux

  
OS/macOS

Affects specifically Lix on macOS

  
performance

make lix go faster

  
regression

This is a regression since some previous version of Lix

  
release-blocker

Blocks public release

  
stability

Fixing this makes the software more stable

  
Status
blocked
Blocked on something

  
Status
invalid
not our bug, duplicate, similar

  
Status
postponed
closed but should maybe look at later (generally with S-wontfix)

  
Status
wontfix
We chose not to change this (see issue comments for more detail).

  
testing

Tests that should be added

  
testing/flakey

Tests that are unreliable/flakey (not to be confused with flakes that test)

  
Topic/Large Scale Installations

Large scale installations of Lix, e.g. NixOS Hydra, Lix CI, big corporate installations etc.

  
ux

makes the user experience better :)

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#796
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?