building
    Updating git repository `https://github.com/georust/geo`
error: failed to sync

Caused by:
  failed to load pkg lockfile

Caused by:
  failed to resolve patches for `https://github.com/rust-lang/crates.io-index`

Caused by:
  failed to load source for dependency `geo`

Caused by:
  Unable to update https://github.com/georust/geo?branch=mkirk/concave-hull-fix-empty-crash#243ad260

Caused by:
  object not found - no match for id (243ad260ba9dec5fe6ab5d184ac625f6ed01b53b); class=Odb (9); code=NotFound (-3)
Traceback (most recent call last):
  File "/nix/store/c7cph7saraq1zq690ch368bjfdlmaypd-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
    main()
  File "/nix/store/c7cph7saraq1zq690ch368bjfdlmaypd-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
    assert list(data.keys()) == ["source"]
AssertionError

In reply to @jonringer:matrix.org
if you do need to apply patches before vendoring, you can declare them with cargoPatches

Interesting. I didn't know that so I used this pattern instead recently. Would cargoPatches be preferable in this case?

cargoDeps = rustPlatform.fetchCargoTarball {
    inherit src patches;
    name = "${pname}-${version}";
```https://github.com/NixOS/nixpkgs/pull/144733/files#diff-a35bcf6b38716a31d2a5ea43b4ff2e6217c591817597572a22d560fa86ba0bb8R28

In reply to @jonringer:matrix.org
if you do need to apply patches before vendoring, you can declare them with cargoPatches

Interesting. I didn't know that so I used this pattern instead recently. Would cargoPatches be preferable in this case?

cargoDeps = rustPlatform.fetchCargoTarball {
    inherit src patches;
    name = "${pname}-${version}";
}

https://github.com/NixOS/nixpkgs/pull/144733/files#diff-a35bcf6b38716a31d2a5ea43b4ff2e6217c591817597572a22d560fa86ba0bb8R28

Interesting. I didn't know that so I used this pattern instead recently. Would cargoPatches be preferable in this case?

cargoDeps = rustPlatform.fetchCargoTarball {
    inherit src patches;
    name = "${pname}-${version}";
}

https://github.com/NixOS/nixpkgs/pull/144733/files#diff-a35bcf6b38716a31d2a5ea43b4ff2e6217c591817597572a22d560fa86ba0bb8R28

Interesting. I didn't know that so I used this pattern instead recently. Would cargoPatches be preferable in this case?

cargoDeps = rustPlatform.fetchCargoTarball {
    inherit src patches;
    name = "${pname}-${version}";
    sha256 = "...";
}

https://github.com/NixOS/nixpkgs/pull/144733/files#diff-a35bcf6b38716a31d2a5ea43b4ff2e6217c591817597572a22d560fa86ba0bb8R28

In reply to @legendofmiracles:matrix.org
I'll play around a bit, thanks for the hint

nix build -f "<nixpkgs>" rustc -I nixpkgs=https://github.com/nixos/nixpkgs/archive/staging-next.tar.gz

Well, I did move it to nixpkgs now
Got it all working, but now I’m getting this error:

ab-street> error: failed to parse manifest at `/build/source/abstio/Cargo.toml`
ab-street> Caused by:
ab-street>   feature `edition2021` is required
ab-street>   consider adding `cargo-features = ["edition2021"]` to the manifest
ab-street> Traceback (most recent call last):
ab-street>   File "/nix/store/bxlx1dy64ywk6spy265jm53qz3a45yc9-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
ab-street>     main()
ab-street>   File "/nix/store/bxlx1dy64ywk6spy265jm53qz3a45yc9-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
ab-street>     assert list(data.keys()) == ["source"]
ab-street> AssertionError

[12:37:15] jon@nixos ~/projects/nixpkgs (staging-next)
$ nix-build -A rustc
/nix/store/449lmdsx8dv2q5fn4xbkxk51d4cg2zih-rustc-1.56.1