From a01aeeb9b1bb9a646bdbc2f590b29285bf65a3e7 Mon Sep 17 00:00:00 2001 From: Robert Hensing Date: Sun, 9 Nov 2025 19:23:47 +0100 Subject: [PATCH] lib/modules: Add false positive info to check coherence assertion Unfortunately, we don't have a good enough way to discern this possibility. Technically we could add yet another attribute, but that does not seem to be worth the cost at this point, in terms of complexity and possibly even performance. I take the blame for this one. I identified the need for the second merge commit in review but didn't require it in the first merge. These changes really should have been done in a single merge. That would have prevented this situation. --- lib/modules.nix | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lib/modules.nix b/lib/modules.nix index a78bd1a92488..e545f9c9707d 100644 --- a/lib/modules.nix +++ b/lib/modules.nix @@ -1147,6 +1147,9 @@ let instead of: baseType // { check = value: /* your check */; } + + Alternatively, this message may also occur as false positive when mixing Nixpkgs + versions, if one Nixpkgs is between 83fed2e6..58696117 (Aug 28 - Oct 28 2025) ''; # Merge definitions of a value of a given type.