summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorSilvan Mosberger <silvan.mosberger@tweag.io>2024-03-01 23:26:39 +0100
committerSilvan Mosberger <silvan.mosberger@tweag.io>2024-03-01 23:26:39 +0100
commit9356555ac073341a1f29a6f293d862085a24ed3c (patch)
tree0e2d3bbf4134d71761eacb79f09b8d51bf7f6da4 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentee9c2b7c6a141a054a8d451b777d0682b5af1751 (diff)
libmicrohttpd: Refactor to inherit
The `pkgs/by-name` check currently fails on the staging-next merge into master (https://github.com/NixOS/nixpkgs/actions/runs/8110296543/job/22167262748) because it contains the changes of https://github.com/NixOS/nixpkgs/pull/278920, which introduced a "new" package using `callPackage` but not using `pkgs/by-name`. This was never noticed in that PR because CI last ran almosts 2 months ago, which is before the check for new packages was introduced. This wouldn't be a problem normally, it's only become a problem because of the staging-next merge into master, which effectively PRs the same change again (and the `pkgs/by-name` check doesn't try to distinguish between branches). The fix for this is a bit special because it's not actually a "new" package, but rather just a new version of an existing package. The `pkgs/by-name` check can't distinguish between such cases though. So instead we make sure that the `pkgs/by-name` check doesn't think of it as a package using `callPackage` by using the recommendation for multi-versioned packages from https://github.com/NixOS/nixpkgs/pull/292214.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions