diff options
| author | Winter <winter@winter.cafe> | 2025-05-13 00:02:38 -0400 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-05-22 21:38:02 +0200 |
| commit | 5240bdf3c63d7516f2bb74cd5e099f993a88ab89 (patch) | |
| tree | b322eb4d5f01fb53018dbc9218090c426e29902f /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 3cc678fad5bfefaefddf6392acce43e35c7a5363 (diff) | |
ci/eval: don't evaluate packages marked as broken
We really can't expect packages that are marked as broken to evaluate,
and *especially* not on unsupported platforms.
For context, we were attempting to eval them *past* the broken throw
previously, which caused fun side effects like [0].
When we set `includeBroken = true` before, this also included unfree
packages. Those would now be excluded, which is not what we want. Thus,
we explicitly enable them separately.
Commit by winterqt, message slightly reworded by wolfgangwalther.
[0]:
https://github.com/NixOS/nixpkgs/issues/355847#issuecomment-2878873137
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions