SpackMaintenance

Debugging

Bad caches

When don't know how this happens, but it is possible to upload to our mirror a build with an incorrect path. Builds in caches are supposed to have padding so they can be installed anywhere. If they captured a non padded path, you might get a "CannotGrowString" error during installation

==> Error: Failed to install perl due to CannotGrowString: Cannot replace b'/cvmfs/mu2e.opensciencegrid.org/packages/perl/5.38.0/linux-almalinux9-x86_64_v2-gcc-11.4.1-5gvcjfeptnu6tfyg7dbfjjb76mk5moaz' with b'/cvmfs/mu2e.opensciencegrid.org/packages2/perl/5.38.0/linux-almalinux9-x86_64_v2-gcc-11.4.1-5gvcjfeptnu6tfyg7dbfjjb76mk5moaz' because the new prefix is longer. To fix this, compile with more padding (config:install_tree:padded_length), or install to a shorter prefix.

Solution is to remove these builds from the cache and re-index it

ssh products@fifeutilgpvm03.fnal.gov
cd rlc_tmp
mv /spack_cache/mu2e/build_cache/linux-almalinux9-x86_64_v2/gcc-11.4.1/perl-5.38.0 .
mv /spack_cache/mu2e/build_cache/linux-almalinux9-x86_64_v2-gcc-11.4.1-perl-5.38.0-5gvcjfeptnu6tfyg7dbfjjb76mk5moaz.spec.json.sig .
( . /home/products/spack/share/spack/setup-env.sh spack ; spack --debug buildcache update-index -k /spack_cache/mu2e )

NoVerifyException

This means that the packages you are trying to install are gpg signed, but but you haven't talk spack to trust the signatures.

==> Error: Failed to install bzip2 due to NoVerifyException: Spack found new style signed binary packages, but was unable to verify any of them.  Please obtain and trust the correct public key.  If these are public spack binaries, please see the spack docs for locations where keys can be found.

This command will go through the mirrors and find the public key signatures, and copy them in the local install

spack buildcache keys --install --trust