What an in-place patch forces a rebuild of

The patch keeps the easyconfig filename and the version. eb-stack rebuild-set closes the deployed easystacks and walks backward from each patched easyconfig through the installed modules. The closure is everything that depends on the patched module within its toolchain generation. An unpinned dependency is resolved inside the dependent’s own generation, so a module built with another generation is not a row.

The walk starts from the easyconfig graph. --prefix and --check-static then read the installed files. The commands are in what an in-place patch forces the European Environment for Scientific Software Installations (EESSI) to rebuild. The output fields are in output formats.

Three classes

  • no-rebuild. Some path from the patched module is made of runtime dependencies. The dependent links the patched package as a shared library. Replacing that library does not require a rebuild.

  • review. Every path uses a builddependency. The dependent may have linked the package statically or embedded it. The graph cannot say which, and the reason says so.

  • must-rebuild. The row is the patched easyconfig, or a bundle whose exts_list names that package and version. The extension is installed as part of the bundle.

The strongest class wins: must-rebuild, then review, then no-rebuild. A runtime path beats a builddependency path, so a module listed in both dependencies and builddependencies is no-rebuild.

An extension makes that bundle must-rebuild. It does not force the same class on modules that depend on the bundle. Those modules are classified by their own edges. A runtime dependency on the bundle is no-rebuild, and the reason names the bundle.

A toolchain edge is indexed and not classified. Patching a compiler is outside these three classes.

A review dependent is reported once. The changed column lists every patched easyconfig that put it there. When --prefix found static archives, the reason names them. The other classes stay one row per edge.

Installed archives

--prefix is the installed prefix of EESSI. The install directory of Name/version is software/Name/version. A static archive is a \*.a file directly under a lib* directory there.

A patched module whose directory exists and contains no such file cannot have been linked statically. A builddependency-only dependent of that module is no-rebuild, and the reason is no static archive installed. Archives that are there keep the row in review, and the reason names them. A missing install directory is a note. The row stays in review. A prefix with no software directory is an error.

Defined symbols

--check-static is off unless it is passed, and it needs --prefix. It reads defined dynamic symbols of each remaining review dependent and compares them with the exports of the patched libraries that put the row in review. The exports come from lib*/*.so and lib*/*.so.*, skipping symlinks. When that set is empty, they come from the global and weak defined symbols in the \*.a members. Version suffixes (@@VERS and @VERS) are stripped before the comparison.

A hit means the dependent defines an export of the patched library, which is what a static link copies in. The row becomes must-rebuild, and the reason names the file and the symbols. No hit, and a readable export set, is no-rebuild. An empty export set stays in review. A missing install directory of the dependent is a note, and the row stays in review.

The scan can go wrong. It sees dynamic symbols only, so a hidden, local, or inlined static link is a false no-rebuild. A short name shared with another library is a false must-rebuild. Scripts, bytecode, and libraries opened with dlopen are invisible. A static archive shows that a static link was possible, not that it happened.

What counts as installed

The reverse walk visits installed modules only. It does not continue through a module that is not installed, so a dependent that is reachable only through an uninstalled intermediate is left out. The patched easyconfig itself is must-rebuild when it is in the deployed graph, even when that module is not installed.

--filter-deps drops dependencies and builddependencies tuples before the walk. It leaves exts_list in place. A filtered package that a bundle includes as an extension still marks that bundle must-rebuild.

A missing easyblock class is a note. The module stays in the set, because it is already installed. A from-commit whose tree was not passed is a note, and the release tree is used for that pin.

Scanner findings

--findings turns a scanner export into the changed list: every installed module it names. The rebuild set is then read twice per module. A backported patch that keeps the version replaces files under the same module path, so the cost is the must-rebuild and review rows. A new version is a new path. EasyBuild writes each dependency version into the dependent’s module file and run path, so the cost is the module and every installed dependent, runtime and builddependency alike. The ratio between the two is the case for backports over bumps, per module.

The same run writes backport.md. A module is listed there when the scanner package or the module name is cross-user or network-facing. The built-in names are the ones named for those two classes: Jupyter server, JupyterLab, and notebook on a shared node; cURL, urllib3, aiohttp, tornado, cryptography, and git for the network. --reachability replaces or adds a name. local-only and not-reachable are accepted from that file and left off the list. Anything else stays unclassified. The strongest class wins when a module matches more than one name.

A Python interpreter is a special case of the two costs. When every named fix stays on the installed minor, the ABI is stable within that minor, so applying the patch release under the same module path costs in_place. Renaming the easyconfig to the new patch version costs bump, the whole Python closure. The annotation does not classify the interpreter.

The list then names the patch file <Name>-<version>_<ID>.patch and the patches and checksums lines for each chosen advisory. The module name is kept when it is the same package (cURL for a scanner row curl). An extension keeps the bundle as the easyconfig and uses the package name in the filename. --filter-deps does not change the reach class. A dropped module is listed as the OS errata stream and is not given that scaffold. A cURL finding states the trade-off of --filter-deps=cURL: new builds only, OS errata instead of the EasyBuild module, and the newer protocol features that choice gives up. --findings accepts Trivy, Grype, and OSV-scanner JSON. Those files do not name a module, so the installed list is the match.

fix-cost.json is that same rebuild set, one advisory at a time. It does not walk the graph again. The bump cost is the union of the modules’ reverse-dependency closures. The in-place cost is the patched module, a bundle whose exts_list or components names the package and version, and a dependent known to link it statically. Static linking is read from the rebuild rows first: a runtime edge is a shared library, no static archive under --prefix is not a static link, and --check-static is a symbol comparison. A remaining builddependency-only row is static when configopts or buildopts request a static build and not a shared one, shared for the opposite, and unknown when the recipe says both or neither. Unknown modules are listed and left out of the in-place total. The recommended route follows justifies_backport: only cross-user and network-facing are backported, and the backport keeps the module path unless a Python fix leaves the minor version. The roll-up unions each strategy and divides by the installed list.

A site that installs from build lists has no easystack. Without --easystack, the installed list is the stack: each module is read as the easyconfig its name gives, and a module that no easyconfig matches is listed as unresolved.

Example

Patch zlib-1.3.1-GCCcore-15.2.0.eb. libpng depends on zlib, so libpng is no-rebuild. Graphviz depends on libpng, so Graphviz is no-rebuild through libpng. CMake lists zlib only as a builddependency, so CMake is review. A bundle whose exts_list names zlib 1.3.1 is must-rebuild. An application that depends on that bundle at runtime is no-rebuild.

The rebuild easystack contains zlib and the bundle, each with rebuild: true. It does not contain libpng.

With --prefix, the CMake row stays in review only when the installed zlib provides a static archive, and the reason names that archive. With --check-static, CMake is must-rebuild when one of its installed Executable and Linkable Format (ELF) files defines an export of that archive, and no-rebuild when none of them does.