Spack Environment Rollback and Package Configuration Schema Interoperability

Question

Environment State Consistency
Spack utilizes spack env load to revert environments to previous states based on history tracking in history.json. While this mechanism manages package versions and dependencies, it operates independently of the underlying package configuration schemas used to define build specifications.

Schema Migration Constraints
When a schema change occurs within the package configuration, the migration scripts update the database to maintain compatibility. However, it is unclear if a rollback to a previous environment state automatically triggers a corresponding reversal of schema migrations or if the environment simply attempts to load old specifications against a newly migrated schema.

This creates a potential discrepancy where the environment state is reverted, but the configuration schema remains at a newer version, potentially leading to validation failures or inconsistent build metadata.

Does spack env load synchronize the configuration schema version with the target environment snapshot?
What is the expected behavior when a rolled-back environment references a package specification that is incompatible with the current schema version?

Tasadduq Burney · Answer

Answer
spack env load restores only the package specification snapshot from history.json; it does not change the Spack configuration schema version, which is tied to the installed Spack release and user configuration files.
Likely explanation
Spack’s environment history tracks concrete specs and dependencies. Schema migrations (e.g., adding, renaming, or removing package options) are applied to the Spack codebase and its internal database independently of environment snapshots. When a rolled‑back environment is loaded, Spack validates the restored spec against the current schema. If the spec uses a deprecated or removed option, validation may fail or produce a warning, and the resulting build metadata can be inconsistent.
Steps to verify and address the mismatch

Load the environment with verbose output to see the applied snapshot:
spack env load myenv --verbose
Check the active Spack configuration and schema version:
spack config show
Compare the snapshot’s spack.yaml (found in the environment’s spack/ directory) with the current config; note any schema‑related differences such as removed options.
Attempt to install a package from the snapshot:
spack install @version
Observe any validation error or warning. If the error mentions an unknown option or a schema mismatch, the spec is incompatible with the current schema.
Depending on the situation, either:

Update the spec in the environment’s spack.yaml to use the current option names, or
Downgrade Spack to a release that still provides the old schema (e.g., spack develop --scope=packages @<old-version> or install an older Spack release).

Missing diagnostic detail
To decide whether to update the spec or downgrade Spack, please confirm the exact Spack version you are running and which specific schema element (e.g., a removed package option) caused the validation failure.

Spack Environment Rollback and Package Configuration Schema Interoperability

Environment State Consistency

Schema Migration Constraints

1 answer

Answer

Likely explanation

Steps to verify and address the mismatch

Missing diagnostic detail

Your perspective belongs here.

0 question comments