diff options
| author | Alyssa Ross <hi@alyssa.is> | 2025-01-24 21:53:46 +0100 |
|---|---|---|
| committer | Alyssa Ross <hi@alyssa.is> | 2025-01-26 15:16:11 +0100 |
| commit | e2afb6a831940aba237b16cd33c9b595b1fcf911 (patch) | |
| tree | 39566734fb2dff14bf590651cc3ef7a284e7cf2b /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 745c9a501585235837dd6de6014230a41afaf93a (diff) | |
treewide: migrate to fetchCargoVendor, batch 6
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 cases could have been included in batch 1, except that
nix-update also changes the formatting of source hash. It should be
possible to verify this in the same way as batch 1, except that the
commands will additionally result in non-functional source hash
changes that I didn't include here.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions