Skip to content

Model Components Using Non-@git.REFs are not parsable by Release Database Upload #419

Description

@CodeGat

Background

PRs like ACCESS-NRI/access-spack-packages#443 have moved components using explicit @git.REF builds to @VERSION builds in which the package.py contains what the actual VERSION refers to. This is in opposition to what the release provenance database expects, which is easily-parsable @git.REFs.

Implementation Plan

  • During the in-environment parsing of provenance packages, attempt to dereference the @VERSION via spacks python API, and return that instead.
  • Also determine whether we can simplify the out-of-environment upload of packages (as in, remove the get_repo_url_at_ref_or_raise() function).

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions