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-24 21:51:27 +0100
committerAlyssa Ross <hi@alyssa.is>2025-01-26 15:09:12 +0100
commit745c9a501585235837dd6de6014230a41afaf93a (patch)
treee490986b1bf5d4480b01a347c43523db9e56bfc7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentcace2b6eae83f813290074bc572ade8dff09c4fe (diff)
treewide: migrate to fetchCargoVendor, batch 5
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. These are a few cases that could have been in batch 1, but weren't for whatever reason. Maybe there were merge conflicts, or a transient network failure. 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
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions