summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorPol Dellaiera <pol.dellaiera@protonmail.com>2025-03-04 09:43:43 +0100
committerPol Dellaiera <pol.dellaiera@protonmail.com>2025-03-04 19:08:09 +0100
commit2e4faebd4d9e4dee920a2c884e0d37cd44a5625e (patch)
tree622856f1596e29c7fa53b10fd1faf5982124699a /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent25e851d0887cb5ca31b77ab038ac6490de1b4875 (diff)
deployer: 7.4.0 -> 7.5.12-unstable-2025-03-02
The release management of deployer is something I've never seen. They basically commit the PHAR file in the source, in a specific branch. They also modify the runner `bin/dep` to use that PHAR. Therefore, this break on NixOS since we are using the PHAR. A workaround is to use the master branch that doesn't contain the PHAR.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions