2 conflicting scotch migrations (6.1.3 & 7.0.2)

[jakirkham]

Currently there are 2 scotch migrations running that are trying to update to different scotch versions. Should we close one of these out (presumably the older one)?

Also somewhat curious how we wound up with 2 of these (as opposed to closing the old one out)

cc @conda-forge/core @conda-forge/scotch

[hmaarrfk]

Also somewhat curious how we wound up with 2 of these (as opposed to closing the old one out)

The bot will eagerly open the second one. It is "somewhat" valid to do, but it is somewhat "wasteful" of maintainer time IMO.

Currently the scotch migrations are stuck at "no solvable" so unless somebody takes action to unstuck them, they will both be open for a pretty long time.

[beckermr]

Right. We've taken some steps to mitigate this but not enough.

We added a feature where the solver checks get turned off after 90 days.

This means at least prs get issued.

We should probably just have the bot spam all prs or simply close the migration after say 9 months.

[hmaarrfk]

i wish that in the case of not solvable that an issue be opened on the feedstock instead of a merge request.

That would help me as a maintainer of the original feedstock, keep both updated.

Maybe even ping both parties.