recipe repo issues: conflicting cray-mpich package

[j-ogas]

stack-config will error when the target recipe has a repo with /packages/cray-mpich. This appears to be because the alps repo is always added, regardless of the -r argument?

[j-ogas]

Also, it appears that one cannot get around this issue by adding a repo.yaml that defines different a namespace, e.g., mysweetrepo, with the hopes of specifying which cray-mpich to use, e.g., alps.cray-mpich vs. mysweetrepo.cray-mpich.

Found 'repo.yaml' file in `myrecipe/repo`
'repo.yaml' is ignored, packages are added to the 'alps' repo

[bcumming]

Hello @j-ogas.
Sorry for the slow reply, I missed this issue.

To summarise, you are trying to provide your own packages/cray-mpich because the default one provided by Stackinator refers to the CSCS artifactory?

Thinking about this, we could move the alps repo out of stackinator, and have the default repo be provided in the system configuration. That way it is packaged with the system-specific configuration?

[j-ogas]

To summarise, you are trying to provide your own packages/cray-mpich because the default one provided by Stackinator refers to the CSCS artifactory?

Precisely. We need to fetch our source tarballs from our internal mirror.

Thinking about this, we could move the alps repo out of stackinator, and have the default repo be provided in the system configuration. That way it is packaged with the system-specific configuration?

That sounds reasonable.