Emit a build list and stack diff

Goal: alongside the lock, get an install-ordered build list for a build pipeline and a markdown diff you can paste straight into a pull request. The commands below write those files under /tmp. Baseline, closure, generation, and reachability are in the glossary.

Add the two flags to solve

stack solve accepts --build-list-out and --stack-diff-out. They are independent: pass either, both, or neither.

eb-stack stack solve \
  --easyconfigs fixtures/gromacs_2025_to_next/easyconfigs \
  --stack-policy fixtures/gromacs_2025_to_next/policies/prefer_newer.json \
  --baseline-easyconfigs fixtures/gromacs_2025_to_next/easyconfigs \
  --lock-out /tmp/emit-stack.lock.json \
  --sbom-out /tmp/emit-stack.cdx.json \
  --build-list-out /tmp/emit-build.list \
  --stack-diff-out /tmp/emit-stack.diff.md

--stack-diff-out needs a baseline lock. Omit --baseline-easyconfigs and the first --easyconfigs tree is that baseline. Pass --baseline-easystack to diff against what those easystacks install. A caller that can form no baseline fails and names --baseline-easyconfigs or --baseline-easystack. There is no --baseline flag.

To diff against what a software layer already installs, pass its easystacks as the baseline instead of an older tree:

eb-stack stack solve \
  --easyconfigs fixtures/gromacs_2025_to_next/easyconfigs \
  --toolchain foss/2025b --root GROMACS \
  --baseline-easystack fixtures/gromacs_2025_to_next/easystacks/gromacs-2024.4.yml \
  --build-list-out /tmp/site.list \
  --build-list-excludes-baseline \
  --stack-diff-out /tmp/easystack.diff.md \
  --lock-out /tmp/easystack.lock.json

The baseline label is the toolchain (foss-2025b), the same shape as the solved lock. /tmp/site.list contains the version-bumped modules in build order, and leaves out what the easystack already installs:

fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenBLAS-0.3.27-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenMPI-5.0.3-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/GROMACS-2025.0-foss-2025b.eb

/tmp/easystack.diff.md opens with Baseline (`foss-2025b`) to solved (`foss-2025b`). Unchanged: 2 (FFTW, Python). Version-bumped: 3 (GROMACS 2024.4 to 2025.0, OpenBLAS 0.3.24 to 0.3.27, OpenMPI 4.1.6 to 5.0.3).

Read the build list

cat /tmp/emit-build.list

One easyconfig path per line, dependencies before the packages that need them (a topological sort over the co-selected stack, ties broken by package name for a deterministic order):

fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/FFTW-3.3.10-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenBLAS-0.3.27-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenMPI-5.0.3-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/Python-3.12.3-foss-2025b.eb
fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/GROMACS-2025.0-foss-2025b.eb

Feed this straight into a sequential build pipeline: xargs -n1 eb build, a Jenkins matrix step, or a plain shell loop.

Read the stack diff

Every co-selected package is classified against the baseline lock as unchanged, added, baseline not in this layer, or version-bumped:

# Stack diff

Baseline (`foss-2025a`) to solved (`foss-2025b`).

## Summary

- **unchanged**: 2
- **added**: 0
- **baseline not in this layer**: 0
- **version-bumped**: 3

## Packages

### FFTW: unchanged

- Baseline: `3.3.10` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025a/FFTW-3.3.10-foss-2025a.eb`)
- Solved: `3.3.10` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/FFTW-3.3.10-foss-2025b.eb`)

### GROMACS: version-bumped

- Baseline: `2024.1` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025a/GROMACS-2024.1-foss-2025a.eb`)
- Solved: `2025.0` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/GROMACS-2025.0-foss-2025b.eb`)
- Change: `2024.1` to `2025.0`

### OpenBLAS: version-bumped

- Baseline: `0.3.23` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025a/OpenBLAS-0.3.23-foss-2025a.eb`)
- Solved: `0.3.27` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenBLAS-0.3.27-foss-2025b.eb`)
- Change: `0.3.23` to `0.3.27`

### OpenMPI: version-bumped

- Baseline: `4.1.5` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025a/OpenMPI-4.1.5-foss-2025a.eb`)
- Solved: `5.0.3` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/OpenMPI-5.0.3-foss-2025b.eb`)
- Change: `4.1.5` to `5.0.3`

### Python: unchanged

- Baseline: `3.12.3` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025a/Python-3.12.3-foss-2025a.eb`)
- Solved: `3.12.3` (`fixtures/gromacs_2025_to_next/easyconfigs/foss-2025b/Python-3.12.3-foss-2025b.eb`)

A tree baseline and an easystack baseline are both labelled with the toolchain (`foss-2025a`, `foss-2025b`). Paste the file body directly into a pull request description; every line names a real version and a real easyconfig path.

Plan a site layer on EESSI 2026.06

The fixture above is one root and one small easystack. A site layer on European Environment for Scientific Software Installations (EESSI) 2026.06 uses the same flags against the trees scripts/fetch-upstream-trees.sh checks out. Source the env.sh it writes. --toolchain foss/2026.1 is the generation named by eessi-2026.06-eb-5.4.0-2026.1.yml. Pass --baseline-commits-from the clone root (git rev-parse --show-toplevel from $EB_EASYCONFIGS). env.sh sets EB_EASYCONFIGS to the easybuild/easyconfigs directory, and that value is not the git root.

There is no GROMACS-*-foss-2026.1.eb in the pinned develop tree. The newest foss GROMACS file there is GROMACS-2026.2-foss-2025b.eb. This exits 1, and the error contains no candidates for root package GROMACS:

eb-stack stack solve \
  --easyconfigs "$EB_EASYCONFIGS" \
  --toolchain foss/2026.1 \
  --root GROMACS \
  --baseline-easystack "$EB_EESSI_SOFTWARE_LAYER/easystacks/software.eessi.io/2026.06/eessi-2026.06-eb-5.4.0-2026.1.yml" \
  --baseline-commits-from "$(git -C "$EB_EASYCONFIGS" rev-parse --show-toplevel)" \
  --build-list-excludes-baseline \
  --lock-out /tmp/site-gromacs.lock.json \
  --build-list-out /tmp/site-gromacs.list \
  --stack-diff-out /tmp/site-gromacs.diff.md

On failure the same message appends dependencies the filtered universe does not provide (for example impi and imkl-FFTW). That list is the whole searched tree, not the root’s own dependencies.

A root that does exist, and that this easystack does not install, is PuLP. The same command with --root PuLP and --lock-out /tmp/site-pulp.lock.json prints:

lock=/tmp/site-pulp.lock.json packages=59

--build-list-excludes-baseline leaves one line, ending in PuLP-3.3.2-foss-2026.1.eb. The diff summary is unchanged 58, added 1, removed 272. removed is the rest of the baseline this one-root solve does not select. It is not a list of modules to uninstall. arpack-ng is already in that baseline closure, so the same command writes an empty build list and added: 0.

stack oom --arch x86_64/amd/zen4 on that easystack, with --easyconfigs "$EB_EASYCONFIGS", prints oom=0 fits=0 builds=339 nodes=2. fits=0 means no build had a row in the memory table. The warning example is the fixture in warn before a job runs out of memory.

The other checks for this layer, without a mounted prefix:

Next steps