The issue with scotch%oneapi is, apparently, a particular instance of division by zero leading to an FPE getting thrown (presumably because the UFSWM build has those flags enabled), possibly in combination with some internal compiler logic related to rounding. In any case we're working with the Scotch devs to confirm the exact code changes needed, which can be implemented via patch. NCO will almost certainly want Scotch built with oneAPI, so I believe this will entail a 1.9.x update to remove the conflict from the package and remove the '%gcc' requirement from common/packages.yaml.