All notable changes to this project are documented here.
stack capacityreads a captured scheduler snapshot and reports, per node and for an exact request, the eligible nodes, the nodes that can fit it and the free fitting slots; missing data stays unknown. The same advice is available through MCP.stack shardtakes an optional storage policy and attaches storage advice to every build phase: phases that fit the shared inode budget keep shared scratch, the rest go to node-local disk where the captured capacity allows. Footprint tables can mark packages that need a real disk.- The MCP server is described for the MCP Registry as
io.github.stackhands/eb-stack, and a workflow publishes it with GitHub Actions OIDC.
- Materialized execution lists are bound to their exact bytes, and phase advice to the generated list.
- Opaque shard roots keep their disk requirements.
- GPU slot division is checked, and CPU advice survives unknown GPU data.
- The footprint buffer used for estimates is the one hashed into the plan.
- File robot roots are normalized in
recipe check.
- The repository is
stackhands/eb-stack; links, docs and the SBOM tool vendor name the stackhands organisation.
- Static x86-64 Linux archives are published by the standard release workflow.
- Failed scheduler observations retain every reservation even when stale-record removal is requested.
- Explicit waiting forecasts arbitrate admission under the shared lock without charging each other's build peaks; setup, admitted, legacy and unknown writers retain their reservations.
- Explicit root module destinations govern installed-state checks, dependency traversal, shard weight and inode estimates without borrowing a same-named root from another module tree.
- Lifted CPU roots contribute build cost only when their destination needs installation; requested rows remain in the emitted lists.
- Mixed destination roots retain every dependency needed by another row's closure, while installed CPU and CVMFS dependencies remain reusable.
- Plan digests include the installed state of explicitly located roots.
- Cargo checksum entries with long crate filenames use multiline dictionaries within the EasyBuild line limit.
- Repeated Cargo bumps replace checksums identified by the original recipe, the emitted recipe and the fetched lockfile, including when the target recipe is present in the robot tree.
- Recipe and module directory walks stay bounded while resolving stack inputs.
- The manual groups installation, first commands and task-specific guides around the executable command surface.
- The crates.io package carries the sources, the TOML tables they include, the README, LICENSE, CHANGELOG and CITATION. The test corpus, fixtures, manual, skills, examples and delivery bundles stay in the repository; the 0.7.0 archive was 1589 files and 13.8 MiB, most of it tests.
- The manual and README describe the 0.7.x GitHub release as carrying every command, and crates.io alone as still 0.3.0; the Org pages that print a version are on the release checklist; CONTRIBUTING names the publish command.
The behaviours the develop line carried and main lacked, ported one test
at a time (120 tests by name, all green on main now).
package bump --foreign RECIPE(MCPforeign): a Spackpackage.pyor conda-forge recipe whose dependencies the bump inspects for names the source.ebnever declared, mapped through the package-config aliases.- Package config: the alias table form rejects unknown keys; empty alias
and virtual names or values, and a patch
sha256that is not a SHA-256, fail the layer;exclude_from_solvematches the post-alias provider; a child profile may be listed before its parent in the same layer; a requirement updates every row that maps to its name and keeps an existing alias. - Package catalog: an exact version wins over an unversioned sibling,
names and versions compare trimmed, a blank
sourceis a missing-source error, replacingsourceresets an inheritedformatand drops inherited checksums, switching toeasybuild-bumpdrops foreign checksums, andsource_checksumsmust be SHA-256 digests. - LuaRocks:
~>is a series range,~=a not-equal,build_dependenciesare build edges, agit+source is a git remote with its tag,hashcounts only as a 64-hex SHA-256,external_dependenciesare residuals, and the plan's easyblock isLuaRocks. Raku:ver<0.10+>is>=0.10and thever,auth,apiandfromadverbs are not the name. - A git checkout source (a commit, or a remote with no download URL)
emits a
git_configdict. - A dependency that spells the module,
('OpenMPI', '5.0.3-GCC-13.3.0'), is an exact pin on that build, from a SYSTEM recipe too; it is not a hole. - Stack pins and exclusions apply to every toolchain-qualified key of a
name; a locked pin on
Perlconstrains the GCCcore and SYSTEM builds. - The bump emits the plan's default profile; a layer's
[package] versionreaches the recipe while--versionwins; a dependency stated in both lists is rewritten when either disagrees with the lock; a vanished dependency is removed wherever its tuple sits on the line; a sibling'spatchesandchecksumsare adopted with the emitted source digest kept and the plan's patch set rebuilt;local_host_arch,local_orderandlocal_equationsderivelocal_binaryand parameterisedconfigopts. - PyPI and PEP 518 requirements gated by an environment marker are opaque
conditions, solver-excluded with a
pypi-markerresidual; build backends and overlay build tools are named only when the plan's own toolchain hierarchy provides them; a language bundle renders its patches, their checksums and configopts; the request's package index reaches the plan in prepare. - Closure: holes carry their versionsuffix into discovery, the companion
key and the cycle path, so
-MPIand-CUDAbuilds are two companions; an unversioned catalog wildcard defers to a unique versioned sibling; a PyPI or CRAN root the robot already provides closes without companions. - SBOM: only a 64-hex digest is a SHA-256 hash, the root hash is the first source that has one, overlay extensions are library components, and the GitHub archive URL is derived only from a github.com remote in any spelling.
- CRAN sanity dirs sit under
lib/R/library/<name>; a Spacktype=("build", "link")dependency is a runtime edge.
- A suffix or module spelling of a candidate answers only an exact
requirement. Against a range it compared as a pre-release of its
version, and
<5admitted a5.0.0-GCCcore-13.3.0build. - A GitHub archive whose repository differs from the package name spells
the account and repository in
source_urls;GITHUB_SOURCEwould 404. - An uppercase declared patch digest verifies, a non-UTF-8 patch copies
into the bundle, overlay claims key on the content digest, and a
dummy-spelled source toolchain bumped ontosystemkeeps its exact dependency pins. - A runtime extra that collapses onto a bundle a build-only extra already locked keeps the bundle off the build-only list.
- An MCP
eb_package_bumpcall without aforeignarray no longer fails with "argument foreign requires at least one path".
rfc9162,rfc9162-tilesandrfc9162-logcome from crates.io at exactly 0.8.1 instead of a git pin, socargo packageresolves them; 0.8.1 reads a partial tile a writer has widened through the widest one, which a reader at a checkpoint behind the tail needs.
- The stack-gap-lint delivery (report, bundle, patches) lives under
deliveries/stack-gap-lint/. Atartifacts/it sat where cargo-dist collects the release artifacts, and the 0.6.1 host step failed trying to uploadartifacts/patchesas a release asset.
- The Apple-silicon release build runs on
macos-15. Themacos-14job dist asked for was cancelled the second it was created, on every attempt, so the 0.5.3 and 0.6.0 releases never reached the host step.
- The tile log carries a sorted-run index of its records in a second,
signed index log inside it at
<tiles>/index:ledger headsigns it under<origin>/indexwith the same key once a run exists,ledger findproves the record in the tile checkpoint and the run manifest in the index checkpoint,auditchecks the index checkpoint's prefix, and a rebuild moves both logs aside. The data tile log still holds exactly the ledger's lines, soledger verifyand the signed heads are unchanged. The index comes fromrfc9162-login the rfc9162 workspace.
- The same code as 0.5.2.
dist hostrefused the v0.5.2 release because dependabot had bumped the action versions inside the generatedrelease.yml;dist-workspace.tomlnow carriesallow-dirty = ["ci"]. The link check excludes everyapi.github.comURL, not only/repos/.
- The same code as 0.5.1. The v0.5.1 tag sits on a commit whose
Cargo.lockand recorded version strings still said 0.5.0, so its release does not build with--locked; 0.5.2 is the release of that fix with every lockstep file at one version.
ledger headon an empty log signs the size-0 head without a checkpoint when no--originis given, andledger verifyof such a head skips the tile-log audit. The checkpoint origin derives from the first record's stack and year, so an empty log has none to derive; the first head after a record checkpoints as before. A site can anchor a fresh ledger on day zero without naming an origin that the first record may contradict.
stack admitfollows GPFS on which inode limit governs: the soft limit below it, the hard limit while the grace period runs (inodes_gracein the quota document, a remaining time), the soft limit again once the grace has expired. The decision reportsgraceandsoft_exceeded.- Rust 1.90 is the minimum.
ordered-float5.5.1 setsrust-version1.90.uuid1.29.0 sets 1.89.0. The CI minimum job builds every target with that compiler. rfc9162comes from crates.io at exactly 0.6.1 instead of a git revision ofleidarljos/deedar. The published crate has the same source as revisiona749a63, so leaf hashes, roots, and signed heads do not change.
EB_STACK_EBnames theebthatrecipe lintruns for--check-contrib, andEB_STACK_EB=noneskips that check with the report saying so. A host whoseebjudges a synthetic recipe that the local checks accept (EasyBuild 5.4.1 refuses the lint fixtures with "mandatory parameters not provided in pyheader: toolchain, homepage, description") made the lint tests and the SBOM page drift check fail there; the default CI, with noeb, never saw it.stack shard --lift-cpu-prerequisites(opt-in) writes CPU-only prerequisites tocpu-prerequisites.list(CPU prefix) while shared accelerator packages stay inprelude.list. Classification matches EasyBuild 5.4.2dependency_names()/ EESSI's install-path hook: build and runtime dependencies after--filter-deps, plus accelerator toolchains — not application package-name lists. CPU-only build-list roots and their missing CPU closure join the CPU list; a missing accelerator prerequisite of a CPU package is refused by resolved graph identity. Default behaviour is unchanged. A lifted recipe from a--from-committree keeps that line's source options for hashing and materialization.stack shard --easyconfigs-repo DIRreads the commit of a--from-commitline from an easybuild-easyconfigs git repository: onegit ls-treeper commit, and onegit cat-file --batchfor the easyconfigs that can decide the plan. A blobless clone serves it, and nothing is written to disk.--commit-cacheserves only a commit the repository lacks.stack shard --materialize --build-robot-path PATHwritessources/v1/<commit>/, the files the planned closures read from each commit at their commit paths with each named easyconfig at the top, a SHA-256 manifestsources/v1/<commit>.json, andprelude.local.listandshard-NN.local.list, whose--from-commitlines read that directory through--robot-pathsinstead of fetching the commit. A line that cannot run that way is copied unchanged and listed with the reason.prelude.list,shard-NN.list, and their lines are unchanged.
eb_easyblock_dry_runandeb_build_testwithrobotpass those directories and then the robot paths EasyBuild is configured with, aseb --show-configreports them, to--robot-paths. The trailing:they passed stands for EasyBuild's built-in default only, so robot paths set inEASYBUILD_ROBOT_PATHSor a configuration file were dropped.stack shardresolves a--from-commitor--from-prline as EasyBuild 5.4 does: the easyconfig the line names comes from the fetched tree, and a dependency comes from the robot path when it has a file of that name and from the fetched tree otherwise. The fetched tree used to win for dependencies too. A dependency whose fetched easyconfig differs from the robot path's is reported as a warning and undershadowedinplan.json.
scripts/gen-llms-txt.pyrunsscripts/llms_leakguard.pybefore it writesllms.txtorllms-full.txt. A link toAGENTS.md,CLAUDE.md, orGEMINI.mdfails that check unless the URL is inscripts/leakguard.toml. The manual index linkhttps://github.com/HaoZeke/eb-stack/blob/main/AGENTS.mdis allowlisted.uvx prek run -aruns the same check.
stack shardresolves a build-list line with--from-commitor--from-pragainst that commit's or pull request's easyconfigs first, then the robot path, the order EasyBuild uses. A dependency such a line shares with another shard goes to the prelude, so two shards do not build it at once.petsc4py-3.25.0-foss-2026.1.eb --from-commit=...and thePETSc-3.25.0-foss-2026.1.ebline it needs plan into one shard, PETSc first. Split over two shards, the second build stops on PETSc's install lock. A prelude line for a module only a fetched tree provides carries that line's--from-commit,--from-prand--include-easyblocks-from-*options. A fetched line that still cannot be resolved stays opaque;plan.jsongives the cause underopaque_reasonand the top-levelopaque, and the command prints awarning:line for it andopaque=<n>in its summary. A--commit-cachedownload that fails before an HTTP status exits 1 and writes nothing; the error names the cache, the commit, the URL, and the transport error. An HTTP status, including 404, stays opaque.stack shardplans a build-list line it cannot resolve as an opaque line when EasyBuild can still build it: the line carries--from-pror--from-commit, or its easyconfig is on the robot path but does not parse (a site recipe that computes its fields in Python). The line packs as its own group with the default weight and no closure, is written to its shard unchanged, andplan.jsongives the reason underopaque. Any other unresolved line is still an error and nothing is written. A list with 22--from-commitlines and seven site recipes failed whole before.examples/easyconfigs-pr-overlap/fetch-prs.shandexamples/eessi-pr-overlap/fetch-prs.shrequest each page of open pull requests and of changed files, 100 at a time. The open list does not stop at 500. A changed-file list that stops at GitHub's cap of 3000 is kept: the pull request is still written, withfile_list_truncatedset, and the record notestruncated at GitHub's limit.stack orderexits 1 when runtime requirements of one name at one toolchain have no version that satisfies every one of them. The error names each requester and the version it resolved. Eigen 3.4.1 required by LAMMPS and Eigen 5.0.0 required by SciPy-bundle, both atfoss-2026.1, is the closurestack solvealready rejects. The command writes no order file. It does not repin a recipe: choosing which exact pin to drop would describe a build the easyconfig does not ask for. Two builds of one name stay in the order when EasyBuild installs them side by side: another toolchain, a system bootstrap pair (binutils 2.40 and 2.42), or a build-only tool (CMake 3.31.11 and 4.2.1). Those are the same package keysstack solveuses.
-
stack footprints,stack shard --inode-quota, andstack admitplan a build campaign around a scratch inode quota instead of discovering it at admission time.stack footprintswritesfootprints.json, the peak build-tree inode count per software name: the peak of the new optional ledger fieldbuild.inodes_peakover the records of each--ledger, then each--tableline (Name<TAB>inodes; the larger when both name a package), then a built-in class table (CP2K 350000; LAMMPS, PyTorch, SeisSol, NVHPC, intel 150000) over a default of 60000.stack shardwrites each shard'sinode_footprint(its largest module footprint plus--inode-line-overhead, 1000 inodes per line) andmax_concurrent_shardsintoplan.json; with--inode-quota N [--inode-footprints footprints.json] [--inode-margin 100000]the cap is the most shards, largest first, that fit under the quota minus the margin, and a shard that does not fit on its own fails the run. The shard lists do not change.stack admit --quota-json FILE|- --footprint N --job ID --reservations DIR [--margin N] [--live-jobs ID,ID]admits a job when the inodes the quota still allows, minus the reservations of the live jobs, cover its footprint plus the margin; on admit it writesDIR/<job>.json, drops a reservation whose job is not live, never counts the job's own earlier reservation, prints one JSON line, and exits 0 or 78. The controller lists the live jobs; eb-stack calls no scheduler.eb_stack_footprintsandeb_stack_admitare the same commands over MCP, andeb_stack_shardtakes the inode arguments. -
ledger tilesandledger find, and a tile log beside every ledger.ledger appendwrites each canonical line into a C2SP tlog-tiles log at<log>.tiles(or--tiles DIR) through therfc9162-tilescrate, with key sidecars overmodule=,pkg=,target=,action=,route=,actor=,id=, andjob=frombuild.job.ledger find --key pkg=PETSc --key route=kvmprints the records carrying every key, each proven in the tile log's checkpoint.ledger head, andledger append --key, sign that checkpoint under the origineb-stack-ledger/<stack>/<year>(or--origin) with the ledger's Ed25519 key.ledger verifyalso checks that the tile log extends the signed head with the same lines and that its checkpoint is signed by the same key, so a changed tile, a rewritten tree state, or a tile log of another ledger is status 1.ledger tileswrites the tile log for an existing ledger or brings it up to date; a tile log that disagrees with the ledger is moved to<dir>.stale-<time>and rebuilt.routeis a new optional record field:native,kvm, orqemu.eb_ledger_tilesandeb_ledger_findare the same commands over MCP, and the other ledger tools taketilesandorigin. -
stack shard --commit-cache DIRreads the trees of--from-commitand--from-prlines from DIR and downloads the missing ones: a commit fromcodeload.github.com/easybuilders/easybuild-easyconfigs(its.ebfiles only), a pull request's changed easyconfigs at its head fromapi.github.com.--commit-tree COMMIT=DIRand--pr-tree N=DIRname trees already on disk.eb_stack_shardtakescommit_cache,commit_treeandpr_tree. -
ledger append,ledger head,ledger show, andledger verifykeep a per-stack software ledger: one JSON Lines file of install, rebuild, retire, move, access, removal, finding, and correction records. Each line is canonical JSON (keys sorted, no whitespace, integers only) with itsindexandidfilled in, and its leaf is the RFC 9162 leaf hash of the line, from therfc9162crate. Heads are signed with Ed25519 under the domaineb-stack-ledger-v1; the key is a PEM path passed on the command line and is refused inside the log's directory.ledger verify --record N --head HEADchecks an inclusion proof andledger verify --from HEAD1 --to HEAD2a consistency proof, so a removed record or a rewritten log is status 1.eb_ledger_append,eb_ledger_head,eb_ledger_show, andeb_ledger_verifyare the same commands over MCP. -
stack order --installedstops the build order at modules already on the machine. A file is a module listing and a directory is an Lmod tree, read the same way asstack gap --installed. The version is the full module version. A listed module is left out of the order, and so are the dependencies that were installed with it.--filter-depsstill drops dependencies first. The modules that remain are chosen with the synthetic GCC-family rulerecipe hierarchy --exportprints. Stdout reportsinstalled=as how many modules the walk stopped at.eb_stack_ordertakes the sameinstalledlist. -
The Model Context Protocol manual lists one tool for every CLI command.
docs/orgmode/reference/mcp.orgnames each tool, including the recipe and easyblock tools that have no command. A test fails when a subcommand's tool is absent from that page. -
stack shadowreports a site-layer recipe that shadows a module the EESSI base stack already provides.--baseis an Lmod tree or a module listing, loaded with the same inventory reader asstack gap. The same software version issame, another version of that name isdifferent, and a base name with no recorded version isunversioned. A name the base does not have is not reported. The command exits 1 when any recipe shadows, or when a recipe does not parse.eb_stack_shadowis the same check. -
stack providedincludes the one-based build-list line on everyprovidedandunparsedfinding in its text report, as it already did for hook, toolchain, family-lock, and licensed findings. -
scripts/dump-module-trees.shcaptures the live site, older EESSI, and target EESSImodule -t availinventories in isolated, purged shells forstack gap. It sources the Lmod bash init when the shell has nomodulefunction. It exits with the module name and the Lmod error when a purge or load fails. It then writes no inventory for that tree. -
stack gapwritesversion-change.tsv, one row per version in the site and older-EESSI inventories. A module in the target ismovedand names its EESSI version; an excluded module issite-only; every other missing route isgoneuntil it lands. -
stack solvewarns on standard error when a foss solve's baseline easystack names an LLVM-family recipe (lfoss,lompi,lfbf, orllvm-compilers) and the stack diff marks that package added. The foss universe cannot see that family, so the added row is the site layer by mistake. The solve still exits 0. Keep one lock per toolchain family, or pass--baseline-also-toolchainfor that family.llvm-compilers-20.1.8andllvm-compilers-21.1.8are the versionsdata/eessi-generations.tomllists for generations 2025b and 2026.1. -
component-reachandrebuild-setrecord a reach class:cross-user,network-facing,local-only,not-reachable, orunclassifiedwhen no built-in name and no--reachabilityfile names the package.component-reachuses the built-in names only.cross-userandnetwork-facingjustify a backport. Component-reach schema is 2. Rebuild-set schema is 5. The component-reach summary printsreach=.rebuild-set.mdends with the class of each patched easyconfig.--reachabilityonrebuild-setapplies to that map as well as tobackport.md. -
stack sbom --backport-listwrites that list for a stack lock.--cveresolves an advisory through Open Source Vulnerabilities (OSV).--osv-cachereads recorded responses and, without--cve, every id inqueries.json.--reachabilityis the samename classfile asrebuild-set. Blast radius is the module plus every locked module that depends on it through a runtime or build edge.local-only,not-reachable, andunclassifiedare recorded and left off the list. A.mdpath also writes the sibling.json.eb_stack_sbomtakes the same optional arguments and reportslisted,recorded, andstackwhen the list is requested. -
stack shardsplits one Jenkins build list into shards that can build at the same time. A line's set is its closure over--easyconfigsminus the modules in--installed-modules-dirLmod trees and--installedlists. Lines whose own easyconfig another line needs share a shard; any other module two or more shards need goes toprelude.list. Groups are packed into at most--shardsshards by--weightsseconds, or one per module.shard-NN.listkeeps the input lines verbatim, dependencies first, andplan.jsonrecords the closures, the shard weights and a SHA-256 of the inputs. A line that cannot be resolved exits 1 and writes nothing.eb_stack_shardis the same command over MCP. -
stack oom --hooks FILEreadsPARALLELISM_LIMITSfrom an EESSIeb_hooks.pyin place of the hook rows ofdata/eessi-bot-resources.toml. The file is parsed as Python and never run. A key may be a module-level string constant such asCPU_TARGET_A64FX, and a repeated key keeps its last value. Adivide_by_factorthat is not an integer is a warning that names the file and line (16 // 2.5is6.0, a float). An op other thandivide_by_factororset_maximum, a**unpacking, or a key that is not a string exits 1 with the line.eb_stack_oomtakeshooks. -
stack oom --hooks FILEwarns on a statement that adds to a name and drops the sum, such asmsg+ "..."in the EESSIpost_ready_hook: the second half of its log message never prints. The warning names the file, the line, and the function;msg += "..."is not reported, and the parallel levels do not change.eb_stack_oomreturns these ashook_warnings. -
stack oom --nodeprints the memory cap beside the level the hook leaves, for a package with anmib_per_job:min(current, memory_mib // mib_per_job), the same quotient asmemory_bytes // (mib_per_job * 2**20). It is not raised to 1, somemory cap 0 (...), not one N MiB job fitssays one compile needs more than the node has.--mib-per-job FILEis a visible alias of--job-memory FILE. Thememorycolumn,limit_by_memoryin place of the hook, is unchanged. -
stack oom --parallel Nand--max-parallel Nmodel a job that sets EasyBuild's--parallelor--max-parallel; the bot sets neither. EasyBuild uses--parallelin place of the core count, capped at max-parallel andmaxparallel. The EESSIpost_ready_hookstill applies its op to the node's cores (det_parallelism()with no arguments) and keeps the result only when it is lower: with--parallel 12on 16 cores libxc gets 16 // 2 = 8, and with--parallel 4it stays at 4. The--nodelines and a warning'sparallelline name the setting that decided, and say when the hook's result was not lower. 0 for either flag is status 2.eb_stack_oomtakesparallelandmax_parallel.
data/build-memory.tomlrecords software-layer #1772 bot job 221273: libxc 7.0.0 with GCC 15.2.0 ran out of the 32 GiB zen4 job atmake -j 5, under a libxc divider of 3 in the software-layer-scripts commit the job used. The zen4 figure is now a lower bound of 6.4 GiB per process, 32 over 5, in place of 4.0, 32 over 8. A libxc warning on that node reads8 x 6.4 GiB = 51.2 GiBand suggestsmaxparallel = 4in place of 7, a divider of 2.5 (6 processes, 38.4 GiB) no longer fits, and the remedy names a reduction of 8, as asked in the review of software-layer-scripts #337 (issuecomment-6599147327).
- The command map lists
stack gaponce: it routes each site module the stack lacks, names the recipe that closes it, and writes one TSV per route.campaign finding claimandcampaign finding resolveeach have a row.stack oomhas a usage block for--arch,--easystack,--easyconfigs,--installed,--profile,--resources,--node,--job-memory(alias--mib-per-job),--hooks,--parallel, and--max-parallel. - The manual index links
llms.txt,llms-full.txt,AGENTS.md, the skills directory, andserver.json, the same discovery files the README names. Client setup stays on the Model Context Protocol page. - How to split one Jenkins build list into shards that build at the same time, with the shared dependencies in a prelude.
- How to plan software-layer pull requests whose builds do not overlap, including the second-version warning a batch records.
- How to regroup a Jenkins build list under the section headers of a previous list.
- How to write a stack lock as the YAML
eb --easystackreads. - How to read the easyblock class, the template values, and the toolchain hierarchy EasyBuild derives.
- How to report the newest stable upstream release of an EasyBuild recipe, and why a listed version was kept or dropped.
- How to read the reproduction scoreboard and hold it to a ratchet file.
- How to report a site-layer recipe that shadows a module the EESSI base stack already provides.
- The out-of-memory how-to checks two forms of libxc's row with
--hooks: a cap of 8,(set_maximum, 8), the form proposed in the review of software-layer-scripts #337, and a reduction of 8,(divide_by_factor, 8), as asked in the review of #337 (issuecomment-6599147327). On the bot's 16-core nodes the cap gives 8, the same as dividing by 2, and pull request 1772 still warns on the 32 GiB zen4 node; the reduction gives 2 and fits. A cap does not scale with the node: it gives 8 on 64 cores and on 12. The fixtures arehooks/set-maximum-8.pyandhooks/divide-8.py.
stack solve in 0.3.0 took the policy file as --policy. The flag is
now --stack-policy, the same spelling package plan and package bump
already used. --policy remains a hidden alias: --help does not list
it, the file is read the same way, and the command prints
warning: --policy is accepted for compatibility. Use --stack-policy.
The Model Context Protocol argument policy warns and is still read;
stack_policy is the spelling to pass. Commands added since 0.3.0
include stack gap, stack oom, stack from-commit, rebuild-set,
pr-overlap, and component-reach.
stack providedfails when a build-list line names software an installed-module list or a baseline lock already provides. The match is the package name, so a different version or toolchain still fails.--allowkeeps a second version. The same command fails a toolchain other than 2026.1 or GCCcore-15.2.0 below it, a per-line--hooks, and a name that only--family-lockcovers.--licensed-filewarns for group-restricted names.--format githuband--format jsonare the CI reports.eb_stack_providedis the same check.stack gaproutes a missing name through an open software-layer pull request (--open-layer) and an open easyconfigs pull request at the generation (--open-easyconfigs), and writes one TSV per route. A toolchain whose version is the generation (lfoss-2026.1) counts as a recipe on that generation, as does an extra toolchain fromdata/eessi-generations.toml.stack gap --site,--older, and--installedread an Lmod module tree ormodule -t avail/module spider -ttext.--olderis an EESSI version loaded beside the site.--installedrepeats for a CPU tree and an accelerator compute-capability tree.--eessi-versionkeeps--open-layereasystacks of that version. The open-pull-request match stays the filename the pull request adds.stack oomwarns when aPARALLELISM_LIMITSdivide_by_factoris not an integer.eb_hooks.pycomputesmax(1, parallel // factor), and a non-integer factor makes//return a float (16 // 2.5is6.0;16 // 2.0is8.0). The estimate uses the numeric floor. The same command modelsset_maximumasmin(parallel, n), a CPU-target key overriding*, and the A64FX divide by 4.limit_by_memory(parallel, mib_per_job)ismax(1, min(parallel, memory_mib // mib_per_job)).memory_mibis the smallest cgroup v2memory.maxon the process's cgroup path, in MiB, orMemTotalwhen no cgroup v2 limit is set.data/job-memory.tomlholdsmib_per_jobper package. A row with no number is unmeasured. libxc 7.0 is unmeasured; its peak has not been measured.--node CORES:MEMORY_MIB[:TARGET]prints the hook parallelism beside that rule.--job-memoryreplaces the table.scripts/compile_rss.pyis a compiler launcher forCMAKE_C_COMPILER_LAUNCHERand for aCCwrapper. It recordsgetrusage(RUSAGE_CHILDREN).ru_maxrssper compile.--summarizepicks the worst compile and suggestsmib_per_jobwith one quarter of headroom. The suggestion is arithmetic on the log, not a measurement of a named package.
stack gapclassifies--filter-depsnames asfiltered. They wereexcluded, in the same bucket as a--exclude-fileline.- The markdown stack diff labels a module the baseline has and this solve
did not select as
baseline not in this layer. The machine-readable kind staysremoved. - Rust 1.88 is the minimum.
time0.3.55, pulled in by cyclonedx-bom, setsrust-version1.88.0. The CI minimum job builds every target with that compiler. scripts/fetch-upstream-trees.shexportsEB_EASYCONFIGSas the robot directoryeasybuild/easyconfigs. The clone root isEB_EASYCONFIGS_DEVELOP.
- A root with no easyconfig on the requested generation is a missing
recipe, including after the GCCcore, gompi, and foss hierarchy is
searched. The error lists the toolchains and versions that have an
easyconfig and names the nearest file to pass as
--toolchain. - A CVE whose only OSV range is GIT is mapped onto release versions.
component-reachuses the advisoryversionslist when it names the releases, and otherwise resolves upstream tags with a cached blobless fetch. An offline lookup keeps the range unparsed. - A package layer's
source_checksums(one SHA-256 per plan source) is applied to the plan and used as the bump checksum when--source-checksumis absent. The command-line digest still wins. SeisSol's layer records the recursive git archive digest and marks Eigen build-only; a bump moves an existing runtime Eigen tuple intobuilddependencies.-DCMAKE_BUILD_TYPE=Releasestays in the SeisSol config options. - Verification commands and the doctor
eb --versionprobe setEASYBUILD_TMPDIRand the target's EasyBuild environment, the same workload prefix a build uses. Compiler-wrapper scrubbing is unchanged. - A CUDA + usempi package listed in overlay policy (
gromacs) getsmpi_numprocspinned on bump (default 2) instead of inheriting$parallelas NUMPROC, andpretestoptsthat count visible GPUs and disable direct GPU communication only on the library-MPI iteration.recipe lintwarnsEB_MAINT_MPI_TEST_RANKSwhen the rank pin is missing. examples/eessi-pr-overlap/fetch-prs.shrewritesraw/andprs/from scratch on every run, so a pull request that closed or stopped touching easystacks does not persist from a stale run; it fetches every pull request head in onegit fetch --stdin(with automatic gc off and two retries) instead of a shallow fetch per pull request that could fail with git exit 128; it reaches the count line and exits 0 when no head easystack names afrom-commitorinclude-easyblocks-from-commitpin; and it clears its three shellcheck findings (SC2178/SC2128 from reusing thefilesarray as a string, SC2012 fromls | wc -l). It matches the easyconfigs script.examples/eessi-pr-overlap/fetch-prs.shreads every open pull request. It listed them with agh pr listlimit of 500 and dropped the rest without a message. It now pages through the pulls API 100 at a time, as the easyconfigs script does, and printsopen pull requests: N.stack arch --probe-sourcesandeb_stack_archwithprobe_sourcesprobe only the architecture families--arch(arch) names. They probed x86_64, aarch64 and riscv64 whatever--archsaid, so--arch x86_64failed on aarch64 and riscv64 wheels, and a recipe that does not parse on an unrequested family aborted the command withsource probe:. With no--archall three are still probed. With one family there is nothing to compare with, so a source it cannot fetch isunreachablerather thanarch-missing, and still exits 1. Two families compare only with each other: a miss isarch-missingwhen the other named family fetched that source slot, andunreachablewhen neither did.classify_build_failureclassesNo space left on deviceandDisk quota exceededasresource. A full disk in an EasyBuild log wascompilebefore.- A version bump moves the file name in a positional checksum's trailing comment to the new version.
- A version bump moves a
local_*commit that is the old release tag's commit to the new tag's commit (RStudio-Server'slocal_git_revnamed the previous release). - A bump writes a package-config layer's build requirement into
builddependencies, and splits a layer's longconfig_optionsintoconfigopts +=lines.build.extra_config_optionsadds options after the recipe's ownconfigoptsexpression. - A package-config layer parameter replaces the recipe's whole value: the
old value's
+=continuations are removed, and aconcatvalue that does not fit one line is written askey =thenkey +=lines. pr-overlap --kind easyconfigsapplies--filter-depsbefore the reverse walk. A filtered dependency such as Java or CUDA is left out ofreverse_dependentsand does not create adepends-onrow.pr-overlap --kind easyconfigsputs a patched easyconfig, and every reverse dependent classedmust-rebuild, intoto_build.reviewandno-rebuildstay on the record and out of the build set.--merge-orderand--impactschedule that set. A pull request that patches a module is ordered before a pull request that builds a dependent of it.- Tests that write a script and then execute it write the file from a
short-lived shell. A sibling fork can no longer leave that script
busy at exec (
Text file busy, ETXTBSY). stack orderreadsEASYBUILD_FILTER_DEPSwhen--filter-depsis omitted, and the flag wins when it is passed. The filtered dependency and the dependencies it would have pulled stay out of the order.stack order,pr-overlap,rebuild-setand the reach commands do not resolve a bare dependency tuple to a SYSTEM recipe. An explicit SYSTEM tuple still does, matchingstack solveandrecipe check.- The build list names every locked module, including two versions of one name at one toolchain, and lists runtime and build dependencies first. It is keyed by name, version, versionsuffix and toolchain, the same identity as the closure SBOM.
--mergedand--impactsay a pull request has no record when it is in the input but changes no easyconfig and no easystack. A number that is not in the input is still reported as unknown.stack solvenames the SYSTEM tuple when a dependency exists only there, the same hintrecipe checkprints.stack solvedoes not resolve a bare dependency tuple to a SYSTEM recipe. A stack whose only candidate is at SYSTEM is rejected unless the tuple names SYSTEM or the recipe itself is SYSTEM.- A closure SBOM keys each component, its checksums and its dependency entry by name, version, versionsuffix and toolchain. Two versions of one name keep their own edges and hashes.
- An unreadable easyconfig tree prints its operating-system error once.
campaign finding claimremoves its lock guard when the claim ends, including when the state file is missing.--merged Nexits 2 when pull request N has no overlap record, the same rejection--impactalready used, and writes no output.recipe check --recipeandrecipe formatname the recipe when the file cannot be read.recipe checksays a bare dependency tuple does not reach SYSTEM, and suggests('Name', 'version', '', SYSTEM), instead of listing SYSTEM as a hierarchy member or a generation.- A missing
--locknames that path once. component-reachrejects a purl type with no carrier model before it creates--out-dir.- An empty
--toolchain-name, or an emptytoolchain_namein a Model Context Protocol (MCP) call, is a usage error. 0.3.0 kept the empty name: inspect wrote a manifest with no toolchain name, and bump failed later on toolchain-<version>. - MCP
policywarns and is still read, the same way the CLI treats--policy.stack_policyis the spelling to pass. - MCP
mergedandimpactreject a bare number. They take an array of pull-request numbers, the same shape as the repeated CLI flags. - The Sphinx build does not start when Org export left
docs/source/index.rstmissing or empty. Rust API generation deletes only the generated tree underdocs/source/crates. - Org export to reStructuredText resolves deferred element values
before ox-rst reads them, and fetches ox-rst
b73eff187eebac24b457688bfd27f09eff434860into a cache outside the tree after checking its sha256.emacs -Qkeeps a user-installed Org or ox-rst from changing the build. A page that fails names its file and the export exits non-zero. Org 9.7 stores~code~text as anorg-element-deferredobject; ox-rst passes that object to a string function. - A foreign package plan no longer treats a SYSTEM bootstrap recipe
(
CMake-3.18.4,pkgconf-1.8.0) as the dependency for a generation that already has that tool on GCCcore. A dependency that names the SYSTEM toolchain still uses the bootstrap recipe. A name that exists only at SYSTEM, such as Java or CUDA, still resolves there, and the emitted recipe writes it('Java', '17', '', SYSTEM). 0.3.0 wrote('Java', '17'), which EasyBuild reads as a build with the recipe's own toolchain. stack solvelabels a baseline parsed from easyconfigs with that baseline's toolchain (foss-2025a), the same shape as the solved generation label.- The build list and stack diff in
docs/orgmode/howto/emit-reports.orgare the filesstack solvewrites for the GROMACS fixture, including Python and OpenMPI 5.0.3. - An easystack baseline uses the same toolchain label as the solved lock
(
foss-2025b), notbaseline-from-easystack-foss-2025b. - Recipe lint modules live under
src/eb_style/sosphinx-rustdocgencan open them. A#[path]attribute is joined onto the parent file and the generator then fails to read the module. A pull-request ref is writtenrefs/pull/N/head. eb-stackprints a failure aserror:and the cause chain. A missing file or a rejected value no longer appends a stack backtrace.- A rejected flag or flag combination exits 2. A missing file, a parse
failure, or a failed check exits 1. See the exit status table in
docs/orgmode/reference/cli.org. - Input failures name the flag, the path, and the value. A pull-request
record that is the wrong shape names
--prand the file.--versionand--generated-atthat do not parse are rejected. A--changedpath that is not a file is not treated as an easyconfig name. A write that fails names the path. target doctorreports a probe that cannot be started as a failed check and still prints the other three layers. A missingpodmanoreessi_container.shused to abort the report before any check was shown.- Profile locks keep a standard robot path from
easybuild/easyconfigs/and otherwise only the recipe filename. A relative--easyconfigspath no longer records the checkout prefix. - Campaign finding summaries name the failure class and the numeric exit status. A command that exits 1 reads as exit 1, and a probe that never starts reads as having no exit status.
eb_package_planreadspackage_index, andeb_package_bumphonorsstrict_patches. Both flags already existed on the command line.eb-stack easyblock-reachkeeps aneasyblockkey on acomponentsorexts_listassignment the parser had to skip. GFE's component list is a comprehension plus a tuple, and that tuple namesCMakeMake.eb-stack easyblock-reachfollows a nested easyblock class and a module-level name bound to a class. QuantumESPRESSO'sEB_QuantumESPRESSOcmake(CMakeMake)is nested insideEB_QuantumESPRESSO, so a change toCMakeMakelists that class and the QuantumESPRESSO easyconfigs. A framework module still reaches the easyblocks that import it and their subclasses.eb-stack pr-overlap --kind easyconfigscountsdepends-ononly when the added module is new to the base tree. An added file for a module the base already provides is not a dependency of another pull request.eb-stack easyblock-reachfollows imports througheasybuild.frameworkandeasybuild.tools. A change totools/run.pyreaches an easyblock that importstools/filetools.pywhen that module importstools/run.py. An easyblock that only imports another easyblock is not reached that way.- The tutorial and how-tos run from this checkout. Upstream EasyBuild
trees come from
scripts/fetch-upstream-trees.sh.pr-overlap,component-reach,rebuild-set, the GROMACS bump, the easystack diff, and the Spack externals script use files in this checkout. A missing EasyBuild program isexamples/targets/missing-easybuild.toml; claiming its finding is the repair how-to. recipe templates --helpsays--exportprints the constant table and the derived-key rules, and that--namewith--versionprints the resolved values.EB_DEP_EMPTY_VERSIONis an error; the command reference no longer lists it as a warning.recipe easyblockuses the framework character map. Thefiletoolskeys writtenr'\''andr'\\'are two-character strings,\'and\\.encode_stringlooks up one character at a time, so'and\pass through. Decoding_apostrophe_and_backslash_writes those keys back.recipe lintJSON includesinfoandin_reviewwhen a finding sets them, the same fieldseb_recipe_lintalready returned. AnEB_FMT_PERCENThit on a%%(...)sescape is info and does not count againstclean.recipe lintaccepts the template names EasyBuild defines: the*minverforms (pyminver,javaminver,perlminver,rminver),cuda_cc_gencode, and the version aliases (ver_maj,ver_maj_min,ver_min,ver_min_patch,ver_patch,version_prefix,version_suffix). Triton was reported asEB_TEMPLATE_UNKNOWNfor%(pyminver)s.EB_CHECKSUM_COUNTcountspostinstallpatcheswith the other patches, and counts sources a file appends in a loop or builds with a comprehension. A length that is only known after the file runs, including a branch onARCH, is left alone. libtool, Geant4-data, Quantum ESPRESSO, glslang and the model recipes were reported as missing checksums they have.recipe lintno longer reportsEB_TEMPLATE_UNKNOWNfor an even run of%in front of(name)s. EasyBuild preserves%%(source)sso the easyblock can format it; STREAM'scmds_mapis that pattern.package planagainst an overlay that is not a full robot names the missing package, the trees it scanned, and--easyconfigsor--easybuild-sourcewith an upstream easybuild-easyconfigs tree fromscripts/fetch-upstream-trees.sh.- An unknown
criteriaentry fails the solve. It used to be dropped, so a typo such as-newestsolved with no optimisation criterion at all and the lock recorded an empty list. stack-diff-outwith no baseline names--baseline-easyconfigsand--baseline-easystack. The previous text told the caller to pass--baseline, which the command line does not accept.eb_campaign_runreports a failed campaign as a tool error. The CLI exits 1 after printing the state. The MCP result now setsisErrorand returns that same state.- A package-plan SBOM keeps a build-only, host-only, or test-only
dependency off
dependsOn. Those refs areeb_stack:buildDependsOnon the root, the same convention a stack SBOM uses. A dependency with no role, or with a run role, stays ondependsOn. stack solve --sbom-outreads dependency edges and source checksums from the easyconfigs the lock names, the same documentstack sbomwrites for that lock.- A relative
easyconfig_pathin a stack lock is the recipe beside the lock file when that file exists, and otherwise the same path against the process directory.stack sbomandeb_stack_sbomshare that lookup and reportrecipes_read,recipes_unreadable, andwith_artifact_facts. eb_stack_sbomreads dependency edges and source checksums from the easyconfigs a lock names, the same wayeb-stack stack sbomdoes. A runtime dependency is a CycloneDXdependsOnedge. A builddependency iseb_stack:buildDependsOn. An unreadable path still contributes nothing, and the document does not invent edges between every package.- A
pyproject.tomlwas never parsed:text.parse::<toml::Value>()reads a TOML value rather than a document, so every build requirement a project states was dropped in silence, and an sdist's own top directory hid the file from the lookup as well. With the data flowing,setuptools,pipandwheelare recognised as coming with the Python module, a backend and its module are one name (poetry-coreis built bypoetry), and a build requirement the tree carries no module for is dropped with a residual rather than kept as a dependency nothing can satisfy. stack solveagainst the upstream tree no longer reports a foss generation as unsatisfiable. A name the system level carries at several versions is one package per version, because that level is the bootstrap layer and every dependency on it pins a version exactly: binutils 2.40 builds the GCCcore that builds binutils 2.42, and EasyBuild installs both.foss-2025alocks 63 packages.- Every easyconfig upstream publishes now parses: 0 skipped of some 20,600,
down from 91. The forms that were being lost, each of which dropped a
whole recipe rather than one field:
version[2:]andpatchlevels[0], a dependency list written with braces (a set, which EasyBuild iterates and builds),[...] + local_extra, a bareARCH, an arch-specific dependency version ({'arch=x86_64': ...}, nine recipes and theJavawrappers), and the string methodssplit/join/replace/lower/upper/strip. - A
versionsuffixthat was assigned and could not be read is refused, on the rule already covering dependency lists: the suffix is part of the module name, so reading it as absent gives the recipe an identity it will not install under. - Recipes are read the way a robot path actually writes them: a
#inside a multi-linedescriptionis no longer a comment (Doxygen names C#, and the closing"""was going with it), f-string versions are read,%%collapses when a recipe formats a template through%,%(pyver)sand its CUDA / R / Java / Perl siblings come from the dependency rather than from the recipe's own version, and('gettext', '0.19.8.1', '', True)means the system toolchain. Skipped easyconfigs across upstream fall from 91 to 43 of some 20,600. - The system toolchain is recognised under its former name,
dummy, which 1374 recipes in a 2019 tree still use. - A dependency that names a module rather than a bare version resolves:
GCC
8.2.0-2.31.1for version 8.2.0 with versionsuffix-2.31.1, and binutils 2.26 with versionsuffix-GCCcore-5.4.0for the build at GCCcore-5.4.0. component-reachhonours the purl type.pkg:cargo/curlandpkg:npm/curldo not match the cURL easyconfig. A purl type with no carrier model exits 2.- An Open Source Vulnerabilities (OSV) range that is not SEMVER or ECOSYSTEM, or an event that does not parse, is reported. A package whose ranges were all unparsed counts as review.
- A Common Vulnerabilities and Exposures (CVE)
component-reachrun sums closure counts into the summary.changed,must-rebuild,review, andno-rebuildcome from the carriers.
rustls-webpki0.103.13 -> 0.103.16 andwebpki-roots1.0.9 -> 1.0.10. 0.103.16 rejects certificate paths that contain the distrusted eMudhra emSign intermediate public keys. 1.0.10 removesemSign ECC Root CA - G3from the bundled root store. The 0.26.11 compatibility crate re-exports that store, so the lock resolves it to 1.0.10.
-
The manual defines closure, generation, baseline, reachability, and the claim ladder in the glossary, and the pages that use those words point at it.
-
stack gap --helpnames fixture files in this repository. A missing--sitefile exits 1 and names the path. -
package plan --helpnames both--package-indexshapes. A file that contains aPackage:field is the CRANPACKAGESindex. A file with noPackage:field is aname==versionlist. -
The install notes require Rust 1.88, write the binary with
install -Dm755to~/.local/bin/eb-stack, and say to put~/.local/binonPATH. The published 0.3.0 binary lacksstack gap,stack oom,stack from-commit,rebuild-set,pr-overlap, andcomponent-reach. A build of this tree printseb-stack 0.4.0. -
The site-layer walk in
docs/orgmode/howto/emit-reports.orgrunsstack solvefor EESSI 2026.06 against the treesscripts/fetch-upstream-trees.shchecks out. There is noGROMACS-*-foss-2026.1.ebin that pin, so the command exits 1 and names the easyconfigs that do exist.baseline not in this layerin the diff is the rest of the baseline a one-root solve did not select. -
Crate keywords are
easybuild,resolvo,sbom,hpc, andmcp. Categories addparser-implementationsandconfigtocommand-line-utilities,development-tools, andscience.pyproject.tomlrecords the same keywords and the PyPI classifiers. The README points atllms.txt,AGENTS.md, the skills, and the Model Context Protocol setup. -
Each HTML page takes its meta description from the first body paragraph.
robots.txtnames the sitemap. The build copiesllms.txt,llms-full.txt, and each page's markdown into the site, and a page that has markdown links that file withrel="alternate". -
server.jsonis the Model Context Protocol registry manifest for cargo packageeb_stack. The manual pagereference/mcprecords the stdio client configuration. The README includes the visiblemcp-name: io.github.HaoZeke/eb-stacktoken. -
Skills for inspect, plan, bump, a stack SBOM, pr-overlap, and the Model Context Protocol server live under
skills/. Each command in those files is one the currenteb-stackbinary runs.AGENTS.mdlists them next to the packaging skills. -
AGENTS.mdnames the gates CI runs:cargo fmt --all --check,cargo clippy --locked --all-targets -- -D warnings,cargo test --locked --all-targets,cargo package --locked,uvx prek run -a, andpixi run -e docs docbld. -
scripts/gen-llms-txt.pywritesllms.txtandllms-full.txtfromdocs/orgmode, plus one markdown file per page. The docs build regenerates the page files. They are not stored in git.llms.txtis the index from the llms.txt specification: a title, a short summary, and lists of links to those pages.cargo test --test llms_txtfails when the committed files drift from the manual. -
Reference and explanation pages use the same checkout checks as the tutorial and how-tos. Bash examples name files that exist in this tree or under
/tmp, and the pages drop the wording those checks reject. -
Walkthrough commands write build lists, locks, SBOMs, diffs, order files, and hash files under
/tmp. -
The pull-request how-to runs on recorded software-layer pull requests 1585 and 1728 and on the recorded open easyconfigs pull requests. The reference example uses those same files.
-
The dependency-closure page runs on recorded slices of easybuild-easyconfigs develop
981d2123, the v5.4.1 easyblocks, framework, and easyconfigs tags, the conda-forge zlib feedstock ate34000ac, and the Spack zlib package ata19611de.docs/examples/sbom-blast-radiusis removed.tests/sbom_page_drift.rsreruns every command on the page. -
The easyconfigs overlap how-to names
pr-overlap --openas the command that fetches pull requests, and its merge-order heading names the easyconfigs depends-on edges.fetch-prs.shis the collector for a clone that already hasghand git. -
The PyPI and Comprehensive R Archive Network (CRAN) how-tos describe the easyblocks the planners emit. A CRAN plan keeps
easyblock = RPackageand emits aBundlerecipe. The command map includesrepro summary. The idle campaign example omitscurrent_recipe, which the state file omits when no recipe is active. -
Keep each command span on one line on the dependency-closure page, and put the remaining actors next to their verbs.
-
Record the dependency-closure page against the commands. The examples directory contains the checksum recipe, both pull-request files, the curl recipes, the easyblock tree, and
Tool-1.0.eb. A test reruns every command on the page and diffs the output. The stack document and the package-plan document keep a build-only dependency offdependsOn. -
Tighten the dependency-closure page. Spell out SBOM, CVE, and MCP on first use, and rewrite the sentences a prose review flagged. Command lines and recorded output are unchanged.
-
Explain what a dependency closure answers, with the fixture commands for a planned stack SBOM, a recipe bump, a checksum-dict version bump, the MCP schema, pull-request overlap, rebuild-set, component-reach, and easyblock-reach. See
docs/orgmode/explanation/sbom-blast-radius.org.stack sbomandeb_stack_sbomread dependency edges from the easyconfigs a lock names. -
Reword the doc comments on
DiffRequest::prandpython_syntax_errorso the generated Rust API pages are valid RST. A span that contains angle brackets is left as a single backtick, and a letter glued to a closing backtick is not an end-string. -
docs/orgmode/howto/easyconfigs-pr-overlap.orgrecords that easyconfigs run: the four pull requests, the develop commit, and the shared Mathematica module.--impactis documented on the software-layer how-to, the CLI page, the format page, and the merge-order explanation.
-
rebuild-set --findingswritesbackport.mdbeside the ranked cost tables. A module is on that list when its scanner package or module name iscross-userornetwork-facing. The built-in names are Jupyter server, JupyterLab, notebook, cURL, urllib3, aiohttp, tornado, cryptography, and git.--reachability(reachabilityoneb_rebuild_set) is aname classfile that replaces one of those names or adds one;local-onlyandnot-reachableare recorded and left off the list. Any other name staysunclassified. A Python interpreter whose fix stays on the same minor is annotated: keeping the module path costs the in-place column, and renaming the easyconfig to that patch version costs the bump column. The count line includesbackport=N. Findings schema version is 2. The samebackport.mdadds a patch scaffold for each chosen module (<Name>-<version>_<ID>.patch, thepatchesandchecksumslines, and a fix commit URL when the export names one).--findingsalso accepts Trivy, Grype, and OSV-scanner JSON. A module--filter-depsdrops is listed as the OS errata stream and is not given a scaffold. A cURL finding records the--filter-deps=cURLtrade-off. -
rebuild-set --findingsalso writesfix-cost.json,fix-cost.tsv, andfix-cost.md. Each advisory is one row. A version bump is the reverse-dependency closure from the rebuild set, and it breaks reproducibility because the module path changes. An in-place patch keeps the name and version, adds<Name>-<version>_<ID>.patchtopatches, and rebuilds the patched module, a bundle that includes it as an extension or a component, and a dependent known to link it statically. A builddependency-only dependent stays out of that count when the recipe and the install cannot say how it was linked. The recommended route uses the same reach classes asbackport.md: an in-place backport forcross-userornetwork-facing, a bump when a Python fix leaves the minor version, and defer otherwise. The roll-up is the fraction of the installed stack each strategy rebuilds. The count line addsfix_routes=Nand those three fractions besidebackport=N. -
stack solve --dot-outand the MCP fielddot_outwrite the solved dependency DAG. A node isname/versionplus the toolchain, and the versionsuffix when the recipe has one. An edge points from a package to a dependency it selected and is labelled with the requirement; a builddependency is dashed. A.svgor.pngpath is rendered with Graphvizdot. Any other suffix is the DOT source. -
stack generationandeb_stack_generationcheck each added entry's toolchain generation against the generation the easystack file name names, the token aftereb-<X.Y.Z>-such as-2025b.yml. An entry whose generation its EESSI version carries but that differs from the file name's generation is a newfilenamefinding, so afoss-2025aentry added to a-2025b.ymlfile is caught even though 2025.06 carries 2025a. The count line now readsoutside=N mixed=N versions=N filename=N, and the MCP tool returns afilenamearray. Non-generation groups such as001-system,010-CUDAandcc70-CUDAare not checked this way. -
stack known-failuresand the MCP tooleb_stack_known_failurestake a--strictflag (strict: true). It prints the same report, then exits 1 (returns a tool error that lists the warnings) when a warning remains, so a pre-bot script or CI job can fail on a known failure with no remedy in place. Remedied hits never count, so a plan whose every hit is remedied exits 0. Without it the behavior and output are unchanged. -
stack batchand the MCP tooleb_stack_batchrun thestack generationsecond-version check over each planned pull request: a name with two versions in one toolchain generation, next to one an earlier batch of the same run adds or the installed list already carries, is a warning inpr-body.md,batch.json(versions.warnings,versions.count) andplan.md.--allow-versions NAME[@GENERATION](repeatable,allow_versionsfor the MCP tool) accepts one, as it does forstack generation. The warnings do not fail the batch; a bad spec is a usage error. The check is skipped when the EESSI version is not in the generation table. -
stack bot-classifyand the MCP tooleb_stack_bot_classifyread EESSI bot comments,_bot_job<id>.resultfiles and job output, and classify each bot job as a real failure (with the campaign build-finding class), ERROR-only noise, an empty tarball, or infra. Text no rule matches staysunclassified. Fixtures are trimmed comments from software-layer pull requests 1873, 1869, 1834, 1760, 1732, 1733, 1818, 1823 and 1741. -
eb-stack stack filesfinds the patch and source files an easystack's easyconfigs need that neither the easyconfig's directory nor the robot path has. Patches of the recipe, its extensions, and its components, patch files named only inchecksums, and sources no URL downloads are looked up the way EasyBuild does, with eachfrom-commitpin's tree on the robot path. A missing patch fails the command (software-layer #1842 and #1048), and a component patch beside a pinned bundle is reported under easybuild-framework#5133 (#1398). A source with no URL is ano_urlwarning.eb_stack_filesruns the same check. -
eb-stack stack generationrefuses an easystack entry whose toolchain is outside the generations of its EESSI version, naming the generation and the version that carries it.data/eessi-generations.tomlis the table: 2023.06 carries 2022b, 2023a and 2023b, 2025.06 carries 2024a, 2025a and 2025b, 2026.06 carries 2026.1. It also refuses easystacks for two EESSI versions in one pull request, and a plan that adds a second version of a software in one generation unless--allow-versionsnames it.--prreadspr-overlap --prJSON and checks only the added lines. The fixtures are software-layer #1472 (pv on GCCcore-12.3.0 in 2025.06), #1834 (fastp for 2025.06 and 2026.06) and #1497 (a second GROMACS on foss-2025b). The foss-2022b and foss-2023a hierarchies are now built in.eb_stack_generationruns the same check. -
eb-stack stack cuda-ccchecks thecuda_compute_capabilitiesof each CUDA-dependent easyconfig in an easystack's closure against the CUDA release it depends on, the EESSI accelerator targets indata/eessi-accelerator-targets.toml, and the easyblock mapping limits indata/easyblock-cuda-capability-map.toml(software-layer #1461). Any finding exits 1.eb_stack_cuda_ccruns the same check. -
eb-stack stack arch --easyconfigsparses each easyconfig once per architecture, so a file the plan names that fails to parse on one architecture is aparse_failedline and exits 1 (software-layer #1798, Go on riscv64).--probe-sourcesresolves each planned easyconfig's sources for x86_64, aarch64, and riscv64 and probes the URLs with HEAD and a ranged GET fallback, reportingunreachableandarch-missingsources (software-layer #1670, Kaleido). The probe is opt-in because it makes network requests.eb_stack_archreturnsparse_failedandsource_findings. -
eb-stack stack known-failureswarns when a plan includes, or depends on, an easyconfig a bot run has already failed on one architecture, and prints the established easyconfig remedy as text.data/arch-known-failures.tomlis the table, each entry citing the software-layer pull request it came from: waLBerla 7.2 on the SVE targets (#1623), Kaleido 0.2.1 on aarch64 (#1670), numba 0.62.0 test failures on a64fx and timeouts on zen2 and sapphirerapids (#1683), orjson on a64fx (#1871, #1829), uv 0.10.9 on a64fx and uv and uv-build on the 2025.06 haswell nodes (#1668, #1871), and the GROMACS sanity check that EESSI's CUDA demotion hook breaks under EasyBuild 5.4 (#1658). A pin that carries the fix, or an easyconfig that already has it, is reported as remedied.stack batchwrites the warnings into eachpr-body.mdandbatch.json.eb_stack_known_failuresruns the same check. -
stack oomand the MCP tooleb_stack_oomwarn when a plan entry is likely to run out of memory in an EESSI bot job. The peak build memory per software and version family is indata/build-memory.toml, and the bot build nodes and theeb_hooks.pyparallelism limits are indata/eessi-bot-resources.toml. Every row cites a real pull request. A warning names the target, the node, the parallel level and the estimate, and suggests amaxparallel, a hook limit or a node with more memory. The command exits 0. The fixtures are the libxc build killed on zen4 in software-layer #1772, Highway in #1692, hipBLASLt and rocBLAS in #1549, and PETSc in #1608. -
eb-stack stack archrefuses a plan that includes, or depends on, an entry an architecture cannot build. The message names the entry and the architecture.data/arch-unsupported.tomlis the list: GDRCopy on riscv64 (software-layer #1775 and #1822) and bwa-mem2 on aarch64 (#1876). With--installed, an entry in a shared easystack that has never been installed on that architecture, and is not in itsadditional_archeasystack, is flagged.stack batchuses the same list before it writes a plan.eb_stack_archruns the same check. -
package bump --fetch-checksumsdecides three more patch cases from the new source: a patch that only creates files the release already contains, a patch whose changes the release carries under different surrounding lines, and a patch that only pinsbazel_depmodulesMODULE.bazeldeclares itself. -
package bump --fetch-checksumsreplaces a patch the new source leaves undecided with a rebased file named for the new release (<Name>-<version>_<description>.patch) found beside the source recipe or under<letter>/<Name>of an--easyconfigsroot, when that file applies. -
package bump --drop-patch NAME=REASONrecords an operator's patch drop with its reason;--latest-secondarymoveslocal_*-versioned later sources (gc'slibatomic_ops) to their newest stable release. The MCP bump tool takesdrop_patchandlatest_secondary. -
eb-stack stack from-commitreports eachfrom-commitandinclude-easyblocks-from-commitpin already contained in the EasyBuild release named by--easybuild-versionor byeb-X.Y.Zin the easystack file name. A released pin whose easyconfig blob matches the tag can be removed. A released pin whose blob differs needs a person. The command exits 1 when any pin is already in the release.eb_stack_from_commitruns the same check. -
The
eb_component_reachschema listsosv_cache, which the CLI accepts as--osv-cache. -
eb-stack pr-overlap --impact Nwritesmerge-impact.toml. For that pull request alone, it names the other open pull requests whose build set shrinks and the depends-on edges from it that resolve. -
scripts/fetch-upstream-trees.shcreates a checkout of pinned easybuilders easyconfigs, easyblocks, and framework trees. TheUpstream treesworkflow sources that cache and runscargo test --include-ignoredevery week, on a push that changes the pinned tree list in that script, and by hand. -
eb_stack_order,eb_stack_easystack,eb_stack_sections,eb_repro_summary,eb_recipe_easyblock,eb_recipe_templates, andeb_recipe_hierarchycall the same runners as the CLI commands. Each tool's schema lists that command's flags. A test fails when a CLI subcommand has no MCP tool. -
eb_pr_overlap,eb_rebuild_set,eb_component_reach, andeb_easyblock_reachcall the same runners as the CLI commands.eb_pr_overlaptakeskindsoftware-layeroreasyconfigs, an easyconfigs closure, a merge order, and--impact. The reports written underout_dirmatch the CLI byte for byte. -
package bump --fetch-checksumsdownloads eachsourcesentry from the recipe'ssource_urlswhen the version changed and--source-checksumwas omitted, and writes the SHA-256 into the recipe and the SBOM. A git checkout, a missing URL, or a failed download stays empty. The attempts aresources.fetch.jsonand asource:fetchresidual. -
eb-stack stack ordersequences every pinned build a set of roots needs. A name the generation builds twice stays twice.--oldesttakes the oldest admissible version of an unpinned requirement.--easystack-outwrites that sequence as an easystack.--hashes-outwrites one sha256 per module over the easyconfig and the hashes of what it needs. -
eb-stack stack easystackwrites a lock as the YAMLeb --easystackreads.--option <file.eb>:<option>=<value>sets a per-fileeboption, spelled without the leading dashes. -
eb-stack stack sectionsregroups a Jenkins build list under the#### Title ####headers of a previous list. Entries keep their flags and whether they are commented out.--unfilednames the header for packages the previous list does not file. -
Packages on that Jenkins build list still need a reproduction score.
eb-stack repro summaryreads the per-case JSON under--scoresand prints the scoreboard table: case, pull request,EXACT/SEMANTIC/MATERIAL, allowance, and residual lines.--jsonprints the case records.--ratchetchecks the run against the committed allowance counts and exits nonzero when they disagree. -
MCP easyblock tools:
eb_module_lint(E999, E501, whitespace,EBM_RUN_CMD,EBM_OLD_SUPER,EBM_CFG_OVERRIDE,EBM_TEST_STEP_OWN_CMD,EBM_THREADED_VARIANT),eb_easyblock_dry_run(eb -x, per-step commands, toolchain options, threaded findings, andfailure_kindofsetup,environment, oreasyblock),eb_build_log, andeb_build_test(only whenEB_STACK_ALLOW_BUILD=1).eb_recipe_apply_suggestionputs a review suggestion on the anchored lines.eb_recipe_diffreports each hunk with the top-level name it touches. -
pr-overlap --kind easyconfigs --open OWNER/NAMEreads the open pull requests of that repository over HTTPS from the public GitHub API and adds them to any--prfiles.--base-refis the git ref for their base text and defaults todevelop.eb_pr_overlaptakes the sameopenandbase_refarguments. Head text comes fromraw.githubusercontent.comat the head commit. A 404 on the base ref means the file was added. No token is sent, and nothing from a pull request is executed. -
eb-stack component-reachlists every easyconfig and installed module that carries a component at a version or version range, inside one toolchain generation, and feeds the recipes that contain it into the rebuild closure. Dependencies, builddependencies, bundle components,exts_listextensions, Cargocrates, and versioned names insourcesorpatchesall count. A Python wheel is its own row: a.whlfilename insourcesorchecksums, anexts_listentry whose source is a wheel, or a top-levelsource_tmplthat names a wheel. A Cargo recipe also matches a crate that appears only as a checksum key such asrustls-webpki-0.102.8.tar.gz; the recipe's own tarball is not that crate. A compat-layer file is an input, not an easyconfig. The output directory containscomponent-reach.toml,component-reach.json, andcomponent-reach.md. Seedocs/orgmode/howto/component-reach.org.--purltakes a package URL such aspkg:cargo/[email protected].--cveresolves an OSV id, follows GitHub Security Advisory (GHSA), RUSTSEC, PYSEC, and GO aliases when the CVE record has only a git range, and keeps named version tags such aslibXpm-3.5.17. Several affected packages are one document withkindcve.--easystack-urlreads a deployed easystack over https.eb_component_reachoneb-stack mcpruns the same query. -
eb-stack rebuild-setreports which installed modules an in-place easyconfig patch forces EESSI to rebuild. It closes the deployed easystacks, walks the installed reverse dependents, and classifies each one from the easyconfig graph:no-rebuildfor a runtime dependency,reviewfor a builddependency only, andmust-rebuildfor the patched easyconfig and for a bundle that includes it as an extension. The output directory containsrebuild-set.json,rebuild-set.md, and onerebuilds/<YYYYMMDD>-eb-<version>-cve-patches.ymlper EasyBuild version containing classmust-rebuildonly. Seedocs/orgmode/howto/rebuild-set.org.--prefixreadslib*/*.afrom the installed prefix: a patched module with no static archive is no-rebuild for a builddependency-only dependent, and a review dependent is one row.--check-staticcompares defined dynamic symbols of the remaining review dependents with the patched library's exports and is off unless it is passed. -
pr-overlapstores each changed easystack and easyconfig on the record (revisions: path, kind, base and head text or blob ids).--merge-orderreads easystack hunk collisions from that text. -
pr-overlap --merge-orderwritesmerge-order.tomland appends a Merge order table tooverlap.md. The order builds each shared module once.--merged Nrepeats, implies--merge-order, and treats those pull requests as already installed. Two easystack edits at the same insertion point, or with the same added entry text, are recorded as conflicts. Seedocs/orgmode/howto/pr-overlap.org. -
pr-overlap --kind easyconfigsreads changed.ebfiles, closes them over the base tree, and writes the modules the base tree does not provide. Other pull requests in the same run can satisfy a dependency. The index rows aresame-file,same-module,shared-new-module, anddepends-on.--installedis optional for this kind. Seedocs/orgmode/howto/pr-overlap.org. -
pr-overlapcloses the easystack lines an open pull request adds and reports the modules more than one of them would build.--prtakes one JSON path or several after the same flag, matching whatin/prs/*.jsonexpands to.--include-pathkeeps one architecture's easystacks,--filter-depsdrops dependencies the way EasyBuild does, and an alias in.modulerc.luacounts as installed when the module it names is. A missing easyblock class is recorded and is not counted as a module to build. Seedocs/orgmode/howto/pr-overlap.org. -
eb-stack easyblock-reachreports which easyconfigs and installed modules a changed easyblock or framework module reaches. Inputs are--file, a--rangein a local clone, or--prfetched asrefs/pull/<n>/head. Matching covers theeasyblockline, the impliedEB_<Name>class, subclasses parsed from the Python class statement, extension classes (exts_defaultclass,exts_classmap, per-extensioneasyblock), and bundle components.--reverseadds the reverse-dependency closure. Output isreach.toml,reach.json, andreach.md. Seedocs/orgmode/howto/easyblock-reach.org. -
Sandboxed recipe file tools on
eb-stack mcp:eb_recipe_read,eb_recipe_list,eb_recipe_edit(exact string replace; a repeated match is not written unlessreplace_allis set), andeb_recipe_write. Paths stay underEB_STACK_WORKSPACEoreb-stack mcp --workspace(otherwise the server's current directory)..., absolute paths outside that root, and symlinks that leave it are rejected. -
recipe lintandeb_recipe_lintreport what upstream checks, without relying oneb --check-contrib(which never reports F541): E999 for a file that is not valid Python; the easyconfigs CI lint (F541, W605, W291); the check-contrib pycodestyle codes (E501, E225-E228, E231); the easyconfigs test-suite checks (EB_PY_NO_USER_SITE,EB_SANITY_PATHS_SHAPE,EB_LOCAL_VAR_NAMING,EB_REDEFINED_PARAM,EB_CHECKSUM_COUNT); and review conventions (EB_FMT_PERCENT,EB_FMT_CONCAT,EB_FMT_MISSING_F,EB_FSTRING_QUOTE_REUSE,EB_FMT_TEMPLATE_VAR,EB_TEMPLATE_UNKNOWN,EB_SHLIB_HARDCODED,EB_DEP_DUPLICATE, andEB_FMT_TEMPLATE_REMOVEDwith--base/base). Every finding has a severity (error or warning) and the output has acleanflag, false while any error or anyEB_FMT_*formatting finding remains (error_freereports errors only); the CLI exits non-zero on errors only. Each EB_FMT_PERCENT finding shows the f-string built from the flagged expression.EB_DEP_EMPTY_VERSIONis an error on a (build)dependency with version''. EB_TEMPLATE_UNKNOWN knows the extension-filter templates (%(ext_name)s,%(ext_version)s,%(src)s) and easyblock-added ones, and skips Python%-dict keys; EB_CHECKSUM_COUNT counts easyblock patch options such aspatch_ctypes_ld_library_path; EB_SHLIB_HARDCODED flags.soonly in library paths and sanity checks.f'lib/%(name)s.{SHLIB_EXT}'is correct and is not flagged. Whenebis onPATH, the same command runseb --check-contriband merges its findings. A missingebis not a lint failure by itself.fixtures/lint_*/contains one bad/good/expected.json fixture per rule, enforced bytests/lint_fixtures.rs. -
Formatting findings are scoped.
EB_FMT_*findings outside the review scope carry"info": trueand do not count againstclean: untouched%%(...)s-escaped%entries, and (with an explicitbase/--base) lines unchanged from the base.review_lineskeeps named lines in scope. -
New errors: EB_FSTRING_ESCAPED_TEMPLATE (
%%(...)sinside an f-string), and in diff mode EB_SANITY_ENTRY_REMOVED and EB_EASYBLOCK_CHANGED, plus the EB_SANITY_PATHS_REMOVED warning.eb_recipe_lintuses the file as the server first saw it in the session as the diff base whenbaseis not given (rebaselineresets it). EB_DEP_EMPTY_VERSION is now an error. -
eb_dep_versionslists the versions of a dependency that have an easyconfig in a local tree, for a toolchain and for other toolchains, and says so (instead of guessing) when there is none or no tree at all. -
eb_recipe_formatrewrites the recipe in place, returns the text withdry_run, and writesoutonly as a.ebpath inside the workspace whose directory exists, so a review fix leaves no stray files. -
eb_recipe_grepsearches files inside the workspace root (literal or regex) and returns path, line, and text per match. -
recipe checkandeb_recipe_checkfail on a recipe that is not valid Python.eb_recipe_checkaccepts a.ebfile ineasyconfigsas the easyconfigs directory it sits in, and reports a clear error for other non-directory paths. -
eb_recipe_checkrequireseasyconfigsto contain at least one path (minItems: 1). An empty list returnsargument easyconfigs requires at least one path. -
package planandpackage bumpraise amissing-easyblockresidual (stageemit, severityjudgment, idmissing-easyblock:<class>) when a package resolves to a generic easyblock and carries variant options that differ between profiles, hand-written test or sanity parameters, or a binary name that follows the profiles.--emit-easyblock(MCP argumentemit_easyblock) renders an easyblock skeleton toeasyblocks/<letter>/<module>.py, includes it with the recipes, and moves the variant options out of the emitted easyconfigs. See "When a package owes an easyblock" indocs/orgmode/reference/package-bundles.org. -
Overlay planning treats existing robot modules as leaves: a
Pythoneasyconfig that namesbinutilsno longer makespackage plan --format pypiunsatisfiable.--easyconfigsis the solve robot only; it does not start package-closure discovery. -
kind = "eessi"target runtime:eessi_container.sh --mode execis the install backend for planned PyPI/CRAN overlays. Plan stays on the host.scripts/eessi-extend-eb.shloadsEESSI-extendand execseb. Seeexamples/targets/eessi-extend.toml. -
exts_listentries are virtual Resolvo provides of the parent bundle. A requirement fornumpyis satisfied bySciPy-bundle(and the same forPython-bundle-PyPI/R-bundle-CRAN) instead of failing as a missing easyconfig. Profile locks collapse the provide to the parent so emitted recipes depend on the bundle, not on a fakenumpymodule. Planningnumpy/scipy/torchas a PyPI root against a robot that already includes them is an empty delta. Without that provider the plan refuses a pip overlay instead of emitting aPythonBundle. Warehouserequires_dist: null(live numpy JSON) parses as no extras. A leftover such aseon-akmcwhose other PyPI deps are not in the robot keeps those names inexts_listinstead of failing the Boolean satisfiability (SAT) solve. -
--format cargoreadsCargo.tomlor crates.io JSON. PyO3/maturin crates emitPythonPackagewith implicitRust,maturin, andbinutils; other crates emitCrate. Host Cargo wrappers (sccache,mold) are unset. Existing robot Rust modules are leaves.--cargo-source/kind = "cargo"closes a PyPI leftover that is a crate (for examplereadcon) as a companion module; remaining pure PyPI holes stayexts_listextras. Overlay extras prepend the install prefix toPYTHONPATHsopip --no-build-isolationsees prior extensions and the loaded EESSI modules. Mesonpy ingest reads an optional PEP 518build_systemobject. Extra site packages and meson wrap natives named in that ingest become SAT requirements; Resolvo takesquill/cbindgen/Eigen/PyYAMLfrom the robot when those modules exist. Do not hand-edit the emitted recipe for those names. Cargo leftovers and mesonpy wraps share one cargo-on-EESSI isolation prelude (cargo::eessi_cargo_host_isolation): host rustc wrappers andRUSTFLAGSare unset,LINKERis EESSI gcc, and the compatldcomes fromuname -m, not a plan-time x86_64 literal. -
--format pypireads Warehouse-shaped JSON or arequirements.txtand emits aPythonBundlewhoseexts_listis the leftover package, with already-provided extras mapped to the parent bundle. -
--format cranreads a DESCRIPTION file, CRAN JSON, or a package list and emits oneRPackagerecipe when the robot carries its imports, or aBundlewithexts_defaultclass = 'RPackage'carrying the leftovers inexts_listwhen it does not. Base-R packages are recorded as residuals. -
Requirement parsing is one implementation shared by the solver and the emitter, covering
==,!=,>=,>,<=,<,~=(PEP 440) and^and~(Cargo). A clause the language cannot express becomes anunparsed-constraintresidual instead of an empty version set. -
Cargo dependencies keep the requirement the manifest states, and
pathandgitdependencies are reported as judgment residuals: neither can be built from a published crate tarball. -
package plan --package-index FILEreads a repository index, either the format CRAN publishes asPACKAGESor a pinned requirements file aspip freezewrites it, supplying versions and checksums for dependencies that state none of their own. A CRAN source now comes from CRAN's contrib location rather than the project home page inDESCRIPTION, and an R bundle carriesexts_default_optionspointing at the current and archived CRAN paths. -
Package identity, the pip-overlay refusal list, PyO3 marker crates and the crate-to-module renames live in
data/overlay-policy.tomlrather than in match arms. -
Name-mode ingest (
--source eon-akmcwith--format pypi) fetches Warehouse / CRAN / crates.io once and writesingest/<format>/. SAT and tests only read that dump. A neighbouring sdist tree overlayspyproject.tomlandsubprojects/*.wrapas build deps; undeclared Python imports are residuals, not silent SAT edges. -
--format luarocksreads a*.rockspec.--format rakureadsMETA6.json. Both lower toForeignRecipeand the same Resolvo path. They are not new solvers. -
Example stack policies
examples/stacks/eessi-python-extras.tomlandexamples/stacks/eessi-r-extras.tomlfor locking EESSI-shipped scientific Python / R providers. -
package plangenerates a recipe with the structure upstream writes. Pointed at a PyPI package atGCCcore-14.2.0, the emitted file is identical in shape to upstream's own recipes:PythonPackagerather than a one-entry bundle,sources = [SOURCE_TAR_GZ], abinutilsbuild dependency, short lists inline, a one-line description in one pair of quotes, and no empty dependency fields. -
--source name==versionfetches one PyPI release rather than whatever is newest, so regenerating an existing recipe describes the same release and the same command gives the same answer tomorrow. -
tests/generation/backtest.pyregenerates upstream's ownPythonPackagerecipes, each with its own recipe hidden from the robot path and its version pinned, and diffs field by field. Over the GCCcore-14.2.0 corpus: easyblock 10/10, toolchain 10/10, dependencies 10/10, builddependencies 10/10, sources 10/10, moduleclass 5/10. -
A
moduleclassis taken from the recipe the tree already carries for a package when there is one, and otherwise inferred from the package's Trove classifiers. Which of the two happened is recorded as a residual, because upstream's own class is a judgement:einopsismathandfonttoolsdevel, and neither follows from the metadata. -
tests/propertybacktests the ordering properties against one commit per year of easybuild-easyconfigs, materialised withgit archive. Sampled roots that order successfully across 26 commits from 2014 to 2026: 312/312.
tests/pr_overlap_easyconfigs_openreplays four open easybuild-easyconfigs pull requests (22823, 24575, 27131, 27215) against develop981d2123. The overlap files match the run on the full tree. The ignored testlive_github_open_easyconfigs_pull_requestreads the public GitHub API.
-
stack solve --stack-diff-outwrites ASCII:tobetween the baseline and solved labels and between versions, parentheses around an easyconfig path, andnonefor a missing value. -
recipe hierarchywithout--exportprints only the known generations.--exportalso prints the synthetic GCC-family rule. The plain command used to print both. -
Package commands,
stack solve, the MCP tools, andskills/golden-replay/replay.shpass--toolchain name/versionand--stack-policy.stack solve --policyfrom 0.3.0 is a hidden alias of--stack-policy: it is omitted from--help, it still names the policy file, and it warnswarning: --policy is accepted for compatibility. Use --stack-policy.--toolchain-nameand--toolchain-versionare hidden aliases of--toolchain name/versionand warn the same way. The MCP argumentpolicywarns and is still read;stack_policyis the spelling to pass. The MCP package tools require a toolchain through the schema'sanyOf, and a call without one namestoolchain. -
The CLI and the MCP tools share one usage error, one toolchain parser, and one foreign-format parser.
-
--toolchain systemand--toolchain SYSTEMselect the SYSTEM toolchain.system/is the same value. The version is empty. -
--helpfor every command includes an example, and every flag has a description. Defaults the command applies are shown there. -
stack solvereads the policy file with--stack-policy, the same flag aspackage planandpackage bump. Package commands take--toolchain name/version, the spellingstack solveuses. An empty version is kept: a SYSTEM recipe has one. A command line without a toolchain version is still rejected. Inspect and plan accept a lone--toolchain-versionand usefoss. Bump does not. -
MCP package tools accept
toolchainasname/version.eb_stack_solvereads the policy file asstack_policy. -
Help examples name
zlib. Production source does not name a package the solver used to special-case. -
The Rust API toctree is added once, by the Sphinx build.
-
The stack docs match the commands: build-list order and versions, the stack-diff labels and punctuation,
solver.criteria, lock-SBOMdependsOnedges, policy hierarchy membership, andstack order,stack easystack, andstack sections. -
Package plan docs list the closure files every
--easyconfigsplan writes. CRAN inspect recordsRPackage. A single PyPI plan emitsPythonPackageand depends on the bundle that already provides a requirement. A Cargo.toml with no crate tarball is refused at plan time; the crates.io JSON is what plan emits from. -
The checked-in zen4 overlap report is the 2026-10-24 cvmfs run: 28 open pull requests, 20 easystack records, 10 shared modules. Closed pull request 1728 is gone and 1692's head is
655310721787. -
The European Environment for Scientific Software Installations (EESSI) 2025.06 component-reach test is ignored unless
scripts/fetch-upstream-trees.shhas checked out the pinned trees. The default test run does not clone or write into the source tree. -
scripts/fetch-upstream-trees.shexports one name per pinned tree and records the EESSI software-layer commit the ignored test reads. -
The component-reach how-to runs on a recorded slice of pinned easybuild-easyconfigs develop
981d2123, licence file included. The easyblock-reach how-to uses the same fetch script. -
The easyconfigs
pr-overlapexample in the CLI reference is a run that writes 4 records, on the recorded open pull requests. -
CI runs every integration test file. Ignore-only files are named by the upstream-trees workflow, which passes
--include-ignored.real_tree_scalestill needs a local robot tree and is not in that list.
First public release: package plan/bump/campaign CLI, Resolvo locks, CycloneDX SBOMs, multi-platform installers (cargo-dist), and operator documentation.
- The public eOn policy targets the core +
with_rgpotproduct on a single foss-2026.1 / GCCcore-15.2.0 generation: no cross-generation PyTorch/xtb pins, no staged cargo-c preconfigopts, torch-family conda host deps excluded from the solve, and readcon-core plus rgpot closed as authored companion easyconfigs.fixtures/eon_core_rgpotfreezes the upstream eOn 2.17.2 draft PR file set as the regression surface.
-
skills/upstream-pr/SKILL.md: easybuild-easyconfigs PR conventions distilled from real merged and rejected PRs (single-generation closures, readable recipes, precedent citation, AI disclosure, test-report lifecycle). -
MCP tools
eb_recipe_lintandeb_stack_sbom, plus explicit optional schemas foreb_package_bump,eb_recipe_check,eb_recipe_format, andeb_stack_solve, so the MCP catalog matches the version-one CLI surface. -
CI job for package catalog, package closure, closure write, and source-root discovery suites (previously only covered by local
cargo test --all-targets). -
Claim-ladder, command-surface, and pipeline diagrams (Graphviz source in the manuals; PNG/SVG under
assets/illustrations/). CLI reference documents package catalog and source-root plan flags. -
Package-neutral source-root discovery for package closure: ordered local EasyBuild, conda-forge, and Spack indexes close robot holes without a committed per-package catalog entry. Explicit catalogs remain optional overrides. EasyBuild bumps preserve toolchain family (for example GCCcore maps to the GCCcore member of the target hierarchy).
-
Public example
examples/package-sources/local-roots.tomland CLI/MCP flags--package-sources,--easybuild-source,--conda-source,--spack-source. -
Catalog provider kinds
foreign(default) andeasybuild-bumpfor package-source catalog entries, so recursive package closure can retarget an existing EasyBuild recipe through the annual-bump pipeline instead of substituting a foreign archive. -
Public package-neutral catalog example at
examples/package-catalog/mixed-providers.toml. -
Canonical schema-versioned package plan shared by conda-forge, Spack, and EasyBuild inputs, with source provenance, structured conditions, variants, rules, build intent, product profiles, output requests, and residuals.
-
Planned CycloneDX SBOM generation from canonical package intent and solved EasyBuild stack locks, including primary source hashes, VCS identities, and hashed distribution references.
-
Per-profile materialization and Resolvo selection with preferred pins, locked pins, candidate exclusions, and recorded fallback outcomes.
-
One conventional EasyBuild recipe and profile lock per installable product profile; default profiles remain unsuffixed.
-
Positional source-checksum overrides at the CLI and MCP emission boundary, with complete source coverage required before a recipe is emitted.
-
Canonical new-package and bump bundles containing
package.plan.json,package.sbom.cdx.json, profile locks, and EasyBuild recipes. -
Layered public TOML build targets covering local/SSH transport, direct/Slurm execution, host/Podman/Docker runtime, and EasyBuild workload.
-
Persisted build campaigns with exact routed commands, independent claim ladder, typed findings, ownership, resolution evidence, and retry supersession.
-
Profile binary-verification commands with package/module/profile placeholders.
-
Version-one CLI and MCP surfaces for package planning, recipe checks, stack solving, targets, campaigns, and finding coordination.
-
Public new-package and annual-bump skills implementing the Hermes/OMP build-evaluation loop.
- Existing-recipe bumps use the same SBOM, manifest, Resolvo lock, EasyBuild emission, target routing, and campaign model as new packages.
- Existing robot artifacts keep independent build-only dependency contexts during package-profile solving, matching EasyBuild's installed artifact model.
- Recipe style lint/format is namespaced under
recipeand remains purely mechanical. - Documentation, examples, CI, and acceptance fixtures use only the version-one command and MCP names.
- CI enforces the Rust 1.88 minimum, formatting, clippy with warnings denied, and public metadata contracts.
- Rust-backed fixture recipes reset Cargo compiler wrappers without exposing host configuration inherited through mounted build paths.
- Campaign state uses an OS-backed exclusive guard with process-identity metadata, so interrupted controllers do not leave permanent stale locks.
- The unreleased scaffold ingest, companion placeholder, intermediate plan, standalone bump, and auto-emitter APIs.
- Compatibility shims and legacy CLI/MCP command names.
- Generated placeholder recipes with dummy sources or checksums.