summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorAlyssa Ross <hi@alyssa.is>2025-01-23 08:45:31 +0100
committerAlyssa Ross <hi@alyssa.is>2025-01-23 11:46:43 +0100
commit63bff8c132d17b960f98d3878d10a410ec584472 (patch)
tree2a362506b7f32c74a6010d4a515c80ab69ca1fc4 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent2aa9dde422e6eb3d6bbc7839dfc9e0f4b21e5624 (diff)
treewide: migrate to fetchCargoVendor, batch 1
Cargo 1.84.0 seems to have changed the output format of cargo vendor again, once again invalidating fetchCargoTarball FOD hashes. It's time to fix this once and for all, switching across the board to fetchCargoVendor, which is not dependent on cargo vendor's output format. It should be possible to reproduce this diff. To do so, get the list of files changed by this commit, e.g. with git diff --name-only, then run the following two commands, each with that list of files as their standard input: xargs sed -i 's/^\(. *\)\(cargoHash\)\b/\1useFetchCargoVendor = true;\n\1cargoHash/' cut -d / -f 4 | xargs -n 1 nix-update --version=skip This will take a long time. It might be possible to parallelize it using xargs' -P option. I haven't tested it.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions