spack: User config is problematic when moving across multiple major versions at once
Steps to reproduce
$ git clone -c feature.manyFiles=true https://github.com/spack/spack.git
$ . spack/share/spack/setup-env.sh
$ module load gcc/11.2.0
$ spack install hdf5%gcc@11.2.0 target=x86_64 +cxx+fortran+hl+pic+shared+threadsafe
Error message
Information on your system
General information
- I have run
spack debug reportand reported the version of Spack/Python/Platform - I have searched the issues of this repo and believe this is not a duplicate
- I have run the failing commands in debug mode and reported the output
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 2
- Comments: 21 (10 by maintainers)
I encountered the same issue when attempting to install a new version of Spack while preserving the existing one. Deleting the old user-scope configuration files located at
~/.spack/resolved this problem.Encountered this problem, and managed to work around it by removing
~/.spack/bootstrap/(which was then recreated by the next spack invocation).Here are the contents of
~/.spack/bootstrap/config/(from before applying the workaround) in case that helps: spack_bootstrap_config.tar.gz.@mark14wu That wouldn’t surprise me. We use update functions to move from
0.Xto0.X+1, in case there is a breaking change. Usually we remove the update after0.X+2so doing a0.X+5transition all at once, while keeping configuration, might be breaking (v0.17 was deprecated a couple years ago, more or less).