From 4aef6f76d4f610367b57d7fb9f389ca035c291df Mon Sep 17 00:00:00 2001 From: Andreas Rammhold Date: Fri, 10 Jul 2026 13:19:56 +0200 Subject: [PATCH 1/3] tests.problems: adjust test code for oldestSupportedRelease=26.05 In 53cd6f263c9a90ae02fdcabceb7db10c60e3d3cd the oldestSupportedRelease version was bumped to 26.05 which caused the meta/problems tests to fail because the `config.allowBrokenPredicate` is now deprecated and the code is warning about it. --- .../problems/cases/allow-broken-predicate-match/default.nix | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkgs/test/problems/cases/allow-broken-predicate-match/default.nix b/pkgs/test/problems/cases/allow-broken-predicate-match/default.nix index 7869bc996809..df18d357e1e8 100644 --- a/pkgs/test/problems/cases/allow-broken-predicate-match/default.nix +++ b/pkgs/test/problems/cases/allow-broken-predicate-match/default.nix @@ -5,7 +5,7 @@ let system = "x86_64-linux"; overlays = [ ]; config = { - allowBrokenPredicate = attrs: lib.getName attrs == "a"; + problems.handlers.a.broken = "ignore"; }; }; in From 00ec5f0eaf00877df594b64b379ec7ea4ba942a8 Mon Sep 17 00:00:00 2001 From: Andreas Rammhold Date: Fri, 10 Jul 2026 13:32:34 +0200 Subject: [PATCH 2/3] doc/release-notes: Add changelog entry for the now deprecated allowBrokenPredicate setting Since 48422decc45a428cab7b4a8fbdc3b07755fd088a the old behaviour is emitting a warning based on the latest supported release version. This documents it. --- doc/release-notes/rl-2611.section.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/release-notes/rl-2611.section.md b/doc/release-notes/rl-2611.section.md index ce3330d0b967..c16ca66b1fca 100644 --- a/doc/release-notes/rl-2611.section.md +++ b/doc/release-notes/rl-2611.section.md @@ -142,10 +142,11 @@ ### Deprecations {#sec-nixpkgs-release-26.11-lib-deprecations} -- Create the first release note entry in this section! +- Setting `config.allowBrokenPredicate` is deprecated in favor of + using `config.problems.handlers.PackageName.broken = "warn"` (or `= + "ignore"`). For more information see [](#sec-allow-broken). ### Additions and Improvements {#sec-nixpkgs-release-26.11-lib-additions-improvements} - Create the first release note entry in this section! - From 1f248f342be91912eca40f657c5eabe12645d565 Mon Sep 17 00:00:00 2001 From: Andreas Rammhold Date: Fri, 10 Jul 2026 15:20:12 +0200 Subject: [PATCH 3/3] tests.problems: Fix `invalid-kind-error` failure With 8fcbb3592984e1f364ec561f491790d854704264 all problem kinds are being used in the error messages. The expected messages were still missing the `maintainerless` kind. --- pkgs/test/problems/cases/invalid-kind-error/expected-stderr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkgs/test/problems/cases/invalid-kind-error/expected-stderr b/pkgs/test/problems/cases/invalid-kind-error/expected-stderr index 6fdf2b1d04b1..0d7cb8f874b6 100644 --- a/pkgs/test/problems/cases/invalid-kind-error/expected-stderr +++ b/pkgs/test/problems/cases/invalid-kind-error/expected-stderr @@ -1,4 +1,4 @@ (stack trace truncated; use '--show-trace' to show the full, detailed trace) error: Refusing to evaluate package 'a-0' in /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-default.nix:11 because it has an invalid meta attrset: - - a.meta.problems.invalid: Problem kind invalid, inferred from the problem name, is invalid; expected enum. You can specify an explicit problem kind with `a.meta.problems.invalid.kind` + - a.meta.problems.invalid: Problem kind invalid, inferred from the problem name, is invalid; expected enum. You can specify an explicit problem kind with `a.meta.problems.invalid.kind`