Make nix doctor give more information like nix-info does, that can be included in bug reports #230

Open
opened 2024-04-08 01:40:24 +00:00 by jade · 6 comments
Owner

It seems very silly that Lix can't produce the nix-info -m output itself, since it is required in bug reports. It seems reasonable that we could add it to nix doctor output.

Sample output of nix-info -m:

 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.23-1-lts, Arch Linux, noversion, rolling`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Lix, like Nix) 2.90.0-lixpre20240403-89c3195`
 - channels(jade): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`
It seems very silly that Lix can't produce the `nix-info -m` output itself, since it is required in bug reports. It seems reasonable that we could add it to `nix doctor` output. Sample output of `nix-info -m`: ``` - system: `"x86_64-linux"` - host os: `Linux 6.6.23-1-lts, Arch Linux, noversion, rolling` - multi-user?: `yes` - sandbox: `yes` - version: `nix-env (Lix, like Nix) 2.90.0-lixpre20240403-89c3195` - channels(jade): `""` - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs` ```
Owner

The -m stands for --markdown — should this also be literally markdown?

The `-m` stands for `--markdown` — should this also be literally markdown?
Author
Owner

Probably by default yeah. Making the thing copy pastable into a bug report would be nice.

Probably by default yeah. Making the thing copy pastable into a bug report would be nice.
qyriad added this to the v2.91 milestone 2024-05-17 19:06:06 +00:00
Author
Owner

(status: there is wip code for this, https://git.lix.systems/qyriad/lix/src/branch/git-series/feature/doctor-info. we will get to it in the future)

(status: there is wip code for this, https://git.lix.systems/qyriad/lix/src/branch/git-series/feature/doctor-info. we will get to it in the future)
jade modified the milestone from v2.91 to post-release 2024-08-13 01:19:36 +00:00
jade self-assigned this 2025-08-20 23:23:04 +00:00
Author
Owner

I often find myself doing the following diagnosis to make sure that the version of nixpkgs is from a reasonable source. this should be part of nix doctor:

  • verify NIX_PATH and flake registry configuration state:
  • nix config show | grep nix-path
  • nix registry list
  • confirm that channels symlinks are dead and going nowhere, so we're using nixpkgs=flake:nixpkgs (thus the flake registry)
I often find myself doing the following diagnosis to make sure that the version of nixpkgs is from a reasonable source. this should be part of nix doctor: - verify NIX_PATH and flake registry configuration state: - nix config show | grep nix-path - nix registry list - confirm that channels symlinks are dead and going nowhere, so we're using nixpkgs=flake:nixpkgs (thus the flake registry)
Owner

I implemented all of this (I didn't impl channel symlinks having to be dead because I use channels in various systems and I don't think we should force people to use the flake registry) in a branch.

Now starts the long and annoying process of writing tests, if you are interested to help, let me know, I can pass on my WIP.

I implemented all of this (I didn't impl channel symlinks having to be dead because I use channels in various systems and I don't think we should force people to use the flake registry) in a branch. Now starts the long and annoying process of writing tests, if you are interested to help, let me know, I can pass on my WIP.
raito self-assigned this 2025-11-30 15:34:03 +00:00
pennae modified the milestone from post-release to 2.95 2025-12-01 14:51:44 +00:00
Member

This issue was mentioned on Gerrit on the following CLs:

  • commit message in cl/5317 ("nix/doctor: print nix related information")
  • commit message in cl/5320 ("nix/doctor: check nixpkgs provenance")
  • commit message in cl/5319 ("nix/doctor: check ambient search paths")
  • commit message in cl/5318 ("nix/doctor: check flake registry")
<!-- GERRIT_LINKBOT: {"cls": [{"backlink": "https://gerrit.lix.systems/c/lix/+/5317", "number": 5317, "kind": "commit message"}, {"backlink": "https://gerrit.lix.systems/c/lix/+/5320", "number": 5320, "kind": "commit message"}, {"backlink": "https://gerrit.lix.systems/c/lix/+/5319", "number": 5319, "kind": "commit message"}, {"backlink": "https://gerrit.lix.systems/c/lix/+/5318", "number": 5318, "kind": "commit message"}], "cl_meta": {"5317": {"change_title": "nix/doctor: print nix related information"}, "5320": {"change_title": "nix/doctor: check nixpkgs provenance"}, "5319": {"change_title": "nix/doctor: check ambient search paths"}, "5318": {"change_title": "nix/doctor: check flake registry"}}} --> This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/5317](https://gerrit.lix.systems/c/lix/+/5317) ("nix/doctor: print nix related information") * commit message in [cl/5320](https://gerrit.lix.systems/c/lix/+/5320) ("nix/doctor: check nixpkgs provenance") * commit message in [cl/5319](https://gerrit.lix.systems/c/lix/+/5319) ("nix/doctor: check ambient search paths") * commit message in [cl/5318](https://gerrit.lix.systems/c/lix/+/5318) ("nix/doctor: check flake registry")
raito modified the milestone from 2.95 to 2.96 2026-03-02 22:29:01 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
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#230
No description provided.