Update dependency: kevm-pyk/src/kevm_pyk/kproj/plugin

[rv-jenkins]

No description provided.

[ehildenb]

@dwightguth any idea what's going on here? This is also blocking other PRs I guess now (eg. #2092). Maybe the two PRs need to be put together, since it's updating K and blockchain-k-plugin at the same time, and they need to sync to being updated to the same K....

[ehildenb]

I've cherry pickede the blockchain update to this PR: #2092, so this one likely can be closed if that one goes throug.h

[dwightguth]

I mean, this is kind of what I would expect to happen if you have two different submodules or pinned commits of the same repo in different parts of the recursive dependency tree of a single repo. So the solution is I guess, maybe, don't do that? Not immediately helpful for the situation you're in, I'm aware, but this type of dependency hell is going to happen under that particular scenario. If you don't want to commit to the invariant that any given repo only depends on one version of any given other repo, this is the sort of thing you'll have to work through.

[ehildenb]

Yeah, that's obvious. Thank you.

I meant more to ask, are there changes that need to happen (in the other PR), other than cherry picking the change to blockchain-k-plugin dependency over to there?

As far as fixing the dependency diamond issue, my personal opinion is that it's not worth it, since this particular problem has happened once in, how long? Maybe a year or two? But open to suggestions.

[ehildenb]

Changes subsumed here: #2092