Created
December 31, 2024 18:05
-
-
Save GrahamcOfBorg/33d24bb6fd2d50fe2f405aa79c9c6304 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| nix-env failed: | |
| error: | |
| … while calling anonymous lambda | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/.gc-of-borg-outpaths.nix:48:12: | |
| 47| tweak = lib.mapAttrs | |
| 48| (name: val: | |
| | ^ | |
| 49| if name == "recurseForDerivations" then true | |
| … from call site | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/lib/attrsets.nix:1247:43: | |
| 1246| f: | |
| 1247| listToAttrs (map (n: nameValuePair n (f n)) names); | |
| | ^ | |
| 1248| | |
| … while calling anonymous lambda | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/top-level/release-lib.nix:146:6: | |
| 145| testOnCross = crossSystem: metaPatterns: f: forMatchingSystems metaPatterns | |
| 146| (system: hydraJob' (f (pkgsForCross crossSystem system))); | |
| | ^ | |
| 147| | |
| … from call site | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/top-level/release-lib.nix:146:14: | |
| 145| testOnCross = crossSystem: metaPatterns: f: forMatchingSystems metaPatterns | |
| 146| (system: hydraJob' (f (pkgsForCross crossSystem system))); | |
| | ^ | |
| 147| | |
| … while calling 'hydraJob' | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/lib/customisation.nix:443:5: | |
| 442| hydraJob = | |
| 443| drv: | |
| | ^ | |
| 444| let | |
| … from call site | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/development/interpreters/python/passthrufun.nix:44:17: | |
| 43| lib.extendDerivation ( | |
| 44| valid value | |
| | ^ | |
| 45| || throw "${name} should use `buildPythonPackage` or `toPythonModule` if it is to be part of the Python packages set." | |
| … while calling 'valid' | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/development/interpreters/python/passthrufun.nix:39:13: | |
| 38| valid = | |
| 39| value: pythonPackages.hasPythonModule value || providesSetupHook value || lib.elem value exceptions; | |
| | ^ | |
| 40| func = | |
| … from call site | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/stdenv/generic/check-meta.nix:511:13: | |
| 510| else if valid == "no" then ( | |
| 511| handleEvalIssue { inherit meta attrs; } { inherit (validity) reason errormsg; } | |
| | ^ | |
| 512| ) | |
| … while calling 'handleEvalIssue' | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/stdenv/generic/check-meta.nix:269:38: | |
| 268| | |
| 269| handleEvalIssue = { meta, attrs }: { reason , errormsg ? "" }: | |
| | ^ | |
| 270| let | |
| … from call site | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/pkgs/stdenv/generic/check-meta.nix:281:8: | |
| 280| else throw; | |
| 281| in handler msg; | |
| | ^ | |
| 282| | |
| … while calling 'handleEvalIssue' | |
| at /ofborg/checkout/1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-0/.gc-of-borg-outpaths.nix:28:37: | |
| 27| | |
| 28| handleEvalIssue = reason: errormsg: | |
| | ^ | |
| 29| let | |
| error: evaluation aborted with the following error message: 'Failed to evaluate miniforge-24.11.0-0: «unknown-meta»: has an invalid meta attrset: | |
| - key 'meta.maintainers' has invalid value; expected listOf<attrsOf<any>>, got | |
| [ | |
| "qxrein" | |
| ] | |
| ' |
Looks like you’re dealing with a tricky Nix/OfBorg evaluation error. While digging through these stack traces and debugging, it might be a good time to check out ways to earn online to make the wait more productive.
From the stack trace it looks like a nix evaluation issue around attribute handling rather than anything repo-specific, so checking recent changes to metaPatterns or nixpkgs versions might help narrow it down. Clear debugging notes like this are appreciated very fair play apk style in terms of transparency and sharing useful error context.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This error trace is actually helpful for pinpointing where the evaluation breaks in Nix—especially around attribute mapping and recursion handling. Clear diagnostics like this save a lot of time, much like platforms that let you Download and earn by making the process straightforward and rewarding.