Unstable fails to build, stable OK (flakes)

Help
1

I have an issue performing a rebuild on my system since the end of June…(flake update on 30 June)

Using unstable with the line

nixpkgs.url = “github:NixOS/nixpkgs/nixos-unstable”;

I get the following error:

error: separateDebugInfo = true in lix requires __structuredAttrs if {dis,}allowedRequisites or {dis,}allowedReferences is set

If I replace with 25.05 -

nixpkgs.url = “nixpkgs/nixos-25.05”;

The build is successful (I’ve tried several dates from 30 June to 8 August).

I have tried nix instead of lix (no change), and removed many config aspects (most of the installed apps for example) with no effect. I can update the flake lock of everything (lix, hyprland, home-manager etc.) except nixos-unstable. My home-manager version is 25.11, following the unstable nixpkgs.

The error stumps me - I have looked at the thread on breaking elements for unstable, searched the discourse, and home-manager for possible causes and nothing seems to help :frowning:

Can anyone give me some pointers to debug? I must have missed something somewhere. Anything appreciated as I’m totally lost!

2

Seems to be related to separateDebugInfo: add symlinks to executable and source for debuginfod support by symphorien · Pull Request #394674 · NixOS/nixpkgs · GitHub, or at least some behavior that said PR documents.

You do need to share the full error to get help though.

1 Like
3

It is probably this one: #917 - error: separateDebugInfo = true in lix requires __structuredAttrs if {dis,}allowedRequisites or {dis,}allowedReferences is set - lix-project/lix - Lix Systems

What works for me right now is running lix from main: Running Lix main | Lix Wiki

First install lix from main and then nix flake update dis the trick for me.

1 Like
4

Thanks for taking the time to respond and the link - much appreciated! I did consider posting the full error but it was several hundred lines and all “internal” nixos modules - none referred to my config at all or any of the modules I might have referenced (such as a package), so I wanted to at least try to reduce the search space for others. This was not my particular, but I have learnt a little more along the way…

5

Thanks! I didn’t check back later and so missed this article. I must also have made a mistake returning the the standard nix, as I tried this again and was successful (after fixing even more errors…) which I thought gave the same error as using lix originally. I am annoyed with myself as lix was my first guess for the issue, and I didn’t pin it down sufficiently, although a lot of the packages I seem to be using at the moment are “broken” in some way which doesn’t help fault finding…