Repository navigation
fix(plan): call a published build stale only when its soname moved - #268
Merged
Merged
Conversation
The first push-triggered run on main (36205360031, cancelled) selected 215 of 397 packages for a one-package change. 78 of them were "stale": a published binary required vala, cvs, lighttpd, mingw32(kernel32.dll), pkgconfig(xproto), python3-alsa... -- Fedora-only dependencies of -devel, MinGW and optional subpackages that neither the factory nor Hummingbird provides at any version. A rebuild cannot change that, so they were selected, with their dependents, on every run. Stale now means what the rule was written for: a required shared library that is unsatisfied while the same library is provided at another version (libavcodec.so.62 against .63, libicuuc.so.77 against .78). On the fresh published image that is 2 packages (enchant2, libgda) instead of 80, and the same one-package change selects 13. Whether the consumer can install what it needs remains the Hummingbird-only transaction's question. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMTLsnqW2jtz5QsNC3W3qv
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
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.
Found by the first push-triggered incremental run on main (36205360031, for #265). I cancelled it: it selected 215 of 397 packages for a one-package change and would have spent hours on cold hermetic builds.
78 of them were "stale": their published binaries require
vala,cvs,lighttpd,mingw32(kernel32.dll)(×14),pkgconfig(xproto)(×13),python3-alsa… These are Fedora-only dependencies of-devel, MinGW and optional subpackages, and nothing in factory ∪ Hummingbird provides them at any version. A rebuild cannot change that, so they were re-selected, with their dependents, on every run. This predates the incremental work; it just stopped being hidden by the cache.Stale now means what the rule was written for: a required shared library that is unsatisfied while the same library is provided at another version (
libavcodec.so.62vs.63,libicuuc.so.77vs.78).Measured against the freshly published
latestand Hummingbird's primary.xml:The remaining 13 are a one-time bootstrap: icu and malcontent-bootstrap are deleted at publish by design, so the NEVR comparison never sees them as published, and samba doesn't match. Once the state label exists (#259), the published inputs are recorded instead and they drop out. Whether the consumer can install what it needs is still the Hummingbird-only transaction's job.
🤖 Generated with Claude Code