fix(examples, record): follow the farms that answer for their own members - #601
Merged
Conversation
…bers
`compat:vulkan-runtime` published a farm whose members needed four sonames
nothing on the artifact's search path carried. The three examples that pin it
moved to 2026.09.10, where the farm closes over its own members and reaches the
host only through a named `*-host-link` package.
Measured on this host, the vulkan example's own record before and after:
members 55, walked 55, missing 4, dangling 0
members 60, walked 59, missing 0, dangling 1
The one remaining finding is `libcrypto.so.1.1`, and it is dangling rather than
missing because the publishing package now says so: OpenSSL 1.1 is end-of-life
upstream, the ecosystem publishes 3.x, and only NVIDIA's PKCS#11 provider asks
for it. `libcrypto.so.3` comes from `xim:openssl` and `libnvcuvid.so.1` from
`xim:nvidia-video-host-link`; no branch harvests a new file from /usr/lib.
The example still runs on the device: `12 24 36 48` and
`device: NVIDIA GeForce RTX 4080`.
Section 7 of the design record no longer files those four findings as open. It
records what repairing them found instead: the defect was in three farms rather
than one, mcpplibs/mcpp-index#376 named the wrong one -- the four came from
`compat:opencl-runtime` -- and the reason written against the fix had measured
the set before the driver's settings GUI was excluded.
Follows mcpplibs/mcpp-index#380 and openxlings/xim-pkgindex#801.
The example names `compat.vulkan-runtime` itself, under a cfg(linux) predicate, and compares that pin against the one recorded in its installed copy of `compat.vulkan`. 1.4.357.0 records 2026.09.07; 1.4.357.1 is the version whose install records 2026.09.10. See mcpplibs/mcpp-index#381.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
compat:vulkan-runtimepublished a farm whose members needed four sonames that nothing on the artifact's search path carried. The three examples that pin it move to2026.09.10, where the farm closes over its own members and reaches the host only through a named*-host-linkpackage.Measured, on this host, from the example's own record
The one remaining finding is
libcrypto.so.1.1, and it is dangling rather than missing because the publishing package now says so: OpenSSL 1.1 is end-of-life upstream, the ecosystem publishes 3.x, and only NVIDIA's PKCS#11 provider asks for it.libcrypto.so.3comes fromxim:openssl,libnvcuvid.so.1fromxim:nvidia-video-host-link. No branch harvests a new file from/usr/lib.The example still runs on the device:
The record
Section 7 no longer files those four findings as open. It records what repairing them found instead:
glx-runtime30 unmet edges,vulkan-runtime5,opencl-runtime4compat:opencl-runtimeFollows mcpplibs/mcpp-index#380 and openxlings/xim-pkgindex#801, both merged.