python-mapnik: 3.0.16 -> unstable-2020-02-24 #81628
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update to fix build errors with mapnik 3.0.23, along with other pending
upstream commits.
Upstream has not tagged a python-mapnik release since 2017. This
unstable commit, however, is also the basis for the python-mapnik
package in Debian testing.
NOTE: This PR is dependent on #81537 (or other fix to GDAL build).
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)nixpkgs-review was run on this PR on top of #81537:
Result of
nixpkgs-review
11 package marked as broken and skipped:
1 package failed to build:
27 package built:
NOTE: The mysql-workbench package that failed to build has not built successfully since 2019-09-30 on hydra and the reason appears unrelated, see: https://hydra.nixos.org/build/113768418