fix(ci): use cross-strip tools when packaging RPMs for non-x86_64 targets#24873
Merged
thomasqueirozb merged 2 commits intomasterfrom Mar 9, 2026
Merged
fix(ci): use cross-strip tools when packaging RPMs for non-x86_64 targets#24873thomasqueirozb merged 2 commits intomasterfrom
thomasqueirozb merged 2 commits intomasterfrom
Conversation
pront
approved these changes
Mar 9, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
After #24864 removed the Docker wrapper for RPM packaging, the host's x86_64
striptool is used duringrpmbuild'sbrp-strippost-install phase. This fails for cross-compiled binaries (armv7, aarch64) sincestripcan't recognize a different architecture's ELF format.Fix by installing
binutils-arm-linux-gnueabihfandbinutils-aarch64-linux-gnuon the runner, and passing the appropriate cross-strip binary torpmbuildvia--define "__strip ..."inpackage-rpm.sh.Vector configuration
NA
How did you test this PR?
Triggered a new nightly run from this branch: https://github.com/vectordotdev/vector/actions/runs/22868431384/job/66341531846
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References