Telcon: 2022 12 14

Held Wednesday December 14th, 9am PT

Attendees

• Peter Scheibel (host)
• Mark Krentel
• David M
• Greg Becker
• Massimiliano Culpo
• Todd Gamblin
• Phil Regier
• Davide DelVento

Announcements

• Greg Becker: Improving error messages - if you wish Spack would output more info about concretizer errors. See slack discussion and PR https://github.com/spack/spack/pull/34500. Feel free to add use cases about Spack error messages to these discussions
  • Note: this specifically concerns the error messages that occur when spack concretize -f fails (or if the implicit concretization step that precedes spack install in an environment fails). If you're not sure whether your request falls into this category, feel free to bring it up and we can quickly identify whether it's the type of error message that we're aiming to improve with the PR.

Agenda

(This will be just Q&A - there are no pre-planned general Spack discussion items)

• (David) Cloning environments:
  • Have an env with a bunch of installed packages
  • Want to reinstall it on some other architecture
  • (Peter) If you use spack env, you can take the spack.yaml from the existing env, and then spack env create newenv <path/to/spack.yaml>
  • (This user was not using spack env, they were just referring to their global installation as an environment)