Background
When installing (or at least doing a spack spec) for access-om2 on Gadi: when you specify the git.version of libaccessom2 and either mom5 or cice5 , the build fails with:
SPEC is unsatisfiable, errors are:
internal_error("Build version weight used for reused package")
internal_error("Reuse version weight used for built package")
This fails for spack spec access-om2 ^libaccessom2@git.2023.10.26 ^mom5@git.2023.11.09 and spack spec access-om2 ^libaccessom2@git.2023.10.26 ^cice5@git.2023.10.19 , but not spack spec access-om2 ^mom5@git.2023.11.09 ^cice5@git.2023.10.19. So it must be something to do with libaccessom2. Specifying the version for only libaccessom2 (aka spack spec access-om2 ^libaccessom2@git.2023.10.26 works fine.
When doing this in a clean spack environment (i.e., in the spack-dev image) it doesn't fail.
Potential Solutions
It's something to do with spacks @git.TAG=SPACK_VERSION, specifically the autogenerated SPACK_VERSION, which might be resolving itself to the same thing for multiple packages.
CodeGat
commented
9 months ago
Background When installing (or at least doing a
spack spec) for access-om2 on Gadi: when you specify thegit.versionoflibaccessom2and eithermom5orcice5, the build fails with:This fails for
spack spec access-om2 ^libaccessom2@git.2023.10.26 ^mom5@git.2023.11.09andspack spec access-om2 ^libaccessom2@git.2023.10.26 ^cice5@git.2023.10.19, but notspack spec access-om2 ^mom5@git.2023.11.09 ^cice5@git.2023.10.19. So it must be something to do with libaccessom2. Specifying the version for only libaccessom2 (akaspack spec access-om2 ^libaccessom2@git.2023.10.26works fine.When doing this in a clean spack environment (i.e., in the
spack-devimage) it doesn't fail.Potential Solutions
@git.TAG=SPACK_VERSION, specifically the autogeneratedSPACK_VERSION, which might be resolving itself to the same thing for multiple packages.