See md5-hashless metadata from run https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/21928764599/job/63327858918?pr=168#step:18:55
Background
We pass in the custom installation directory for UKMO-restricted data through a spack --config-scope, not through an environment. This means that the metadata creation script is currently uninformed about the custom restricted directory, which leads to it getting the default prefix for a given package. This package doesn't have to be installed either, and since we don't have the custom scope we need, we get the assumed prefix, which has no binaries, and hence no md5 sums.
Implementation Plan
See if there is a way via spacks API to load custom configuration scopes for a given environment, or invocation.
See md5-hashless metadata from run https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/21928764599/job/63327858918?pr=168#step:18:55
Background
We pass in the custom installation directory for UKMO-restricted data through a
spack --config-scope, not through an environment. This means that the metadata creation script is currently uninformed about the custom restricted directory, which leads to it getting the default prefix for a given package. This package doesn't have to be installed either, and since we don't have the custom scope we need, we get the assumed prefix, which has no binaries, and hence no md5 sums.Implementation Plan
See if there is a way via
spacks API to load custom configuration scopes for a given environment, or invocation.