lorri: use cargoHash instead of cargoSha256

[wolfgangwalther]

Evaluation is broken for lorri, because #323983 renamed cargoSha256 to cargoHash, but #322749 updated cargoSha256 at the same time.

Pinging @JohnRTitor and @SuperSandro2000 as those who merged the two PRs.

[emilazy]

Doesn’t look like this fixed the eval error on ofborg. cargoSha256 is meant to just warn anyway, so I wonder what’s going on here.

[emilazy]

Ah, I see – inherit cargoHash; was causing the error before. I have no idea why it’s still broken, though.

[wolfgangwalther]

Ah, I see – inherit cargoHash; was causing the error before.

Yeah, this was breaking Check pkgs/by-name / check (pull_request_target) for me in the other PR, so that should be good.

I have no idea why it’s still broken, though.

Hm. This is just because the base branch is still broken, I guess:

The branch this PR will merge in to does not cleanly evaluate, and so this PR

[wolfgangwalther]

This is just because the base branch is still broken

Which ofc is fine - because this PR only has the fix for it.

So, I guess this can't pass ofborg-eval before this is merged.

[toonn]

LGTM, I also needed this locally.

[wolfgangwalther]

I don't understand how this happened either. Looking at the commits, I can't see where it was changed back to cargoSha256. Really odd, but solved.

[emilazy]

I think it came from an automatic staging merge.