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.
The dontConfigure line can be removed in staging, as it's the default
there.
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.
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.
The previous patch was impure, because native-tls and its dependencies
weren't locked, and so Cargo would fetch the latest possible versions
from the network. This meant that the gg-jj.cargoDeps FOD was broken
since the first time native-tls or one of its dependencies released a
new version. To do this reproducibly we need to include all the added
dependencies in the lockfile.
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.
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.
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.
This reverts commit e3967be411.
The 3.3.2 tag appears to have been deleted before Hydra had a chance
to fetch it. Revert to a version that we can actually build. (An
attempt to update to 3.3.3 is currently stuck with failing CI.)
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.
Upstream sadly decided to fix the incorrect Cargo.lock we were
applying a patch for by rewriting the tag. :(
Diff of sources before and after:
diff --git 1/nix/store/yh0jcja9psq44dlis8jw93s62bfah5ys-source/Cargo.lock 2/nix/store/0l9wq5fxgxhaq0pp7p0yd38815x8rbqy>
index f01f824..e00d079 100644
--- 1/nix/store/yh0jcja9psq44dlis8jw93s62bfah5ys-source/Cargo.lock
+++ 2/nix/store/0l9wq5fxgxhaq0pp7p0yd38815x8rbqy-source/Cargo.lock
@@ -328,7 +328,7 @@ dependencies = [
[[package]]
name = "swayws"
-version = "1.1.1"
+version = "1.2.0"
dependencies = [
"clap",
"env_logger",
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.
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.
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.
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.
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.
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.
Alyssa Ross