Telcon: 2022 08 17

(Held August 17th 2022)

Attendees

• Peter Scheibel (host)
• David DelVento
• Mark Krentel
• Massimiliano Culpo
• Phil Regier
• Srinath Vadlamani
• Umashankar Sivakumar
• Wileam Phan
• Tammy Dahlgren

Agenda items

• (Davide) if I have a production install of Spack at 0.18, and I want to update Spack to 0.18.1, what do I need to be careful about?
• (Wileam) Ping on #32136 for local build cache
• (Davide) Ping on spec comparisons
• (Davide) Desire to duplicate an installation
  • The environment will not concretize the same time if you copy the spack.yaml
  • Is the spack.lock useful for this?
    • Hypothetical procedure (note: I need to make sure this will work, but currently I think this is the only way to get the desired behavior):
      • Copy the spack.lock file from the staging installation environment to the corresponding environment in the production installation
      • Also copy over spack.yanl if that changed
      • spack install in the environment in the production installation
      • (Do not run spack concretize -f or the spack.lock will be discarded)
  • The installation might have many environments (so copying one environment may not address all of it)
  • How to regenerate the lmod hierarchy

Possible Agenda items

• (Chris) Options for spack style checking of user package repos (see https://github.com/spack/spack/pull/31938).
• (Brian) Sanitizing repo, getting rid of improperly-concretized packages (i.e. how do I get rid of old stuff I don't use now)
  • (in particular reuse)
• (Mark) Ping on #27247
• (Matt) Package reuse is nice, but how can we refresh a single package?
  • E.g. want to use the newest version of spectrum-mpi
• (Matt) How does spack deprecate handle refreshing module files for packages that depend on a deprecated spec in an lmod hierarchy?
  • e.g. if you deprecate the old MPI, does the lmod refresh use the newer MPI in the hierarchy
• (Massimiliano) Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-06-08: multiple build systems used by one package
• (Matt) if we build an environment, and one package fails, then module files are not generated
  • Want spack module refresh but only to generate module files that haven't been generated yet
• Updating compiler wrapper to strip -Werror (optionally): https://github.com/spack/spack/pull/30284
• (Wileam) Adding fpm as a build system
  • Issue on fpm repo: https://github.com/fortran-lang/fpm/issues/79
• Default action for concretization in environments: https://github.com/spack/spack/pull/29942#issuecomment-1097287194
• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-06: warning() directive
• (Wileam) Can externals detection be expanded from executables only to arbitrary files (e.g. header or .a/.so library files)?
  • For llvm@13 and @14 with +gold, see issue comment and PR https://github.com/spack/spack/pull/30954
  • BLAS detection is also affected, see https://spackpm.slack.com/archives/C5W7NKZJT/p1659734369147249
• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-13: not in spec syntax
• (Phil) Issues with SSL signature authentication at SNL, see https://spackpm.slack.com/archives/G7XED8NAD/p1660009273764719